<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: iMXRT 1020 problem with flash memory in i.MX RT Crossover MCUs</title>
    <link>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/iMXRT-1020-problem-with-flash-memory/m-p/2345770#M36459</link>
    <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/166213"&gt;@miroslavmartine&lt;/a&gt;,&lt;/P&gt;
&lt;P&gt;If you are still experiencing this issue, please follow the steps described on the following knowledge base article:&amp;nbsp;&lt;A href="https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs-Knowledge/RT-board-recovery-for-debugger-connect-issues/ta-p/1635260" target="_blank"&gt;RT board recovery for debugger connect issues&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;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.&lt;/P&gt;
&lt;P&gt;BR,&lt;BR /&gt;Edwin.&lt;/P&gt;</description>
    <pubDate>Mon, 06 Apr 2026 19:19:44 GMT</pubDate>
    <dc:creator>EdwinHz</dc:creator>
    <dc:date>2026-04-06T19:19:44Z</dc:date>
    <item>
      <title>iMXRT 1020 problem with flash memory</title>
      <link>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/iMXRT-1020-problem-with-flash-memory/m-p/2302438#M36101</link>
      <description>&lt;P&gt;Hi everybody,&lt;/P&gt;&lt;P&gt;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:&lt;/P&gt;&lt;P&gt;&lt;FONT size="2"&gt;&lt;EM&gt;&lt;SPAN&gt;File 'evkmimxrt1020_pit.axf' load failure: Ef(11). No flash configured at the specified address.&amp;nbsp;&lt;/SPAN&gt;&lt;/EM&gt;&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Yesterday I tried to flash a .bin file (built result from NuttX RTOS) into MCU and after that this strange behavior started...&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Could someone give me an advice to solve it? &lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;-------------------------------------------------------------&lt;/P&gt;&lt;P&gt;Whole listing:&lt;/P&gt;&lt;DIV&gt;&lt;DIV&gt;&lt;P&gt;&lt;EM&gt;Executing flash operation 'Program' (Program file into flash: evkmimxrt1020_pit.axf) - Wed Jan 28 21:48:35 CET 2026&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;Checking MCU info...&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;Scanning for targets...&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;Executing flash action...&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;LinkServer RedlinkMulti Driver v25.6 (Jun 26 2025 19:34:05 - crt_emu_cm_redlink.exe build 1017)&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;( 0) Reading remote configuration&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;Wc(03). No cache support.&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;Found chip XML file in C:/NXPWorkspace/evkmimxrt1020_pit/Debug\MIMXRT1021xxxxx.xml&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;( 5) Remote configuration complete&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;Reconnected to existing LinkServer process.&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;============= SCRIPT: RT1020_connect.scp =============&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;RT1020 Connect Script&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;DpID = 0BD11477&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;APID = 0x04770041&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;Disabling MPU&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;Configure FlexRAM for 128KB OC RAM, 64KB I-TCM, 64KB D-TCM&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;Finished&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;============= END SCRIPT =============================&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;Probe Firmware: CMSIS-DAP (ARM)&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;Serial Number: 0226000016120f1800000000000000000000000097969905&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;VID:PID: 0D28:0204&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;USB Path: \\?\hid#vid_0d28&amp;amp;pid_0204&amp;amp;mi_03#8&amp;amp;153f1c76&amp;amp;0&amp;amp;0000#{4d1e55b2-f16f-11cf-88cb-001111000030}&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;Using memory from core 0 after searching for a good core&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;( 30) Emulator Connected&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;( 40) Debug Halt&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;( 50) CPU ID&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;debug interface type = CoreSight DP (DAP DP ID 0BD11477) over SWD TAP 0&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;processor type = Cortex-M7 (CPU ID 00000C27) on DAP AP 0&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;number of h/w breakpoints = 8&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;number of flash patches = 0&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;number of h/w watchpoints = 4&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;Probe(0): Connected&amp;amp;Reset. DpID: 0BD11477. CpuID: 00000C27. Info: &amp;lt;None&amp;gt;&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;Debug protocol: SWD. RTCK: Disabled. Vector catch: Disabled.&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;Content of CoreSight Debug ROM(s):&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;RBASE E00FD000: CID B105100D PID 000008E88C ROM (type 0x1)&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;ROM 1 E00FE000: CID B105100D PID 04000BB4C8 ROM (type 0x1)&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;ROM 2 E00FF000: CID B105100D PID 04000BB4C7 ROM (type 0x1)&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;ROM 3 E000E000: CID B105E00D PID 04000BB00C Gen SCS (type 0x0)&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;ROM 3 E0001000: CID B105E00D PID 04000BB002 Gen DWT (type 0x0)&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;ROM 3 E0002000: CID B105E00D PID 04000BB00E Gen (type 0x0)&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;ROM 3 E0000000: CID B105E00D PID 04000BB001 Gen ITM (type 0x0)&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;ROM 2 E0041000: CID B105900D PID 04001BB975 CSt ARM ETMv4.0 type 0x13 Trace Source - Core&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;ROM 2 E0042000: CID B105900D PID 04004BB906 CSt type 0x14 Debug Control - Trigger, e.g. ECT&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;ROM 1 E0040000: CID B105900D PID 04000BB9A9 CSt type 0x11 Trace Sink - TPIU&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;ROM 1 E0043000: CID B105F00D PID 04001BB101 Sys (type 0x0)&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;NXP: MIMXRT1021xxxxx&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;failed to find a target memory area to use to test the Debug Access Port&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;DAP stride is 1024 bytes (256 words)&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;( 65) Chip Setup Complete&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;Connected: was_reset=false. was_stopped=true&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;( 70) License Check Complete&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;File 'evkmimxrt1020_pit.axf' load failure: Ef(11). No flash configured at the specified address.&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;(100) Target Operation Failed&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;Unable to perform operation!&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;Command failed with exit code 1&lt;/EM&gt;&lt;/P&gt;&lt;DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;</description>
      <pubDate>Wed, 28 Jan 2026 21:08:07 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/iMXRT-1020-problem-with-flash-memory/m-p/2302438#M36101</guid>
      <dc:creator>miroslavmartine</dc:creator>
      <dc:date>2026-01-28T21:08:07Z</dc:date>
    </item>
    <item>
      <title>Re: iMXRT 1020 problem with flash memory</title>
      <link>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/iMXRT-1020-problem-with-flash-memory/m-p/2302695#M36106</link>
      <description>&lt;P&gt;I have already done small progress - with help of this amazing article&amp;nbsp;&lt;A href="https://mcuoneclipse.com/2019/01/02/regaining-debug-access-of-nxp-i-mx-rt1064-evk-executing-wfi/" target="_self"&gt;https://mcuoneclipse.com/2019/01/02/regaining-debug-access-of-nxp-i-mx-rt1064-evk-executing-wfi/&lt;/A&gt;&amp;nbsp;I managed to erase external flash. However, if I want to debug or upload FW, I get following error:&lt;/P&gt;&lt;LI-SPOILER&gt;&lt;DIV&gt;&lt;DIV&gt;&lt;P&gt;&lt;SPAN&gt;Failed on connect: Ee(42). Could not connect to core.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;No connection to chip's debug port&lt;/SPAN&gt;&lt;/P&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/LI-SPOILER&gt;&lt;P&gt;It seems that SWD is out of work at the moment, but how to fix it?&lt;/P&gt;</description>
      <pubDate>Thu, 29 Jan 2026 08:22:10 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/iMXRT-1020-problem-with-flash-memory/m-p/2302695#M36106</guid>
      <dc:creator>miroslavmartine</dc:creator>
      <dc:date>2026-01-29T08:22:10Z</dc:date>
    </item>
    <item>
      <title>Re: iMXRT 1020 problem with flash memory</title>
      <link>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/iMXRT-1020-problem-with-flash-memory/m-p/2345770#M36459</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/166213"&gt;@miroslavmartine&lt;/a&gt;,&lt;/P&gt;
&lt;P&gt;If you are still experiencing this issue, please follow the steps described on the following knowledge base article:&amp;nbsp;&lt;A href="https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs-Knowledge/RT-board-recovery-for-debugger-connect-issues/ta-p/1635260" target="_blank"&gt;RT board recovery for debugger connect issues&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;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.&lt;/P&gt;
&lt;P&gt;BR,&lt;BR /&gt;Edwin.&lt;/P&gt;</description>
      <pubDate>Mon, 06 Apr 2026 19:19:44 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/iMXRT-1020-problem-with-flash-memory/m-p/2345770#M36459</guid>
      <dc:creator>EdwinHz</dc:creator>
      <dc:date>2026-04-06T19:19:44Z</dc:date>
    </item>
  </channel>
</rss>

