FRDM-MCXW71 NBU Firmware Setup

[goran_petrushev]

I have been playing around with the FRDM-MCXW71 board recently and I encountered some uncertainties while trying to set up the NBU firmware.

I followed through this guide for it and what I noticed is that it's quite old. My confusion is specifically regarding the .sb3 files that are in the SDK used for flashing the firmware. In the guide, said file is named differently, it is just mcxw71_nbu_ble_1_9_14_1.sb3

When I went digging in the SDK for this file, I found 3 different files going by:

• mcxw71_nbu_ble_hadm_hosted.sb3
• mcxw71_nbu_ble_hosted.sb3
• mcxw71_nbu_ble_xp_hosted.sb3

There is also a .xip file with the same name for each one of these. I tried looking around to find any explanation about the difference between these but I couldn't find any. Furthermore, I tried running the bm beacon example with each firmware file and it only worked with mcxw71_nbu_ble_hadm_hosted.sb3

Thanks in advance for reading and answering

[marek-trmac]

Hi,

you might find additional info here:

Getting Started with FRDM-MCXW71 | NXP Semiconductors

Processor-specific workflows — MCUXpresso Secure Provisioning Tool 25.03 25.03 documentation

[MrShen]

Using the MCUXpresso Secure Provisioning Tool 25.09 manufacturing tool to perform NBU firmware updates. After selecting to run the application SB file and clicking start, it also fails. May I ask what the problem is? How can it be resolved? Thank you!

[PakostaP]

It is impossible to tell from the provided information.

Did you use an SB file from the SDK that is signed with NXP keys? If so, it can only be used with the FRDM board, as those boards have pre-burned NXP keys.

If you are using a custom SB file, did you use the correct keys for signing it? Also, are the commands in the SB file correct?

Both scenarios how to update NBU FW are described in the documentation linked by Marek.

[MrShen]

I don't have a FRDM board. Could you provide the pre-burned NXP keys and the burning method? If not, where can I find the custom SB file, or the SB configuration files and binary files such as *.yaml files that need to be imported for the custom SB file? Thank you!

[marek-trmac]

Hi @MrShen 

if you really want to use NXP "demo" keys used on EVK board, start Secure Provisioning Tool and go to main menu > File > New Workspace, select the processor with a board and in the profile select "Plain signed image running on onchip flash FRDM-MCXW71 keys".

If you want to generate new keys, select ""Plain signed image running on onchip flash"

As a source application, select any sample application from the drop down list.

Create new workspace and build the bootable image.

After that follow the flow described in Processor-specific workflows — Secure Provisioning Tool 25.09

[MrShen]

Hello, according to the steps, Create new workspace and build the bootable image. In the menu bar, select 'Tools' > 'Manufacturing Tools', after executing Write image, execute Apply SB image,''mcxw71_nbu_ble_1_9_14_0.sb3". After the NBU firmware update is successful. Now when debugging the program in MCUXpresso IDE, debugging cannot proceed, Error: Wire Ack Fault - target connected.

  

[MrShen]

Resolved! The jumper was not connected, thank you!

[MrShen]

Hello, according to the instructions you mentioned, after selecting to create a new workspace, I built the image file. Then I used the tool—the manufacturing tool—to write the application SB image, i.e., the file "mcxw71_nbu_ble_1_9_14_0.sb3". However, after clicking "Start", the firmware download still failed.

When using the custom SB file method, it was mentioned that the NBU firmware should be copied to the workspace as "source_images\nbu_firmware.xip". Where can this NBU firmware be found, and which specific file is it? Please provide it if possible.

After selecting the advanced command "update-nbu-firmware", a prompt appears indicating that the file "nbu_firmware.xip" cannot be found. This prevents the generation of the SB file, so please also provide this file if available.

[PakostaP]

Hello,

For every .sb file with NBU firmware, there is a corresponding .xip file. Therefore, the SDK should contain a file named mcxw71_nbu_ble_1_9_14_0.xip. If you copy this file into the source_image folder and rename it to nbu_firmware.xip, it will enable the update_nbu_firmware command, and you're good to go.

[MrShen]

OK,Thank you！