LP-CC2652RB: Sleep mode basic questions

makerwolf

Part Number: LP-CC2652RB

Hello, please apologize the simple question, but I am struggling again to find the right documentation.

I am developing a sleep zed sensor that should periodically wake up, do measuements, report if values have changed and go back to sleep. it has one button which should also wake the device up and run the same measurement/report code.

As far as I have understood, a sleepy end device would automatically go to sleep? But how would I get the device to wake up after a specified period?

thank you!

over 3 years ago

+1 Ryan Brown1 over 3 years ago

TI__Guru**** 219577 points

Hello makerwolf,

Sleepy ZEDs are designed to go to sleep any time the MCU is in the idle state, essentially meaning that no other tasks are active and running. This can be interrupted any time the application task code execution is triggered by a hardware interrupt, for example a GPIO or timer. Hence you should initialize a clock, much like zclSampleSw_initializeClocks does for EndDeviceRejoinClk, in order to wake up periodically. There is also a Functional Clock description in the Z-Stack User's Guide.

Regards,
Ryan

0 YiKai Chen over 3 years ago

Guru 735695 points

Yes, a sleeping end device would automatically go to sleep and you can setup timer event to wake up SOC.

0 makerwolf over 3 years ago

Prodigy 130 points

thank you very much! love the simplicity.

0 makerwolf over 3 years ago

Prodigy 130 points

So, if a zed device still consumes 1.9mA while Idle, I suppose that means there is still a task busy? How would I go about finding out which task this is, oder is there maybe some configuration that I overlooked?

0 YiKai Chen over 3 years ago in reply to makerwolf

Guru 735695 points

You should check if there is busy loop in your system or if all IO pins are set properly.

0 makerwolf over 3 years ago in reply to YiKai Chen

Prodigy 130 points

if you have any hints on how to find otu which loop is busy, I'm all ears! I've had very little luck using the debugger so far. It skips around code lines in random order and does not display a lot of variables. I feel like driving blind when I try using it ...

regardless, by searching other forum threads it seems I've figured out the issue, by enabling CUI_DISABLE preprocessor flag the idle current goes down to 14µA. I have yet to find the part of the documentation that mentions this, but i'm glad I found it. Now I only need to refactor the code for my single button out of the UI code that gets disabled by this flag. Should be no problem.

+1 Ryan Brown1 over 3 years ago in reply to makerwolf

TI__Guru**** 219577 points

Please refer to the Power Configuration and Debugging sections of the Z-Stack User's Guide. Removing compiler optimizations from the project settings will increase the debugger interface's fluency.

Regards,
Ryan

Zigbee & Thread

Zigbee & Thread forum

LP-CC2652RB: Sleep mode basic questions