RTOS/CC2652R: changing Semaphore_pend from BIOS_WAIT_FOREVER to BIOS_NO_WAIT

Walter Macamos

Part Number: CC2652R

Tool/software: TI-RTOS

Hi TI Team,

Originally in zed_switch, you use Semaphore_pend with BIOS_WAIT_FOREVER in zclSampleSw_process_loop function.

I tried to make it unblocking BIOS_NO_WAIT or some timeout value (40ms) but I encountered erratic problem of always getting commissioning notification forever.

Is it recommended to do this?

By the way, the purpose of using unblocking is because I wanted to initialize the watchdog in the for loop.

Regards,

Walter

over 4 years ago

0 IUsedToBeARealPerson (M-W) over 4 years ago

TI__Guru 58425 points

Hi Walter,

I would not recommend such changes unless you can verify the program flow. If the example is designed to block until the semaphore is released, then releasing this pre-maturely is not a good idea. To what degree do you want to initialize the WD, can you not do this earlier in the application as part of the initialization process?

0 Walter Macamos over 4 years ago in reply to IUsedToBeARealPerson (M-W)

Genius 5345 points

Hi M-W,

I agree, we can init WD in int process.
There is only 1 loop here. I use this for clearing the WD timer periodically.
Best Regards,
Walter

0 IUsedToBeARealPerson (M-W) over 4 years ago in reply to Walter Macamos

TI__Guru 58425 points

Hi Walter,

I would then suggest you look into an alternative way of clearing the WD timer, possibly using a Clock instance for example.

0 Walter Macamos over 4 years ago in reply to IUsedToBeARealPerson (M-W)

Genius 5345 points

Hi M-W,

Thanks for your positive feedback.

Regards,
Walter

Zigbee & Thread

Zigbee & Thread forum

RTOS/CC2652R: changing Semaphore_pend from BIOS_WAIT_FOREVER to BIOS_NO_WAIT