Problem with OTA DFU using nrfutil

RE: Problem with OTA DFU using nrfutil

jPolo777 — Tue, 26 Oct 2021 14:26:52 GMT

I followed some of the ble_peripheral examples (that use the SoftDevice) and put the same start IROM1 address and size that are 0x27000 and 0xD9000 respectively in the application project that I want to update OTA and it worked! Thanks for the advice.

RE: Problem with OTA DFU using nrfutil

Einar Thorsrud — Mon, 25 Oct 2021 13:33:23 GMT

[quote user="jPolo777"]2. Yes, I test my application without flashing the bootloader (nor the SoftDevice) and it works.[/quote]

I see. Please note that the blinky_freertos example if you have not modified it starts at address 0, so you need to modify this to use it with a SoftDevice (even if the example does not use the SoftDevice it must be located immediately after the SoftDevice as you need that for the BLE bootloader. The fact that this works without having a SoftDevice means that you have not done this, and thus it cannot work in the setup you want (SoftDevice + BLE Bootloader).

So you need to relocated it the application. I suggest you look at an example that use the same SoftDevice version as you and see the linker configuration there. Then I suggest you test it with a SoftDevice (even though not using it) to see that it works. Once that is in place you can move forward to test DFU.

RE: Problem with OTA DFU using nrfutil

jPolo777 — Mon, 25 Oct 2021 13:24:37 GMT

1. If I'm not wrong, the firmware I'm using (the blinky_freertos example) doesn't use the SoftDevice.
2. Yes, I test my application without flashing the bootloader (nor the SoftDevice) and it works.

RE: Problem with OTA DFU using nrfutil

Einar Thorsrud — Mon, 25 Oct 2021 07:15:19 GMT

Hi,

Did you build your firmware and bootloader to use the same SoftDevice version? Did you test that the application you built works without flashing the bootloader (so if the device only has the SoftDevice + application)?

RE: Problem with OTA DFU using nrfutil

jPolo777 — Fri, 22 Oct 2021 15:42:41 GMT

Hi Einar. Thanks for replying. I changed the softdevice and now I'm using the s140_nrf52_7.0.1 which corresponds to the ID 0xCA and it seems to work! I get the message Device programmed in the command window. However, the firmware that I used to do the DFU (FreeRTOS blinky led) doesn't work in the target (the leds doesn't blink). What did I do wrong? Though, I followed this guide.

RE: Problem with OTA DFU using nrfutil

Einar Thorsrud — Fri, 22 Oct 2021 10:24:59 GMT

The error indicates that the SoftDevice you have listed as required (ID 0xCA) is not found on the device. Do you know which SoftDevice you built your application for, and which SoftDevice is already on the device you try to update? If it is the same, then you just need to use the correct SoftDevice ID with the --sd-req option. If the SoftDevice is not the same, then you should include also the SoftDevice in the package you generate.