Connecting to LPC-Link2 in ubuntu virtualbox

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

Connecting to LPC-Link2 in ubuntu virtualbox

1,267 Views
jeroenreeskamp
Contributor I

Hello,

I'm trying to set up an automated build and flashing sequence in a virtual machine that is running Ubuntu 19.10 using virtual box

I run into problems when i try to flash a device

First I boot the link 

user@user-VirtualBox:/usr/local/mcuxpressoide/ide/binaries$ ./boot_link2
/usr/local/mcuxpressoide/ide/binaries/dfu_boot -s ./boot_link2 -n LPC-Link2 -v 0x1fc9:0x000c -i /usr/local/mcuxpressoide/ide/binaries/../binaries/LPC432x_CMSIS_DAP_V5_361.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/binaries/../binaries/LPC432x_CMSIS_DAP_V5_361.bin.hdr
Booted LPC-Link2 (1fc9:000c) with /usr/local/mcuxpressoide/ide/binaries/../binaries/LPC432x_CMSIS_DAP_V5_361.bin.hdr

this all goes well, but when i try to flash the device i get the following

user@user-VirtualBox:/usr/local/mcuxpressoide/ide/binaries$ ./crt_emu_cm_redlink -flash-load-exec "/home/Desktop/barcode_reader/focus54114/EEPROM_writer/Debug/EEPROM_writer.axf" -vendor=NXP -pLPC54114J256
Ns: MCUXpresso IDE RedlinkMulti Driver v11.1 (Dec 4 2019 19:02:41 - crt_emu_cm_redlink build 5)
Wc(03). No cache support.
Nc: Found part description in XML file LPC5411x.xme
Nc: Restarted LinkServer process (PID 2879).

DEVICE ATTACH 1FC9:0090 Bus: 001 Device: 005
Nc: Reconnected to existing LinkServer process.
Ns: redlink server client - failed to receive response (to op 26) from server after 2000ms - Connection timed out (rc 110)
Nc: Server OK but no connection to probe 0 core -2(ANY) (after 3 attempts) - Ee(42). Could not connect to core.
Ed:02: Failed on connect: Ee(42). Could not connect to core.
Et:31: No connection to chip's debug port
user@user-VirtualBox:/usr/local/mcuxpressoide/ide/binaries$ ./crt_emu_cm_redlink -flash-load-exec "/home/Desktop/barcode_reader/focus54114/EEPROM_writer/Debug/EEPROM_writer.axf" -vendor=NXP -pLPC54114J256
Ns: MCUXpresso IDE RedlinkMulti Driver v11.1 (Dec 4 2019 19:02:41 - crt_emu_cm_redlink build 5)
Wc(03). No cache support.
Nc: Found part description in XML file LPC5411x.xme
Nc: Reconnected to existing LinkServer process.
Ns: redlink server client - failed to receive response (to op 26) from server after 2000ms - Connection timed out (rc 110)
Nc: Connecting to probe 0 core 0 (using server started externally) reports:
'Ee(42). Could not connect to core.'
Nc: Retrying...
Ns: redlink server client - failed to receive response (to op 26) from server after 2000ms - Connection timed out (rc 110)
Ns: redlink server client - failed to receive response (to op 26) from server after 2000ms - Connection timed out (rc 110)
Nc: Reconnected to existing LinkServer process.
Ns: redlink server client - failed to receive response (to op 26) from server after 2000ms - Connection timed out (rc 110)
Nc: Server OK but no connection to probe 0 core -2(ANY) (after 3 attempts) - Ee(42). Could not connect to core.
Ed:02: Failed on connect: Ee(42). Could not connect to core.
Et:31: No connection to chip's debug port

Any clue as to what I should do to make it work?

Tags (1)
0 Kudos
2 Replies

1,064 Views
davidcabanis
Contributor I

I am having the same problem but running Ubuntu 16.04 LTS 64bit (Virtualbox) .

> lsusb

Bus 001 Device 003: ID 1fc9:0090 NXP Semiconductors

Trying to flash the device I get:

Executing flash operation 'Program' (Program file into flash: Debug/LPC55S69_hello_world_ns.axf) - Wed Mar 04 09:35:16 GMT 2020
Checking MCU info...
Scanning for targets...
Executing flash action...
MCUXpresso IDE RedlinkMulti Driver v11.1 (Dec  4 2019 19:02:41 - crt_emu_cm_redlink build 5)
(  0) Reading remote configuration
Wc(03). No cache support.
Found chip XML file in /home/doulos/MCUXpresso_11.1.0_3209/workspace/Arm Cortex-v8M Exercises/ex_1/LPC55S69_hello_world_ns/Debug/LPC55S69.xml
(  5) Remote configuration complete
Reconnected to existing LinkServer process.
redlink server client - failed to receive response (to op 26) from server after 2000ms - Connection timed out (rc 110)
Connecting to probe 1 core 0 (using server started externally) reports:
'Ee(42). Could not connect to core.'
Retrying...
redlink server client - failed to receive response (to op 26) from server after 2000ms - Connection timed out (rc 110)
redlink server client - failed to receive response (to op 26) from server after 2000ms - Connection timed out (rc 110)
Reconnected to existing LinkServer process.
redlink server client - failed to receive response (to op 26) from server after 2000ms - Connection timed out (rc 110)
Server OK but no connection to probe 1 core 0 (after 3 attempts) - Ee(42). Could not connect to core.
Failed on connect: Ee(42). Could not connect to core.
No connection to chip's debug port
(100) Target Connection Failed
Unable to perform operation!
Command failed with exit code 1

For information I am using the examples provided in the SDK. The same examples work fine in Windows 10. Do you have any suggestions?

Kindly,

David.

0 Kudos

1,064 Views
ZhangJennie
NXP TechSupport
NXP TechSupport

Hi

MCUXpresso IDE 11.1 was only tested on Ubuntu Linux® 16.04 LTS / 18.04 LTS (64-bit host OS only)

No test on 19.10

Please use the IDE on your recommend platform:

Host operating systems:

  • Microsoft® Windows® 7/8/10 (64 bit only)
  • Ubuntu Linux® 16.04 LTS / 18.04 LTS (64-bit host OS only)
  • macOS 10.11 -> 10.14

Have a nice day,

Jun Zhang

0 Kudos