Adding mcuboot to BLE peripheral fails to link properly on nRF52840 dongle

RE: Adding mcuboot to BLE peripheral fails to link properly on nRF52840 dongle

mytzyiay — Fri, 22 Jul 2022 22:14:53 GMT

I put my mcuboot config options in the west command line because a couple of them are computed dynamically at build time. But I think you can stuff the static ones into child_image/mcuboot/prj.conf as some of the samples do. I haven't tried this and I don't know what the VSCode plugin will/won't pick up.

Also, if you don't support a non-OTA configuration, you could just rename pm_ota.yml to pm_static_nrf52840dongle_nrf52840.yml . I used the override because I do most of my everyday development on non-OTA-enabled images (simpler, quicker build/flash time) and then switch to OTA builds when I'm ready to deploy them in the lab.

I think that if you're debugging the device, you probably want mcuboot_CONFIG_DISABLE_FLASH_PATCH=n

RE: Adding mcuboot to BLE peripheral fails to link properly on nRF52840 dongle

Caycee — Fri, 22 Jul 2022 16:02:44 GMT

After patching multi_image.cmake and then modifying the command line for my particulars, this DOES work.

I'd prefer to do the same in VSCode where I have my other projects. I have to 'Debug' the unit from VSCode to flash the dongle since running 'Flash' from there does a rebuilds and fails.

But at least I have a path forward for the moment.

RE: Adding mcuboot to BLE peripheral fails to link properly on nRF52840 dongle

mytzyiay — Thu, 21 Jul 2022 23:36:48 GMT

This is working for me on my custom app:

west build \
 --pristine \
 --build-dir=build \
 --board nrf52840dongle_nrf52840 \
 -- \
 -DPM_STATIC_YML_FILE=pm_ota.yml \
 -D"mcuboot_CONFIG_BOARD_HAS_NRF5_BOOTLOADER=n" \
 -D"CONFIG_BOARD_HAS_NRF5_BOOTLOADER=n" \
 -D"mcuboot_CONFIG_USB_DEVICE_STACK=n" \
 -D"mcuboot_CONFIG_MCUBOOT_SERIAL=n" \
 -D"mcuboot_CONFIG_DISABLE_FLASH_PATCH=y" \
 -D"mcuboot_CONFIG_BOOT_SIGNATURE_KEY_FILE=\"/foo/bar/key.pem\"" \
 -D"CONFIG_MCUBOOT_IMAGE_VERSION=\"1.2.3\"

Part of the problem is that the default mcuboot build will include the USB serial recovery code, which makes the bootloader image much larger. I had to turn it off to get below 0xc000 bytes.

Also had to patch NCS with https://github.com/nrfconnect/sdk-nrf/pull/7997

pm_ota.yml uses this static map:

mcuboot:
 address: 0x0
 size: 0xc000

mcuboot_primary:
 address: 0xc000
 size: 0x74000
mcuboot_pad:
 address: 0xc000
 size: 0x200
app:
 address: 0xc200
 size: 0x73e00
mcuboot_primary_app:
 address: 0xc200
 size: 0x73e00
 span: [ app ]

mcuboot_secondary:
 address: 0x80000
 size: 0x74000

zboss_nvram:
 address: 0xf5000
 size: 0x8000
zboss_product_config:
 address: 0xfd000
 size: 0x1000
settings_storage:
 address: 0xfe000
 size: 0x2000

sram_primary:
 address: 0x20000000
 size: 0x40000
 region: sram_primary