This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

DFU via OTA for SD+BLE and APP with different SDK and Softdevice

I have a firmware version present SDK 13.1 and S132  SoftDevice v4.0.5

I am trying to do a DFU (just SD+BL first) which now has SDK 16.0 and S113 SoftDevice v7.0.1
But my package gets rejected by nrfConnect and it displays SD version failure.

I tried the following command in nrfutil : 

>> nrfutil pkg generate --key-file private.pem --hw-version 52 --sd-req 0xCC,0x102--bootloader quuppa_tag_s113_nRF52832_bootloader_V4.hex --bootloader-version 1 --softdevice s113_nrf52_7.0.1_softdevice.hex --sd-id 0xCC,0x102 SD_BL2.zip

Please let me know how I can perform an OTA with different SDK and softdevice versions. Thank you so much!!

Parents
  • Hi,

    Seem you upgrade from S132 v4.0.5 to  S113 SoftDevice v7.0.1. The SD ID of s132_nrf52_4.0.5 is 0x9F, and s113_nrf52_7.0.1 is 0xCC. 

    So, --sd-id and --sd-req should look like this --sd-req 0x9F,0xCC and --sd-id 0xCC.

    See the DFU package combinations:

    the two SDs may have different IDs. The first update requires --sd-req to be set to the ID of the old SD. The APP update requires the ID of the new SD. The new ID must be set using --sd-id parameter. This parameter was added in nRF Util v3.1.0 and is required since v3.2.0 in case the package should contain SD (+ BL) + APP. Also, the new ID is copied to --sd-req list so that in case of a link loss during the APP update the DFU process can be restarted. In this case, the new SD would overwrite itself, so --sd-req must contain the ID of the new SD.

    -Amanda H.

  •   



    I now believe it has something to do while sending the application. Is there a way I could debug the CRC or the gatt characteristics being written? Thanks!

Reply Children
Related