NRF5340 Network Core USB DFU with dfu-util

[MKir]

We are using NRF5340 and interface with a host system via USB. As the USB stack supports the DFU device class, we plan to use that for firmware updates, and use dfu-util on the host side. We want to implement the update in the bootloader to remove the requirement for external flash for the second firmware slot.

Is this supported at all?

I have seen a similar issue, but that discusses the possibility of simultaneous update and does not show how the network image can be downloaded: devzone.nordicsemi.com/.../use-dfu-util-to-perform-multi-image-dfu-from-application

Downloading works well with the application image, using the following command line:

dfu-util -d 1915:b171 -e
dfu-util -d 1915:b172 -D app_image.bin

However, I have not succeeded in updating the network core by issuing the following command:

dfu-util -d 1915:b172 -D net_image.bin

The configuration we use:

sysbuild.conf

SB_CONFIG_BOOTLOADER_MCUBOOT=y
SB_CONFIG_MCUBOOT_MODE_SINGLE_APP=y

# Make the net core image updatable and signed
SB_CONFIG_SECURE_BOOT_NETCORE=y
SB_CONFIG_NETCORE_APP_UPDATE=y

prj.conf for MCUBOOT

CONFIG_MAIN_STACK_SIZE=10240

CONFIG_SINGLE_APPLICATION_SLOT=y
CONFIG_FLASH=y
CONFIG_BOOT_USB_DFU_WAIT=y
CONFIG_BOOT_USB_DFU_WAIT_DELAY_MS=60000
CONFIG_USB_DFU_WILL_DETACH=y
CONFIG_USB_DFU_ENABLE_UPLOAD=n
CONFIG_USB_DFU_REBOOT=n

CONFIG_BOOT_USB_DFU_NO_APPLICATION=y

# PID and VID are the same as in application
CONFIG_USB_DEVICE_PID=0xb171
CONFIG_USB_DEVICE_VID=0x1915
# PID in DFU mode is one higher than during normal operation
CONFIG_USB_DEVICE_DFU_PID=0Xb172

pm_static.yml

app:
  address: 0x20200
  region: flash_primary
  size: 0xcfe00
mcuboot:
  address: 0x0
  region: flash_primary
  size: 0x20000
mcuboot_pad:
  address: 0x20000
  region: flash_primary
  size: 0x200
mcuboot_primary:
  address: 0x20000
  orig_span: &id001
  - mcuboot_pad
  - app
  region: flash_primary
  size: 0xd0000
  span: *id001
mcuboot_primary_app:
  address: 0x20200
  orig_span: &id002
  - app
  region: flash_primary
  size: 0xcfe00
  span: *id002
settings_storage:
  address: 0xf0000
  region: flash_primary
  size: 0x10000
mcuboot_primary_1:
  address: 0x0
  size: 0x38000
  device: flash_ctrl
  region: ram_flash

[AHaug]

Hello,

We want to implement the update in the bootloader to remove the requirement for external flash for the second firmware slot.

I understand this need and requirement and it is a feature that's in the making for NCS.

As briefly mentioned in https://www.linkedin.com/posts/nordic-semiconductor_introducing-the-nrf-connect-sdk-bare-metal-activity-7366726990546104321-03xG?utm_source=share&utm_medium=member_desktop&rcm=ACoAACBLfxoBqFOYLbAjars5fOj1EIXIvvDBdiM (and maybe in https://webinars.nordicsemi.com/events/34049549399?n=Introducing%20nRF%20Connect%20SDK%20Bare%20Metal%20option&event_id=34049549399&hsLang=en), the single bank OTA feature is something that we've introduced in NCS Bare Metal (for 54L15 only), and that will make its way into NCS in the future.

This does however not help you right now as it's not supported yet.

I have seen a similar issue, but that discusses the possibility of simultaneous update and does not show how the network image can be downloaded: devzone.nordicsemi.com/.../use-dfu-util-to-perform-multi-image-dfu-from-application

As I briefly mentioned in the ticket you refer to, dfu-util is not supported, so any implementation you choose to use will have to be a proprietary solution that you adapt yourself. For the nRF5340 I would recommend you to stick to the supported methods for DFU, i.e simultaneous update of net and app-core as well as the supported tools

Kind regards,
Andreas 

[MKir]

Thanks Andreas,

I see that simultaneous multi-image update only works with a dual-slot configuration. Is it possible to have non-simultaneous update of the network core with a single slot configuration (CONFIG_SINGLE_APPLICATION_SLOT /SB_CONFIG_MCUBOOT_MODE_SINGLE_APP) with serial recovery / mcumgr?

I have seen a comment here from 3 years ago that says no.

[AHaug]

Hi,

Good thing you asked. I've not tested this myself, but afaik it is possible to do since ~NCS v2.7.0 according to https://docs.nordicsemi.com/bundle/ncs-latest/page/nrf/app_dev/device_guides/nrf53/serial_recovery.html. I had a look through https://academy.nordicsemi.com/courses/nrf-connect-sdk-intermediate/lessons/lesson-9-bootloaders-and-dfu-fota/topic/exercise-1-dfu-over-uart/ to see if it was covered here, but only serial recovery of the application is covered there.

Let me know if the serial recovery docs linked above is enough for you to validate if this solution can work for you.

One of the reasons for why we recommend simultaneous DFU of both cores on the 5340 is in case you make some changes that may break the interface between the app and net-core. For instance let's say that you first do an update of the network core over BLE where the interface has changed. When you reboot after the swap you may be left in a situation where the app core does not know how to communicate with the netcore and thus you don't have BLE available to revert/update the app core and you will be forced to either reprogram or do serial recovery. Simultaneous OTA ensures that the appcore is built to be able to communicate with the netcore and you have the option to revert the update since you do dual bank slot.

Kind regards, 
Andreas

[MKir]

Hello,

Thanks a lot. I got it to work with dual slot setup, after debugging the single slot setup which I understood here to be possible: https://docs.nordicsemi.com/bundle/ncs-latest/page/nrf/app_dev/device_guides/nrf53/serial_recovery.html

I did not manage and I believe the documentation is misleading in this respect. I've opened  Documentation page for NRF5340 serial recovery.