RE: What does the BLE event 0x57 mean?

timapus — Sat, 15 Jun 2019 07:35:36 GMT

It is very helpful, thanks!

RE: What does the BLE event 0x57 mean?

hmolesworth — Fri, 14 Jun 2019 22:15:28 GMT

This helps; I'm showing decimal instead of hex, but 0x57 = 87 decimal. I like to see all events without having to search for them, note the ones handled elsewhere in ble_gap_event() are simply commented out as they already have a trace message - start by uncommenting all then comment out the duplicates:.

 //      case BLE_GAP_EVT_ADV_REPORT: //      case BLE_GAP_EVT_CONNECTED: //      case BLE_GAP_EVT_DISCONNECTED: //      case BLE_GAP_EVT_CONN_PARAM_UPDATE: //      case BLE_GAP_EVT_SEC_PARAMS_REQUEST: case BLE_GAP_EVT_SEC_INFO_REQUEST: case BLE_GAP_EVT_PASSKEY_DISPLAY: case BLE_GAP_EVT_KEY_PRESSED: case BLE_GAP_EVT_AUTH_KEY_REQUEST: case BLE_GAP_EVT_LESC_DHKEY_REQUEST: case BLE_GAP_EVT_AUTH_STATUS: case BLE_GAP_EVT_CONN_SEC_UPDATE: //      case BLE_GAP_EVT_TIMEOUT: //      case BLE_GAP_EVT_RSSI_CHANGED: //      case BLE_GAP_EVT_ADV_REPORT: case BLE_GAP_EVT_SEC_REQUEST: //      case BLE_GAP_EVT_CONN_PARAM_UPDATE_REQUEST: case BLE_GAP_EVT_SCAN_REQ_REPORT: //      case BLE_GAP_EVT_PHY_UPDATE_REQUEST: //      case BLE_GAP_EVT_PHY_UPDATE: case BLE_GAP_EVT_DATA_LENGTH_UPDATE_REQUEST: case BLE_GAP_EVT_DATA_LENGTH_UPDATE: case BLE_GAP_EVT_QOS_CHANNEL_SURVEY_REPORT: case BLE_GAP_EVT_ADV_SET_TERMINATED:

// BLE_GATTC_EVTS - GATT case BLE_GATTC_EVT_PRIM_SRVC_DISC_RSP: case BLE_GATTC_EVT_REL_DISC_RSP: case BLE_GATTC_EVT_CHAR_DISC_RSP: case BLE_GATTC_EVT_DESC_DISC_RSP: case BLE_GATTC_EVT_ATTR_INFO_DISC_RSP: case BLE_GATTC_EVT_CHAR_VAL_BY_UUID_READ_RSP: case BLE_GATTC_EVT_READ_RSP: case BLE_GATTC_EVT_CHAR_VALS_READ_RSP: case BLE_GATTC_EVT_WRITE_RSP: case BLE_GATTC_EVT_HVX: case BLE_GATTC_EVT_EXCHANGE_MTU_RSP: //      case BLE_GATTC_EVT_TIMEOUT: case BLE_GATTC_EVT_WRITE_CMD_TX_COMPLETE:

// BLE_GATTS_EVTS - GATT case BLE_GATTS_EVT_WRITE: case BLE_GATTS_EVT_RW_AUTHORIZE_REQUEST: case BLE_GATTS_EVT_SYS_ATTR_MISSING: case BLE_GATTS_EVT_HVC: case BLE_GATTS_EVT_SC_CONFIRM: case BLE_GATTS_EVT_EXCHANGE_MTU_REQUEST: //      case BLE_GATTS_EVT_TIMEOUT: case BLE_GATTS_EVT_HVN_TX_COMPLETE: if (p_ble_evt->header.evt_id { NRF_LOG_INFO("p_ble_evt: } else { NRF_LOG_INFO("Unhandled } break;

// BLE_GAP_EVTS - GAP Event IDs - uniquely identify an event coming from the stack to the application // 16 Connected to peer // 17 Disconnected from peer // 18 Connection Parameters updated // 19 Request to provide security parameters // 20 Request to provide security information // 21 Request to display a passkey to the user // 22 Notification of a keypress on the remote device // 23 Request to provide an authentication key // 24 Request to calculate an LE Secure Connections DHKey // 25 Authentication procedure completed with status // 26 Connection security updated // 27 Timeout expired // 28 RSSI report // 29 Advertising report // 30 Security Request // 31 Connection Parameter Update Request // 32 Scan request report // 33 PHY Update Request // 34 PHY Update Procedure is complete // 35 Data Length Update Request // 36 LL Data Channel PDU payload length updated // 37 Channel survey report // 38 Advertising set terminated Client Event IDs // 48 Primary Service Discovery Response event // 49 Relationship Discovery Response event // 50 Characteristic Discovery Response event // 51 Descriptor Discovery Response event // 52 Attribute Information Response event // 53 Read By UUID Response event // 54 Read Response event // 55 Read multiple Response event // 56 Write Response event // 57 Handle Value Notification or Indication event // 58 Exchange MTU Response event // 59 Timeout event // 60 Write without Response transmission complete Server Event IDs. // 80 Write operation performed // 81 Read/Write Authorization request // 82 A persistent system attribute access is pending // 83 Handle Value Confirmation // 84 Service Changed Confirmation // 85 Exchange MTU Request // 86 Peer failed to respond to an ATT request in time // 87 Handle Value Notification transmission complete < NUM_BLE_EVENTS) %d %s",p_ble_evt->header.evt_id, ble_evt_description[p_ble_evt->header.evt_id]); p_ble_evt->header.evt_id: %d",p_ble_evt->header.evt_id);

