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.

CC2745R10-Q1: Processing of Connection Event Callback Function

Part Number: CC2745R10-Q1

I am considering a process based on basic_ble to obtain and display the RSSI when a connection event occurs. I have implemented a similar function on the CC2652 (simple_peripheral), where the connection event callback function stores the data in a message queue, and the processing is done when there is a message in the queue. It seems that basic_ble does not have such processing.

My question is, is it acceptable to display the information of the connection report structure within the connection event callback function? Or is it better to use a queue? 

 

 

Best regards.

 

  • Hello Yamanaka-san,

    Basic_BLE does have this functionality. The project uses a message queue system to indicate the application when specific functions are completed or starting. The processing can be done within the event, or you can use BLEAppUtil_invokeFunction() to add a function to the queue.

    The BLEAPPUTIL_CONN_NOTI_CONN_EVENT_ALL can be used to look at the RSSI or other connection event information. On Basic_BLE you will need to create a new event handler to track the BLEAppUtil_ConnEventNotiEventMaskFlags_e events. You can display information from each connection event on from the queue of events. Notice, this is already done with the events already implemented within Basic_BLE. 

    Let me know if you have any questions. 

    Thanks,

    Isaac

  • Hi,

    Thank you for your response. I have a few questions.

    > or you can use BLEAppUtil_invokeFunction() to add a function to the queue.

    I understand that this function puts the message in a queue, but how do I dequeue it?

    > On Basic_BLE you will need to create a new event handler to track the BLEAppUtil_ConnEventNotiEventMaskFlags_e events.

    It says to create an event handler, does this mean that it will determine the message taken from the queue and process it?

    > Notice, this is already done with the events already implemented within Basic_BLE. 

    What does this mean? Does it mean that there is a part of the function that retrieves information from the connection report structure that can be retrieved when a connection event occurs?

    I apologize for my limited understanding.

    I look forward to your continued support.

  • Hello Yamanaka-san, 

    My last response is incorrect. I noticed you opened another thread about this issue. I will close this thread and respond on the new thread. 

    For future reference, please do not open repeat threads with the same question. 

    Thanks,
    Isaac

  • Hi,

    I apologize. I will post it in another thread.

    Thank you very much.