From a2366dc9d3f08dc0fdccdbd6a3fd7082b0737f83 Mon Sep 17 00:00:00 2001 From: Pete Blois Date: Mon, 30 Mar 2015 13:17:10 -0700 Subject: [PATCH] Setting correct length for BTSTACK_EVENT_STATE event. The second byte of the data is the length of the remaining data (in this case the HCI_STATE_WORKING byte). This was passing 0 indicating that there was no data when in fact there was. --- ble/sm.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/ble/sm.c b/ble/sm.c index 6143f8e01..de7205e53 100644 --- a/ble/sm.c +++ b/ble/sm.c @@ -1365,7 +1365,7 @@ static void sm_handle_encryption_result(uint8_t * data){ // SM INIT FINISHED, start application code - TODO untangle that if (sm_client_packet_handler) { - uint8_t event[] = { BTSTACK_EVENT_STATE, 0, HCI_STATE_WORKING }; + uint8_t event[] = { BTSTACK_EVENT_STATE, 1, HCI_STATE_WORKING }; sm_client_packet_handler(HCI_EVENT_PACKET, 0, (uint8_t*) event, sizeof(event)); } return; @@ -2186,4 +2186,4 @@ void gap_random_address_set_update_period(int period_ms){ if (gap_random_adress_type == GAP_RANDOM_ADDRESS_TYPE_OFF) return; gap_random_address_update_stop(); gap_random_address_update_start(); -} \ No newline at end of file +}