CC2652R7: Max limit for creating the Clock instances using the API "Util_constructClock"

srinivasa rao veeravalli

Part Number: CC2652R7

Hi Team,

As part of our development with the CC2652r7 we are using the timer related API's like '' Util_constructClock"to create the timer instancess based on some BLE messages.

we have doubt on timer instancess, by using the same clock ID how many clock instancess we can create with differnt timeout values.

For Eg: For every BLE request message we are creating the soft timer instancess for giving the reply for each request message with certain delay among between different requests.

Regards,

Srinivas.V

6 days ago

0 Lea 6 days ago

TI__Expert 5910 points

Hi !

You should be using only one timer instance per Clock_Struct object you have. In your example where you are creating a timer instance per BLE request, I am recommending you to dynamically allocate a Clock_Struct object, and to add call Util_constructClock on it. Once you have finished processing and responding to the BLE message, you can call the Clock_destruct function and then free the Clock_Struct object you have created.

Kind regards,
Lea

0 Ryan Brown1 6 days ago

TI__Guru**** 218697 points

Hi Srinivas,

I'm assuming this is based on a related thread: CC2652R7: Device(CC2652R7) is going to Brick state in Run time over period of time.

Here is the similar documentation for your v5.20 SDK

https://dev.ti.com/tirex/content/simplelink_cc13xx_cc26xx_sdk_5_30_01_01/docs/ble5stack/ble_user_guide/html/ble-stack-tirtos/clocks.html
https://dev.ti.com/tirex/content/simplelink_cc13xx_cc26xx_sdk_5_30_01_01/docs/ble5stack/ble_user_guide/doxygen/ble/html/group___util.html

I recommend that you re-use clock instances instead of creating new ones for each BLE message trigger.

Regards,
Ryan

Bluetooth®︎

Bluetooth forum

CC2652R7: Max limit for creating the Clock instances using the API "Util_constructClock"