This is the text description array, verbose but helpful:

// BLE_GAP_EVTS - GAP Event IDs - uniquely identify an event coming from the stack to the application
static char * ble_evt_description[] =
{
/*                                           */ " 0 ?",
/*                                           */ " 1 ?",
/*                                           */ " 2 ?",
/*                                           */ " 3 ?",
/*                                           */ " 4 ?",
/*                                           */ " 5 ?",
/*                                           */ " 6 ?",
/*                                           */ " 7 ?",
/*                                           */ " 8 ?",
/*                                           */ " 9 ?",
/*                                           */ "10 ?",
/*                                           */ "11 ?",
/*                                           */ "12 ?",
/*                                           */ "13 ?",
/*                                           */ "14 ?",
/*                                           */ "15 ?",
/* BLE_GAP_EVT_ADV_REPORT:					 */
/* BLE_GAP_EVT_CONNECTED:                    */ "16 Connected to peer",
/* BLE_GAP_EVT_DISCONNECTED:                 */ "17 Disconnected from peer",
/* BLE_GAP_EVT_CONN_PARAM_UPDATE:            */ "18 Connection Parameters updated",
/* BLE_GAP_EVT_SEC_PARAMS_REQUEST:           */ "19 Request to provide security parameters",
/* BLE_GAP_EVT_SEC_INFO_REQUEST:             */ "20 Request to provide security information",
/* BLE_GAP_EVT_PASSKEY_DISPLAY:              */ "21 Request to display a passkey to the user",
/* BLE_GAP_EVT_KEY_PRESSED:                  */ "22 Notification of a keypress on the remote device",
/* BLE_GAP_EVT_AUTH_KEY_REQUEST:             */ "23 Request to provide an authentication key",
/* BLE_GAP_EVT_LESC_DHKEY_REQUEST:           */ "24 Request to calculate an LE Secure Connections DHKey",
/* BLE_GAP_EVT_AUTH_STATUS:                  */ "25 Authentication procedure completed with status",
/* BLE_GAP_EVT_CONN_SEC_UPDATE:              */ "26 Connection security updated",
/* BLE_GAP_EVT_TIMEOUT:                      */ "27 Timeout expired",
/* BLE_GAP_EVT_RSSI_CHANGED:                 */ "28 RSSI report",
/* BLE_GAP_EVT_ADV_REPORT:                   */ "29 Advertising report",
/* BLE_GAP_EVT_SEC_REQUEST:                  */ "30 Security Request",
/* BLE_GAP_EVT_CONN_PARAM_UPDATE_REQUEST:    */ "31 Connection Parameter Update Request",
/* BLE_GAP_EVT_SCAN_REQ_REPORT:              */ "32 Scan request report",
/* BLE_GAP_EVT_PHY_UPDATE_REQUEST:           */ "33 PHY Update Request",
/* BLE_GAP_EVT_PHY_UPDATE:                   */ "34 PHY Update Procedure is complete",
/* BLE_GAP_EVT_DATA_LENGTH_UPDATE_REQUEST:   */ "35 Data Length Update Request",
/* BLE_GAP_EVT_DATA_LENGTH_UPDATE:           */ "36 LL Data Channel PDU payload length updated",
/* BLE_GAP_EVT_QOS_CHANNEL_SURVEY_REPORT:    */ "37 Channel survey report",
/* BLE_GAP_EVT_ADV_SET_TERMINATED:           */ "38 Advertising set terminated",
/*                                           */ "39 ?",
/*                                           */ "40 ?",
/*                                           */ "41 ?",
/*                                           */ "42 ?",
/*                                           */ "43 ?",
/*                                           */ "44 ?",
/*                                           */ "45 ?",
/*                                           */ "46 ?",
/*                                           */ "47 ?",
/*LE_GATTC_EVTS - GATT Client Event IDs      */
/* BLE_GATTC_EVT_PRIM_SRVC_DISC_RSP:         */ "48 Primary Service Discovery Response event",
/* BLE_GATTC_EVT_REL_DISC_RSP:               */ "49 Relationship Discovery Response event",
/* BLE_GATTC_EVT_CHAR_DISC_RSP:              */ "50 Characteristic Discovery Response event",
/* BLE_GATTC_EVT_DESC_DISC_RSP:              */ "51 Descriptor Discovery Response event",
/* BLE_GATTC_EVT_ATTR_INFO_DISC_RSP:         */ "52 Attribute Information Response event",
/* BLE_GATTC_EVT_CHAR_VAL_BY_UUID_READ_RSP:  */ "53 Read By UUID Response event",
/* BLE_GATTC_EVT_READ_RSP:                   */ "54 Read Response event",
/* BLE_GATTC_EVT_CHAR_VALS_READ_RSP:         */ "55 Read multiple Response event",
/* BLE_GATTC_EVT_WRITE_RSP:                  */ "56 Write Response event",
/* BLE_GATTC_EVT_HVX:                        */ "57 Handle Value Notification or Indication event",
/* BLE_GATTC_EVT_EXCHANGE_MTU_RSP:           */ "58 Exchange MTU Response event",
/* BLE_GATTC_EVT_TIMEOUT:                    */ "59 Timeout event",
/* BLE_GATTC_EVT_WRITE_CMD_TX_COMPLETE:      */ "60 Write without Response transmission complete",
/*                                           */ "61 ?",
/*                                           */ "62 ?",
/*                                           */ "63 ?",
/*                                           */ "64 ?",
/*                                           */ "65 ?",
/*                                           */ "66 ?",
/*                                           */ "67 ?",
/*                                           */ "68 ?",
/*                                           */ "69 ?",
/*                                           */ "70 ?",
/*                                           */ "71 ?",
/*                                           */ "72 ?",
/*                                           */ "73 ?",
/*                                           */ "74 ?",
/*                                           */ "75 ?",
/*                                           */ "76 ?",
/*                                           */ "77 ?",
/*                                           */ "78 ?",
/*                                           */ "79 ?",
/*LE_GATTS_EVTS - GATT Server Event IDs.     */
/* BLE_GATTS_EVT_WRITE:                      */ "80 Write operation performed",
/* BLE_GATTS_EVT_RW_AUTHORIZE_REQUEST:       */ "81 Read/Write Authorization request",
/* BLE_GATTS_EVT_SYS_ATTR_MISSING:           */ "82 A persistent system attribute access is pending",
/* BLE_GATTS_EVT_HVC:                        */ "83 Handle Value Confirmation",
/* BLE_GATTS_EVT_SC_CONFIRM:                 */ "84 Service Changed Confirmation",
/* BLE_GATTS_EVT_EXCHANGE_MTU_REQUEST:       */ "85 Exchange MTU Request",
/* BLE_GATTS_EVT_TIMEOUT:                    */ "86 Peer failed to respond to an ATT request in time",
/* BLE_GATTS_EVT_HVN_TX_COMPLETE:            */ "87 Handle Value Notification transmission complete",
};
#define NUM_BLE_EVENTS (sizeof(ble_evt_description)/sizeof(ble_evt_description[0]))

