Wireless MCUのトピックRe: KW45 First Time Programming

KW45 First Time Programming

cnew01 — Wed, 03 Sep 2025 12:41:28 GMT

I am trying to program a custom KW45-based PCB for the first time. I tried using MCUXpresso. The J-Link could upload my program over SWD but when I tried entering debug mode the board halts at address 0x14816fdc. Further research has shown that the NBU for the Bluetooth coprocessor needs to be uploaded. I've tried AN13838, but my board cannot be discovered over UART. I've been looking into AN14003, but it's information is out of date with regards to the current SPSDK. What do I do?

Re: KW45 First Time Programming

cnew01 — Wed, 03 Sep 2025 13:08:57 GMT

I will clarify that LPUART0 TX and RX pins are accessible on this custom board through a header.

Re: KW45 First Time Programming

luis_maravilla — Thu, 04 Sep 2025 17:03:51 GMT

Hello

The memory address you mention refers to ROM-Boot [Table 16 KW45 Reference Manual], On KW45, only boot ROM has access to the NBU flash,

For more information about ROM boot process flow please refer to AN14003 Figure 2

As you are using a KW45 chip from fabric for your custom PCB; Could you help us confirm if your KW45 chip from fabric was already fuse burned as the process described in AN14003?

And if there was already fuse burned, Could you confirm if the default KW45B41Z-EVK Keys [SBKDK and RoTKTH] described in Chapter 5.2.1 [AN14003] were used? Or you use custom generated keys for the board.

Also for confirmation, Have you done an updating NBU before on the chip?

Best Regards

Luis

Re: KW45 First Time Programming

cnew01 — Thu, 04 Sep 2025 20:53:00 GMT

The fuses had not been burned yet, the KW45 is from fabric. Updating the NBU on the chip has not been done before.

Re: KW45 First Time Programming

luis_maravilla — Thu, 04 Sep 2025 21:29:31 GMT

Hello,

I need to confirm if your end goal is using the custom KW45-based PCB same as the KW45B41Z-EVK using SDK examples or is intended for custom applications?

As this will interferes on the fuses that are needed to be burn in chip.

For updating the NBU image to a KW45 device two types of keys must be written to KW45 fuse, By default, RoTKTH and SB3KDK are provided for KW45B41Z-EVK board; but in a factory chip the keys in the fuse are null.

Therefore, for Factory chips, the customer needs to burn fuses related for end goal following the instructions in [AN14003 Programming the KW45 flash for Application and Radio firmware via Serial Wire Debug during mass production]

If you want to use your board for development same as the KW45B41Z-EVK you could use the same keys values from the KW45B41Z-EVK board directly [Described in AN14003 Chapter 5.2.1 Figure 9]; If you want to use your board for a different end product or custom end application; I would recommend creating your own keys and generating the sb3 file using the .xip file for a new NBU image dedicated to your end product

Then Updating NBU; If you want to use your board for development same as the KW45B41Z-EVK you can use the same sb3 file that its inside SDK folder for updating the NBU, if you want to use your board for a different end product or custom end application you should create your own sb3 file for uploading the NBU image following the instructions described in Chapter 4 in AN14003.

It's important to mention that the method of burning the fuse provided in this document cannot be reversed. The keys programmed to fuses on KW45 cannot be changed anymore. Therefore, it is recommended to modify the fuse with caution.

Best Regards

Luis

Re: KW45 First Time Programming

cnew01 — Fri, 05 Sep 2025 20:14:46 GMT

Luis:
I'm trying to implement the app note, I will be using the default keys just to validate functionality on this custom board. In an14003, Test_ota_partition on Page 13 is not defined in the OTAP example or the rest of the code provided. What is this variable supposed to be?

Re: KW45 First Time Programming

luis_maravilla — Mon, 08 Sep 2025 17:44:55 GMT

Hello,

The test_ota_partition function utilizes the OtaPartition_t structure defined in fwk_platform_ota.h. used to manage OTA operations used in other steps described in AN14003.

This structure describes the characteristics of the Over-the-Air (OTA) update partition, including parameters such as offset, size, sector and page sizes, and whether the flash is internal or external.

As outlined in Application Note AN14003 comment where Test_ota_partition is used, indicates to use internal flash so we need to initialize the parameters and true for using internal flash.

This is something every customer would need to implement by their own. Also, I attached the structure with definitions [Taken from fwk_platform_ota.h]

typedef struct { uint32_t start_offset; /*!< Offset of firmware update partition in flash device. The physical address is translated by flash driver */ uint32_t size; /*! Size of firmware update storage expressed in bytes */ uint32_t sector_size; /*! Sector size of flash used for OTA, usually 4kB for external flash but varies for internal flash */ uint32_t page_size; /*! Page size of flash device : minimal program size*/ bool internal_flash; /*! true if internal flash, false for SPI NOR Flash */ uint32_t spi_baudrate; /*! SPI baudrate concerns only external flash if flash config is not used KW45 case */ } OtaPartition_t;

Best Regards

Luis

Re: KW45 First Time Programming

cnew01 — Tue, 09 Sep 2025 19:55:44 GMT

I've tried following an14003 section 5 (omitting section 3) using the evk sb3. The one modification I made was setting
loader_info.partition_desc = PLATFORM_OtaGetOtaInternalPartitionConfig();
I'm still encountering the same error once merging the generated binary and the SB3. What would you reccomend I look into?

