Flash verification error at 0x08000000 in FRDM-RW612

Vamsi_Tulasi · ‎02-03-2025

Hi,
I am unable to flash a program into a new frdm-rw612 board using the MCUXpresso for VS code - Version: 24.12.71.
The error message and the console output are attached below when I tried to flash the example program[frdmrw612_hello_world_virtual_com] imported from the SDK repository using J-link/SEGGER flash programmer - Version: 8.12a tool's CLI and GUI.

I have tried mass erase of the flash banks, updated the MCU-link firmware - Version: 3.153 as per the user manual, flashed examples from different SDK versions (24.12.00 and 2.16.000) nothing resolved the issue.

Error:
J-Link: Flash download: Bank 0 @ 0x08000000: 1 range affected (65536 bytes)
J-Link: Flash download: Total: 1.141s (Prepare: 0.292s, Compare: 0.123s, Erase: 0.002s, Program: 0.483s, Verify: 0.105s, Restore: 0.133s)
J-Link: Flash download: Program speed: 132 KB/s
****** Error: Verification failed @ address 0x08000000
Error while programming flash: Verify failed.

Script processing completed.

Complete Console Output:

[2025-02-03T11:46:15.871] [proc] [info] Cmd: C:\PEMicro\gdbserver\pegdbserver_console.exe -showhardware
[2025-02-03T11:46:15.882] [proc] [info] Cmd: C:\NXP\LinkServer_24.12.21\LinkServer.exe probes --json
[2025-02-03T11:46:15.895] [proc] [info] Cmd: C":\Program Files\SEGGER\JLink_V812a\JLinkGDBServerCL.exe" -listprobes USB
[2025-02-03T11:46:18.997] [proc] [info] Cmd: C":\Program Files\SEGGER\JLink_V812a\JLink.exe" -if SWD -speed auto -commanderscript e:\nxp_projects\frdmrw612_lpc_gpio_led_output\script.jlink -device RW612 -SelectEmuBySN 1062798820
[2025-02-03T11:46:22.403] [proc] [error] C:\Program Files\SEGGER\JLink_V812a\JLink.exe exited with code 1
[2025-02-03T11:46:22.403] [proc] [error] SEGGER J-Link Commander V8.12a (Compiled Jan 9 2025 14:39:11)
DLL version V8.12a, compiled Jan 9 2025 14:38:21

J-Link Command File read successfully.
Processing script file...
J-Link>ExitOnError 1
J-Link Commander will now exit on Error
J-Link>r
J-Link connection not established yet but required for command.
Connecting to J-Link via USB...O.K.
Firmware: J-Link MCU-Link V1 compiled Oct 9 2024 11:01:41
Hardware version: V1.00
J-Link uptime (since boot): 0d 00h 42m 54s
S/N: 1062798820
USB speed mode: High speed (480 MBit/s)
VTref=3.300V
Target connection not established yet but required for command.
Device "RW612" selected.

