Mcuxpresso LPC-Link2 not working on a new computer

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Mcuxpresso LPC-Link2 not working on a new computer

1,994 Views
p0ulp3
Contributor I

Hello,

I have been using MCUxpresso for a few years with a valid project for LPC11C24. It worked fine both for compiling and flashing the target board.

I have just received a new computer (brand new), and installed Mcuxpresso on it, in order to check everything is alright. But I cannot flash the target even if I am using the same target, same USB cable, same LPCxpresso debug probe !

The error is always : 

[Connected on port 3025]
redlink> ProbeList
Index = 1
Manufacturer = NXP Semiconductors
Description = LPC-LINK2 CMSIS-DAP V5.224
Serial Number = BSEWO1CT
VID:PID = 1FC9:0090
Path = \\?\hid#vid_1fc9&pid_0090&mi_00#7&29c7e89f&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
redlink> ProbeStatus
Index = 1
Manufacturer = NXP Semiconductors
Description = LPC-LINK2 CMSIS-DAP V5.224
Serial Number = BSEWO1CT
VID:PID = 1FC9:0090
Path = \\?\hid#vid_1fc9&pid_0090&mi_00#7&29c7e89f&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
IsOpen = FALSE
WireInitialized = FALSE
WireProtocol = JTAG
CoresConfigured = FALSE
PacketSize = 1024
Reference Count = 0
HasSWV = FALSE
HasETM = FALSE
HasJTAG = TRUE
HasSWD = TRUE
Probe Type = CMSIS-DAP
Probe Reference Count = 0
redlink> ProbeList
Index = 1
Manufacturer = NXP Semiconductors
Description = LPC-LINK2 CMSIS-DAP V5.224
Serial Number = BSEWO1CT
VID:PID = 1FC9:0090
Path = \\?\hid#vid_1fc9&pid_0090&mi_00#7&29c7e89f&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
redlink> ProbeStatus
Index = 1
Manufacturer = NXP Semiconductors
Description = LPC-LINK2 CMSIS-DAP V5.224
Serial Number = BSEWO1CT
VID:PID = 1FC9:0090
Path = \\?\hid#vid_1fc9&pid_0090&mi_00#7&29c7e89f&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
IsOpen = FALSE
WireInitialized = FALSE
WireProtocol = JTAG
CoresConfigured = FALSE
PacketSize = 1024
Reference Count = 0
HasSWV = FALSE
HasETM = FALSE
HasJTAG = TRUE
HasSWD = TRUE
Probe Type = CMSIS-DAP
Probe Reference Count = 0
redlink> ProbeIsOpen 1
FALSE
redlink> ProbeOpenByIndex 1
Probe Handle 1 Open
redlink> WireIsConnected 1
FALSE
redlink> WireSwdConnect 1
Error reading from server (redlinkserv.exe):
Read timed out
Error: Hardware interface transfer error

 

or 

[Started server]
[Connected on port 3025]
redlink> ProbeList
Index = 1
Manufacturer = NXP Semiconductors
Description = LPC-LINK2 CMSIS-DAP V5.224
Serial Number = BSEWO1CT
VID:PID = 1FC9:0090
Path = \\?\hid#vid_1fc9&pid_0090&mi_00#7&29c7e89f&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
redlink> ProbeStatus
Index = 1
Manufacturer = NXP Semiconductors
Description = LPC-LINK2 CMSIS-DAP V5.224
Serial Number = BSEWO1CT
VID:PID = 1FC9:0090
Path = \\?\hid#vid_1fc9&pid_0090&mi_00#7&29c7e89f&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
IsOpen = FALSE
WireInitialized = FALSE
WireProtocol = JTAG
CoresConfigured = FALSE
PacketSize = 1024
Reference Count = 0
HasSWV = FALSE
HasETM = FALSE
HasJTAG = TRUE
HasSWD = TRUE
Probe Type = CMSIS-DAP
Probe Reference Count = 0
redlink> ProbeIsOpen 1
FALSE
redlink> ProbeOpenByIndex 1
Error: Probe not open

 

If I unplug the board from the failing computer and plug it to the old computer, it works ! So it cannot be the LPC-Link2 probe or its firmware.

I cannot use anymore this old computer. The new one is a Dell, core i7 etc nothing exotic.

What can I look for to investigate ?

I tried to reinstall the drivers, to reinstall even windows without success !

The device appears as "LPC-LinkII UCom Port" (pilote 2.0.0.0) and as "LPC based USB device" in the device manager.

I have tried many different USB ports without success.

The target board is powered by an external power supply, the red led of the debug probe is always blinking.

The autorizations are fine in the Firewall of Windows.

Please any help will be highly appreciated ! I suspect I am missing something but I cannot see what.

Regards

0 Kudos
8 Replies

1,985 Views
converse
Senior Contributor V

Try a different USB port. So,e USB ports are not capable of supplying sufficient power.

0 Kudos

1,981 Views
p0ulp3
Contributor I

Hello, unfortunately I have already tried all USB ports and also a USB hub with external power suppli without success.

0 Kudos

1,976 Views
converse
Senior Contributor V

The log you posted indicates JTAG is selected, but LPC11 is SWD only. Is you debug setup correctly?

0 Kudos

1,972 Views
p0ulp3
Contributor I

Hello, here is a similar log but from the computer working. I think that the JTAG is selected at start but then if the function ProbeOpenByIndex works, then WireSwdConnect will select the SWD instead.

