OTA upgrade example, application upgrade via j-link

Question

I am successfully using the ZigBee OTA upgrade example, but the firmware upgrade takes quite long, approximately a half an hour, so it is not an adequate time at the firmware development stage.
Now my workflow looks like:
1) Test new firmware features without the OTA upgrade cluster;
2) Copying the changes to the main project with the OTA upgrade cluster.
Is there any way to flash the new client firmware (with OTA cluster) just from Segger Embedded Studio using flash_placement.xml? If it is possible, could you please provide the example?

AndreasF · Accepted Answer

Hi Anna. Sorry for not clarifying enough. My idea of your problem was that you wanted to do a upgrade of your client firmware without having to do OTA, correct? About the settings: As you can see here, there is many "settings" and each with an purpose. For example, the CRC value (0x67E076C0) is checked by the bootloader when it is booted, if the value is not correct the device will not boot. That is why you have to generate new settings page when you upgrade your device. The settings page also has to be signed with the private key you used to generate the bootloader and the client with. Is this more clear? How to upload a new firmware without doing it OTA: I've used the command line tool nrfutil when I did this test, as I'm not quite sure how SES behaves when it comes to sectorerase. But you can still do this by flashing the output .hex file SES provides. 1. You generate a private key and the dfu_public_key .c file. nrfutil keys generate priv.pem nrfutil keys display --key pk --format code priv.pem --out_file dfu_public_key.c 2. You generate the 1st edition of your bootloader and client and sign them with your generated key. 3. You generate and sign a bootloader settings page for the client, you merge this settings page with the client. nrfutil settings generate --family NRF52840 --application .hex --application-version 0x01010101 --bootloader-version 1 --bl-settings-version 2 --app-boot-validation VALIDATE_ECDSA_P256_SHA256 --key-file priv.pem settings.hex mergehex -m .hex settings.hex -o dfu_client.hex 4. You do the following programming with cmd: nrfjprog -f nrf52 -e nrfjprog -f nrf52 -r --program .hex --chiperase nrfjprog -f nrf52 -r --program .hex nrfjprog -f nrf52 -r --program .hex --sectorerase You have now programmed the first edition of your client and bootloader. If you now do any modifications to you client, you simply clean the client project, and build it over again. If you wish to upgrade your device with your modified client project, you do this: 1. Clean and rebuild the project. 2. You generate and sign a bootloader settings page for the modified client, you merge this settings page with the modified client. nrfutil settings generate --family NRF52840 --application .hex --application-version 1 --bootloader-version 1 --bl-settings-version 2 --app-boot-validation VALIDATE_ECDSA_P256_SHA256 --key-file priv.pem settings.hex mergehex -m .hex settings.hex -o dfu_client.hex 3. You do the following programming with cmd: nrfjprog -f nrf52 -r --program dfu_client.hex --sectorerase nrfjprog -r And that's it! AnnaR said: Does the bootloader settings also changes with each client firmware update, and need to be regenerated each time by nrfjprog? So, it appears as I cannot automate somehow this process via Segger Embedded Studio? Yes, it does change and you need to regenerate it with nrfutil . I hope this clears up a few things. Best regards, Andreas

OTA upgrade example, application upgrade via j-link

Top Replies