- Forums
- Product Forums
- General Purpose MicrocontrollersGeneral Purpose Microcontrollers
- i.MX Forumsi.MX Forums
- QorIQ Processing PlatformsQorIQ Processing Platforms
- Identification and SecurityIdentification and Security
- Power ManagementPower Management
- Wireless ConnectivityWireless Connectivity
- RFID / NFCRFID / NFC
- Advanced AnalogAdvanced Analog
- MCX Microcontrollers
- S32G
- S32K
- S32V
- MPC5xxx
- Other NXP Products
- S12 / MagniV Microcontrollers
- Powertrain and Electrification Analog Drivers
- Sensors
- Vybrid Processors
- Digital Signal Controllers
- 8-bit Microcontrollers
- ColdFire/68K Microcontrollers and Processors
- PowerQUICC Processors
- OSBDM and TBDML
- S32M
- S32Z/E
-
- Solution Forums
- Software Forums
- MCUXpresso Software and ToolsMCUXpresso Software and Tools
- CodeWarriorCodeWarrior
- MQX Software SolutionsMQX Software Solutions
- Model-Based Design Toolbox (MBDT)Model-Based Design Toolbox (MBDT)
- FreeMASTER
- eIQ Machine Learning Software
- Embedded Software and Tools Clinic
- S32 SDK
- S32 Design Studio
- GUI Guider
- Zephyr Project
- Voice Technology
- Application Software Packs
- Secure Provisioning SDK (SPSDK)
- Processor Expert Software
- Generative AI & LLMs
-
- Topics
- Mobile Robotics - Drones and RoversMobile Robotics - Drones and Rovers
- NXP Training ContentNXP Training Content
- University ProgramsUniversity Programs
- Rapid IoT
- NXP Designs
- SafeAssure-Community
- OSS Security & Maintenance
- Using Our Community
-
- Cloud Lab Forums
-
- Knowledge Bases
- ARM Microcontrollers
- i.MX Processors
- Identification and Security
- Model-Based Design Toolbox (MBDT)
- QorIQ Processing Platforms
- S32 Automotive Processing Platform
- Wireless Connectivity
- CodeWarrior
- MCUXpresso Suite of Software and Tools
- MQX Software Solutions
- RFID / NFC
- Advanced Analog
-
- NXP Tech Blogs
- Home
- :
- Wireless Connectivity
- :
- Wireless MCU
- :
- KW45 First Time Programming
KW45 First Time Programming
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
KW45 First Time Programming
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
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?
luis_maravilla
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
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
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
luis_maravilla
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
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 m...]
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
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I will clarify that LPUART0 TX and RX pins are accessible on this custom board through a header.
