FTU OTA Failed.

[Shreyas Shivalkar]

I am new to nordic ble chips. I am using nrf52832 ble chip, s132_nrf52_3.0.0_softdevice I am trying to update firmware on the air. But I am getting an error that I do not understand. I have attached the screenshot to log from nrf connect app.

Please help me understand the error. Thanks in advance.

[bjorn-spockeli]

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.

[Shreyas Shivalkar]

Thanks for the feedback. It worked.

[bjorn-spockeli]

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.

[tkstreet]

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!

[Vasa]

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.

[bjorn-spockeli]

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?