Failed on connect: Ep(01). Target marked as not debuggable.

VictorDiaconu — Thu, 17 Dec 2020 15:50:41 GMT

Hi guys,

I have now a problem. Pleas help me. I can't start the Debug session on LPCXpresso 55s28.

Early it work fine, but after that I done a mistake by Flash Erase and now debug session doesn't start anymore.

I wanted to Erase the Flash Memory. But I forgot to set jumper J10.

I have done:

1. Press reset button.
2. Open Gui Flash Tool
3. at Erase Tab I selected Mass erase and pusch the Run... Button.

Hier are the errors :

MCUXpresso IDE RedlinkMulti Driver v11.2 (Sep 22 2020 13:23:35 - crt_emu_cm_redlink build 19)
Found chip XML file in D:/EMV_SW_NG/EMV_SW_NG_VoxioA/Debug\LPC55S28.xml
Reconnected to existing LinkServer process.
Probe Firmware: LPC-LINK2 CMSIS-DAP V5.224 (NXP Semiconductors)
Serial Number: ORAWCQCQ
VID:PID: 1FC9:0090
USB Path: \\?\hid#vid_1fc9&pid_0090&mi_00#9&575fa1&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
Using memory from core 0 after searching for a good core
On debug connection - use system reset, stalling when 0x50000040 is accessed
Retask read watchpoint 1 at 0x50000040 to use for boot ROM stall
state - running or following reset request - re-read of state failed - rc Nn(05). Wire ACK Fault in DAP access
failed to use debug bus when CPU is stalled - Nn(05). Wire ACK Fault in DAP access
state - running or following reset request - re-read of state failed - rc Nn(05). Wire ACK Fault in DAP access
failed to use debug bus when CPU is stalled - Nn(05). Wire ACK Fault in DAP access
state - running or following reset request - re-read of state failed - rc Nn(05). Wire ACK Fault in DAP access
failed to use debug bus when CPU is stalled - Nn(05). Wire ACK Fault in DAP access
state - running or following reset request - re-read of state failed - rc Nn(05). Wire ACK Fault in DAP access
failed to use debug bus when CPU is stalled - Nn(05). Wire ACK Fault in DAP access
state - running or following reset request - re-read of state failed - rc Nn(05). Wire ACK Fault in DAP access
failed to use debug bus when CPU is stalled - Nn(05). Wire ACK Fault in DAP access
state - running or following reset request - re-read of state failed - rc Nn(05). Wire ACK Fault in DAP access
failed to use debug bus when CPU is stalled - Nn(05). Wire ACK Fault in DAP access
state - running or following reset request - re-read of state failed - rc Nn(05). Wire ACK Fault in DAP access
failed to use debug bus when CPU is stalled - Nn(05). Wire ACK Fault in DAP access
state - running or following reset request - re-read of state failed - rc Nn(05). Wire ACK Fault in DAP access
failed to use debug bus when CPU is stalled - Nn(05). Wire ACK Fault in DAP access
state - running or following reset request - re-read of state failed - rc Nn(05). Wire ACK Fault in DAP access
failed to use debug bus when CPU is stalled - Nn(05). Wire ACK Fault in DAP access
state - running or following reset request - re-read of state failed - rc Nn(05). Wire ACK Fault in DAP access
failed to use debug bus when CPU is stalled - Nn(05). Wire ACK Fault in DAP access
state - running or following reset request - re-read of state failed - rc Nn(05). Wire ACK Fault in DAP access
failed to use debug bus when CPU is stalled - Nn(05). Wire ACK Fault in DAP access
state - running or following reset request - re-read of state failed - rc Nn(05). Wire ACK Fault in DAP access
failed to use debug bus when CPU is stalled - Nn(05). Wire ACK Fault in DAP access
state - running or following reset request - re-read of state failed - rc Nn(05). Wire ACK Fault in DAP access
failed to use debug bus when CPU is stalled - Nn(05). Wire ACK Fault in DAP access
state - running or following reset request - re-read of state failed - rc Nn(05). Wire ACK Fault in DAP access
failed to use debug bus when CPU is stalled - Nn(05). Wire ACK Fault in DAP access
state - running or following reset request - re-read of state failed - rc Nn(05). Wire ACK Fault in DAP access
failed to use debug bus when CPU is stalled - Nn(05). Wire ACK Fault in DAP access
state - running or following reset request - re-read of state failed - rc Nn(05). Wire ACK Fault in DAP access
failed to use debug bus when CPU is stalled - Nn(05). Wire ACK Fault in DAP access
state - running or following reset request - re-read of state failed - rc Nn(05). Wire ACK Fault in DAP access
failed to use debug bus when CPU is stalled - Nn(05). Wire ACK Fault in DAP access
state - running or following reset request - re-read of state failed - rc Nn(05). Wire ACK Fault in DAP access
failed to use debug bus when CPU is stalled - Nn(05). Wire ACK Fault in DAP access
state - running or following reset request - re-read of state failed - rc Nn(05). Wire ACK Fault in DAP access
failed to use debug bus when CPU is stalled - Nn(05). Wire ACK Fault in DAP access
state - running or following reset request - re-read of state failed - rc Nn(05). Wire ACK Fault in DAP access
failed to use debug bus when CPU is stalled - Nn(05). Wire ACK Fault in DAP access
Debug bus check after stop (MemAP 0x84770001) FAILS - Nn(05). Wire ACK Fault in DAP access
Failed on connect: Ep(01). Target marked as not debuggable.
Connected&Reset. Was: NotConnected. DpID: 6BA02477. CpuID: 00000D21. Info: <None>
Last stub error 0: OK
Last sticky error: 0x10 POWER AIndex: 0
Debug bus selected: MemAp 0
DAP Speed test unexecuted or failed
Debug protocol: SWD. RTCK: Disabled. Vector catch: Enabled.
error closing down debug session - Nn(05). Wire ACK Fault in DAP access

