Hello !
I try to find in latest nRF connect samples template for typical nRF5340 application ( app+ network cores, mcuboot+b0n bootloaders) with posibility to configure all components and build all of them at once ( multiimage/child images). But looks like no any example where all components are easily visible.
As usually CONFIG_BT=y is in use and no any glue how b0n bootloader is configured there.
I have taken multicore sample and apply mcuboot config from sample Bluetooth: Peripheral UART application.
The folder tree looks like this :
.
├── aci
│ └── CMakeLists.txt
├── child_image
│ └── mcuboot.conf
├── CMakeLists.txt
├── cpunet
│ ├── child_image
│ │ └── b0n.conf
│ ├── CMakeLists.txt
│ ├── Kconfig
│ ├── ___pm.yml
│ ├── prj.conf
│ └── src
│ └── main.c
├── Kconfig
├── pm_static.yml
├── prj.conf
├── README.rst
├── sample.yaml
├── src
│ └── main.c
└── zephyr
└── module.yml
Build work for all cores and bootloaders.
I can flash it by west -v flash -d ./build --skip-rebuild -r nrfjprog and execute app_core update by using mcumgr.
BUT
it build only updates for app core e.g
[196/208] Generating ../../zephyr/app_update.bin
[197/208] Generating ../../zephyr/app_signed.hex
[199/208] Generating ../../zephyr/app_test_update.hex
1. no any updates for networkcore at all only composite images for nrfjprog type of flashing.
2. Configuration file for b0n is not taken in account , not visible it in build log ( mcuboot.conf is visible and configuration is taken)
─ child_image
│ │ └── b0n.conf
b0n is added to cpunet by line CONFIG_SECURE_BOOT=y
How I can configure build hierarchy for be able to generate netcore updates ?
How to configure b0n bootloader properly e.g via what config file ?
What configuration flags are need for create similar Serial recovery method of update ( both cores) like in
Bluetooth: Peripheral UART application sample. Looks like b0n usage SDK is hidden a bit.
Regards,
Eugene
