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.

LP-CC2652RB: Implementing application specific logic in zclGenericApp_process_loop()

Part Number: LP-CC2652RB
Other Parts Discussed in Thread: Z-STACK

Good morning.

I'm developing a custom firmware based on zr_genericapp on some LP-CC2652RB.

Until now, i worked mainly on zcl_genericapp.c, zcl_genericapp_data.c, setting up in the zclGenericApp_Init() my custom endpoints, clusters, attributes, peripherals and a periodic timer callback.

Now, i need a place where to place my sensors and data logic (time consuming SPI and UART usage in a state machine), and if possible i don't want to block the Z-Stack process, the timer callbacks blocks it, and putting my logic in zclGenericApp_process_loop (after removing the blocking Semaphore_pend(appSemHandle, BIOS_WAIT_FOREVER )) is also not a solution.

Am i really in need of another task? If yes, do i have to take care of semaphores / mutex in any way if i have to share put in my cluster attributes?

Thank you in advance for any hint.

Roberto