[riot-notifications] [RIOT-OS/RIOT] board suggestion: nRF52840-dongle (#12189)

chrysn notifications at github.com
Thu Sep 12 17:35:05 CEST 2019

Gathering a few more data points on the upload process here. I think that being able to use this upload process could also give us the ability to use the thingy:52's OTA upload process as long as we don't override its bootloader or the softdevice on it. [espruino](https://www.espruino.com/Thingy52) have a build process that outputs flashable zip files for their firmware, so I suppose it's possible with reasonable tools.

The zephyr project [has support for this board](https://docs.zephyrproject.org/latest/boards/arm/nrf52840_pca10059/doc/index.html), which seems to indicate that things can be quite straightforward; I'll try to get forward from there.

(I've started playing around with the hex and zip files from the dodo example; that may not have future relevance but if we need to dig around further it may help:

Uploading usually works from classical Intel HEX files. Those (taking the blinky example from [dodo](http://www.d0d0.pro/index.php/2018/09/23/programming-the-new-nordic-chip-nrf52840-and-usb-dongle-board-pca10059-featuring-it/) as a starting point) contain the program at 0x00001000 (which, in the zip file, ends up in a .bin) and some other data at address 0x00000000 whose presence or content no bearing on the resulting zip file. The zip files also contain a JSON manifest and a .dat file that describes suitable firmware and hardware versions, requirements on the softdevice's presence and a checksum of the binary data. (Basically the contents of `nrfutil pkg display zip.zip`)


You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.riot-os.org/pipermail/notifications/attachments/20190912/67bb6c92/attachment.htm>

More information about the notifications mailing list