Can one nrf51x22 transfer its firmware to another OTA?

RE: Can one nrf51x22 transfer its firmware to another OTA?

AlexDM0 — Wed, 15 Oct 2014 15:23:44 GMT

Thanks! I'm kinda new to this and the documentation is not always very clear on everything. thanks for the quick response, now I have a better idea in which direction to setup my timetable.

RE: Can one nrf51x22 transfer its firmware to another OTA?

John — Wed, 15 Oct 2014 15:09:57 GMT

I don't know about the DFU host code availability. You could look on Github where there are a number of Nordic projects available. Worst case, the DFU message flow and behavior is extensively documented in the SDK documentation. You could write your own pretty easily, it would just take some time.

The nrf should be able to read the application binary out of program space since it can be accessed as NVRAM.

RE: Can one nrf51x22 transfer its firmware to another OTA?

AlexDM0 — Wed, 15 Oct 2014 15:03:48 GMT

Thank you for the answer! I don't suppose the DFU host code is freely available? I believe I've only seen it as a precompiled file to flash the nordic usb dongle..

Could the nrf read it's own data from flash and send that to the other one?

Regards,

Alex

RE: Can one nrf51x22 transfer its firmware to another OTA?

John — Wed, 15 Oct 2014 14:53:16 GMT

After thinking about this for a minute, I don't see any reason why not.

At the end of the day any device that is using DFU to reprogram other devices is merely reading and writing characteristics on the DFU service. There isn't anything special about that. You'd just need to implement the DFU host code/state machine in your application FW.