nRF54L15 : Reducing OTA Image Size for Low-Bandwidth Cellular Networks

[jay]

Hi,

We’re developing a product using the nRF54L15 with OTA updates over a cellular network.
Since we’re using a low-data-rate cellular connection, the large image sizes generated by the nRF Connect SDK make firmware updates difficult. This results in frequent disconnections, longer module on-times, and higher power consumption, which isn’t ideal for our low-power application.

To mitigate this, we’re looking for a solution where:

1. The firmware image is compressed on the server side before transmission.

2. The device decompresses the image locally before writing it to the secondary (update) slot.

Are there any popular methods, proven implementations, or recommended libraries from Nordic for such a setup?
Any guidance on how to implement this effectively would be greatly appreciated.

Thanks & Regards,
Jay

[Vidar Berg]

Hi,

Please have a look at the "Memory footprint optimization" chapter of the SDK documentation for general recommendations on how to reduce the memory footprint and the MCUboot image compression chapter if you are looking to use image compression.

Best regards,

Vidar

[jay]

Hi Vidar,

Thanks for the quick response! I’ll go through it shortly. get back to you soon..

regards,
Jay

[jay]

Hi,

Vidar Berg said:

MCUboot image compression chapter if you are looking to use image compression.

However, since MCUboot image compression only works in upgrade-only mode and does not support reverting to previous versions, this approach isn’t feasible for us.

Our devices will be deployed in locations without physical access, so using upgrade-only mode could lead to a permanently bricked device if the update fails mid-process.

please let me know if you have any other suggestion that can be work rather then above two method.

regards,
jay