From 95f01b082ef9c40280b4286e6fca3cae6a1090cf Mon Sep 17 00:00:00 2001 From: Michael Dietz Date: Mon, 7 Mar 2016 11:36:37 +0100 Subject: [PATCH] Also need to specify the image type. --- README.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/README.md b/README.md index b4a3e5a..75ce037 100644 --- a/README.md +++ b/README.md @@ -38,7 +38,8 @@ Where `````` is one of ```nrf51``` or ```nrf52```. ## Updating the SoftDevice or Bootloader -When updating the application nothing special needs to be done - the only input required is APPLICATION.hex. However it is possible to update the SoftDevice or Bootloader as well. +When updating the application nothing special needs to be done - the only input required is APPLICATION.hex. However it is possible to update the SoftDevice or Bootloader as well. The user will need to specify the image type of the update +when transferring a SoftDevice or Bootloader in dfu.provision() (i.e. dfu.provision(device, buffer, dfu.ImageType.SoftDevice);) along with the following: Softdevice: When updating the SoftDevice we must not rewrite the [Master Boot Record (MBR)](https://infocenter.nordicsemi.com/topic/com.nordic.infocenter.s132.sds.v0.5/dita/softdevices/s130/mbr_bootloader/mbr_bootloader.html?cp=1_3_0_0_9). As the MBR is included in Nordic's SoftDevices at the beggining of FLASH, the end address of the MBR will need to be specified when converting the hex file (i.e. hex2bin(softdevice.hex, 0x1000);). This way when updating the SoftDevice