Connecting to target via SWD
InitTarget() start
SWD selected. Executing JTAG -> SWD switching sequence.
DAP initialized successfully.
DMAP_REG_ID: DM-AP IDCODE detected: 0x002A0000
DHCSR: 0x05180000
InitTarget() end - Took 9.04ms
Found SW-DP with ID 0x6BA02477
DPIDR: 0x6BA02477
CoreSight SoC-400 or earlier
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: 0x84770001, ADDR: 0x00000000)
Iterating through AP map to find AHB-AP to use
AP[0]: Core found
AP[0]: AHB-AP ROM base: 0xE00FF000
CPUID register: 0x410FD214. Implementer code: 0x41 (ARM)
Feature set: Mainline
Cache: No cache
Found Cortex-M33 r0p4, Little endian.
FPUnit: 8 code (BP) slots and 0 literal slots
Security extension: implemented
Secure debug: enabled
CoreSight components:
ROMTbl[0] @ E00FF000
[0][0]: E000E000 CID B105900D PID 000BBD21 DEVARCH 47702A04 DEVTYPE 00 Cortex-M33
[0][1]: E0001000 CID B105900D PID 000BBD21 DEVARCH 47701A02 DEVTYPE 00 DWT
[0][2]: E0002000 CID B105900D PID 000BBD21 DEVARCH 47701A03 DEVTYPE 00 FPB
[0][3]: E0000000 CID B105900D PID 000BBD21 DEVARCH 47701A01 DEVTYPE 43 ITM
[0][5]: E0041000 CID B105900D PID 002BBD21 DEVARCH 47724A13 DEVTYPE 13 ETM
[0][6]: E0042000 CID B105900D PID 000BBD21 DEVARCH 47701A14 DEVTYPE 14 CSS600-CTI
Memory zones:
Zone: "Default" Description: Default access mode
Cortex-M33 identified.
Reset delay: 0 ms
ResetTarget() start
Reset via SYSRESETREQ and reset pin + halt after bootloader
ROM entered ISP command handling loop. Re-enable the debug access.
MSPLIM cleared
ResetTarget() end - Took 119ms
Device specific reset executed.
J-Link>loadfile e:\nxp_projects\frdmrw612_hello_world_virtual_com_new\armgcc\debug\hello_world_virtual_com.hex
'loadfile': Performing implicit reset & halt of MCU.
ResetTarget() start
Reset via SYSRESETREQ and reset pin + halt after bootloader
ROM entered ISP command handling loop. Re-enable the debug access.
MSPLIM cleared
ResetTarget() end - Took 118ms
Device specific reset executed.
Downloading file [e:\nxp_projects\frdmrw612_hello_world_virtual_com_new\armgcc\debug\hello_world_virtual_com.hex]...
J-Link: Flash download: Bank 0 @ 0x08000000: 1 range affected (65536 bytes)
J-Link: Flash download: Total: 1.141s (Prepare: 0.292s, Compare: 0.123s, Erase: 0.002s, Program: 0.483s, Verify: 0.105s, Restore: 0.133s)
J-Link: Flash download: Program speed: 132 KB/s

****** Error: Verification failed @ address 0x08000000
Error while programming flash: Verify failed.

Script processing completed.

Attached the ports shown in the device manager:

Vamsi_Tulasi · ‎02-03-2025

I have updated the mcu-link firmware to cmsis-dap(version - 3.153) and tried flashing the binary file using linkserver(version - 24.12.21).
But still not able to flash the program.

Flash region summary:
Flash region summary
--region "memoryInstance_1,0x8000000,0x800000,RW61X_FlexSPI_A_SFDP_QSPI.cfx"
--region "memoryInstance_2,0x18000000,0x800000,RW61X_FlexSPI_A_SFDP_QSPI_S.cfx"
--region-default "memoryInstance_1"

Flashing error(without erase before flashing):
Nt: Loading 'tmp2txa86si.elf' ELF 0x00000000 len 0x816C
Ed:05: File 'tmp2txa86si.elf' load failure: Ef(11). No flash configured at the specified address.
Pc: (100) Target Operation Failed
CRITICAL: Critical error
ERRMSG: Exception: Flash operation exited with code 1

Flashing error(Erase before flashing):
Pb: 1 of 1 ( 0) Writing sectors 0-8 at 0x08000000 with 33132 bytes
Ps: ( 0) at 08000000: 0 bytes - 0/33132
Ec: op ProgramPage (0x8000000, 0x20004478, 0x4000) status 0x1 - driver reported driver error - EXTSPI driver rc -1 (0xFFFFFFFF)

Nc: Sectors written: 9, unchanged: 0, total: 9
Nc: Closing flash driver RW61X_FlexSPI_A_SFDP_QSPI.cfx
Pb: (100) Writing Flash ended with an error.
Ed:05: File 'lpc_gpio_led_output.elf' load failure: Ef(49): Flash driver operation gave error.
Pc: (100) Target Operation Failed
CRITICAL: Critical error
ERRMSG: Exception: Flash operation exited with code 1

Full console output of the above three operations is attached below:

C:\NXP\LinkServer_24.12.21>LinkServer probes
# Description Serial Device Board
--- ----------------------------------------- ------------- -------- -------
1 MCU-LINK on-board (r0E7) CMSIS-DAP V3.153 2RMBUEB5TPN5S

