• State Resolved
  • Locked Locked
  • Replies 4 replies
  • Subscribers 51 subscribers
  • Views 520 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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: ANCS caller information not receiving

vignesh s
Intellectual 512 points
Part Number: CC2340R5

Hi,

We are using CC2340R5 basic ble oad peripheral code with ANCS and basic ble peripheral code with ANCS SDK :  simplelink_lowpower_f3_sdk_7_10_00_35. I have connected my Iphone and notifications has enabled, when i tried to call to that iphone and caller  information receiving in my peripheral device. When after eighth  call caller  information not receiving in my peripheral device. Same project tried in  SDK :  simplelink_lowpower_f3_sdk_7_20_00_29 When after nineth, call caller  information not receiving in my peripheral device. Same project tried in  SDK : simplelink_lowpower_f3_sdk_7_20_01_10 When after seventh, call caller  information not receiving in my peripheral device. Module restart is required to get the call information. So upon every module power restart , only seven call information receiving in peripheral device .

 We have tried modifying the connection interval and stack size and heap size also. 

CCS: code Composer Studio 12.3.0   - SDK :  simplelink_lowpower_f3_sdk_7_10_00_35

CCS: code Composer Studio 12.4.0   - SDK :  simplelink_lowpower_f3_sdk_7_20_00_29

CCS: code Composer Studio 12.5.0   - SDK : simplelink_lowpower_f3_sdk_7_20_01_10


Same ANCS working fine with CC2642 and CC2640R5.

Thank you.

  • +1
    TI__Guru** 101450 points

    Hi Vignesh,

    Thank you for reaching out.

    I am afraid it is a bit difficult for me to comment here as I do not have access to the code you are running on the CC2340R5.

    In general, I would recommend to leverage the Debugging Guide.This way you could assess whether the device is entering an error loop. The ROV could also be leveraged in order to verify the heap and tasks' stacks.

    I hope this will help,

    Best regards,

  • 0
    TI__Guru** 101450 points

    Hi,

    For other readers, the issue seems to be caused by some notification data not being properly freed. The fix consists in ensuring the data is freed.

     In app_data.c > GATT_EventHandler, at the end of the case “ATT_HANDLE_VALUE_NOTI” (line 159 for me) please add the following line:

    GATT_bm_free(&(gattMsg->msg), ATT_HANDLE_VALUE_NOTI);

    Best regards,

  • 0 in reply to Clément
    Intellectual 512 points

    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.

    CCS: code Composer Studio 12.5.0   - SDK : simplelink_lowpower_f3_sdk_7_20_01_10

    thanks,

    Vignesh.