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 pumpi on Wed Feb 25 07:01:37 MST 2015
Many thanks!
Redlink is now working with the latest hdr file !!!  :)

I still have problems with the latest CMSIS-DAP FW.
Here is what I did:
- Removed the virual COM-Port driver in the dev manager
- Unplugged LPC-Link and plugged it in again => no triangle in the device manager, even no device related to LPC-Link visible, LPCXpresso unable to detect the Debugger
- Installed Drivers from LPCXpresso 7.6.2 directory => COM-Port is back again (and only this one), but no CMSIS-DAP is detected by LPCXpresso.

=> Wrt CMSIS-DAP in combination with the latest FW no progress.

Do you have further suggestions? Thanks in advance.

[lpcware]

Content originally posted in LPCWare by lpcxpresso-support on Mon Feb 23 02:32:22 MST 2015
Thanks for the Info. Lets try and clear your Windows Device driver problems.

[list]
  [*]First of all, boot LPC-Link2 with the original Redlink V5_58 image.
  [*]Open Device Manager (run devmgr.msc from the Windows Start-Run button)
  [*]If you see any devices with the warning Triangle against them, unintstall them (Right-click and select Uninstall) and if visible, select the Delete the driver option
  [*]If you see a Redlink serial port listed under Ports, uninstall that too
[/list]

Now repeat for the (latest) CMSIS-DAP firmware

Now, go back and boot LPC-Link2 with the original Redlink image. If you are prompted by Windows to install Drivers, use the Drivers directory within the LPCXpresso 7.6.2 installation. And do the same for the CMSIS-DAP firmware.

Please let me know how you get on.

[lpcware]

Content originally posted in LPCWare by pumpi on Sun Feb 22 06:19:38 MST 2015
Okay. First, the listusb result without any LPC stuff connected.

VID: 03F0 PID: 5B12 (HP Officejet Pro 8100 (REST))
VID: 03F0 PID: 5B12 (USB-Druckerunterstützung)
VID: 03F0 PID: 5B12 (USB-Verbundgerät)
VID: 0409 PID: 005A (Generic USB Hub)
VID: 0409 PID: 005A (Generic USB Hub)
VID: 0424 PID: 2228 (USB-Massenspeichergerät)
VID: 0424 PID: 2602 (Generic USB Hub)
VID: 04A9 PID: 1904 (CanoScan LiDE 100)
VID: 05E3 PID: 0608 (Generic USB Hub)
VID: 13D3 PID: 3306 (Realtek RTL8191SU Wireless LAN 802.11n USB 2.0 Network Adapter)
VID: 1A40 PID: 0201 (Generic USB Hub)
VID: 1BCF PID: 05CF (HID-konforme Maus)
VID: 1BCF PID: 05CF (HID-konformes Benutzersteuergerät)
VID: 1BCF PID: 05CF (HID-konformes Gerät)
VID: 1BCF PID: 05CF (HID-konformes Gerät)
VID: 1BCF PID: 05CF (HID-konformes Gerät)
VID: 1BCF PID: 05CF (HID-Tastatur)
VID: 1BCF PID: 05CF (USB-Verbundgerät)
VID: 1BCF PID: 05CF (USB Human Interface Device)
VID: 1BCF PID: 05CF (USB Human Interface Device)
VID: 8087 PID: 0020 (Generic USB Hub)
VID: 8087 PID: 0020 (Generic USB Hub)

To keep the post as short as possible, I will only post the the deltas of the listusb command output:

1. Here are the results with JP5 open (CMSIS-DAP mode) [=> no emulator detected by LPCXpresso]:

C:\nxp\LPCXpresso_7.6.2_326\lpcxpresso\bin>scripts\listusb
VID: 1FC9 PID: 0090 (LPC-LinkII UCom Port)

C:\nxp\LPCXpresso_7.6.2_326\lpcxpresso\bin>boot_link2   /* I do not have boot_lpc_link2 command, but I guess you meant boot_link2 */
Nothing to boot

C:\nxp\LPCXpresso_7.6.2_326\lpcxpresso\bin>scripts\listusb
VID: 1FC9 PID: 0090 (LPC-LinkII UCom Port)

C:\nxp\LPCXpresso_7.6.2_326\lpcxpresso\bin>wmic path Win32_PnpEntity where (service like "%%dfu%%" ) get pnpdeviceid
Keine Instanzen verfügbar.

