debugging no more possible with lpc4357 + NXP LPC-LINK

[lpcware]

Content originally posted in LPCWare by srinivasR on Mon Oct 19 04:22:06 MST 2015
Hi ,

I was debugging a SDRAM test application on my board from LPCXpresso v7.9.2 and found some issues with code. Stopped the current debug session and when started the next session, all of sudden I am not able to download code to micro. Until the problem occurred I was able to debug completely.


I get below errors

LPCXpresso Debug Driver v7.9 (Aug 11 2015 15:47:31 - crt_emu_lpc18_43_nxp build 262)
Failed on connect: Ee(07). Bad ACK returned from status - wire error.
Connected&Reset. Was: NotConnected. CpuID: 00000000. Info: HID64HS12
Error 0: OK
Last sticky error: 0x0 AIndex: 0
Debug bus selected: MemAp 0
DAP Speed test succeeded after adjusting speed 31 times
Debug protocol: JTAG Frequency 3000 KHz. RTCK: Disabled. Vector catch: Enabled.
(100) Target Connection Failed
02. Failed to connect
Bad ACK returned from status - wire error
Emu(0) COnnected&Reset. Was notconnected.CPUID: 000000.info.HID64HS12

Error in final launch sequence
Failed to execute MI command:
-target-select extended-remote | crt_emu_lpc18_43_nxp -msg-port=25322 -g -mi -2 -pLPC4357 -vendor=NXP -vc -e0 -wire=hidjtag -scan C:\\Users\\srv2kor\\Documents\\LPCXpresso_7.9.2_493\\workspace\\freertos_blinky\\Debug\\freertos_blinky_Debug.jtag -cache=disable -flash-driver=LPC18x7_43x7_2x512_BootA.cfx
Error message from debugger back end:
Remote communication error.  Target disconnected.: No error.
Remote communication error.  Target disconnected.: No error.

Please help to recover the debug.

[lpcware]

Content originally posted in LPCWare by lpcxpresso-support on Tue Oct 20 09:32:15 MST 2015


The previous suggestions did not require you to boot the part into the ISP. That's where you're at now. You're going to need to boot the part into the ISP, so you need ISP and RESET in order to do this. Once you're successful booting the board, erase flash and figure out what change in your code caused the problem.

Thanks and regards,
LPCXpresso Support

[lpcware]

Content originally posted in LPCWare by srinivasR on Tue Oct 20 01:46:22 MST 2015

Hi ,

I tried the suggested options. with SWD, I get below errors. Not sure, how to get the board  ( ngx lpc4357 Xplorer )back to debug state. I am looking into ISP mode for possible options, but ISP pin ( p2_7) is not come-out.

How to recover now?

LPCXpresso Debug Driver v7.9 (Aug 11 2015 15:47:31 - crt_emu_lpc18_43_nxp build 262)
Debug bus check after stop (MemAP 0x4770011) FAILS - Em(12). System rejected access at location 0x00590C3C - verify PopulatiŽ™%9ÀN
Failed on connect: Em(12). System rejected access at location 0xE000EDF0 - verify Population of memory and peripherals
Connected&Reset. Was: NotConnected. CpuID: 00000000. Info: HID64HS12
Error 0: OK
Last sticky error: 0x18 POWER PROTCOL AIndex: 0
Debug bus selected: MemAp 0
DAP Speed test succeeded after adjusting speed 32 times
(Chip indicated error - Em(12). System rejected access at location 0xE000EDF0 - verify Population of memory and peripherals)
Debug protocol: SWD Frequency 3000 KHz. RTCK: Disabled. Vector catch: Disabled.
(100) Target Connection Failed

[lpcware]

Content originally posted in LPCWare by lpcxpresso-support on Mon Oct 19 16:35:00 MST 2015
The output you posted suggests the LPC-Link1 simply cannot establish a debug connection to your target processor. Presuming your application did not enable CRP in the last build or disable one of the pins used for debug, check the usual things:

1. Ensure there are no orphaned arm-none-eabi-gdb.exe or crt_emu_lpc18_43_nxp.exe processes in the task list.
2. Power on/off the LPC-Link1 and your board.
3. Check the JTAG ribbon cable connection, and JTAG ribbon cable.
4. Determine whether the LPC-Link1 can debug any other target processor. An easy check is to load an image to the processor attached to the LPC-Link1, provided the LPC-Link1 is not separated from it.
5. Delete and recreate your launch/debug configuration. If your last debug configuration used the JTAG  protocol, try to connect debug with the SWD protocol.

I can tell you I just loaded the LPCOpen freertos_blinky image for the LPC4337 using an LPC-Link1 and encountered no trouble whatsoever.

Thanks and regards,
LPCXpresso Support