Cannot stop advertising BLE

RE: Cannot stop advertising BLE

Einar Thorsrud — Fri, 18 Aug 2023 07:15:59 GMT

Hi Xander,

[quote user="Xander To"]However, isn’t it weird that the board crash when I change the BLe status code? Can it be possible?[/quote]

It depends on what you mean by "crash" and what actually happens with the board. Withoug debugging we don't know what is happening, but most likely there is a good explanation. So I am looking forward to seeing what you find from debugging (starting with the error code).

[quote user="Xander To"]UPDATE: After a bit of testing, I believe calling the advertising_stop() to soon after disconnectBLE() can cause advertising not to be stopped. Therefore, I change the advertise config to not advertise after disconnect and restart advertising wherever I want.[/quote]

Sounds good, that is a much better approach in this case (automatically re-starting advertising mostly makes sense if you always want to start advertising after a disconnect).

Br,

Einar

RE: Cannot stop advertising BLE

Xander To — Thu, 17 Aug 2023 15:23:53 GMT

Hi Einar,

I will check the error code once we get a J-Link/DK to debug as I’m working on a custom board at the moment. However, isn’t it weird that the board crash when I change the BLe status code? Can it be possible?

Regarding the advertising issue, the advertising_stop is called after the disconnection is executed, so I still don’t understand why BLE is still advertised. Does it mean I call this function to fast and the disconnectBLE function doesn’t have enough time to actually disconnect BLE and start advertising BLE?

UPDATE: After a bit of testing, I believe calling the advertising_stop() to soon after disconnectBLE() can cause advertising not to be stopped. Therefore, I change the advertise config to not advertise after disconnect and restart advertising wherever I want.

Best regards,

Xander

RE: Cannot stop advertising BLE

Einar Thorsrud — Thu, 17 Aug 2023 12:39:55 GMT

Hi Xander,

[quote user=""]However, the board crashes when it encounters the APP_ERROR_CHECK line of disconnectBLE function. Therefore, I removed the APP_ERROR_CHECK line. I know this is not good but just for testing. This time, the board doesn't terminate the BLE and the board doesn't crash of course.[/quote]

This indicates that the "crash" was that APP_ERROR_CHECK() was called with an error code. Have you checked what the error code was? A simple way to do it could be to enable debug logging (enable logging, and build with DEBUG and DEBUG_NRF enabled). Or just inspect from a debugger.

Also, sometimes it can be OK to ignore an error, but then that specific error should be handled explicitly, and you should know why you get it and why it is OK to ignore it (the same way as you do with NRF_ERROR_INVALID_STATE).

[quote user=""]Secondly, the advertising_stop() function doesn't stop advertising after a disconnection as I can still scan for its BLE after the board terminates the connection. Did I do it incorrectly?[/quote]

Based on what you write, the advertising module should be configured to start advertising after a connection is terminated. And that will happen even if you have stopped advertising before (while a connection was active). So you would have to stop advertising again. Or change your approach and set ble_adv_on_disconnect_disabled to true, and handle starting of advertising after disconnects yourself (to only do it when you want to).

Einar