nRF5340 Multi image build with MCUBOOT + netboot

RE: nRF5340 Multi image build with MCUBOOT + netboot

Simon — Tue, 13 Jul 2021 13:31:30 GMT

Could you upload your application (or a simple project that demonstrates the issue), so I can reproduce the error "E: settings_subsys_init failed (err -37)" and try to get to the bottom of it.

I can make the ticket private if you would like to.

RE: nRF5340 Multi image build with MCUBOOT + netboot

Simon — Mon, 12 Jul 2021 15:18:01 GMT

Ah, I understand. I'm really sorry for being too quick to answer. I will look into it tomorrow.

RE: nRF5340 Multi image build with MCUBOOT + netboot

Alexander Thorstensen — Mon, 12 Jul 2021 07:24:30 GMT

This is exactly what I am trying to do, but for the code we have developed for the network core and application core. We are not running sample projects on any of the cores, and the challenge here is to implement this functionality for custom projects running on each of the cores.

RE: nRF5340 Multi image build with MCUBOOT + netboot

Simon — Mon, 12 Jul 2021 00:18:29 GMT

All you need to do is the following

Set CONFIG_BOOTLOADER_MCUBOOT=y in the applications prj.conf (e.g. ncs/nrf/samples/bluetooth/mesh/light_switch/prj.conf)
Set CONFIG_SECURE_BOOT=y in the network core sample (will be ncs/zephyr/samples/bluetooth/hci_rpmsg/prj.conf when building Bluetooth examples for the nRF53 DK).
Build the BLE sample
- This can be done by running the following commands:
  - cd <ncs location>/ncs/nrf/samples/bluetooth/mesh/light_switch
  - west build -b nrf5340dk_nrf5340_cpuapp
- If the the two conditions below are met, the hci_rpmsg sample will always be included as a child image (which will make it a multi image build)
  - Using the board name nrf5340dk_nrf5340_cpuapp
  - Bulding a BLE example (e.g. the mesh light_switch sample, or the sample nrf/samples/bluetooth/peripheral_uart)
Then you can see that the sample hci_rpmsg is added as a child image:
And that CONFIG_SECURE_BOOT=y for the network core sample (hci_rpmsg):
- When CONFIG_SECURE_BOOT=y in the network core sample (hci_rpmsg) the netboot will be included as well
Next you can run west flash from <ncs location>/ncs/nrf/samples/bluetooth/mesh/light_switch and both the network core and the application core will get flashed with respectively the hci_rpmsg sample and the light_switch sample (If you use SEGGER, the net core won't get flashed automatically, and you need to flash it separately).
Then you can follow the steps under Network core Bootloader-->Testing
- If you see the log "Done updating network core", it works successfully

It does not seem like it is necessary to execute step 2 (set CONFIG_SECURE_BOOT=y) in the hci_rpmsg, as it will happen automatically, as explained in the documentation:

Best regards,

Simon

RE: nRF5340 Multi image build with MCUBOOT + netboot

Alexander Thorstensen — Thu, 08 Jul 2021 14:44:09 GMT

My understanding was that this would enable mcuboot for the application core, but not for the network core. The additional steps were all in an effort to add bootloader support for the network core.

My approach was based on the solution documented here: https://developer.nordicsemi.com/nRF_Connect_SDK/doc/1.5.0/nrf/samples/nrf5340/netboot/README.html

The end goal is to implement a recovery mode where both the application core and network core can receive new images from a serial interface. I am new to zephyr and the nRF SDK, and more than happy to take a different approach if you have suggestions.

RE: nRF5340 Multi image build with MCUBOOT + netboot

Simon — Thu, 08 Jul 2021 14:02:40 GMT

[quote user=""]Enable MCUBOOT with netboot support on the application core[/quote][quote user=""]Enabeling multi-image build breakes the settings subsys on the network core[/quote]

Why are you doing this? If you set CONFIG_BOOTLOADER_MCUBOOT=y in the pjr.conf of you application, the mcuboot will get added as a child image and you will have a multi image build (the partition manager will also get enabled and used to partition the flash). There is no need to enable multi-image build in this case explicitly.

Best regards,

Simon