2025-04-07 8:52 AM - last edited on 2025-04-07 8:54 AM by Andrew Neil
Moved from STM8 forum.
Hello ST Community,
I am experiencing an issue with BLE OTA functionality on my STM32WB-based custom board.
I have ported the OTA functionality from the official NUCLEO BLE OTA example project to my custom service and characteristic, and it has been working fine with the ST BLE Toolbox Android app v1.4.2.
However, after updating the app to v1.4.3 (March 2025), the OTA process consistently fails. No changes were made to the firmware between tests. If I downgrade the app back to v1.4.2, OTA works reliably again.
Additionally, I noticed that STM32CubeMX was recently updated to v6.14.0, whereas my firmware was originally developed using CubeMX v6.11.0. I'm trying to determine whether the problem lies in the new app version, CubeMX updates, or a combination of both.
Are there any breaking changes or modifications in OTA behavior with ST BLE Toolbox v1.4.3?
Has the OTA protocol or image transfer mechanism changed (e.g., chunk size, MTU, characteristic behavior)?
Are there any BLE stack or middleware changes in CubeMX v6.14.0 that could impact OTA functionality, especially when using custom characteristics instead of the default?
This issue is blocking OTA functionality in production, so any clarification or guidance would be greatly appreciated.
Thanks
2025-04-07 10:12 AM
Hello @Dhruvbusa
I've escalated this behavior to the concerned team to be considered on the coming release (under internal ticket number 206990).
Best Regards.
STTwo-32
To give better visibility on the answered topics, please click on Accept as Solution on the reply which solved your issue or answered your question.