I am running SES and have changed the Thingy project. How do I create a DFU ZIP file?
I am running SES and have changed the Thingy project. How do I create a DFU ZIP file?
Sorry that question probably wasn't clear enough. I am running Segger Embedded Studio, and I have the Thingy-52 project, which I can compile using SES. I have made changes to the project and I want to update the Thingy-52 using the DFU. Is that possible? How do I generate a ZIP file using the output of SES? Does this include the Softdevice and bootloader? I would think I need the existing public-private keys?
I have created DFU ZIP files before, for my own custom projects. Here was a previous Windows batch line I used:
..\nrfutil pkg generate --hw-version 52 --application-version 1 --application hex\ble_app_buttonless_dfu_pca10040_s132.hex --sd-req 0xAF --key-file keys\private.key hex\TestProject.zip
Of course to do this for Thingy I would need to know the existing keys!
HI Brian,
we do not share the private key for the factory programmed bootloader on the Thingy:52. So if you want to create your own custom applications for the Thingy:52, then you need to erase the factory bootloader and then re-flash the Thingy:52 with the Secure Bootloader example from the Thingy SDK where you add your own public key.
Best regards
Bjørn
So what do I use to flash the board, since I obviously need to directly plug in? Do you have a cable spec? What JTAG/programming device do you use and/or is available? The app implies you can load a custom setup via DFU!
You can use the Debug Out connector on any nRF51 or nRF52 DK with the Jlink On-Board Programmer to flash the Thingy:52. You can also use any J-Link Programming/Debug Probe.
The connector is a 10-pin 2x5 Socket-Socket 1.27mm IDC (SWD) Cable, like this: https://www.adafruit.com/product/1675
The need for a new private key and re-compilation of the bootloader is stated here: https://nordicsemiconductor.github.io/Nordic-Thingy52-FW/documentation/dfu_generating.html.