RTOS/LAUNCHXL-CC26X2R1: Using Clock function or Creating another Task?

Trevor Hsu

Genius 4585 points

Part Number: LAUNCHXL-CC26X2R1

Tool/software: TI-RTOS

We have a user case that needs to read the GPIO status every 500ms.

Currently, I just use Clock function to do the job, and have not encountered any problems.

But I found a note from BLE_User_Guide:

Attention

Clock functions must not call blocking kernel APIs or TI-RTOS driver APIs! Executing long routines will impact real-time constraints placed in high priority tasks allocated for wireless protocol stacks!

It looks like that I can't use the clock function to read the GPIO status, right?

thanks

Trevor

over 6 years ago

0 Severin Suveren over 6 years ago

TI__Mastermind 23730 points

Reading a value from a GPIO pin in a Clock function is fine, as it is a very fast operation with minimal overhead.

0 Trevor Hsu over 6 years ago in reply to Severin Suveren

Genius 4585 points

HI Severin Suveren,

Thanks for your reply, Could you help confirm that the following driver APIs can be run in the clock function?

ADC_convert();
I2C_transfer()
SPI_transfer()
UART_read();
UART_write();

thanks.

Trevor

0 Severin Suveren over 6 years ago in reply to Trevor Hsu

TI__Mastermind 23730 points

Any blocking operations should be avoided. ADC_convert() is a blocking operation and should be avoided.

All other functions support asynchronous operations (sometimes called callback mode), which is fine. However, is blocking mode is used, then they should be avoided.

0 Trevor Hsu over 6 years ago in reply to Severin Suveren

Genius 4585 points

Hi Severin Suveren,

I got it, thank you.

Trevor

Bluetooth®︎

Bluetooth forum

RTOS/LAUNCHXL-CC26X2R1: Using Clock function or Creating another Task?