NRF5340 Builds with precompiled images NCS 2.1 / NCS 2.7

[dstude]

Hi -

Using nrf5340 and ncs 2.1/2.7 

To ensure we are testing and integrating the originally released bootloaders and net core images, we'd like to be able to use `west build` to incorporate any or all of the following precompiled images in the final merged build outputs and flash if commanded.

mcuboot
b0n
hci_rpmsg/hci_ipc

For mcuboot, we've had success with CONFIG_MCUBOOT_BUILD_STRATEGY_USE_HEX_FILE and CONFIG_MCUBOOT_HEX_FILE, but don't seem to be able to use similar config options for b0n and hci_ipc.

Thanks!

[Edvin]

Hello,

Is there a reason why you want to program precompiled .hex files, and not just build and program the radio core and bootloader and NSIB bootloader (b0) together with the application firmware?

I am not sure it is possible to add these like you want to do. For this, I think it would be easier to cherry pick each hex file that you want to test, and then either program them separately using nrfjprog, or merge them using merghex (part of nRF Command Line Tools/nrfjprog) before programming them using nrfjprog.

I understand that you want to test the original bootloader, but the original network core? Wouldn't that typically be updated together with the application core?

Best regards,

Edvin

[dstude]

The product already deployed has a certain MCUboot, b0n and hci_rpmsg.  Like you point out, we can upgrade hci_rpmsg, of course, so that may be considered a little more optional, but we'd still need to make sure we're integrating to the original b0n as well.

[Edvin]

I understand. It might be possible using some KConfig magic, but it is not clear to me where the .hex file that is used instead of building MCUBOOT should be placed, and what it should be called. I guess it is possible to look it up by searching for where it is used. But seeing as you need to find the same for B0n, and optionally hci_rpmsg, then I would think it is easier to program these separately in a bash/bat script that will program these custom files, and then use nrfjprog to program only the application hex file for your application's build folder. 

Best regards,

Edvin

[dstude]

Thanks.   That's the strategy we are using.  

For the future, any chance sysbuild offers a mechanism to do this?

[Edvin]

Hello,

At least it has a different way of linking in other applications that are intended to run on different cores, and merge them together in one build and flash operation, where as now it is mostly used to link in MCUBOOT, B0n and hci_rpmsg, as fixed applications for some certain KConfigs. I believe it is possible to link in other applications for the network core today, but I must admit I am not sure how to do it. I tried it about a year ago, without succeeding, and used the scripts instead. 

I have not looked too much into this yet, but I believe you will find some relevant information here:

https://docs.nordicsemi.com/bundle/ncs-latest/page/nrf/app_dev/config_and_build/sysbuild/sysbuild_images.html

Best regards,

Edvin