CC2652R: Clock_start context and best practices

Matt Gaidica1

Part Number: CC2652R
Other Parts Discussed in Thread: SYSBIOS

I have some clocks that are being handled (Clock_start, Clock_stop) inside of HWIs, is this always a bad idea? A similar example would be, I want to stop a clock when the device disconnects which is in SimplePeripheral_processGapMessage()... is that okay?

I used the SimplePeripheral_clockHandler() for all my callbacks/timeouts, but some clocks need to stop before they timeout. In all these cases I'm not destroying or creating clocks, I'm just stopping them, and previous posts suggest even if Stop_clock is called on the same object multiple times, it does no harm.

SDK 5.20

over 4 years ago

0 Ryan Brown1 over 4 years ago

TI__Guru**** 223727 points

Hey Matt,

I think that the ti.sysbios.knl.Clock module in the TI-RTOS Kernel Runtime APIs will help provide the information you need. Clock APIs outside of construct/create/delete/destruct are callable from a HWI thread, therefore using them inside SimplePeripheral_processGapMessage is fine. And the previous posts are correct, it is fine to use Stop_clock on a clock object which is already stopped.

Regards,
Ryan

0 Matt Gaidica1 over 4 years ago in reply to Ryan Brown1

Expert 1540 points

Oh, yea that's really helpful. Thanks, Ryan!

Bluetooth®︎

Bluetooth forum

CC2652R: Clock_start context and best practices