AnsweredAssumed Answered

LPC-Link2 Could not connect to core

Question asked by Vitaliy Livnov on Nov 17, 2017
Latest reply on Nov 18, 2017 by LPCX presso support

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?

Attachments

Outcomes