FTU OTA Failed.

RE: FTU OTA Failed.

bjorn-spockeli — Tue, 26 Nov 2019 20:08:44 GMT

Vasa: This question is over 3 years old. Can you please open a new question where you state which SDK version you are using and which nrfutil version you are using?

RE: FTU OTA Failed.

Vasa — Tue, 26 Nov 2019 16:31:53 GMT

Hi, i faced the same problem while receiving firmware (NRF_DFU_RES_CODE_INSUFFICIENT_RESOURCES). But i generated external firmware (not for nrf, but for stm32) and specify --external-app key in nrfutil. I try to receive 300kb firmware for STM32. I did not use mergehex utility. nRF52810 is used. What might be a problem? Thanks.

RE: FTU OTA Failed.

tkstreet — Thu, 12 Jul 2018 00:56:11 GMT

Ahh, I had been doing this as well. It is a bit vague in the infocenter documentation on this point. It may be worth revising the text to make this distinction more clear. Nonetheless, thank you for the help!

RE: FTU OTA Failed.

bjorn-spockeli — Mon, 29 May 2017 06:32:28 GMT

Great! I would appreciate if you could mark the answer as coorect/accepted by clicking the check-mark in the grey circle to the left of the answer.

RE: FTU OTA Failed.

Shreyas Shivalkar — Fri, 26 May 2017 17:43:20 GMT

Thanks for the feedback. It worked.

RE: FTU OTA Failed.

bjorn-spockeli — Fri, 26 May 2017 12:50:07 GMT

The bootloader settings hex must not be merged with the bootloader hex when you're creating a BLE DFU image as this will add an additional 4kB to the hex file. You should only merge the settings with the bootloader hex when you're flashing the combined image to your nRF52 device using a programmer and you want the device to boot to the application and not stay in bootloader mode.

RE: FTU OTA Failed.

Shreyas Shivalkar — Mon, 22 May 2017 19:16:36 GMT

I am using sample bootloader image with minor modification. Instead of setting and clearing gpio to enter bootloader mode, I am using setting and clearing retention registers to enter the bootloader mode. Softdevice version s132_pca10040 and my custom firmware image.

Steps taken to generate firmware + bootloader image.

nrfutil settings generate --family NRF52 --application --application-version 5 --bootloader-version 2 --bl-settings-version 1
Merging

mergehex -m <saber_Bl_settings image> -o
Steps taken to generate OTA firmware build image

nrfutil pkg generate --hw-version 52 --sd-req 0x8C --application-version 5 --application --key-file private.pem sdfu_package.zip

RE: FTU OTA Failed.

bjorn-spockeli — Mon, 22 May 2017 07:54:29 GMT

If you take a look at DFU Transport layer documentation, found here, you'll see that NRF_DFU_RES_CODE_INSUFFICIENT_RESOURCES means that there is not enough memory for the data object, i.e. the firmware image is to large. Please describe all the steps you took when performing the DFU, e.g are you using the sample images in the SDK or did you generate your own DFU image? If so, post the nrfutil command used to generate it.