The issue of uploading the same update package during Bluetooth OTA

RE: The issue of uploading the same update package during Bluetooth OTA

Menon — Wed, 06 Aug 2025 09:35:39 GMT

Hello,

Good to hear that your issue has been resolved for the moment. Please don’t hesitate to create a new ticket if you encounter any further issues.

Kind regards,
Abhijith

RE: The issue of uploading the same update package during Bluetooth OTA

llly — Wed, 06 Aug 2025 01:33:47 GMT

Thank you for your reply

At present, a relatively rare method has been used to implement the function I need, and this problem has been temporarily solved

RE: The issue of uploading the same update package during Bluetooth OTA

Menon — Wed, 30 Jul 2025 07:33:19 GMT

Hello,

Using mcumgr, list the currently active image and retrieve its hash. Then, locally compute the hash of the update package you intend to send. If the hashes match, you can skip the upload, knowing that the device already has the exact same firmware. See the Image Management section, which explains how to retrieve the current firmware hash.

Kind regards,
Abhijith

RE: The issue of uploading the same update package during Bluetooth OTA

Menon — Mon, 28 Jul 2025 18:01:01 GMT

Hello,

I’m checking internally on this, as I’m not completely sure about the query you’ve raised. I’ll update you as soon as I hear back from the relevant teams.

Please note that there may be some delay in gathering information due to the summer vacation period here in Norway.

Kind regards,
Abhijith