lpcware

Could not connect to core

Discussion created by lpcware Employee on Jun 15, 2016
Latest reply on Jun 15, 2016 by lpcware
Content originally posted in LPCWare by ezharkov on Sun Nov 10 11:50:32 MST 2013
LPC LINK2, LPC1788.

LPCXpresso_6.1.0_164 often gets into a state in which it keeps saying "Could not connect to core". Cycling power on LPC LINK2, MCU, restarting LPCXpresso, etc, sometimes helps, sometimes not.

What core is it trying to connect and why cannot it connect to it?

When LPCXpresso_6.1.0_164 is in that mode, crt_emu_cm_redlink from LPCXpresso_5.2.4_2122 still works just fine!

Below is the output from LPCXpresso_6.1.0_164's crt_emu_cm_redlink.

Eugene


Ni: LPCXpresso RedlinkMulti Driver v6.0 (Sep 17 2013 18:02:04 - crt_emu_cm_redlink build 244)
Pc: (  0) Reading remote configuration
Nc: Looked for chip XML file in C:/nxp/LPCXpresso_6.1.0_164/lpcxpresso/bin/LPC1788.xml

Nc: Looked for vendor directory XML file in C:/nxp/LPCXpresso_6.1.0_164/lpcxpresso/bin/NXP_directory.xml

Nc: Found generic directory XML file in C:/nxp/LPCXpresso_6.1.0_164/lpcxpresso/bin/crt_directory.xml

Pc: (  5) Remote configuration complete
client: connecting to 127.0.0.1
Ed:02: Failed on connect: Ee(36). Could not connect to core.
Et: Emu(0): Conn&Reset. Was: None. DpID: 00000000. CpuID: 00000000. Info: (null)
Error 0: (null)
Last sticky: 0. AIndex: 0
No MemAp selected
Pc: (100) Target Connection Failed

Outcomes