Updating one nRF52 DK board with another nRF52 DK board automatically via OTA DFU

RE: Updating one nRF52 DK board with another nRF52 DK board automatically via OTA DFU

Einar Thorsrud — Wed, 09 Jun 2021 18:17:46 GMT

Hi,

This implementation is from nrfutil, which is a python script running on a PC. All the DFU logic etc is on the PC, and the nRF is only used as a BLE connectivity device using the pc-ble-driver. The upgrade image is stored on a PC in this case and never resided on the nRF.

If your use case is to have a computer connected, and run the DFU process from there, this is useful. If not, then you cannot reuse anything, though you can look at the DFU master implementation as a reference for how you would implement it on the nRF.

RE: Updating one nRF52 DK board with another nRF52 DK board automatically via OTA DFU

tjhasan — Wed, 09 Jun 2021 14:28:59 GMT

I had a feeling that this was the case.

That being said, the dfu_transport_ble.py defines a function 'send_firmware' as follows:

def send_firmware(self, firmware):

In this function, how is the "firmware" passed to the function? Is it via the local path to the firmware on my system (PC)?

Is there an example that uses the dfu_transport_ble.py in any capacity that I can use as a reference?

RE: Updating one nRF52 DK board with another nRF52 DK board automatically via OTA DFU

Einar Thorsrud — Wed, 09 Jun 2021 12:15:35 GMT

Hi,

Nordic does not provide any code example on how to do this. You need to store the whole image (bin file + init packet/.dat file from the dfu .zip image) on the DFU master and send that to the nRF being upgraded. Exactly how you transfer and store this on the DFU master is up to you and could depend on your specific requirements. (Depending on the size of the image it could also be that you would need to store it on external flash rather than the internal one).