• State Not Answered
  • Replies 13 replies
  • Subscribers 87 subscribers
  • Views 546 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 355183
Options

NCS Bare Metal - Build images separately

tdfilip

Hello

Is there a possibility to build MCUBoot, SoftDevice, Firmware Loader and Application separately and then merge it manually? Or to build MCUboot + SoftDevice + Firmware Loader and separately Application, and merge them manually?

If so, could you guide me on how to do it e.g. on mcuboot_recovery_entry sample?

Regards,
Filip

Parents Reply
  • 0 in reply to Amanda Hsieh

    I went through that example but that's not the case.

    I want to build Firmware Loader with MCUBoot and SoftDevice, without even having an application. Then I want to be able to merge the output image with an application developed separately. How can I build the nrf-bm/application/firmware_loader/ble_mcumgr so in build output I have Firmware Loader image, SoftDevice image and MCUBoot image without having the main application?

    Regards,
    Filip

Children
  • 0 in reply to tdfilip

    You can use <build_dir>/installer_softdevice_firmware_loader.bin for Installer Update image (DFU) with SoftDevice and firmware loader updates.

  • 0 in reply to Amanda Hsieh

    Okay. Could you guide me how to build this <build_dir>/installer_softdevice_firmware_loader.bin without having an application? I need a standalone firmware loader which can be then merged with an external application.

    I tried west build -b bm_nrf54l15dk/nrf54l15/cpuapp/s115_softdevice/mcuboot nrf-bm/applications/firmware_loader/ble_mcumgr but this builds the firmware loader as firmware loader and as application. I would like to build this nrf-bm/applications/firmware_loader/ble_mcumgr as standalone firmware loader.

    Regards,
    Filip

  • 0 in reply to tdfilip

    Please use samples/boot/mcuboot_recovery_entry and refer to MCUboot: Recovery entry to build. Then, you will find the installer_softdevice_firmware_loader.bin file under the build folder. 

  • 0 in reply to Amanda Hsieh

    So you suggest to build the sample application samples/boot/mcuboot_recovery_entry and use its firmware loader for merging with custom applications?

    Maybe I should describe what I want to achieve.
    I want to have a repository with firmware loader (based on the nrf-bm/applications/firmware_loader/ble_mcumgr but with my custom changes) and use it as bootloader submodule for various applications. I want to be able to build this firmware loader separately from the application. Then, I want to build the application itself and merge it with the firmware loader, mcuboot and softdevice into one hexfile. Is it possible?

    Regards,
    Filip

  • 0 in reply to tdfilip
    tdfilip said:
    So you suggest to build the sample application samples/boot/mcuboot_recovery_entry and use its firmware loader for merging with custom applications?

    You can refer to that example to enable the required configs to build the firmware loader as a sub-image. 

    tdfilip said:
    I want to have a repository with firmware loader (based on the nrf-bm/applications/firmware_loader/ble_mcumgr but with my custom changes) and use it as bootloader submodule for various applications. I want to be able to build this firmware loader separately from the application. Then, I want to build the application itself and merge it with the firmware loader, mcuboot and softdevice into one hexfile. Is it possible?

    You can use nrf-bm\applications\firmware_loader\ble_mcumgr as a base to customize for your requirements, and use SB_CONFIG_BM_FIRMWARE_LOADER_IMAGE_PATH to set your custom ble_mcumgr in the sysbuild.conf.

Related
Terms of service