An alternative to DFU + BLE using a single bank

RE: An alternative to DFU + BLE using a single bank

Menon — Fri, 06 Sep 2024 09:06:20 GMT

Hello,

I know it can be a bit frustrating, but in BLE OTA DFU, the device writes the new firmware to a separate area of memory (the secondary slot). After the update, the device switches to this secondary slot and verifies its integrity. If the new firmware is valid, the device continues using it; otherwise, it reverts to the old firmware. With a single bank, there's no separate space to store the new firmware during the update process. I apologize if you already know this, but I wanted to explain why single-bank DFU is not supported.

Additionally, I personally don't recommend using our old nRF5 SDK, as it is in maintenance mode and no further development will be made

Kind Regards,

Abhijith

RE: An alternative to DFU + BLE using a single bank

_lumac — Thu, 05 Sep 2024 17:25:38 GMT

Hi Abhijith,

Thank you for your reply.

It's a shame not to have the option of a single bank. I have no other option but to switch to the old nRF5 SDK.

Best regards,

Luis

RE: An alternative to DFU + BLE using a single bank

Menon — Thu, 05 Sep 2024 14:00:56 GMT

Hello,

The approach you mentioned is technically feasible, but I currently don't have a specific reference or implementation to provide. You may need to develop your own solution. A potentially better approach could be to consider adding an external flash for the secondary slot. Additionally, you could refer to the memory optimization guide to reduce the application size to some extent.

Kind Regards,

Abhijith