bt_conn_disconnect does not result in .disconnect callback

[AGeegee]

NCS3.0.0 , NRF52840

calling bt_conn_disconnect does not result in the disconnect callback being called.

the conn state seems to be stuck in BT_CONN_DISCONNECTING. I have to manually run a private function 'bt_conn_cleanup_all()' which results in the CB being called.

How can I get the disconnect callback to be called after calling the bt_conn_disconnect?

Thanks!

[Hung Bui]

Hi Adrian, 
Could you give some more info about the set up ? 
Did you call bt_conn_disconnect() from the peripheral or from the central ? 
Did you reproduce the issue in one of our sample ? Could you try with central_uart and peripheral_uart ?

[AGeegee]

Hi,

I called bt_conn_disconnect() from the main loop on the peripheral. It was not with a sample, a custom application.

The central is a Windows PC. Not able to test out the peripheral/central uart i'm afraid.

The disconnect callback DOES get called if I turn the Bluetooth on the Central off. But it does not trigger when calling bt_conn_disconnect  from the NRF52 Peripheral

[Hung Bui]

Hi, 

Have you made sure bt_conn_disconnect() doesn't return any error  ?

Please try to test with other central for example with a phone. 
Can you reproduce the issue on a sample and send it here to so we can check ? 

[AGeegee]

Yes I tried the UART example, and it worked as expected.

When I inspected my code on my application, I was calling:

mpsl_lib_uninit();

mpsl_lib_init();

Calling uninit, then init must corrupt the BT controller somehow.

[Hung Bui]

Hi Adrian, 
Could you try to put a delay between the mpsl_lib_uninit() and mpsl_lib_init() ? Say 100ms. 
It takes some time for the crystal to re-initialize.  
Could you give some more info why you want to reinitalize mpsl ? After the reinitialization how do you initialize BLE ? 
Can you reproduce the issue with a sample by adding mpsl_lib_uninit(), mpsl_lib_init() in