topic Re: RT1020 does not debug/ does not connect | 15: target error from Read Memory in i.MX RT Crossover MCUs

RT1020 does not debug/ does not connect | 15: target error from Read Memory

VolcanicCheese — Tue, 27 Jul 2021 02:34:55 GMT

I was trying to implement the example powermode driver to my project. When attempting to change the powermode, the dev board hard faulted. Now, the dev board refuses program. Another board does not even connect to the computer anymore. It shows this message on the debug console. I believe the problem comes from changing the clock frequency when there is sdram code implemented. I was wondering how I could make the board program again and how to potentially avoid this problem again. Thank you!

MCUXpresso IDE RedlinkMulti Driver v11.3 (Mar 30 2021 16:50:12 - crt_emu_cm_redlink build 18)
Found chip XML file in C:/Users/jaeye/Documents/MCUXpressoIDE_11.3.1_5262/workspace/evkmimxrt1020_freertos_hello/Debug\MIMXRT1021xxxxx.xml
Reconnected to existing LinkServer process.
============= SCRIPT: RT1020_connect.scp =============
RT1020 Connect Script
DpID = 0BD11477
APID = 0x04770041
Disabling MPU
Configure FlexRAM for 128KB OC RAM, 64KB I-TCM, 64KB D-TCM
Finished
============= END SCRIPT =============================
Probe Firmware: DAPLink CMSIS-DAP (ARM)
Serial Number: 0226000047784e4500299003d917000fe561000097969900
VID:PID: 0D28:0204
USB Path: \\?\hid#vid_0d28&pid_0204&mi_03#7&1aee426a&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
Using memory from core 0 after searching for a good core
debug interface type = CoreSight DP (DAP DP ID 0BD11477) over SWD TAP 0
processor type = Cortex-M7 (CPU ID 00000C27) on DAP AP 0
number of h/w breakpoints = 8
number of flash patches = 0
number of h/w watchpoints = 4
Probe(0): Connected&Reset. DpID: 0BD11477. CpuID: 00000C27. Info: <None>
Debug protocol: SWD. RTCK: Disabled. Vector catch: Disabled.
Content of CoreSight Debug ROM(s):
RBASE E00FD000: CID B105100D PID 000008E88C ROM (type 0x1)
ROM 1 E00FE000: CID B105100D PID 04000BB4C8 ROM (type 0x1)
ROM 2 E00FF000: CID B105100D PID 04000BB4C7 ROM (type 0x1)
ROM 3 E000E000: CID B105E00D PID 04000BB00C Gen SCS (type 0x0)
ROM 3 E0001000: CID B105E00D PID 04000BB002 Gen DWT (type 0x0)
ROM 3 E0002000: CID B105E00D PID 04000BB00E Gen (type 0x0)
ROM 3 E0000000: CID B105E00D PID 04000BB001 Gen ITM (type 0x0)
ROM 2 E0041000: CID B105900D PID 04001BB975 CSt ARM ETMv4.0 type 0x13 Trace Source - Core
ROM 2 E0042000: CID B105900D PID 04004BB906 CSt type 0x14 Debug Control - Trigger, e.g. ECT
ROM 1 E0040000: CID B105900D PID 04000BB9A9 CSt type 0x11 Trace Sink - TPIU
ROM 1 E0043000: CID B105F00D PID 04001BB101 Sys (type 0x0)
NXP: MIMXRT1021xxxxx
DAP stride is 1024 bytes (256 words)
XML Error - no license-type XML file 'crt_common.xme' on path.
note - part information contained no product license-type data
Inspected v.2 External Flash Device on SPI MIMXRT1020-EVK_IS25LP064.cfx
Image 'MIMXRT1020-EVK_IS25LP064A Mar 22 2021 08:15:06'
Connected: was_reset=false. was_stopped=true
Awaiting telnet connection to port 3331 ...
GDB nonstop mode disabled (using allstop mode)
After error Nn(05). Wire ACK Wait in DAP access -
Failed to read address register in DAP - Nn(05). Wire ACK Wait in DAP access
Target error from Read Memory: Em(17). Debug port inaccessible after access at location 0x60006A60
FreeRTOS stack backtrace is enabled
Opening flash driver MIMXRT1020-EVK_IS25LP064.cfx
Target error from Commit Flash write: Nn(05). Wire ACK Wait in DAP access
GDB stub (crt_emu_cm_redlink) terminating - GDB protocol problem: Pipe has been closed by GDB.
state - running or following reset request - re-read of state failed - rc Nn(05). Wire ACK Wait in DAP access

Re: RT1020 does not debug/ does not connect | 15: target error from Read Memory

jeremyzhou — Tue, 27 Jul 2021 06:40:37 GMT

Hi,
Thank you for your interest in NXP Semiconductor products and for the opportunity to serve you.
Firstly, I'd like to know which board you tested, next, please follow the below steps to restore the board.
1) Configure the board to Serial Downloader mode.
2) Power on the board, debug the demo project.
3) After that, power off and recover the board to the original mode, then power on again.
4) Give a debug again.
Have a great day,
TIC

-------------------------------------------------------------------------------
Note:
- If this post answers your question, please click the "Mark Correct" button. Thank you!

- We are following threads for 7 weeks after the last post, later replies are ignored
Please open a new thread and refer to the closed one, if you have a related question at a later point in time.
-------------------------------------------------------------------------------

Re: RT1020 does not debug/ does not connect | 15: target error from Read Memory

VolcanicCheese — Tue, 27 Jul 2021 13:25:17 GMT

I am using the MIMXRT1020-EVK board. How do I configure the board to Serial Downloader mode? Also, would this solution work on board that does not seem to power-up when connecting with a micro USB. Thank you! I appreciate all the help given.

Re: RT1020 does not debug/ does not connect | 15: target error from Read Memory

jeremyzhou — Wed, 28 Jul 2021 02:28:03 GMT

Hi,
Thanks for your reply.
1) How do I configure the board to Serial Downloader mode?
-- Please refer to the MIMXRT1020 EVK Board Hardware User's Guide.
2) would this solution work on board that does not seem to power-up when connecting with a micro USB.
-- Whether you mean the board can't power-up yet now, if yes, you'd better check the power supply setting of the MIMXRT1020 EVK Board and the above guide also introduce the information.
Have a great day,
TIC

-------------------------------------------------------------------------------
Note:
- If this post answers your question, please click the "Mark Correct" button. Thank you!