I had installed MCUXpresso 10.0.0 build 344 on Ubuntu 16.04 and my LPCLink2 probe was working fine. I have found that after upgrading to Ubuntu 17.04 that the probes can no longer be found and debugging fails. I have also tried with an LPC11u68 xpresso v2 board with the same result. The system is able to both probes, but ProbeList returns no probes.
[ 133.076818] usb 1-1: new high-speed USB device number 7 using xhci_hcd
[ 133.217912] usb 1-1: New USB device found, idVendor=1fc9, idProduct=000c
[ 133.217916] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 133.217919] usb 1-1: Product: LPC
[ 133.217921] usb 1-1: Manufacturer: NXP
[ 133.217923] usb 1-1: SerialNumber: ABCD
Bus 001 Device 007: ID 1fc9:000c NXP Semiconductors
No probes found
Has anyone managed to get the probe working under Ubuntu 17.04?
I'm also having a similar problem using McuXpresso 10.0.2_411 (downloaded today) on Ubuntu 17.04 communicating with a FRDM-KL27/upgrdaded to boot Pemicro_v118.sda.
When I switch to P&E (after cutting J18) I'm getting same effect as not finding
Bus 001 Device 017: ID 1357:0503 P&E Microcomputer Systems USB-ML-12 HCS08/HCS12 Multilink
Thanks for the information. We will aim to address this in a future release but our develop and test remains on the LTS version.
As of now, I think the best option is to pre-program your LPC-Link2 with debug probe firmware (rather than booting on demand) - so it will always appear as ID 1fc9:0090 NXP Semiconductors when connected.
We have a tool to do this called LPCScrypt LPCScrypt v1.8.0|NXP that can automate the process ... now some weasel words. This tool is pending an update to support the latest debug probe firmware etc. Although the older firmware will work without issue, you could patch an LPCScrypt installation with the latest firmware from the MCUXpresso IDE Install at ide/bin -> LPC432_CMSIS_DAP_V5_182.bin.hdr to LPCScrypt/probe_firmware_LPCLink2 . Also, the host software for this tool is 32 bit and not tested in Ubuntu 17.04.
If you have access to more than one LPC-Link2 (or another LinkServer compatible debug probe), you could perform the same programming operation using MCUXpresso IDE by connecting the debug probe to the target LPC-Link2's LPC4370 'J2' connection.
Then create a dummy project (or use any existing project), select this and click the GUI Flash Programmer 'Chip' Icon.
From the dialogue, you need to specify the flash driver as shown (else the projects driver will be used), browse to the firmware in ide/bin directory, and then set the base address of the LPC-Link2 SPIFI flash at 0x14000000, then click OK.
To use your programmed LPC-Link2 debug probe, ensure that the link JP1 (nearest the USB connector) is made and reboot the probe.
Thank you for your report and help with this issue.
To help us investigate - could I ask you to connect a LPC-Link2 - run lsusb.
Then try to boot the LPC-Link2 probe via the boot_link2 script located in the ide/bin directory
Run lsusb one more time and then paste the result back to this thread.
Bus 001 Device 039: ID 1fc9:000c NXP Semiconductors
/usr/local/mcuxpressoide/ide/bin/dfu_boot -s ./boot_link2 -n LPC-Link2 -v 0x1fc9:0x000c -i /usr/local/mcuxpressoide/ide/bin/../bin/LPC432x_CMSIS_DAP_V5_182.bin.hdr
Looking for DFU devices with VID 1fc9 PID 000c ...
dfu-util -d 1fc9:000c -c 1 -i 0 -t 2048 -R -D /usr/local/mcuxpressoide/ide/bin/../bin/LPC432x_CMSIS_DAP_V5_182.bin.hdr
Booted LPC-Link2 (1fc9:000c) with /usr/local/mcuxpressoide/ide/bin/../bin/LPC432x_CMSIS_DAP_V5_182.bin.hdr
Bus 001 Device 042: ID 1fc9:0090 NXP Semiconductors
After running boot_link2 manually, I am able to see the probe in MCUXpresso. After disconnecting and reconnecting, it is not visible until I rerun the command by hand. It looks like MCUXpresso is not booting the probe. Even when I hit the "Boot Debug Probe" button it does not work.
I have discovered two more pieces of information:
Is MCUXpresso initialising the probe differently than LPCXpresso is? Could it be related to a missing library that I have the i386 version installed, and not the x64 version that MCUXpresso is expecting?