Cannot boot LPC Link 2 on LPCxpresso V3.

[albertcimpoesu]

I'm getting a weird message as output of dfu-util --list :

Found Runtime: [1fc9:000c] devnum=0, cfg=1, intf=0, alt=0, name="DFU"
Found Runtime: [1fc9:000c] devnum=0, cfg=1, intf=0, alt=0, name="UNDEFINED"

Both devices appear simultaneously and I get prompted to remove one device, but there is only one device connected.
Due to this I can't boot the LPC Link2.

This prevents MCUXpresso from launching a debug session (It simply hangs).

The probe is working because I can use the CMSIS-DAP firmware.

Any ideas about how to fix this?

[lpcxpresso_supp]

OK, good to hear you are now up and running - and thanks for confirming your "fix.

Regards,

MCUXpresso IDE Support

[albertcimpoesu]

I found a fix for this:
Update the dfu-util executable and libraries to the latest version.

[lpcxpresso_supp]

What IDE version are you running and on which host OS (and version)?

In the first place, I would suggest running through the suggestions in section 14.12, "Using and troubleshooting LPC-Link2" in the MCUXpresso IDE v10.0.2 User Guide. For instance, trying to manually boot may give some additional clues.

And you could also try pre-programming the latest firmware into flash (rather than relying on softloading by the IDE) using LPCScrypt (http://www.nxp.com/lpcscrypt) - though this will also rely on DFU booting too.

[ Note - if your board came with CMSIS-DAP firmware pre-programmed into the onboard LPC-Link2, then the IDE will also be able to connect via that, it just probably won't be the latest (1.8.x) firmware version]

Regards,

MCUXpresso IDE Support

[albertcimpoesu]

Sorry for the delayed response,
the IDE is version 10.0.2_411 on Windows 10 with the latest updates.
None of the guides for manually booting the probe don't work because of the dfu-util issue.
The probe works with the CMSIS-DAP firmware and I can use MCUXpresso and Keil to flash the target.
But I can't boot the Link2 to reflash with any other firmware.

I also tried reinstalling windows so it's not an issue with the OS.