MCX MicrocontrollersのトピックRe: Secondary Bootloader + Dual Image Setup

Secondary Bootloader + Dual Image Setup

maknxp — Tue, 31 Mar 2026 09:13:02 GMT

We have a secondary bootloader, put in Flash Bank1 IFR0 region (0x0100_8000 to 0x100FFFF). The BOOT_SRC within CMPA is set to 2 for transferring control to Secondary Bootloader from BOOTROM on Power-Up. It works correctly. We can transfer the control to Main Application residing at address 0x0000_0000.

We would like to have DUAL Main Application setup and not quite sure how exactly it works. We would like to store a Second copy Main Application at 0x0008_0000. Essentially, first one is at 0x0000_0000, can grow up to 0x0007_FFFF and second one is at 0x0008_0000 which can grow up to 0x000F_FFFF, occupying 512 KB each.

We understood about the Flash Remap feature. which is programming FLASH_REMAP_SIZE from CMPA to kind of partition the on chip flash. We also understood that the selection of the image will be decided by BOOTROM code.

In our case the, the boot process also have our secondary bootloader as mentioned above and it is the one which always executes after BOOTROM. The question is how to use the Dual Main Application (on On-chip Flash and REMAP feature) with Secondary Bootloader (on Bank1Ifr0).

Re: Secondary Bootloader + Dual Image Setup

Alice_Yang — Tue, 31 Mar 2026 10:58:48 GMT

Hello @maknxp

In your secondary bootloader, you need to read the version numbers of both images and then decide which one to launch.
By the way, which NXP MCU are you using?

Thank you.

Alice

Re: Secondary Bootloader + Dual Image Setup

klt4xc — Mon, 04 May 2026 12:34:39 GMT

thanks for the information!

Re: Secondary Bootloader + Dual Image Setup

klt4xc — Tue, 05 May 2026 10:48:15 GMT

Taking a closer look at that NXP forum discussion on implementing a secondary bootloader with a dual image setup, the core issue is how to properly manage firmware updates while ensuring the device can still boot if something goes wrong. The setup described involves storing two application images and using a secondary bootloader to decide which one to run, typically based on integrity checks or version control. The key takeaway is that the bootloader must contain clear logic to validate images and safely switch between them when needed, rather than relying on external triggers. This kind of structured decision-making is essential for maintaining system stability during updates. In a similar way, systems that use voice to text ai also depend on processing input data through defined logic to produce accurate and reliable outputs, showing how important well-designed evaluation flows are across different types of technology.