Regarding usage of power management config files

[Priyadharshini]

Hi,

   I am using nrf5340 kit. I would like to enable and test power management in mesh chat example.

1.  Can you please tell me the usage of below config file usage.

                  #define CONFIG_PM 1
                  #define   CONFIG_PM_DEEP_SLEEP_STATES 1

                  #define CONFIG_HAS_POWER_STATE_DEEP_SLEEP_1 1

2. Can you please tell me which power mode will be default during SYSTEM ON  

                  a) CONSLAT

                   b) LOWPWR

3. Configurations which should be enabled in prj.config file for power management.

4. Also tell me how the clock initialization takes place in nrf connect sdk based codes

               a) Is this requires Zephyr rtos for initialization

                b) How the clock control is possible in application and network core

                 c) Will all the  nrf mesh examples use the network and application clocks together.

 5. Kindly tell me which config file should be enabled for waking up all the peripherals and CPU from idle state.

6. Is there examples in nrf connect sdk which explains the power and clock management code flow in a detailed way.

[Simonr]

Hi

1. I'm not sure what exact information you're after, but it is stated as follows in the nRF53430 Product Specification:

System ON sleep:

"In System ON, all functional blocks, such as the CPU and peripherals, can be in an idle or run state depending on the configuration set by the software and the state of the executing application. The network core's CPU and peripherals can be in an idle state, run state, or Force-OFF mode (see Force-OFF mode).

The PMU can switch the appropriate internal power sources on and off, depending on how much power is needed at any given time. The power requirement of a peripheral is directly related to its activity level, which increases and decreases when specific tasks are triggered or events are generated."

System OFF sleep:

System OFF is the deepest power-saving mode the system can enter. In this mode, the system's core functionality is powered down and all ongoing tasks are terminated.

The device can be put into System OFF mode using the register SYSTEMOFF . The following signals/actions cause a wakeup from System OFF:

• The DETECT signal, generated by the GPIO peripheral
• The ANADETECT signal, generated by the LPCOMP peripheral
• The SENSE signal, generated by the NFCT peripheral to wake-on-field
• A valid USB voltage on the VBUS pin is detected
• A debug session is started
• A pin reset

When the device wakes up from System OFF, a system reset is performed. For more details, see Application core reset behavior.

One or more RAM sections can be retained in System OFF depending on the RAM retention settings in the peripheral VMC — Volatile memory controller.

Before entering System OFF, all on-going EasyDMA transactions should be completed. This is accomplished by making sure that the EasyDMA enabled peripheral is not active when entering System OFF. It is also recommended that the network core is in an idle state (i.e. peripherals are stopped and CPU is idle).

2. Please check out the examples in the nRFConnect SDK, as this is dependent on the application.

3. Force OFF mode is used by the application core to force the Network core to Force-OFF mode. Yes, this will be called by the application core and stop the network core.

Best regards,

Simon