Getting message dialog "No device connected. Press Download when Connected"

[lpcware]

Content originally posted in LPCWare by jonathan84clark on Fri Oct 31 09:33:31 MST 2014
I am attempting to create a fully automated programming fixture. This fixture will be run by a PC that has no monitor, keyboard or mouse.

The problem is that the file bootLPCXpresso.cmd throws a dialog that says,
"No device connected. Press Download when Connected"

I have tried the following to resolve this issue:
-Plugged LPC-Link into multiple USB ports
-Uninstalled and Reinstalled LPC link in the device manager.
-Uninstalled and Reinstalled LPCXpresso
-Turned off my Windows firewall
-Unplugged and plugged back in the LPC-Link board.
-Checked the forums for similar issues, there was one created in 2011 that didn't help at all.

Not one of these solutions has fixed this issue. Interestingly enough, the file still boots LPC-Link but it requires the user to click (with the mouse) on that dialog. This is a big problem for a machine that wont have a mouse!

I also am not sure why a software engineer would do this. One obvious use-case for booting the LPC-Link with a batch file is to do so programmatically for automation purposes. But having this file open a dialog that requires user input defeats the entire purpose of doing that.

This message also makes no sense for two reasons.
1. No device connected: My LPC-Link board is not only connected to my computer but is being recognized by LPCXpresso as a valid programming board.
2. Press Download when Connected: What? There is no download button? Where is this mystery button supposed to reside? It certainly is not on the dialog.

If anyone has seen or knows anything about this issue, please let me know. I would really like to find out what is going on.

Thanks,

Jonathan L Clark
Firmware Engineer

[lpcware]

Content originally posted in LPCWare by lpcxpresso-support on Fri Oct 31 12:10:57 MST 2014
Thanks for letting us know.

[lpcware]

Content originally posted in LPCWare by jonathan84clark on Fri Oct 31 11:26:15 MST 2014
Okay, I figured it out. Its all about permissions!

This .cmd file was being run on a computer that I setup myself. The Administrator account on that computer had no password protection (so the computer would log in automatically on boot-up). Apparently that is what was keeping it from running.

I guess this makes sense because the Windows Management Instrumentation (WMI) that is accessed when this script runs, requires administrative privileges.

Solution
-Created password protection for my Windows administrator account.

This does make things a little harder because now I need to write a script that will log me in automatically, but that is not too bad. Now I am just happy that bootLPCXpresso.cmd is able to run!

Thanks,

Jonathan L Clark

[lpcware]

Content originally posted in LPCWare by lpcxpresso-support on Fri Oct 31 10:09:09 MST 2014
DFUApp really is a GUI, with a command line interface grafted on. This was a tool written by somebody a very long time ago and it is very difficult to stop the GUI entirely.

The IDE and the command line script both use the exact same tool to boot LPC-Link, namely DFUApp. I don't understand how it can work from the GUI and not from the command line.

To find out what is going on, you might want to try running in the GUI mode. From a command prompt, type

dfuapp /s gui

Note that our modern debug adapter - LPC-Link2 - uses a true command line application to boot it. LPC-Link2 costs about $20 and is quicker and more reliable, so you may want to consider using that instead.