Regarding usage of power management config files

RE: Regarding usage of power management config files

Simonr — Thu, 08 Apr 2021 07:48:27 GMT

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

RE: Regarding usage of power management config files

Priyadharshini — Wed, 07 Apr 2021 06:25:11 GMT

Hi,

1. Can you please tell me how the following power management is handled in nf5340

1. System on sleep

2. System off sleep

2. Also tell me the APIs involved during system on and system off.

3. Is force off state will be used in application core.

RE: Regarding usage of power management config files

Simonr — Wed, 07 Apr 2021 06:16:50 GMT

I'm sorry, NCS is the only SDK solution we have that supports NRF5340, so we don't have any power management (example or library) outside of the Zephyr RTOS.

Best regards,

Simon

RE: Regarding usage of power management config files

Priyadharshini — Tue, 06 Apr 2021 14:52:14 GMT

Hi,

4 a) Can you please tell me the power management in nrf5340 possible without using Zephyr rtos

RE: Regarding usage of power management config files

Simonr — Tue, 06 Apr 2021 14:05:01 GMT

1. CONFIG_PM is explained here. As for CONFIG_HAS_POWER_STATE_DEEP_SLEEP_1 and CONFIG_PM_DEEP_SLEEP_STATES, where did you find these? Can you provide some information on this, as I didn't find any reference to these defines in the Zephyr, KConfig or NCS documentation.

2. This depends on what project you're using. Typically you'll need to use constant latency only if for instance you need to take an action within <1us, the current consumption will be higher in constant latency mode. In low power mode, the current consumption is a very few uA and is the common usage for any battery powered product.

3. Please check out the power management subsystem in Zephyr and NCS power manager module documentation for more information on this.

a) Is what required in Zephyr RTOS for initialization? I'm afraid I don't understand the question?

b) How clock control is done in and between the two cores on the nRF53 is done in the Power Management Unit inside the SoC. Please see the Power and Clock management section in the PS for details.

c) Yes, only the network core will have access to the radio peripheral in nRF53, and in most cases (unless the application is very simple) the application core will need to run the actual application.

5. I don't think this would be a config file, but rather a call to a task waking the device up.

6. See links in question 3.

Best regards,

Simon