"Write Image" fails at "Erase Flash" step in FRDM-RW612

[Nokhysh]

Following the instructions on the site below, I executed "Write Image,"
but it fails at the "Erase Flash" step, as shown in the attached image.

Could you please tell me how to resolve this?

https://community.nxp.com/t5/Wi-Fi-Bluetooth-802-15-4/How-to-solve-flashing-problems-in-FRDM-RW612-f...

[Nokhysh · Accepted solution]

Build and Write completed with the following settings.

 

[marek-trmac]

Hi @Nokhysh 

can you go to main menu > Targets > Boot memory and open the memory configuration dialog and use "Test" button to verify the configuration is correct. On the screenshot I can see you are using FCB - are you sure the FCB contains configuration that matches your memory?

[Nokhysh]

こんにちは、  @marek-trmac 

Thank you for your reply.

The test passes.

Based on the log below, I believe it matches the FCB memory size (64MiB).

Best Regards,

Naoki.

[marek-trmac]

Hi @Nokhysh 

the "Test" button in the boot memory configuration verifies also read access to the memory. It seems you have read access. The problem might be in the write access.

If the original issue is still reproducible, I'd recommend to check write access. You can go to main menu > Tools > Flash programmer, configure the memory and try to write any block.

Also, based on the name of the FCB file on your screenshot, I suppose the FCB was taken from source image. Not sure what image you have, the FCB from the source image might not be properly configured for write. You can also consider using default tool configuration (simplified FCB). The default configuration was tested on FRDM board, and it should work.

[Nokhysh]

Hi, @marek-trmac .

I was getting an error with "Erase Flash" for the file with memory size 18180h.

However, I have now successfully loaded the file starting from address 0x08000000.

I am using the same image file as the one mentioned on this site:

https://community.nxp.com/t5/Wi-Fi-Bluetooth-802-15-4/How-to-solve-flashing-problems-in-FRDM-RW612-f...

Where can I find the tool's default simplified FCB file?

Best Regards,

Naoki.

[marek-trmac]

Hi

>I was getting an error with "Erase Flash" for the file with memory size 18180h.

Do you mean if there is an error for the longer file (and small file works)? Can you describe how to reproduce the problem, so I can check on my side?

[Nokhysh]

Hi, @marek-trmac 

I apologize for the misunderstanding.
The issue is unrelated to the file size; it fails during the "Erase Flash" process.

The method to reproduce the issue is in the attached procedure.
In step 7, when I try to "Write image," an error occurs during the "Erase Flash" process.

I would appreciate it if you could investigate this issue.

Best Regards,
Naoki.

[liborukropec]

Hi,

>>Where can I find the tool's default simplified FCB file?

There's no simplified FCB "file". If you want to use simplified configuration, simply select the first radio button in the "Boot Memory Configuration" dialog.

Regards,
Libor

[Nokhysh]

Hi, @liborukropec @marek-trmac 

I found the simplified FCB settings.
However, when I test with the attached FCB, it results in an error.

Best Regards,
Naoki.

[marek-trmac]

Hi @Nokhysh ,

I'll try to reproduce the issue from your last comment on our side. Can you please confirm how to reproduce it:

- you have Secure Provisioning Tool 25.06

- you have FRDM-RW61x board connected via USB (without USB hub)

- for new workspace created for RW612, the default flash memory configuration (simplified FlexSPI NOR) does not work

[Nokhysh]

Hi, @marek-trmac 

Please see my answers to your questions below.

• I am using Secure Provisioning Tool 25.06.

• I have the FRDM-RW612 connected with two USB cables.
  However, since I needed to connect in ISP mode, I tried the connection method described in the following PDF: FRDM-RW612_ISP_and_Temperature_sensor_over_BLE.pdf.

• With the default memory configuration(W25Q512JVFIQ), the "simplified Flex SPI NOR" option causes an error.

Best Regards,
Naoki.

[marek-trmac]

Hi @Nokhysh 

