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.

CC2642R: Forcing CC2642R standby mode by the application

Part Number: CC2642R

Can the user (application) force the CC2642R to switch from active/idle to standby mode in order to save power or is it managed independently by the CC2642R?

Use case : Working at active mode for a short period of time for various system calculation -> entering standby mode for predefined period and waking back to active mode upon that time period (repeating this process)

  • I suppose you are running BLE application and you can use simple_peripheral, which enable POWER_SAVING and would go to standby mode when there is nothing to handle. Your application can setup periodic event to handle its tasks and the device would go back sleeping automatically after exiting the event.

  • I use the BLE of the CC2642R about 1% of the time - only for maintenance. Most of the time it is not connected to other BLE devices. It manages other peripherals and doing calculations. It is required to receive data from other components through UART -> do some calculations and switch to stand by mode for a specific period of time. After that period of time it should switch to active -> do the calculation again and go back to stand by. I can use an external peripheral to wake it from stand by using GPIO but can I periodically switch to stand by upon application request (after finishing the calculation) and from stand by to active upon internal timer?

  • Yes, you can create a periodic event to wakeup CC2642R from standby.

  • Thank you for the information. If I can create an internal event to wakeup CC2642R from standby (for example using a timer), Can I also create an internal event to enter into standby from active mode (under the required policy and requirements)?

  • As I had replied, CC2642R running simple_peripheral would enter standby mode automatically when there is nothing to process and I don't think your application has to take care of this.