iMXRT 1020 problem with flash memory

[miroslavmartine]

Hi everybody,

I have got the RT1020-EVK board and if I would like to flash it (via GUI Flash tool or debugger), following error message appears:

File 'evkmimxrt1020_pit.axf' load failure: Ef(11). No flash configured at the specified address. 

Yesterday I tried to flash a .bin file (built result from NuttX RTOS) into MCU and after that this strange behavior started...

Could someone give me an advice to solve it?

-------------------------------------------------------------

Whole listing:

Executing flash operation 'Program' (Program file into flash: evkmimxrt1020_pit.axf) - Wed Jan 28 21:48:35 CET 2026

Checking MCU info...

Scanning for targets...

Executing flash action...

LinkServer RedlinkMulti Driver v25.6 (Jun 26 2025 19:34:05 - crt_emu_cm_redlink.exe build 1017)

( 0) Reading remote configuration

Wc(03). No cache support.

Found chip XML file in C:/NXPWorkspace/evkmimxrt1020_pit/Debug\MIMXRT1021xxxxx.xml

( 5) Remote configuration complete

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: CMSIS-DAP (ARM)

Serial Number: 0226000016120f1800000000000000000000000097969905

VID:PID: 0D28:0204

USB Path: \\?\hid#vid_0d28&pid_0204&mi_03#8&153f1c76&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}

Using memory from core 0 after searching for a good core

( 30) Emulator Connected

( 40) Debug Halt

( 50) CPU ID

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

failed to find a target memory area to use to test the Debug Access Port

DAP stride is 1024 bytes (256 words)

( 65) Chip Setup Complete

Connected: was_reset=false. was_stopped=true

( 70) License Check Complete

File 'evkmimxrt1020_pit.axf' load failure: Ef(11). No flash configured at the specified address.

(100) Target Operation Failed

Unable to perform operation!

Command failed with exit code 1

[miroslavmartine]

I have already done small progress - with help of this amazing article https://mcuoneclipse.com/2019/01/02/regaining-debug-access-of-nxp-i-mx-rt1064-evk-executing-wfi/ I managed to erase external flash. However, if I want to debug or upload FW, I get following error:

破坏者

Failed on connect: Ee(42). Could not connect to core.

No connection to chip's debug port

It seems that SWD is out of work at the moment, but how to fix it?

[EdwinHz]

Hi @miroslavmartine,

If you are still experiencing this issue, please follow the steps described on the following knowledge base article: RT board recovery for debugger connect issues

It is similar to what you have already done, but it's an updated and more complete version that should allow you to regain debug access to your board.

BR,
Edwin.