I tried today with SEC tool 25.06, MS Windows 11:

- connect FRDM-RW612 with two USB cables

- created new workspace for RW612

- main menu > Target > Boot Memory - Test: PASSED

- I used "C:\nxp\MCUX_Provi_25.06_final\bin\_internal\data\sample_data\targets\RW612\source_images\frdmrw612_gpio_led_output.s19" to build the image, I did not used FCB from the image

- Build + Write: PASSED

Summary: I did not reproduce any issue

[Nokhysh]

Hi, @marek-trmac 

Regarding the device that was failing verification during flushing, as mentioned in the first agenda item, were you able to successfully write the image to it?
Verification Error 2:
https://community.nxp.com/t5/Wi-Fi-Bluetooth-802-15-4/How-to-solve-flashing-problems-in-FRDM-RW612-f...

Also, please tell me the settings to use that do not involve the FCB (File Control Block).
Are you saying that the following settings are incorrect?

Best Regards,
Naoki.

[marek-trmac]

Hi @Nokhysh ,

>Regarding the device that was failing verification during flushing, as mentioned in the first agenda item, were you able to successfully write the image to it?

Yes, by "Build And Write" I mean I used SEC tool and, in the tool, I successfully built bootable image and wrote it into the flash.

>Also, please tell me the settings to use that do not involve the FCB (File Control Block).

I did not use FCB, I used the simplified configuration, which is default for new configuration. I did not use any FCB from the image. All my steps are described in the previous response.

I'd recommend to read the paragraph: User interface — MCUXpresso Secure Provisioning Tool 25.06 so you understand, what is the relationship between simplified configuration and full FCB configuration. 

If you want me to test any FCB, you need to describe what exactly should I test and where to find the FCB. I suppose you understand, FCB is configuration of the external flash, so if FCB is not correct, the flash will not work.

[Nokhysh]

Hi, @marek-trmac 

The test succeeds with the simplified FCB.
However, it fails to write, just like last time.

Best Regards,
Naoki.

[marek-trmac]

Hi @Nokhysh ,

on your screenshot I can see you are using advanced (InField) life cycle. I'd recommend to use the basic use case until you are sure the memory configuration is valid.

In advanced life cycle, the ISP commands are limited. If you are using advanced life cycle, you need to do hard reset after every write command.

Also, I have already tested write with my board using simplified flash config and confirmed it works on my side. I have described step by step how to reproduce it. If it does not work on your side, I'd recommend to follow my steps or describe your steps. Otherwise, it is really difficult to understand, where the problem is on your side.

[Nokhysh]

Hi, @marek-trmac 

I will summarize my procedure from the beginning.

• Connected the RW612 with two USB cables.

• Set the RW612 to ISP mode.

• The connection test via UART was successful.

• There were no issues building the attached image file.

• There were no problems testing with the Boot Memory configuration of the completed FCB.

• An error occurs during "Erase Flash" when writing.

I would appreciate it if you could point out any errors.

Best Regards,
Naoki.

[marek-trmac]

Hi @Nokhysh ,

based on the latest screenshot, I can see you are using FCB taken from source image instead simplified configuration. Not sure what image you have, the FCB from the source image might not be properly configured for write. You can also consider using default tool configuration (simplified FCB). The default configuration was tested on FRDM board, and it should work.

I'd recommend to read the paragraph: User interface — MCUXpresso Secure Provisioning Tool 25.06 so you understand, what is the relationship between simplified configuration and full FCB configuration. 

[Nokhysh]

Hi, @marek-trmac 

I'm using a Flash Programmer Tool, and both the 'Write' and 'Erase' operations fail.
However, the 'Read' operation succeeds.
What could be the possible causes for this?"

Best Regards,
Naoki.

[Nokhysh]

Hi, @marek-trmac 

A test was conducted using a simplified FCB and the boot memory configuration of the verified W25Q512JVFIQ(default), which resulted in a failure.

Best Regards,
Naoki.