OTA from application layer

RE: OTA from application layer

Susheel Nuguru — Wed, 21 Feb 2024 19:39:12 GMT

Sure, no problem.

RE: OTA from application layer

Rytis — Wed, 21 Feb 2024 18:30:05 GMT

Hello,

Thank You for information. We will dig deeper into your solution.

I'll keep this thread open for a while in case of new questions.

Rytis

RE: OTA from application layer

Susheel Nuguru — Thu, 15 Feb 2024 08:08:42 GMT

As you might have known, our DFU solution has the memory laid out similar to your image. We do have an experimental feature to support the encryption, download, validation, and activation of a firmware image for an external device. There is unfortunately no example for it. However, it is documented. Here are some resources you can start with:

Encrypting and packing the image: https://infocenter.nordicsemi.com/topic/ug_nrfutil/UG/nrfutil/nrfutil_update_external_app.html
- Even though the documentation page is under DFU over Zigbee, it is valid for all cases.
DFU Library configuration NRF_DFU_SUPPORTS_EXTERNAL_APP
DevZone case: https://devzone.nordicsemi.com/f/nordic-q-a/68413/how-to-use-external-app-firmware-update

The application is "activated" by triggering a callback at the end of the download. You will need to implement the callback to forward the image to the external device. In your case, you want to do so via BLE. However, we don't have any support for sending DFU from a nRF Device.

It is still possible. This DevZone case goes into the topic: https://devzone.nordicsemi.com/f/nordic-q-a/76980/dfu-controller-in-central-nrf52-device.

RE: OTA from application layer

Rytis — Tue, 13 Feb 2024 16:48:33 GMT

Hello,

1. Only one device(peripheral) is advertising, other devices(mobile phone + central1 and central2 devices) connects to this peripheral, so mobile phone connects to only one device directly.

2. Preferably yes.

We are woried about porting whole project to nRF Connect SDK. We do not have much experience with this SDK and Zephyr OS, so we would like to stick with nRF5 SDK + freeRTOS.

New FW image encapsulated to our own protocol looked like easiest solution, but now I can see that is is wrong assumption :)

According information i found there are three ways:

* Adopt system to use nRF5 SDK DFU procedure. Am I right what this solution is älmost ready to use in iOS and Android?

* Try to understand and adopt background DFU project from this post (not easy to find this ticket)

* Write our own custom solution + custom bootloader.

Rytis

RE: OTA from application layer

Hieu — Tue, 13 Feb 2024 14:55:46 GMT

Hi Rytis,

Am I right to understand that:

The mobile phone app can connect to all devices in your topology, even though the image doesn't show that.
You want the DFU process to run over your own protocol

If so then I am afraid we don't have an out of the box solution in the nRF5 SDK, but it's solely due to point 2.

However, the nRF Connect SDK's DFU solution works exactly as you want. Is changing to this SDK an option for you? We recommend NCS for all new projects anyway, as the nRF5 SDK is in maintenance mode.

If you must stay with the nRF5 SDK, could you please elaborate why you need the image encapsulated in your protocol, so that we can help you look for solutions?

Please keep in mind that the nRF5 SDK solution already supports encryption of the image, as well as encryption of the connection via BLE bonding.

Hieu

RE: OTA from application layer

Susheel Nuguru — Mon, 12 Feb 2024 16:46:32 GMT

Rytis, I did not manage to answer you today. I will take a look at your description tomorrow and will try to reply to you. Thanks for your patience.