Unknown HCI errors

[Marius Heil]

Hi,

I do receive undefined HCI errors in my disconnection handler. I wait for the BLE_GAP_EVT_DISCONNECTED event and use the bleEvent->evt.gap_evt.params.disconnected.reason parameter to find out the status code which I do then compare with the list of possible errors. But i often receive HCI error 62 (0x3E) and sometimes others. Is that a known issue?

Thanks

[Ulrich Myhre]

Hi Marius,

What do you mean by undefined? 0x3E is defined as BLE_HCI_CONN_FAILED_TO_BE_ESTABLISHED in ble_hci.h. It means that the initiator found a device to connect to, but failed during the actual connection establishment. This can be due to white-listing on the peer, range or CRC errors/collisions on air at the same time as the connect request was sent. Collisions can happen due to other initiators connecting or active scanners sending a scan request.

Search of BLE_HCI_CONN_FAILED_TO_BE_ESTABLISHED or 0x3E here on DevZone to find threads like this one or perhaps the answer to this thread that explains this behavior better.

[Marius Heil]

Oh, I am very sorry. It seems like my header file was outdated. Thanks a lot for clarifying the error message :-)