C:\nxp\LPCXpresso_7.6.2_326\lpcxpresso\bin>wmic path Win32_PnpEntity where (service like "%%hid%%" ) get pnpdeviceid
PNPDeviceID
HID\VID_1BCF&PID_05CF&MI_01&COL01\9&3AC134FA&0&0000
HID\VID_1BCF&PID_05CF&MI_00\9&2A31F936&0&0000
AVSTREAM\MTSHID.VIRTUAL\5&294DC066&0&0
HID\MTSHID.VIRTUAL\6&21C66D4F&0&0000
USB\VID_1BCF&PID_05CF&MI_00\8&314911DA&0&0000
USB\VID_1BCF&PID_05CF&MI_01\8&314911DA&0&0001

2. And again with JP5 installed (RedLink mode) and the V4_65 version renamed to V5_58 (see my previous post) [=> works as expected]:

C:\nxp\LPCXpresso_7.6.2_326\lpcxpresso\bin>scripts\listusb
VID: 1FC9 PID: 000C (LPC based USB device)

C:\nxp\LPCXpresso_7.6.2_326\lpcxpresso\bin>boot_link2
Booting LPC-Link2 with LPC432x_Redlink_V5_58.bin.hdr  /* Note: This LPC432x_Redlink_V5_58.bin.hdr file is actually just a renamed LPC432x_Redlink_V4_65.bin.hdr */
LPC-Link2 booted

C:\nxp\LPCXpresso_7.6.2_326\lpcxpresso\bin>scripts\listusb
VID: 21BD PID: 0006 (HID-konformes Gerät)
VID: 21BD PID: 0006 (USB-Eingabegerät)

/* wmic command output left out -- it's exactly the same as above */

3. Another run with with JP5 installed but now with the original *V5_58*.hdr file as it was distributed in the 7.6.2 installer package [=> no emulator detected by LPCXpresso]:

C:\nxp\LPCXpresso_7.6.2_326\lpcxpresso\bin>scripts\listusb
VID: 1FC9 PID: 000C (LPC based USB device)

C:\nxp\LPCXpresso_7.6.2_326\lpcxpresso\bin>boot_link2
Booting LPC-Link2 with LPC432x_Redlink_V5_58.bin.hdr
LPC-Link2 booted

C:\nxp\LPCXpresso_7.6.2_326\lpcxpresso\bin>scripts\listusb
VID: 21BD PID: 0006 (LPC-LINK2 REDLINK)

/* This time we see a RedLink device. But this device is NOT detected by LPCXpresso. */
/* Again, leaving out the wmic command output as it's exactly the same as above */

Many thanks for your support!!


Edit:
The Redlink Device is listed in the device manager - but no driver is found (neither automatically nor by manually searching any of the relevant directories - even the install directory of lpc_driver_setup.exe)

Edit 2:
Tried a standalone LPC-Link 2: Same results. -- Okay, not really surprising. But I thought I should give it a try...
BTW: Should I mention that I have flashed both, LPC54102 board as well as the LPC-Link2, with the latest version (2.02) of the configuration tool? Maybe this is the root cause for the CMSIS-DAP problems??? Just an idea...

