This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

CC2340R5: Issue with continuous connection and disconnection

Part Number: CC2340R5

Hi,

      We are using CC2340R5  basic ble peripheral code with ANCS and I have addressed an issue where look at the TI forum thread link 

https://e2e.ti.com/support/wireless-connectivity/bluetooth-group/bluetooth/f/bluetooth-forum/1286109/cc2340r5-ancs-caller-information-not-receiving 

Then I have added GATT_bm_free(&(gattMsg->msg), ATT_HANDLE_VALUE_NOTI); in In app_data.c > GATT_EventHandler, at the end of the case “ATT_HANDLE_VALUE_NOTI”.when i tried to call to that iPhone and caller  information receiving in my peripheral device  receiving n number of times but facing the other issues and the test cases listed below 

 And here the test cases: 

 Test Case 1: Basic_ble with ANCS implementation.(iPhone) 

  1. Connecting to the BLE module--> pairing --> notification enabled.
  2. After successful connection making the incoming call to the connected mobile with the module. Module receives the incoming notification in UART.
  3. Now I am to terminate the connection by disabling the Bluetooth from the mobile Bluetooth settings and after few seconds enabling the Bluetooth from the settings mobile will auto connect to the module.
  4. After multiple connection and disconnection mobile and module indicates in connected state but making the incoming call to the connected mobile with the module. Module will not receive the incoming notification in UART.
  5. When this condition occurs module need a power reset to recover. 

 Test Case 2: Basic_ble with ANCS implementation.(Android) 

  1. Connecting to the BLE module--> pairing --> notification enabled.
  2. Now I am to terminate the connection by disabling the Bluetooth from the mobile Bluetooth settings and after few seconds enabling the Bluetooth from the NRF application.
  3. After multiple connection and disconnection module is not advertising(weather advertisement is happening or not conformed using spectrum analyser and module current).
  4. When this condition occurs module need a power reset to recover.

Note : These issues facing before and after the implementation of GATT_bm_free(&(gattMsg->msg), ATT_HANDLE_VALUE_NOTI);

CCS: code Composer Studio 12.5.0   - SDK : simplelink_lowpower_f3_sdk_7_20_01_10

thanks,

Vignesh.

  • Hi Vignesh,

    Thank you for reaching out. Do you have access to a BLE packet sniffer? If so, then could you take a sniffer log of the over the air activity occuring leading up to the hanging behavior? Are you also able to recreate the behavior while the device is in debug mode, pause execuation, and share the call stack?

    Best Regards,

    Jan