AnsweredAssumed Answered

the periph_rtc example for lpc1549 somehow disabled the debug probe.How can I restore it?the periph_rtc example for lpc1549 somehow disabled the debug probe.How can I restore it?

Question asked by Marco Paglia on Apr 24, 2018
Latest reply on Apr 24, 2018 by LPCX support

The periph_rtc example for lpc1549 from the LPCOpen libraries somehow disabled the debug probe.How can I restore it? This is the console output:

 

MCUXpresso RedlinkMulti Driver v10.1 (Dec 19 2017 16:58:35 - crt_emu_cm_redlink build 390)
Reconnected to existing redlink server (PID 4294967295)
Connecting to probe 1 core 0 (server PID unknown) gave 'OK'
============= SCRIPT: LPC15RunBootRomConnect.scp =============
DpID = 2BA01477
Wire Ack Fault - target connected?
Wire Ack Fault - target connected?
Wire Ack Fault - target connected?
Halt on reset vector catch
Wire Ack Fault - target connected?
Wire Ack Fault - target connected?
Wire Ack Fault - target connected?
Wire Ack Fault - target connected?
Halt on watchpoint write of ROMWSCTRL register
Wire Ack Fault - target connected?
Wire Ack Fault - target connected?
============= END SCRIPT =====================================
Probe Firmware: LPC-LINK2 CMSIS-DAP V5.183 (NXP Semiconductors)
Serial Number:  KRAWAQFR
VID:PID:  1FC9:0090
USB Path: \\?\hid#vid_1fc9&pid_0090&mi_00#8&101ee3f8&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
connection failed - Ee(FF). Redlink interface error 255... Retrying
Failed on connect: Ee(FF). Redlink interface error 255.
Connected&Reset. Was: NotConnected. DpID: 00000000. CpuID: 00000000. Info: <None>
Last stub error 0: OK
Last sticky error: 0x0 AIndex: 0
Debug bus selected: MemAp 0
DAP Speed test unexecuted or failed
Debug protocol: SWD. RTCK: Disabled. Vector catch: Enabled.
(100) Target Connection Failed
error closing down debug session - Ee(FF). Redlink interface error 255.

Outcomes