Re: Failed on connect: Ep(01). Target marked as not debuggable.

diego_charles — Fri, 18 Dec 2020 18:21:41 GMT

Hi @VictorDiaconu

I hope you are doing well!

So, If you try to trigger the mass erase once again with J10 installed or releasing ISP button after reset the process fails again?

From my experience, you can set the MCU into ISP mode ( by installing J10 when the board or releasing ISP button after refer ) and then trigger a mass erase. However you do not need to set the MCU into ISP mode to trigger a mass erase. Having the MCU into ISP mode, helps to recover debugger connection in some cases, see Regainning debug access to target MCU. After the mass erase was succesful, you may want to uninstall the J10 to trigger a debug session.

Also, to recover the MCU , we can try by using Flash magic Tool , J-link commander or even an external debug probe, if required we can check them.

Regards,

Diego

Re: Failed on connect: Ep(01). Target marked as not debuggable.

VictorDiaconu — Mon, 04 Jan 2021 06:30:46 GMT

Hi diego_charles,

Thank you for your reply.

Yes, I done the mass erase many time, but this did not help me. After that I remember that early I have change the Debug Configuration Settings. And I setted them all to default. And now it work very well.

It is stranger for me, erally with another Debug Configuration i can debug the Code. And after a short way to erase the chip (three step to erase the chip) I must first to set the Debug Configuration back to make all work properly.

Finally Debug Configuration are not important for me. More important that I can debug again.

Thank you for your help diego_charles.

Best regards

Victor Diaconu

Re: Failed on connect: Ep(01). Target marked as not debuggable.

diego_charles — Mon, 04 Jan 2021 15:43:53 GMT

Hi @VictorDiaconu

Thank you for your reply as well,

Happy new year,

Diego.

LPC MicrocontrollersのトピックRe: Failed on connect: Ep(01). Target marked as not debuggable.

Failed on connect: Ep(01). Target marked as not debuggable.

Re: Failed on connect: Ep(01). Target marked as not debuggable.

Re: Failed on connect: Ep(01). Target marked as not debuggable.

Re: Failed on connect: Ep(01). Target marked as not debuggable.