example:ble_app_uart + secure_bootloader
sdk:17.1
hello.
Well, a strange phenomenon occurred when I was testing the connection between our ble device and the app。
Our app uses p_manuf_specific_data to identify whether to connect.
So we call advertising_init () first and then call ble_advertising_start(&m_advertising, BLE_ADV_MODE_FAST)
to start advertisment.
Then we change the value of m_manuf_specific_data.company_identifier during program work by calling LL_BLE_SetManu(0x0d0d) or LL_BLE_SetManu(0x0f0f)
As a result, all of them are working properly. But when I reboot the device, the company_identifier changes in a strange way.
When I boot up normally, call advertising_init () first, then call LL_BLE_SetManu(0x0d0d) .company_identifier will be setting to 0x0d0d finally.
At this time, I turned the device off for entering sleep, and then turned it back on, so that he called advertising_init () first, and then called LL_BLE_SetManu(0x0f0f) .
company_identifier will change as strange as in the video,I don't know why 0x0d0d appears and don't want it to appear, will the adv data be stored in flash?
What can I do to prevent 0x0d0d from reconnecting my device to my app?
Looking forward to your reply. Thank you