LPC-Link2 Could not connect to core

cancel
Showing results for 
Search instead for 
Did you mean: 

LPC-Link2 Could not connect to core

Jump to solution
1,487 Views
vitaliylivnov
Contributor III

Hello! We have created the first LPCOpen project for LPC-Link2 and now we have problems with its connection to MCUXpresso. When debugging starts, we get the following errors.
In the console:

MCUXpresso RedlinkMulti Driver v10.0 (Jun 22 2017 23:31:55 - crt_emu_cm_redlink build 272)
Reconnected to existing redlink server (PID 4294967295)
Connecting to probe 1 core 0 (server PID unknown) gave 'Ee(36). Could not connect to core.'
Connecting to probe 1 core 0 (server PID unknown) gave 'Ee(36). Could not connect to core.'
Connecting to probe 1 core 0 (server PID unknown) gave 'Ee(36). Could not connect to core.'
Server OK but no connection to probe 1 core 0 (after 3 attempts) - Ee(36). Could not connect to core.
Failed on connect: Ee(36). Could not connect to core.
No connection to chip's debug port
error closing down debug session - Em(02). MEM-AP is not selected.

In the message box:

Error in final launch sequence
Failed to execute MI command:
-target-select extended-remote | crt_emu_cm_redlink -msg-port=52478 -g -mi -2 -pLPC4370 -vendor=NXP -ResetScript=LPC18LPC43ExternalFLASHBootResetscript.scp -reset= -ProbeHandle=1 -CoreIndex=0 -cache=disable --telnet 3332
Error message from debugger back end:
Remote communication error. Target disconnected.: No error.
Remote communication error. Target disconnected.: No error.

Jumper JP1 and JP2 are open. Tell me please, what are we doing wrong?

Labels (1)
0 Kudos
1 Solution
585 Views
lpcxpresso_supp
NXP Employee
NXP Employee

Yes, you can use a J-Link to debug the LPC-Link2, or, another LPC-Link2. I guess it wasn’t clear what you were trying to do, but the LPC-Link2 can’t debug itself. You need a separate probe.

Thanks and regards,

MCUXpresso Support 

View solution in original post

5 Replies
586 Views
lpcxpresso_supp
NXP Employee
NXP Employee

Yes, you can use a J-Link to debug the LPC-Link2, or, another LPC-Link2. I guess it wasn’t clear what you were trying to do, but the LPC-Link2 can’t debug itself. You need a separate probe.

Thanks and regards,

MCUXpresso Support 

View solution in original post

585 Views
lpcxpresso_supp
NXP Employee
NXP Employee

This very much sounds like you are trying to debug your LPC-Link2 using the same LPC-Link2? You cannot do this - the LPC-Link2 cannot act as both a debug probe and a target board at the same time.

If you do have a separate target board - what is the target board, what MCU does it have fitted, how are you powering it, and how are you connecting it to the LPC-Link2?

Regards,

MCUXpresso IDE Support

0 Kudos
585 Views
vitaliylivnov
Contributor III

Thanks for your answer. No, I don't have separate target board. Can I use J-Link for debugging LPC-Link2 controller? And if so, how to set it up in MCUXpresso?

0 Kudos
585 Views
lpcxpresso_supp
NXP Employee
NXP Employee

It almost sounds like your probe hasn't booted. The MCUXpresso IDE will DFU boot the probe if it's not found. Delete your launch configurations, and power cycle your probe. Be certain no rogue redlinkserv, crt_emu_cm_redlink, or arm-none-eabi-gdb processes are running. If the probe boots successfully, the IDE will show the probe details for you to select. Let us know what you find.

Thanks and regards,

MCUXpresso Support

0 Kudos
585 Views
vitaliylivnov
Contributor III

1. If I understand you correctly, then here is the window that appeared after all the actions done and start debugging.

probes_list.png

2. I have Segger J-Link programmer. Can I use it for debugging of LPC-Link2 board?

0 Kudos