C:\NXP\LinkServer_24.12.21>LinkServer flash --probe #1 rw612:frdm-rw612 regions
INFO: Exact match for rw612:frdm-rw612 found
INFO: Selected device RW612:FRDM-RW612
INFO: Getting available probes
INFO: Selecting probe by index
INFO: Selected probe #1 2RMBUEB5TPN5S (MCU-LINK on-board (r0E7) CMSIS-DAP V3.153)
INFO: MCU-Link firmware update `check`: Probe ([2RMBUEB5TPN5S] [MCU-LINK on-board (r0E7) CMSIS-DAP V3.153]) is already running the same firmware version as the included firmware version [3.153]
Firmware update `check`: not required - forced update can be performed using: `LinkServer probe #1 update forced`
Ns: LinkServer RedlinkMulti Driver v24.12 (Dec 18 2024 18:34:07 - crt_emu_cm_redlink.exe build 869)
Pc: ( 0) Reading remote configuration
Wc(03). No cache support.
Nc: Found generic directory XML file in C:\Users\TULASI~1.K\AppData\Local\Temp\tmpgcaba79r\crt_directory.xml
Pc: ( 5) Remote configuration complete
Nc: Reconnected to existing LinkServer process.
Nc: not running connect script in attach mode
Nc: Probe Firmware: MCU-LINK on-board (r0E7) CMSIS-DAP V3.153 (NXP Semiconductors)
Nc: Serial Number: 2RMBUEB5TPN5S
Nc: VID:PID: 1FC9:0143
Nc: USB Path: 0001:000e:00
Nc: Using memory from core 0 after searching for a good core
Pc: ( 30) Emulator Connected
Nc: processor is in secure mode
Pc: ( 40) No Halt on Attach
Pc: ( 50) CPU ID
Nc: debug interface type = CoreSight DP (DAP DP ID 6BA02477) over SWD TAP 0
Nc: processor type = Cortex-M33 (CPU ID 00000D21) on DAP AP 0
Nc: number of h/w breakpoints = 8
Nc: number of flash patches = 0
Nc: number of h/w watchpoints = 4
Nc: Probe(0): Connected&Reset. DpID: 6BA02477. CpuID: 00000D21. Info: <None>
Nc: Debug protocol: SWD. RTCK: Disabled. Vector catch: Disabled.
Ns: Content of CoreSight Debug ROM(s):
Nc: RBASE E00FF000: CID B105100D PID 04000BB4C9 ROM (type 0x1)
Nc: ROM 1 E000E000: CID B105900D PID 04000BBD21 CSt ARM ARMv8-M type 0x0 Misc - Undefined
Nc: ROM 1 E0001000: CID B105900D PID 04000BBD21 CSt ARM DWTv2 type 0x0 Misc - Undefined
Nc: ROM 1 E0002000: CID B105900D PID 04000BBD21 CSt ARM FPBv2 type 0x0 Misc - Undefined
Nc: ROM 1 E0000000: CID B105900D PID 04000BBD21 CSt ARM ITMv2 type 0x43 Trace Source - Bus
Nc: ROM 1 E0041000: CID B105900D PID 04002BBD21 CSt ARM ETMv4.0 type 0x13 Trace Source - Core
Nc: ROM 1 E0042000: CID B105900D PID 04000BBD21 CSt ARM CTIv2 type 0x14 Debug Control - Trigger, e.g. ECT
Nc: NXP: RW612
Nc: DAP stride is 1024 bytes (256 words)
Nc: Inspected v.2 External Flash Device on SPI RW61X_FlexSPI_A_SFDP_QSPI.cfx
Nc: Image 'RW61X_FlexSPI_A_SFDP_QSPI Flash Dec 18 2024 17:24:32'
Nc: Can't query uninitialized dynamic flash driver in attach mode - assuming base 0x8000000 len 0x800000
Nc: Inspected v.2 External Flash Device on SPI RW61X_FlexSPI_A_SFDP_QSPI_S.cfx
Nc: Image 'RW61X_FlexSPI_A_SFDP_QSPI Flash Dec 18 2024 17:24:03'
Nc: Can't query uninitialized dynamic flash driver in attach mode - assuming base 0x18000000 len 0x800000
Pc: ( 65) Chip Setup Complete
Pc: ( 70) License Check Complete
Flash region summary
--region "memoryInstance_1,0x8000000,0x800000,RW61X_FlexSPI_A_SFDP_QSPI.cfx"
--region "memoryInstance_2,0x18000000,0x800000,RW61X_FlexSPI_A_SFDP_QSPI_S.cfx"
--region-default "memoryInstance_1"

