OTA DFU ISSUE

RE: OTA DFU ISSUE

bjorn-spockeli — Thu, 24 Jan 2019 09:43:53 GMT

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.

RE: OTA DFU ISSUE

daniel — Thu, 24 Jan 2019 07:37:38 GMT

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

RE: OTA DFU ISSUE

bjorn-spockeli — Wed, 23 Jan 2019 16:12:33 GMT

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