Re: KW45 First Time Programming

luis_maravilla — Wed, 10 Sep 2025 20:47:42 GMT

PLATFORM_OtaGetOtaInternalPartitionConfig returns internal partition configuration structure, what you could try is make the initialization manually, to ensure the internal flash is selected and the values start at 0.

Let me know if that worked for you.

OtaPartition_t Test_ota_partition = 
{
    /*start_offset*/ 0,\
    /*size*/         0,\
    /*sector_size*/  0,\
    /*page_size*/    0,\
    /*internal_flash*/ true,\
    /*spi_baudrate*/ 0,\
};

loader_info.partition_desc = &Test_ota_partition;

Re: KW45 First Time Programming

cnew01 — Fri, 12 Sep 2025 18:40:43 GMT

This didn't work. I'm still going to that address in the boot memory when trying to debug. Anything else I can look into?

Re: KW45 First Time Programming

luis_maravilla — Mon, 15 Sep 2025 20:39:24 GMT

Could you help us share a log failure or message error?

What you could look into, As you mentioned you are using the Default keys for fuse burning with AN14003, Could you help us try to update the NBU image with the instructions described in section 3.3 Updating NBU for Wireless Examples as the sb3 file in SDK apply for the default keys burned in KW45 board.

Could you help us confirm that the process of fuse burning went correctly? If not, could you help us sharing the error shown?

Could you confirm if you can enter ISP mode without problem?

Re: KW45 First Time Programming

cnew01 — Fri, 26 Sep 2025 13:14:42 GMT

I cannot find the Tools > Manufacturing Tool in MCUXpresso as the guide that was sent specifies. Is there more up to date information available?

Re: KW45 First Time Programming

luis_maravilla — Fri, 26 Sep 2025 18:48:59 GMT

Hello,

This instruction refers to the "MCUXpresso Secure Provisioning Tool", I would recommend using the latest version "MCUXpresso Secure Provisioning Tool 25.06" of your OS, you can download the tool from this link: MCUXpresso Secure Provisioning Tool Downloads, also creating a new workspace in the tool.

Regards

Luis

Re: KW45 First Time Programming

cnew01 — Fri, 26 Sep 2025 19:08:06 GMT

Luis:
I have installed the SPSDK and have found the tool you have mentioned. My current issue is since I don't have an onboard device for USB I must use a USB to UART Converter. In attempting that the software cannot find my board (on the USB port with my USB to TTL converter I'm getting the error message below.

I can confirm that I used the nxpdebugmbox cmd -f kw45b41z8 ispmode -m 1 command in the terminal to set it to ISP mode and the terminal indicates that has taken place successfully.

Re: KW45 First Time Programming

luis_maravilla — Mon, 29 Sep 2025 22:51:29 GMT

Hello

Could you please help us confirm whether you're able to flash and run any program on your board—excluding wireless or Bluetooth Low Energy examples?, this is for, I’d like to confirm whether the board still fails to operate even when running a program that doesn’t require the NBU.

I recommend testing one of the examples available in the SDK to verify basic functionality.

Additionally, please ensure that your board’s serial connection is correctly configured by comparing it with the KW45B41Z-EVK schematics. You can consult the schematics at the following link: KW45B41Z Evaluation Kit Board Schematics

Best Regards

Luis

Re: KW45 First Time Programming

cnew01 — Tue, 30 Sep 2025 12:36:04 GMT

The program will get stuck at 0x14816fdc even when it's the LED Blinky example.

Re: KW45 First Time Programming

luis_maravilla — Wed, 01 Oct 2025 22:24:55 GMT

Could you help us confirm in which OEM state is the KW45? You can use the blhost tool command "blhost -p COMx get-property 0x01" and can you share with us the response? Also Could you help us share with us what it is the complete part number of your KW45?

You can check the part number information with the table 1 in the datasheet KW45B (radio) and KW45Z (MCU) Data Sheet

Best Regards, Luis

Re: KW45 First Time Programming

cnew01 — Thu, 02 Oct 2025 17:34:22 GMT

The part number is here: KW45B41Z83AFTBR
I am unable to use blhost.

Whenever I try I get the following:

I have a USB to UART adapter that is connected to LPUART0 pins.

I can do the following below:

The debug log referenced by the error is attached. My USB to TTL Serial should be connected at COM15

Re: KW45 First Time Programming

luis_maravilla — Fri, 03 Oct 2025 19:05:25 GMT

Hello,

Could you help us check if your board is being correctly detected as a COM port [UART] in Device Manager tool in your computer, under the section Ports (COM & LPT)? This will help confirm the active COM connection. Based on the image, the command appears to be using COM15, while the debug_log indicates COM7

In device manager you should see something like this

If you confirm the connection being COM7; please retry the blhost command [blhost -p COM7 get-property 0x01] to verify a success response connection.

If this command succeeds, please retry the MCUXpresso Secure Provisioning Tool step using COM7 instead of COM15 to update the NBU image.

Please let me know your findings.

Best Regards

Luis

Re: KW45 First Time Programming

cnew01 — Wed, 08 Oct 2025 16:25:02 GMT

The blhost is not detecting my UART to USB converter that i have connected to the board. Im using a different converter on COM8 but I am having the same issue I was having with the converter on COM15.