![]() |
nrfxlib API 3.3.99
|
Disconnection Complete. More...
#include <sdc_hci_evt.h>
Data Fields | |
| uint8_t | status |
| uint16_t | conn_handle |
| uint8_t | reason |
Disconnection Complete.
The description below is extracted from Core_v6.3, Vol 4, Part E, Section 7.7.5
This event occurs when a connection is terminated. The status parameter indicates if the disconnection was successful or not. The reason parameter indicates the reason for the disconnection if the disconnection was successful. If the disconnection was not successful, then the value of the reason parameter shall be ignored by the Host. For example, this can be the case if the Host has issued the HCI_Disconnect command and there was a parameter error, or the command was not presently allowed, or a Connection_Handle that didn’t correspond to a connection was given.
If Connection_Handle identifies a CIS on the Central, then the handle and the associated data paths of that CIS shall remain valid (irrespective of whether the disconnection was successful or not). If Connection_Handle identifies a CIS on the Peripheral and Status is zero, then the handle and the associated data path of that CIS shall be deleted. If Connection_Handle identifies any other kind of connection and Status is zero, then the handle shall be deleted. If Connection_Handle identifies an LE ACL connection and Status is zero, then any associated CS configurations shall also be deleted.
Note: When a physical link fails, one HCI_Disconnection_Complete event will be returned for each logical channel on the physical link with the corresponding Connection_Handle as a parameter.