OTA DFU ISSUE

[daniel]

Hello,

We are working with nrf52832  which have a custom application with SDK 13.1 and softdevice s132_nrf52_4.0.5_softdevice, we have migrated to sdk 15.2 s132_nrf52_6.1.0_softdevice and  we want to update these devices over ble dfu.

Next nrfutil commands are used in order to create dfu package (APP + BL + SD) :

 nrfutil settings generate --family NRF52 --no-backup --application.hex --application-version 2 --bootloader-version 2 --bl-settings-version 2 bootloadersettings.hex
 mergehex.exe -m bootloader.hex bootloadersettings.hex -o bootloader_complete.hex
 mergehex.exe -m s132_nrf52_6.1.0_softdevice.hex bootloader_complete.hex application.hex -o full.hex

nrfutil pkg generate --hw-version 52 --application.hex --application-version 2 --bootloader bootloader_complete.hex --bootloader-version 2 --softdevice s132_nrf52_6.1.0_softdevice.hex --sd-req 0x9F,0xAF --sd-id 0xAF --key-file private_pem pkg.zip

So we try to update over dfu with nRF Connect  the pkg.zip then device disconnects and we got next error: Remote DFU error: EXTENDED ERROR SD version failure (code = 7). "The array of supported SoftDevices for the update does not contain the FWID of the current SoftDevice or the first FWID is '0' on a bootloader which requires the SoftDevice to be present. "

We also have tried to update just with dfu packet BLE + SD and we got the same error. 

SD version is correct set to 0xAF. What can we do to solve this issue? 

Thanks in advance

[bjorn-spockeli]

HI Daniel, 

the bootloader settings should not be added in a DFU firmware image, it should only be merged with the SD+APP+BL when you flash the firmware to the device using a programmer and want the device to boot to the application and not the bootloader. 

Are you sure that its the S132 v4.0.5 that is present on the device? Can you try adding more SD IDs, e.g. --sd-req 0x95,0x98,0x99,0x9E,0x9F,0xAF ? 

Best regards 
Bjørn

[daniel]

Hi Bjorn,

Now it is working, the problem was I merged bootloader_settings with bootloader.hex and pkg needs to be created just with bootloader.hex, is there any reason it just happens with diferents softdevice or sdk?

Thanks for your help

[bjorn-spockeli]

HI Daniel, 

No, I was sort of expecting that you would get the NRF_DFU_RES_CODE_INSUFFICIENT_RESOURCES (i.e. not memory forhte bootloader object) after the  EXTENDED ERROR SD version failure (code = 7) was resolved due to the settings page being outside the bootloader region. 

I dont think that this should be related to different SD or SDK versions.