OTA_REBOOT_REQUEST characteristic not displaying "Upload File" option

[ShenChuanAn]

I created the OTA application by following this YouTube video:
https://www.youtube.com/watch?v=mRzZOa3jmuM&list=PLnMKNibPkDnG9JRe2fbOOpVpWY7E4WbJ-&index=14https://www.youtube.com/watch?v=mRzZOa3jmuM&list=PLnMKNibPkDnG9JRe2fbOOpVpWY7E4WbJ-&index=13

After performing an OTA update using the OTA application I created, the OTA_ReBoot characteristic does not show the "Upload File" button—only a Write button is visible, as shown in Figure 1.

The settings for OTA_REBOOT_REQUEST were configured based on Table 1 in AN5247 (see Figure 2).

So my questions are:

1. How should I modify the configuration to make the OTA_ReBoot characteristic appear as shown in Figure 3 (with an "Upload File" button)?

2. Alternatively, if I don't modify the program, can the OTA upgrade still proceed normally in the next update?

[FilipKremen · Accepted solution]

Hello,

the "Reboot on OTA app" section is implemented probably only for P2PServerOTA and HeartRateOTA example.

However, you can write to the OTA REBOOT REQUEST characteristic (for example "010710" (HEX) to reboot).

You should modify the project if you want to use OTA.

Best regards,

Filip Kremen

[ShenChuanAn]

Hello Filip,

Thank you for the clarification.

If I would like to implement OTA functionality in my own project (not based on P2PServerOTA or HeartRateOTA), could you please advise what specific modifications I need to make? For example:

What services and characteristics need to be added?

Which files or functions from the OTA example should be integrated?

How should I handle the OTA Reboot Request characteristic and its associated command (e.g., "010710")?

Are there any required changes in the linker script or bootloader settings?

Any guidance or reference to relevant documentation or examples would be greatly appreciated.

Best regards,

ShenChuanAn

[FilipKremen]

Hello,

you need to add REBOOT_REQUEST characteristic to be able to reboot on OTA app.

Also, you have to handle the request in the code, please check the P2PServer_OTA example. (P2PS_STM_BOOT_REQUEST_EVT)

The OTA app is flashed at 0x08000000 address, and your user app should be at 0x08007000 address.

(you need to change the address in the linker script file as it mentioned in the documents below)

I recommend having a look at these two documents where the examples are explained more in details.

Over-the-air application and wireless firmware update for STM32WB series microcontrollers - Application note

How to build wireless applications with STM32WB MCUs - Application note

If something isn't clear to you, please let me know.

Best regards,

Filip Kremen

[ShenChuanAn]

Hi Filip,

Thanks again for your help.
I've resolved the issue with the OTA update — everything is now working as expected.

However, I have one follow-up question:
You mentioned writing "010710" (in HEX) to the OTA REBOOT REQUEST characteristic to trigger a reboot. I tried it and it works, but I couldn’t find any documentation in AN5247 or the example projects explaining the meaning or structure of this specific value.

Could you please explain what "010710" represents, or point me to the relevant documentation?

Thanks again for your support.

Best regards,

Best regards,
ShenChuanAn

[FilipKremen]

Hello,

I'm glad it's working for you.

Regarding the value, please visit page 14 Table 1. Reboot request characteristics.

"01" - Boot on OTA app

"07" - first sector index where the new user app should be downloaded

"10" - number of sectors to erase

Best regards,

Filip Kremen