C:\NXP\LinkServer_24.12.21>LinkServer flash --probe #1 rw612:frdm-rw612 load E:\nxp_projects\frdmrw612_lpc_gpio_led_output\armgcc\debug\lpc_gpio_led_output.hex
INFO: Exact match for rw612:frdm-rw612 found
INFO: Selected device RW612:FRDM-RW612
INFO: Getting available probes
INFO: Selecting probe by index
INFO: Selected probe #1 2RMBUEB5TPN5S (MCU-LINK on-board (r0E7) CMSIS-DAP V3.153)
INFO: MCU-Link firmware update `check`: Probe ([2RMBUEB5TPN5S] [MCU-LINK on-board (r0E7) CMSIS-DAP V3.153]) is already running the same firmware version as the included firmware version [3.153]
Firmware update `check`: not required - forced update can be performed using: `LinkServer probe #1 update forced`
Ns: LinkServer RedlinkMulti Driver v24.12 (Dec 18 2024 18:34:07 - crt_emu_cm_redlink.exe build 869)
Pc: ( 0) Reading remote configuration
Wc(03). No cache support.
Nc: Found generic directory XML file in C:\Users\TULASI~1.K\AppData\Local\Temp\tmpo69mooki\crt_directory.xml
Pc: ( 5) Remote configuration complete
Nc: Reconnected to existing LinkServer process.
Wc: ============= SCRIPT: RW61x_connect.scp =============
Wc: RW61x Connect Script
Wc: Connecting to Probe Index = 1
Wc: This probe = 1
Wc: This TAP = 0
Wc: This core = 0
Wc: DpID = 6BA02477
Wc: ============= END SCRIPT ============================
Nc: Probe Firmware: MCU-LINK on-board (r0E7) CMSIS-DAP V3.153 (NXP Semiconductors)
Nc: Serial Number: 2RMBUEB5TPN5S
Nc: VID:PID: 1FC9:0143
Nc: USB Path: 0001:000e:00
Nc: Using memory from core 0 after searching for a good core
Pc: ( 30) Emulator Connected
Nc: processor is in secure mode
Pc: ( 40) Debug Halt
Pc: ( 50) CPU ID
Nc: debug interface type = CoreSight DP (DAP DP ID 6BA02477) over SWD TAP 0
Nc: processor type = Cortex-M33 (CPU ID 00000D21) on DAP AP 0
Nc: number of h/w breakpoints = 8
Nc: number of flash patches = 0
Nc: number of h/w watchpoints = 4
Nc: Probe(0): Connected&Reset. DpID: 6BA02477. CpuID: 00000D21. Info: <None>
Nc: Debug protocol: SWD. RTCK: Disabled. Vector catch: Disabled.
Ns: Content of CoreSight Debug ROM(s):
Nc: RBASE E00FF000: CID B105100D PID 04000BB4C9 ROM (type 0x1)
Nc: ROM 1 E000E000: CID B105900D PID 04000BBD21 CSt ARM ARMv8-M type 0x0 Misc - Undefined
Nc: ROM 1 E0001000: CID B105900D PID 04000BBD21 CSt ARM DWTv2 type 0x0 Misc - Undefined
Nc: ROM 1 E0002000: CID B105900D PID 04000BBD21 CSt ARM FPBv2 type 0x0 Misc - Undefined
Nc: ROM 1 E0000000: CID B105900D PID 04000BBD21 CSt ARM ITMv2 type 0x43 Trace Source - Bus
Nc: ROM 1 E0041000: CID B105900D PID 04002BBD21 CSt ARM ETMv4.0 type 0x13 Trace Source - Core
Nc: ROM 1 E0042000: CID B105900D PID 04000BBD21 CSt ARM CTIv2 type 0x14 Debug Control - Trigger, e.g. ECT
Nc: NXP: RW612
Nc: DAP stride is 1024 bytes (256 words)
Nc: Inspected v.2 External Flash Device on SPI RW61X_FlexSPI_A_SFDP_QSPI.cfx
Nc: Image 'RW61X_FlexSPI_A_SFDP_QSPI Flash Dec 18 2024 17:24:32'
Nc: Opening flash driver RW61X_FlexSPI_A_SFDP_QSPI.cfx
Nc: VECTRESET requested, but not supported on ARMv8-M CPUs. Using SOFTRESET instead.
Nc: Using SOFT reset to run the flash driver
Nc: Flash variant 'RW61X_FlexSPI_A_SFDP_QSPI Flash Dec 18 2024 17:24:32' detected (64MB = 16384*4K at 0x8000000)
Nc: Closing flash driver RW61X_FlexSPI_A_SFDP_QSPI.cfx
Nc: Inspected v.2 External Flash Device on SPI RW61X_FlexSPI_A_SFDP_QSPI_S.cfx
Nc: Image 'RW61X_FlexSPI_A_SFDP_QSPI Flash Dec 18 2024 17:24:03'
Nc: Opening flash driver RW61X_FlexSPI_A_SFDP_QSPI_S.cfx
Nc: VECTRESET requested, but not supported on ARMv8-M CPUs. Using SOFTRESET instead.
Nc: Using SOFT reset to run the flash driver
Nc: Flash variant 'RW61X_FlexSPI_A_SFDP_QSPI Flash Dec 18 2024 17:24:03' detected (64MB = 16384*4K at 0x18000000)
Nc: Closing flash driver RW61X_FlexSPI_A_SFDP_QSPI_S.cfx
Pc: ( 65) Chip Setup Complete
Pc: ( 70) License Check Complete
Nt: Loading 'tmp2txa86si.elf' ELF 0x00000000 len 0x816C
Ed:05: File 'tmp2txa86si.elf' load failure: Ef(11). No flash configured at the specified address.
Pc: (100) Target Operation Failed
CRITICAL: Critical error
ERRMSG: Exception: Flash operation exited with code 1