And a few safety checks:

STATIC_ASSERT(BLE_GAP_EVT_CONNECTED            == 0x10, "Enum Check Fails - BLE_GAP_EVTS");
STATIC_ASSERT(BLE_GATTC_EVT_PRIM_SRVC_DISC_RSP == 0x30, "Enum Check Fails - BLE_GATTC_EVTS");
STATIC_ASSERT(BLE_GATTS_EVT_WRITE              == 0x50, "Enum Check Fails - BLE_GATTS_EVTS");
STATIC_ASSERT(BLE_GAP_EVT_ADV_SET_TERMINATED       == 38, "Enum Check Fails - BLE_GAP_EVTS");
STATIC_ASSERT(BLE_GATTC_EVT_WRITE_CMD_TX_COMPLETE  == 60, "Enum Check Fails - BLE_GATTC_EVTS");
STATIC_ASSERT(BLE_GATTS_EVT_HVN_TX_COMPLETE        == 87, "Enum Check Fails - BLE_GATTS_EVTS");

RE: What does the BLE event 0x57 mean?

timapus — Fri, 14 Jun 2019 21:38:11 GMT

Thank you!

RE: What does the BLE event 0x57 mean?

natersoz — Mon, 10 Jun 2019 03:48:19 GMT

See the file in the SDK :

nRF5_SDK_15.3.0_59ac345/components/softdevice/s132/headers/ble_gatts.h

I'm referencing the softdevice 132, but the others will be the same.

Search for enum BLE_GATTS_EVT. Line 89.

You will see that the first entry in the enum is BLE_GATTS_EVT_BASE. You can find that value in ble_ranges.h (same directory).

The value of BLE_GATTS_EVT_BASE is 0x50. Increment through the enum and you will find 0x57 is BLE_GATTS_EVT_HVN_TX_COMPLETE.

That event means that your indication or notification as been transmitted, and if I understand the softdevice correctly, the packets successfully received by the peer at the link layer.

Your data made it! Party time.

I highly recommend that you employ an editor with tagging capabilities and tag the softdevice and portions of the SDK you intend to use (or perhaps all of it).