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

Not able to perform DFU (FOTA) using nRF Connect Application or nRF ToolBox

Hi, I am trying to initiate Firmware Upgrade using the nRF Connect Mobile Application (also tried using nRF ToolBox).

As described in the below link - github.com/.../init packet handling

I created the ZIP File following the steps in the PDF file - How to create INIT File for nRF as mentioned in the link above. I have initiated upload using following steps -

  1. ZIP File created using nRF UTILITY
  2. .BIN and .DAT file

The error which I am getting is - After successfully starting Bootloader, the device is getting disconnected.

Please find the attached log of nRF LoggernRFLogger_Error.txt and .DAT Filefirmware.dat In the Log, you can see that after below byte is written to initiate DFU on characteristic, the connection is terminated. "D 14:38:28.776 [DFU] gatt.writeCharacteristic(00001531-1212-efde-1523-785feabcd123) A 14:38:32.142 [DFU] Jump to bootloader sent (Op Code = 1, Upload Mode = 4)"

Note: I am able to successfully perform DFU using Master Control Panel version 3.10 Device Information - Chip nRF52832, Softdevice support - S130 and S132. Mobile Used - Samsung A7 -2015, Android 6.0

Parents
  • Could you explain this: "Connections fails as soon as it calls DFUTarg" ?

    Are you updating only the application or the application and softdevice and bootloader ? If you only update application you should not include the softdevice and bootloader.

    You may want to capture a sniffer trace, it would reveal what happened over the air. If you don't have the hardware for sniffer, you can try to debug the bootloader and check if the app managed to connect the bootloader.

Reply
  • Could you explain this: "Connections fails as soon as it calls DFUTarg" ?

    Are you updating only the application or the application and softdevice and bootloader ? If you only update application you should not include the softdevice and bootloader.

    You may want to capture a sniffer trace, it would reveal what happened over the air. If you don't have the hardware for sniffer, you can try to debug the bootloader and check if the app managed to connect the bootloader.

Children
No Data
Related