FRDM-RW612: Error while programming flash: Verify failed

bmathukiya · ‎02-03-2025

Hi There,

Flashing failed for FRDM-RW612

I tried erasing the board. It works fine but is not able to program the board.

below is the MCUXpresso Console log

Executing flash operation 'Program' (Program executable into flash Debug/frdmrw612_hello_world.axf) - Mon Feb 03 13:55:49 IST 2025
Checking MCU info...
Scanning for targets...
Executing flash action...
SEGGER J-Link Commander V8.12a (Compiled Jan  9 2025 14:43:13)
DLL version V8.12a, compiled Jan  9 2025 14:42:08
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 01h 24m 30s
S/N: 1067701573
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: 0x05100000
InitTarget() end - Took 2.36ms
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:
"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 113ms
Device specific reset executed.
J-Link>h
PC = 1302B460, CycleCnt = 00000000
R0 = 00000000, R1 = 5AC33CA5, R2 = 00000001, R3 = 5AC33CA5
R4 = 3012F5FC, R5 = 50002E24, R6 = 55AACC33, R7 = 33CCAA55
R8 = 5AA55AA5, R9 = FCF0030F, R10= C33CA55A, R11= 55AACC33
R12= 3012F5FC
SP(R13)= 30125A38, MSP= 30125A38, PSP= 00000000, R14(LR) = 1302B421
XPSR = 01000000: APSR = nzcvq, EPSR = 01000000, IPSR = 000 (NoException)
CFBP = 00000001, CONTROL = 00, FAULTMASK = 00, BASEPRI = 00, PRIMASK = 01
MSPLIM = 00000000
PSPLIM = 00000000
Security extension regs:
MSP_S = 30125A38, MSP_NS = 00000000
MSPLIM_S = 00000000, MSPLIM_NS = 00000000
PSP_S = 00000000, PSP_NS = FFFFFFFC
PSPLIM_S = 00000000, PSPLIM_NS = 00000000
CONTROL_S  = 00, FAULTMASK_S  = 00, BASEPRI_S  = 00, PRIMASK_S  = 01
CONTROL_NS = 00, FAULTMASK_NS = 00, BASEPRI_NS = 00, PRIMASK_NS = 00
FPS0 = 00000000, FPS1 = 00000000, FPS2 = 00000000, FPS3 = 00000000
FPS4 = 00000000, FPS5 = 00000000, FPS6 = 00000000, FPS7 = 00000000
FPS8 = 00000000, FPS9 = 00000000, FPS10= 00000000, FPS11= 00000000
FPS12= 00000000, FPS13= 00000000, FPS14= 00000000, FPS15= 00000000
FPS16= 00000000, FPS17= 00000000, FPS18= 00000000, FPS19= 00000000
FPS20= 00000000, FPS21= 00000000, FPS22= 00000000, FPS23= 00000000
FPS24= 00000000, FPS25= 00000000, FPS26= 00000000, FPS27= 00000000
FPS28= 00000000, FPS29= 00000000, FPS30= 00000000, FPS31= 00000000
FPSCR= 00000000
J-Link>loadfile "/home/bhavya/Documents/MCUXpresso_24.12.148/workspace/frdmrw612_hello_world/Debug/frdmrw612_hello_world.hex" 0x8000000
'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 113ms
Device specific reset executed.
Downloading file [/home/bhavya/Documents/MCUXpresso_24.12.148/workspace/frdmrw612_hello_world/Debug/frdmrw612_hello_world.hex]...
J-Link: Flash download: Bank 0 @ 0x08000000: 1 range affected (65536 bytes)
J-Link: Flash download: Total: 0.647s (Prepare: 0.181s, Compare: 0.113s, Erase: 0.005s, Program: 0.164s, Verify: 0.107s, Restore: 0.076s)
J-Link: Flash download: Program speed: 390 KB/s
****** Error: Verification failed @ address 0x08000000
Error while programming flash: Verify failed.
Script processing completed.
Unable to perform operation!
Command failed with exit code 1

Installed SDK:

Thank you,

Bhavya

sofiaurueta · ‎02-06-2025

Hello,

Hope you are doing well.

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

bmathukiya · ‎02-09-2025

Hi @sofiaurueta

Yes, I was able to flash the board previously. I had flashed light-switch-combo-app https://github.com/NXP/matter/blob/v1.4.0.0/examples/light-switch-combo-app/nxp/rt/rw61x/README.md

After that, I was trying to reflash the board and this issue arose.

I am trying to follow the steps you shared in FRDM-RW612 Getting Started. Wi-Fi CLI on VS Code but FRDM-RW612 SDK but the link seems broken.

I must say NXP's documentation seems untested. I have also faced various issues in following the quick start for UG10178: Quick Start to the Matter Demo NXP CHIP Tool app, FRDM-RW612 and FRDM-MCU W71

Thank you,

Bhavya

bmathukiya · ‎02-10-2025

Hi @sofiaurueta,

I have tried to follow the steps to flash the WiFi CLI app using VS code. But getting the same error.

I am attaching the screenshot for your reference.

Can you please look into this.

Thank you,

Bhavya

Ricardo_Zamora · ‎02-11-2025

Hi Bhavya,

Could you please clarify if you selected the FRDM (and not the RD) when building the matter application?

If you selected the RD, (or did not select any option), the binary for the RD was generated. So, please follow this guide: Unlock FRDM-RW612 flash - NXP Community

Best Regards,

Ricardo

bmathukiya · ‎02-12-2025

Hi @Ricardo_Zamora

Yes, I have selected the FRDM only. I have flashed the light-switch-combo-app matter firmware and can test it. But after that, I cannot flash another firmware; the previous firmware is also not booting up.

I have also tried the long manual activity mentioned in the Unlock FRDM-RW612 flash - NXP Community link but the issue is still the same.

Thank you,

Bhavya

sofiaurueta · ‎02-17-2025

Hello Bhavya,

Could you try to do a mass-erase as shown in this guide: RT board recovery for debugger connect issues

Best regards,

Ana Sofia

bmathukiya · ‎02-19-2025

Hi @sofiaurueta,

I have already done the mass erase at a very first instant and also mentioned the same in this ticket's 1st reply. Mass erase works fine.

The guide RT board recovery for debugger connect issues which you are pointing is for MIMXRT1060-EVK and I have FRDM-RW612. Can you please guide the steps for FRDM-RW612

Thank you,

Bhavya

bmathukiya · ‎02-19-2025

Hi @sofiaurueta

I have also tried to test the external flash using SPT tool but it is also failed. Below is the snapshot for the same.

Thank you,

Bhavya

sofiaurueta · ‎02-19-2025

Hello Bhavya,

Could you follow the steps to the Unlock FRDM-RW612 flash guide once again?

Before running the last blhost steps "Now run the following (YOUR BINARY should be the path and file in which the binary is located):"

Please do the following:

Open a Terminal (such as TeraTerm or PuTTY) and share with me the output of the example. I would like to see that the example to unlock the flash is running correctly.

Best regards,

Ana Sofia