C:\NXP\LinkServer_24.12.21>LinkServer flash --probe #1 rw612:frdm-rw612 load --erase-all E:\nxp_projects\frdmrw612_lpc_gpio_led_output\armgcc\debug\lpc_gpio_led_output.elf
INFO: Exact match for rw612:frdm-rw612 found
INFO: Selected device RW612:FRDM-RW612
INFO: Getting available probes
INFO: Selecting probe by index
INFO: Selected probe #1 2RMBUEB5TPN5S (MCU-LINK on-board (r0E7) CMSIS-DAP V3.153)
INFO: MCU-Link firmware update `check`: Probe ([2RMBUEB5TPN5S] [MCU-LINK on-board (r0E7) CMSIS-DAP V3.153]) is already running the same firmware version as the included firmware version [3.153]
Firmware update `check`: not required - forced update can be performed using: `LinkServer probe #1 update forced`
Ns: LinkServer RedlinkMulti Driver v24.12 (Dec 18 2024 18:34:07 - crt_emu_cm_redlink.exe build 869)
Pc: ( 0) Reading remote configuration
Wc(03). No cache support.
Nc: Found generic directory XML file in C:\Users\TULASI~1.K\AppData\Local\Temp\tmp8j952wvg\crt_directory.xml
Pc: ( 5) Remote configuration complete
Nc: Reconnected to existing LinkServer process.
Wc: ============= SCRIPT: RW61x_connect.scp =============
Wc: RW61x Connect Script
Wc: Connecting to Probe Index = 1
Wc: This probe = 1
Wc: This TAP = 0
Wc: This core = 0
Wc: DpID = 6BA02477
Wc: ============= END SCRIPT ============================
Nc: Probe Firmware: MCU-LINK on-board (r0E7) CMSIS-DAP V3.153 (NXP Semiconductors)
Nc: Serial Number: 2RMBUEB5TPN5S
Nc: VID:PID: 1FC9:0143
Nc: USB Path: 0001:000e:00
Nc: Using memory from core 0 after searching for a good core
Pc: ( 30) Emulator Connected
Nc: processor is in secure mode
Pc: ( 40) Debug Halt
Pc: ( 50) CPU ID
Nc: debug interface type = CoreSight DP (DAP DP ID 6BA02477) over SWD TAP 0
Nc: processor type = Cortex-M33 (CPU ID 00000D21) on DAP AP 0
Nc: number of h/w breakpoints = 8
Nc: number of flash patches = 0
Nc: number of h/w watchpoints = 4
Nc: Probe(0): Connected&Reset. DpID: 6BA02477. CpuID: 00000D21. Info: <None>
Nc: Debug protocol: SWD. RTCK: Disabled. Vector catch: Disabled.
Ns: Content of CoreSight Debug ROM(s):
Nc: RBASE E00FF000: CID B105100D PID 04000BB4C9 ROM (type 0x1)
Nc: ROM 1 E000E000: CID B105900D PID 04000BBD21 CSt ARM ARMv8-M type 0x0 Misc - Undefined
Nc: ROM 1 E0001000: CID B105900D PID 04000BBD21 CSt ARM DWTv2 type 0x0 Misc - Undefined
Nc: ROM 1 E0002000: CID B105900D PID 04000BBD21 CSt ARM FPBv2 type 0x0 Misc - Undefined
Nc: ROM 1 E0000000: CID B105900D PID 04000BBD21 CSt ARM ITMv2 type 0x43 Trace Source - Bus
Nc: ROM 1 E0041000: CID B105900D PID 04002BBD21 CSt ARM ETMv4.0 type 0x13 Trace Source - Core
Nc: ROM 1 E0042000: CID B105900D PID 04000BBD21 CSt ARM CTIv2 type 0x14 Debug Control - Trigger, e.g. ECT
Nc: NXP: RW612
Nc: DAP stride is 1024 bytes (256 words)
Nc: Inspected v.2 External Flash Device on SPI RW61X_FlexSPI_A_SFDP_QSPI.cfx
Nc: Image 'RW61X_FlexSPI_A_SFDP_QSPI Flash Dec 18 2024 17:24:32'
Nc: Opening flash driver RW61X_FlexSPI_A_SFDP_QSPI.cfx
Nc: VECTRESET requested, but not supported on ARMv8-M CPUs. Using SOFTRESET instead.
Nc: Using SOFT reset to run the flash driver
Nc: Flash variant 'RW61X_FlexSPI_A_SFDP_QSPI Flash Dec 18 2024 17:24:32' detected (64MB = 16384*4K at 0x8000000)
Nc: Closing flash driver RW61X_FlexSPI_A_SFDP_QSPI.cfx
Nc: Inspected v.2 External Flash Device on SPI RW61X_FlexSPI_A_SFDP_QSPI_S.cfx
Nc: Image 'RW61X_FlexSPI_A_SFDP_QSPI Flash Dec 18 2024 17:24:03'
Nc: Opening flash driver RW61X_FlexSPI_A_SFDP_QSPI_S.cfx
Nc: VECTRESET requested, but not supported on ARMv8-M CPUs. Using SOFTRESET instead.
Nc: Using SOFT reset to run the flash driver
Nc: Flash variant 'RW61X_FlexSPI_A_SFDP_QSPI Flash Dec 18 2024 17:24:03' detected (64MB = 16384*4K at 0x18000000)
Nc: Closing flash driver RW61X_FlexSPI_A_SFDP_QSPI_S.cfx
Pc: ( 65) Chip Setup Complete
Pc: ( 70) License Check Complete
Nt: Loading 'lpc_gpio_led_output.elf' ELF 0x08000000 len 0x816C
Nc: Opening flash driver RW61X_FlexSPI_A_SFDP_QSPI.cfx
Nc: VECTRESET requested, but not supported on ARMv8-M CPUs. Using SOFTRESET instead.
Nc: Using SOFT reset to run the flash driver
Nc: Flash variant 'RW61X_FlexSPI_A_SFDP_QSPI Flash Dec 18 2024 17:24:32' detected (64MB = 16384*4K at 0x8000000)
Pb: ( 0) Mass erasing Flash
Pb: 1 of 1 ( 0) Writing sectors 0-8 at 0x08000000 with 33132 bytes
Ps: ( 0) at 08000000: 0 bytes - 0/33132
Ec: op ProgramPage (0x8000000, 0x20004478, 0x4000) status 0x1 - driver reported driver error - EXTSPI driver rc -1 (0xFFFFFFFF)

