Link2 Debugger/Emulator Not Found

[lpcware]

Content originally posted in LPCWare by drnow on Sun Nov 23 16:04:49 MST 2014
I recently purchased an LPCXpresso54102 board that has an integrated Link2 debug probe.  However, I have been unable to program and debug the board using the Link2 probe for some reason.  Steps so far with my Windows 8.1 machine include downloading and installing the latest versions of LPCXpresso and LPCOpen, and then importing and building a simple project, 'periph_blinky'.  However, when I reach the "Debug" step in the process, the following window pops up:

Connect to emulator:  LPC-Link(WinUSB) or RDB-Link
LPC-Link (WinUSB) or RDB-Link not found.
This could be because it is disconnected, not powered, or already in use

As far as I can tell, the Link2 debug has been connected, and a driver for it has been installed.  For example, in the computers Device Manager under Ports, there is a device "LPC-LinkII UCom Port (COM3)".  This device comes and goes in the Device Manager window depending on whether the 54102 board is plugged in.  I have uninstalled and reinstalled the driver for this device, as well as tried a different USB cable. 

Any suggestions?

[lpcware]

Content originally posted in LPCWare by lpcxpresso-support on Mon Nov 24 11:11:00 MST 2014
"Stalled on bus operation" means that the debugger has spotted that the target has gone to sleep (WFI). If the message is on constantly, it means the target is permanently asleep. The debugger continue to work perfectly. Why do you think it does not work?

The reason why this application does not produce the expected results when trying to reduce the tick rate to 5Hz is because it overflows the Systick Timer reload Mask (24bits). 100Mhz/10 does not overflow, but 100Mhz/5 does.There is a check for this in the SystickConfig call, which returns an error code (which is not being checked for in this simple example), so the Systick is never setup and so the application sits in the while(1) WFI ; loop...

Please try to use the debugger and step through the code, and you will then get a better understanding of what is going on.

[lpcware]

Content originally posted in LPCWare by drnow on Mon Nov 24 10:00:53 MST 2014
Support,
I'm gradually making progress with the debugger in LPCXpresso IDE.  Using the periph-blinky program from LPCOne, I can get the debugger to run the program.  However, in the left lower corner of the IDE the phrase "Stalled on bus operation" flashes on and off. 

When I change the flashing rate to 5 hz (from the 10 initially in the program) the debugger/program does not run, and the "Stalled on bus operation" in the left lower corner stays on continuously, without flashing. 

Why can't the debugger work if the rate is reduced to 5 hz?

[lpcware]

Content originally posted in LPCWare by lpcxpresso-support on Mon Nov 24 07:49:00 MST 2014
A couple of thoughts.

1. You have to terminate a debug session before starting another. Unfortunately, with CMSIS-DAP connections we can't detect this (like we can for the 'Redlink' version of LPC-Link2), so you have to remember to do this at the end of each debug session.
2. If you run into this problem, you can kill the Redlink server. Press the Red Link icon on the main toolbar, and in the Redlink console view that appears, press the Kill button

However, I would recommend using Redlink firmware instead of CMSIS-DAP. To do this, just remove 'Link DFU' jumper between the 2 USB connectors and unplug/replug. LPCXpresso will now boot the Redlink firmware next time you start a debug session.
http://www.lpcware.com/content/faq/lpcxpresso/lpc-link2-support

BTW: There is no need to delete the launch configuration again. I just recommended this as a quick way to reset it to pick up your LPC-Link2.

[lpcware]

Content originally posted in LPCWare by drnow on Mon Nov 24 07:35:59 MST 2014
Support,

Thanks for your reply.  The good news is, it worked once.  The bad news is, I cannot get the debugger to work a second time.

I followed your suggestion about deleting the launch configuration.  After the Debug button was pressed, oddly a Windows Firewall warning came on screen.  Clicking thru resulted in the debugger eventually connecting to the IDE and the target, and I was able to debug the program. 

However, I then tried modifying the code (one line).  I recompiled this modified program without problems, but when attempting to debug it, I ran into an error.  I don't have that the details of that error.  I then re-tried your suggestion of deleting the launch configuration.  I got the following error messages:

Error in final launch sequence
Reason:
Error in final launch sequence

Details:
Error: Error reported  by server (redlinkserv.exe)
RedlinkAPI: Invalid index
CMSIS-DAP has been terminated and will be restarted
Please restart your debug session
If the problem recurs, please power cycle your debug probe and restart LPCXpresso


I then restarted LPCXpresso, and power cycled the board, and debugged the program again.  I was given the choice to Connect to emulator: NXP LPC5410x (master) and selected the only choice, named LPC-Link-II CMSIS-DAP.  Clicking thru, I again got the above error messages.

Suggestions?

[lpcware]

Content originally posted in LPCWare by lpcxpresso-support on Mon Nov 24 00:06:37 MST 2014
For some reason, the debugger Launch configurtion has been configured to use an LPC-Link1, not a Link2. The simplest things is to delete the launch configuration and then press the Debug button on the Quickstart panel to reacreate it and start a debug session:
http://www.lpcware.com/content/faq/lpcxpresso/launch-configuration-menu