NCS Bare Metal - Build images separately

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
  • Hi Filip

    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?

    When DFU is enabled in the application, the build system outputs build files (image files):

     

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

    Please refer to the steps in MCUboot: Recovery entry/Testing.

    Regards,
    Amanda H.

  • 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

  • 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

  • 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.

  • That would work if I wanted to build an application with a custom firmware loader together. However, I want to build them separately:
    1. MCUBoot + SoftDevice
    2. Firmware Loader
    3. Application
    and then merge it manually because I want to be able to use different NCS Bare Metal versions for the firmware loader and the application.

    Regards,
    Filip

  • Hi Filip,

    This could lead to version conflicts and other potential problems. 

    Please ensure the NCS Bare Metal versions are consistent for the mcuboot+Sofdevice, firmware loader, and the application. 

    I will be out of the office for the next two weeks and will not be able to answer the case. If you need urgent support, please create a new support case.

    Merry Christmas & Happy New Year!

    Amanda H.

     

  • Hi,
    Is your application based on NCS Bare Metal, or a completely different toolchain?

Reply Children
Related