Edit 3  :
I have found an old version of the configuration tool (V 1.11) on my PC.
Unbelievable: CMSIS-DAP is working like charm when flashing this firmware version - for both the standalone LPC-Link2 as well as the LPC-Link2 V2 on the 54102 board. (okay, this FW doesn't support the COM port - but this is more than acceptable)

[lpcware]

Content originally posted in LPCWare by lpcxpresso-support on Sun Feb 22 01:58:00 MST 2015
Please try the following:

Connect LPC-Link2, open a command window and run the following commands:

 cd nxp\lpcxpresso_version...\lpcxpresso\bin
scripts\listusb
boot_lpc_link2
scripts\listusb
wmic path Win32_PnpEntity where (service like "%%dfu%%" ) get pnpdeviceid
wmic path Win32_PnpEntity where (service like "%%hid%%" ) get pnpdeviceid

and post the results

[lpcware]

Content originally posted in LPCWare by pumpi on Sat Feb 21 16:01:10 MST 2015
Unfortunately, even redlink is not working "out of the box" with 7.6.2: Trying to start a debug session on my LPCXpresso 54102 board ends up in a timeout failure when downloading the LPC432x_Redlink_V5_58.bin.hdr file to the debugger.
But I have found a workaround: Simply renaming the LPC432x_Redlink_V4_65.bin.hdr file (which seems to be an older version??) into LPC432x_Redlink_V5_58.bin.hdr makes redlink work.
Strange thing - but redlink is now working which is already a step forward!
BTW: Any idea why the V5 hdr file leads to a timeout -- and why there are two versions of the ".hdr file"??

Concerning CMSIS-DAP: No success under WIN7. I have again and again deleted and installed the drivers (even with and without re-running lpc_driver_setup.exe) - but I am stuck.
BTW: JLINK works - but this is not supported by LPCXpresso...

The funny thing is that a Ubuntu 14.04 VM (running under VMware - on the same machine) recognizes the CMSIS-DAP debugger as well as the redlink version (= JP5 plugged in). Unfortunately, my LPC-Link-I devices are not detected by the VM.

So, in total I am currently stuck with:
LPC-Link-I: WIN7 (ok),  Linux-VM (not detected)
LPC-Link-II (redlink): WIN7 (ok after .hdr file exchange, timeout otherwise),  Linux-VM (ok - out of the box)
LPC-Link-II (CMSIS-DAP): WIN7 (no chance),  Linux-VM (ok - out of the box)
LPC-Link-II (JLINK): WIN7 (detected),  Linux-VM (- not tested so far -)

My suspicion is that there is (somewhere) some old driver stuff from previous LPCXpresso versions (over the time I have installed several of them) lying around that conflicts (somehow) with the new LPC-Link-II driver.

Any idea how to reasonably clean up (without re-installing Windows) would be welcome...

[lpcware]

Content originally posted in LPCWare by lpcxpresso-support on Fri Feb 20 03:55:13 MST 2015
If you continue to have driver setup issues with using the CMSIS-DAP firmware, you may be able to get things working more quickly with LPCXpresso IDE by powering the board off, putting a jumper onto JP5, then powering back up again. This should then allow LPCXpresso to automatically download redlink firmware instead.

Regards,
LPCXpresso Support

[lpcware]

Content originally posted in LPCWare by davidrojas on Fri Feb 20 03:20:06 MST 2015
Yes, it is that one, but if I remember correctly (I don't have the board on my table right know, so I cannot plug it in to check), when you remove the driver there was a checkbox that said "Remove driver software" that you need to check. If you don't find this option, another thing you can do is poke around the file system until you find the .inf file from this driver and manually delete it.

[lpcware]

Content originally posted in LPCWare by pumpi on Fri Feb 20 03:02:01 MST 2015
Thank you for the immediate reply.
Unfiortunately, that's what I already did - with no success:
The only driver I see in the Device Manager is the UCOM-Port Driver. (Did you remove more than this one?)

After removing this driver and plugging the board again, Windows searches for a LPC-Link-II CMSIS DAP driver...
But finally I end up with only the UCOM Driver installed - and, of course, no debug connection from LPCXpresso.

BTW: "listusb" does also not show any othe devices than the UCOM.

I am Using LPCXpresso 7.6.2 and have also run the "lpc_driver_setup.exe" which is required for driver setup according to the 54102-board user manual.

[lpcware]

Content originally posted in LPCWare by davidrojas on Fri Feb 20 00:42:44 MST 2015
You have to go to the Control Panel -> Device manager in windows, when it is pluged-in, and completely remove the drivers (uninstall), so when you plugin it in again it starts searching again like it is a new device.

[lpcware]

Content originally posted in LPCWare by pumpi on Thu Feb 19 16:45:48 MST 2015
I have exactly the same issue: COM port is visible but no CMSIS-DAP etc - and no debug access to the LPC54102 board.
Could you please explain in more detail how you solved the issue?
I reinstalled the drivers several times already. So far no success...
I even tried a different PC -> same problem.
Any hint is welcome!

[lpcware]

Content originally posted in LPCWare by davidrojas on Thu Dec 18 11:23:30 MST 2014
Yes, it was a Windows driver issue. I removed completely the driver, files and everything, plugged it again and it detected and installed all the drivers. The problem is it has different devices on the same physical port, so if windows screws up after installing the first one, it keeps thinking it is working because it found a device (the virtual port in this case) already.

Thanks for the help!

[lpcware]

Content originally posted in LPCWare by lpcxpresso-support on Thu Dec 18 09:15:13 MST 2014
These are the devices listed by listusb with the CMSIS-DAP firmware:

VID: 1FC9 PID: 0090 (HID-compliant device)
VID: 1FC9 PID: 0090 (HID-compliant device)
VID: 1FC9 PID: 0090 (LPC-LinkII UCom Port)
VID: 1FC9 PID: 0090 (USB Composite Device)
VID: 1FC9 PID: 0090 (USB Input Device)
VID: 1FC9 PID: 0090 (USB Input Device)

As I said, I suspect a Windows driver issue.

[lpcware]

Content originally posted in LPCWare by davidrojas on Thu Dec 18 08:42:05 MST 2014
No missing drivers, I have reinstalled the LPC-Link drivers, and still nothing. I tried the listusb, and the only HID device I have is the mouse. The LPC-LinkII UCom Port is still showing up, and it is in fact working correctly as a UART bridge.

[lpcware]

Content originally posted in LPCWare by lpcxpresso-support on Thu Dec 18 08:22:28 MST 2014
It is possible that this is a Windows driver issue. Are there any missing drivers reported by Device Manager?

Note that the debugger uses the HID interface to CMSIS-DAP which does not show in Device Manager (will, it does, but only as a HID-compliant device.

You can use the listusb script in the Scripts directory to see what is actually there.

[lpcware]

Content originally posted in LPCWare by davidrojas on Thu Dec 18 08:12:06 MST 2014
Yes, I'm running LPCXpresso 7.5.0 in windows 7, clean version recently installed in this laptop. I didn't bother to try to recover the CMSIS-DAP with the configuration tool, because I'm better off using Redlink, but still I don't think the image that comes off-the-shelf with board is correct. The LPC-Link UCom Port is the only thing that is showing in the device list in windows, not the rest of the devices, and LPCXpresso can't find any debugger.

Now I just flashed the LPC-Link with the configuration tool, followed the instructions, no errors, but still LPCXpresso can't find the CMSIS-DAP debugger.

[lpcware]

Content originally posted in LPCWare by lpcxpresso-support on Thu Dec 18 07:27:34 MST 2014
You can recover the CMSIS-DAP image by running the LPC-Link Configuration tool:
http://www.lpcware.com/lpclink2-config-tool

However, if you are seeing the LPC-Link UCom Port, then that strongly hints that the CMSIS-DAP image is there.

Are you using LPCXpresso v7.5.0? That is *required* for complete support for this part (do no use any earlier beta).

[lpcware]

Content originally posted in LPCWare by davidrojas on Thu Dec 18 04:33:23 MST 2014
My LPCxpresso54102 is acting the same way, just out of the box, installed driver, plug it in (without the J5 jumper), and only the "LPC-Link UCom Port (COM)" is showing in the device list. I tried to start the debugger with lpcxpresso, clicked on search for every emulator available, an nothing is coming up. If I put the jumper, then it is recognized as an LPC device and debugging using Redlink server works like a charm.
It looks like, contrary to the documentation, these boards are not coming with CMSIS-DAP burned by default. It doesn't matter to me, because Redlink works better and allows it to debug both cores at once, but please update the documentation or fix the coming boards.

Another thing that I don't see clear is that it doesn't seem possible to debug and use only the Cortex-M0+, it always needs a proper image for the Cortex-M4 that at least wakes up the Cortex-M0+ before putting himself to sleep. In the app notes it looks that way, but then when you create a new project in lpcxpresso, it gives you 4 options: Cortex-M4, Cortex-M0+, Cortex-M4-master and Cortex-M0+-slave. From this it seems that a stand-alone Cortex-M0+ image burned in flash would boot properly, but it is not.

[lpcware]

Content originally posted in LPCWare by drnow on Tue Nov 25 02:56:28 MST 2014
Thanks.  The ISP and RESET combo worked to allow the IDE/debugger to gain control of the target.  I can now resume my exploration of the IDE, debugger and M4/M0.

Drnow
Atlanta, GA, USA

[lpcware]

Content originally posted in LPCWare by lpcxpresso-support on Tue Nov 25 01:03:34 MST 2014
The rtc example is (amongst other things) showing how to put the chip into power down mode. When in this state, the debugger cannot gain access as the debug (SWD) is switched off too (to save power).

This FAQ explains how to recover pretty much any LPC family chip that gets into a mode that prevents debug access.
http://www.lpcware.com/content/faq/lpcxpresso/regaining-debug-access
[On the LPC54102 LPCXpresso board, hold down the 'ISP' button, press and release 'RESET' and then release 'ISP']

Note: this is not a fault of the debugger - it physically cannot gain control of the chip

[lpcware]

Content originally posted in LPCWare by drnow on Mon Nov 24 19:39:06 MST 2014
Support,
Thanks for your help and your patience getting me over several hurdles.  I've used lots of software before, including several IDE's, and I must say yours presents special challenges. 

I understand your comment about stepping thru code, and why the debugger was permanently asleep.  Now though, I have a different problem, possibly brought on by starting up another program from the LPC Open set, where I tried periph_rtc and got it to run successfully.  That works fine, and I am able to receive text via the USB port without problems.

However, I am now unable to connect to the target using the debugger.  Returning to the periph_blinky program, when attempting to debug it I get the following message:

Target reported errors
Reason:
02: Failed to connect
Could not connect to core
31:  No connection to emulator device

Could the 54102 be in a state that does not allow the debugger to connect to it?

Thanks,
Drnow
Atlanta, GA, USA