The issue is that I don't see a delta in the log between both computers.. except the ProbeOpenByIndex function not working.

[Started server]
[Connected on port 3025]
redlink> ProbeList
Index = 1
Manufacturer = NXP Semiconductors
Description = LPC-LINK2 CMSIS-DAP V5.224
Serial Number = BSEWO1CT
VID:PID = 1FC9:0090
Path = \\?\hid#vid_1fc9&pid_0090&mi_00#7&29c7e89f&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
redlink> ProbeStatus
Index = 1
Manufacturer = NXP Semiconductors
Description = LPC-LINK2 CMSIS-DAP V5.224
Serial Number = BSEWO1CT
VID:PID = 1FC9:0090
Path = \\?\hid#vid_1fc9&pid_0090&mi_00#7&29c7e89f&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
IsOpen = FALSE
WireInitialized = FALSE
WireProtocol = JTAG
CoresConfigured = FALSE
PacketSize = 1024
Reference Count = 0
HasSWV = FALSE
HasETM = FALSE
HasJTAG = TRUE
HasSWD = TRUE
Probe Type = CMSIS-DAP
Probe Reference Count = 0
redlink> ProbeList
Index = 1
Manufacturer = NXP Semiconductors
Description = LPC-LINK2 CMSIS-DAP V5.224
Serial Number = BSEWO1CT
VID:PID = 1FC9:0090
Path = \\?\hid#vid_1fc9&pid_0090&mi_00#7&29c7e89f&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
redlink> ProbeStatus
Index = 1
Manufacturer = NXP Semiconductors
Description = LPC-LINK2 CMSIS-DAP V5.224
Serial Number = BSEWO1CT
VID:PID = 1FC9:0090
Path = \\?\hid#vid_1fc9&pid_0090&mi_00#7&29c7e89f&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
IsOpen = FALSE
WireInitialized = FALSE
WireProtocol = JTAG
CoresConfigured = FALSE
PacketSize = 1024
Reference Count = 0
HasSWV = FALSE
HasETM = FALSE
HasJTAG = TRUE
HasSWD = TRUE
Probe Type = CMSIS-DAP
Probe Reference Count = 0
redlink> ProbeIsOpen 1
FALSE
redlink> ProbeOpenByIndex 1
Probe Handle 1 Open
redlink> WireIsConnected 1
FALSE
redlink> WireSwdConnect 1
DpID = 0BB11477
redlink> CoresConfigured 1
TRUE
redlink> WireIspReset 1
redlink> ProbeStatus
Index = 1
Manufacturer = NXP Semiconductors
Description = LPC-LINK2 CMSIS-DAP V5.224
Serial Number = BSEWO1CT
VID:PID = 1FC9:0090
Path = \\?\hid#vid_1fc9&pid_0090&mi_00#7&29c7e89f&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
IsOpen = TRUE
WireInitialized = TRUE
WireProtocol = SWD
CoresConfigured = TRUE
PacketSize = 1024
Reference Count = 0
HasSWV = FALSE
HasETM = FALSE
HasJTAG = TRUE
HasSWD = TRUE
Probe Type = CMSIS-DAP
Probe Reference Count = 0
redlink> quit
[Closed]

0 Kudos

1,961 Views
ZhangJennie
NXP TechSupport
NXP TechSupport

Hi

I suggest you follow below link to check your LPC Link2 issue.

https://community.nxp.com/t5/LPCXpresso-IDE-FAQs/LPC-Link2-fails-to-enumerate-with-CMSIS-DAP-firmwar...

 

Try to use LPCScrypt to update LPC Link2 firmware with Jlink, see how it works.

 

Have a nice day,

Jun Zhang

0 Kudos

1,957 Views
p0ulp3
Contributor I

Hello,

 

Thanks for the hint, but it wasn't successful. I have tried to check the installed drivers using your link, it appears both the 1.0.0.0 and 2.0.0.0 were available, but the version 2.0.0.0 was the one used (based on the device manager). I have uninstalled the 1.0.0.0 drivers, rebooted, no success. I have tried also LPCScrypt, and reboot, without success.

My list of driver is 100% identical to the one of the working computer but it still not works. 

Could it be something related to the last version of windows ?

In the device manager, on both computers, I see the same behavior, the lpc based usb device is active, then it becomes inactive and the LPC-LinkII UCom Port (COM6) becomes active. But only one of the computers works.

You are talking about updating the firmware of the LPC-Link2 with Jlink but reading the NXP doc, I was thinking that the firmware was updated each time I perform a debug ? So it will be reseted if I update it no ?

0 Kudos

1,949 Views
p0ulp3
Contributor I

Hello again,

After updating the firmware to the JLink version, the GUI Flash tool appeared to be working.

The debug wasn't but after a search here : https://community.nxp.com/t5/MCUXpresso-Community-Articles/MCUXpresso-IDE-v11-0-1-Segger-LPC-Debug-H...

I can now Flash and also Debug with a Jlink probe (even if it's always the LPC-Link2), but I have kept the JP1 jumper on. Nothing to worry about this ?

I still think there is some issue with the compatibility of Windows with the CMIS-DAP firmware, anyway thanks all for the support, I highly appreciate and can continue working

Have a nice day.

0 Kudos

1,942 Views
ZhangJennie
NXP TechSupport
NXP TechSupport

After updating the firmware, fit JP1 to use it as a programming tool . then reconnect the board to the host computer. You should see the debug probe enumerate on the host’s USB system.

 

Have a nice day,

Jun Zhang

0 Kudos