Nc: Sectors written: 9, unchanged: 0, total: 9
Nc: Closing flash driver RW61X_FlexSPI_A_SFDP_QSPI.cfx
Pb: (100) Writing Flash ended with an error.
Ed:05: File 'lpc_gpio_led_output.elf' load failure: Ef(49): Flash driver operation gave error.
Pc: (100) Target Operation Failed
CRITICAL: Critical error
ERRMSG: Exception: Flash operation exited with code 1

C:\NXP\LinkServer_24.12.21>

cristiantepus · ‎02-07-2025

Hi,

There is a similar situation in which the board (flash) might be locked in case you tried (by mistake) to write a RD-RW612-BGA board image on a FRDM-RW612 board.

There is an article how you can unlock the board in such a case: https://community.nxp.com/t5/NXP-Designs-Knowledge-Base/Unlock-FRDM-RW612-flash/ta-p/2015561

Regards,

Cristian

sofiaurueta · ‎02-06-2025

Hello,

Were you able to flash the board before? And if so, which was the last SDK example that was running on the board?

Can you help me by following the steps to the FRDM-RW612 Getting Started. Wi-Fi CLI on VS Code and let me know if the issue persists?

Best regards,

Ana Sofia

Vamsi_Tulasi · ‎02-06-2025

No, I was unable to flash the board. I have performed the steps as per the "FRDM-RW612 Getting Started. Wi-Fi CLI on VS Code - NXP Community" But still I am unable to flash the board.

