cannot debug device anymore

mhanuel — Sun, 01 Mar 2020 12:43:46 GMT

Hi,

I was using the EVK, nothing fancy and suddenly I cannot connect more using the DAP interface. I have tried to connect using my J-Link Plus and same thing. Here is the output log of J-Link

Could not connect to target.
SEGGER J-Link GDB Server V6.62c Command Line Version
JLinkARM.dll V6.62c (DLL compiled Feb 21 2020 17:43:19)
Command line: -nosilent -swoport 2332 -select USB -telnetport 2333 -singlerun -endian little -noir -speed auto -port 2331 -vd -device MIMXRT1011DAE5A -if SWD -halt -reportuseraction
-----GDB Server start settings-----
GDBInit file: none
GDB Server Listening port: 2331
SWO raw output listening port: 2332
Terminal I/O port: 2333
Accept remote connection: localhost only
Generate logfile: off
Verify download: on
Init regs on start: off
Silent mode: off
Single run mode: on
Target connection timeout: 0 ms
------J-Link related settings------
J-Link Host interface: USB
J-Link script: none
J-Link settings file: none
------Target related settings------
Target device: MIMXRT1011DAE5A
Target interface: SWD
Target interface speed: auto
Target endian: little
Connecting to J-Link...
$$UserActionStart$$: Firmware update
Updating firmware: J-Link V10 compiled Jan 7 2020 16:51:47
Replacing firmware: J-Link V10 compiled Oct 22 2019 16:28:15
Waiting for new firmware to boot
New firmware booted successfully
$$UserActionEnd$$: Firmware update
J-Link is connected.
Device "MIMXRT1011DAE5A" selected.
Firmware: J-Link V10 compiled Jan 7 2020 16:51:47
Hardware: V10.10
S/N: 600104418
Feature(s): RDI, FlashBP, FlashDL, JFlash, GDB
Checking target voltage...
Target voltage: 3.33 V
Listening on TCP/IP port 2331
Connecting to target...
Found SW-DP with ID 0x0BD11477
DPIDR: 0x0BD11477
Scanning AP map to find all available APs
AP[1]: Stopped AP scan as end of AP map has been reached
AP[0]: AHB-AP (IDR: 0x04770041)
Iterating through AP map to find AHB-AP to use
AP[0]: Core found
AP[0]: AHB-AP ROM base: 0xE00FD000
Found SW-DP with ID 0x0BD11477
Failed to power up DAP
ERROR: DAP error while reading AIRCR.
ERROR: Could not connect to target.
Target connection failed. GDBServer will be closed...Restoring target state and closing J-Link connection...
Shutting down...
Could not connect to target.

Does someone know the possible root cause of this?

Will appreciate any response,

Re: cannot debug device anymore

lucas_cao — Mon, 02 Mar 2020 08:18:28 GMT

Can you find RT1010 disk?

Re: cannot debug device anymore

alex_rodriguez — Mon, 02 Mar 2020 15:25:47 GMT

It may that your code is causing it to go into a reset loop. Try setting it to Serial Downloader mode (dip SW8 to 0001), erasing the flash (or even just downloading an application you know works like the hello world demo), and then setting back to internal boot (dip sw8 0010).

Erasing flash using MCUXpresso:

-Alex

Embedded Software and Tools ClinicのトピックRe: cannot debug device anymore

cannot debug device anymore

Re: cannot debug device anymore

Re: cannot debug device anymore