The issue of uploading the same update package during Bluetooth OTA

[llly]

I am using the 54l10 chip, and after compiling the project, I will receive a hex firmware and a zip update package. The bin firmware and hex firmware in this update package are exactly the same. When I download the hex firmware to the device and upload the zip update package to the device via Bluetooth, the device will skip the upload directly and continue running the current app.
I now want to obtain information about the uploaded update package in the application layer, such as checking whether the uploaded update package is completely consistent with the currently running firmware in the application layer. What should I do?  I know that mcumgr will automatically compare the hash values of the new firmware and the currently running firmware, but this is not done within the app, and the app cannot monitor this event

I tried using CONFIG_MCUMGR_GRP_IMG_UPLOAD_CHECK_HOOK and CONFIG_MCUMGR_GRP_IMG_STATUS_HOOKS .HOOKS, but in this case, none of these events will be triggered, and I will only receive these event callbacks when uploading different versions of the update package

[Menon]

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

[llly]

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