Full console output:

Connecting to target via SWD

InitTarget() start

SWD selected. Executing JTAG -> SWD switching sequence.

DAP initialized successfully.

DMAP_REG_ID: DM-AP IDCODE detected: 0x002A0000

DHCSR: 0xFFFFFFFF

ROM entered ISP command handling loop. Re-enable the debug access.

InitTarget() end - Took 14.9ms

Found SW-DP with ID 0x6BA02477

DPIDR: 0x6BA02477

CoreSight SoC-400 or earlier

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: 0x84770001, ADDR: 0x00000000)

Iterating through AP map to find AHB-AP to use

AP[0]: Core found

AP[0]: AHB-AP ROM base: 0xE00FF000

CPUID register: 0x410FD214. Implementer code: 0x41 (ARM)

Feature set: Mainline

Cache: No cache

Found Cortex-M33 r0p4, Little endian.

FPUnit: 8 code (BP) slots and 0 literal slots

Security extension: implemented

Secure debug: enabled

CoreSight components:

ROMTbl[0] @ E00FF000

[0][0]: E000E000 CID B105900D PID 000BBD21 DEVARCH 47702A04 DEVTYPE 00 Cortex-M33

[0][1]: E0001000 CID B105900D PID 000BBD21 DEVARCH 47701A02 DEVTYPE 00 DWT

[0][2]: E0002000 CID B105900D PID 000BBD21 DEVARCH 47701A03 DEVTYPE 00 FPB

[0][3]: E0000000 CID B105900D PID 000BBD21 DEVARCH 47701A01 DEVTYPE 43 ITM

[0][5]: E0041000 CID B105900D PID 002BBD21 DEVARCH 47724A13 DEVTYPE 13 ETM

[0][6]: E0042000 CID B105900D PID 000BBD21 DEVARCH 47701A14 DEVTYPE 14 CSS600-CTI

Memory zones:

Zone: "Default" Description: Default access mode

Cortex-M33 identified.

'loadfile': Performing implicit reset & halt of MCU.

ResetTarget() start

Reset via SYSRESETREQ and reset pin + halt after bootloader

ROM entered ISP command handling loop. Re-enable the debug access.

MSPLIM cleared

ResetTarget() end - Took 118ms

Device specific reset executed.

Downloading file [e:\NXP_SDKs\components\conn_fwloader\fw_bin\rw61x_sb_wifi_a2.bin]...

J-Link: Flash download: Bank 0 @ 0x08000000: 1 range affected (589824 bytes)

J-Link: Flash download: Total: 6.515s (Prepare: 0.340s, Compare: 1.844s, Erase: 0.009s, Program: 3.920s, Verify: 0.212s, Restore: 0.187s)

J-Link: Flash download: Program speed: 146 KB/s

****** Error: Verification failed @ address 0x08400000

Error while programming flash: Verify failed.

Script processing completed.

lpc_gpio_output is the only example project that is getting flashed successfully, but I was unable to run it.
Debug console output:

Launching GDB server: "C:\\Program Files\\SEGGER\\JLink_V812a\\JLinkGDBServerCL.exe" -SettingsFile "E:\\nxp_projects\\frdmrw612_lpc_gpio_led_output\\armgcc\\debug\\JLink_lpc_gpio_led_output.jlink" -nosilent -singlerun -endian little -noir -speed 4000 -port 2330 -vd -device RW612 -if SWD -reportuseraction -nogui -select usb=1062798820 -halt -swoport 2332 -telnetport 2331 Please check TERMINAL tab (GDB server console) for output from "C:\Program Files\SEGGER\JLink_V812a\JLinkGDBServerCL.exe"

Output radix now set to decimal 10, hex a, octal 12.

Input radix now set to decimal 10, hex a, octal 12.

Program stopped, probably due to a reset and/or halt issued by the debugger.

Resetting target

Executed SetRestartOnClose=1

Resetting target

warning: could not convert 'main' from the host encoding (CP1252) to UTF-32. This normally should not happen, please file a bug report.

Console output during flash:

Connecting to target via SWD

InitTarget() start

SWD selected. Executing JTAG -> SWD switching sequence.

DAP initialized successfully.

DMAP_REG_ID: DM-AP IDCODE detected: 0x002A0000

DHCSR: 0x05100000

InitTarget() end - Took 7.19ms

Found SW-DP with ID 0x6BA02477

DPIDR: 0x6BA02477

CoreSight SoC-400 or earlier

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: 0x84770001, ADDR: 0x00000000)

Iterating through AP map to find AHB-AP to use

AP[0]: Core found

AP[0]: AHB-AP ROM base: 0xE00FF000

CPUID register: 0x410FD214. Implementer code: 0x41 (ARM)

Feature set: Mainline

Cache: No cache

Found Cortex-M33 r0p4, Little endian.

FPUnit: 8 code (BP) slots and 0 literal slots

Security extension: implemented

Secure debug: enabled

CoreSight components:

ROMTbl[0] @ E00FF000

[0][0]: E000E000 CID B105900D PID 000BBD21 DEVARCH 47702A04 DEVTYPE 00 Cortex-M33

[0][1]: E0001000 CID B105900D PID 000BBD21 DEVARCH 47701A02 DEVTYPE 00 DWT

[0][2]: E0002000 CID B105900D PID 000BBD21 DEVARCH 47701A03 DEVTYPE 00 FPB

[0][3]: E0000000 CID B105900D PID 000BBD21 DEVARCH 47701A01 DEVTYPE 43 ITM

[0][5]: E0041000 CID B105900D PID 002BBD21 DEVARCH 47724A13 DEVTYPE 13 ETM

[0][6]: E0042000 CID B105900D PID 000BBD21 DEVARCH 47701A14 DEVTYPE 14 CSS600-CTI

Memory zones:

Zone: "Default" Description: Default access mode

Cortex-M33 identified.

'loadfile': Performing implicit reset & halt of MCU.

ResetTarget() start

Reset via SYSRESETREQ and reset pin + halt after bootloader

ROM entered ISP command handling loop. Re-enable the debug access.

MSPLIM cleared

ResetTarget() end - Took 115ms

Device specific reset executed.

Downloading file [e:\nxp_projects\frdmrw612_lpc_gpio_led_output\armgcc\debug\lpc_gpio_led_output.hex]...

O.K.

J-Link>qc

Script processing completed.