Verdin AM623 partial I/O module power consumption

Technical Support
,
1

Dears,

I am looking for some information related to the power consumption of the Verdin AM623 SoM when it is set in Partial I/O low power mode.

In the documentation is available the power consumtion in mW when set in deep sleep mode, but I can’t find the values for this extreme low power setting.

Moreover, I would like to have a list of the module peripherals that can be disabled to save as much power as possible, with some indication of the commands / overlays settings to do so.

Thanks,

Andrea

2

Hi, I’m the Toradex AI Assistant.

I might make mistakes. Our support team will step in if needed. If I answered your question, please tick the “Solution” checkbox. For follow-up questions to me, please use @ToradexAI in your post.

Did you like my answer? :+1: :-1:

Power Consumption Information for Verdin AM62

Unfortunately, the available documentation doesn’t contain specific power consumption values for the Partial I/O low power mode on the Verdin AM62 (which includes the AM623 variant). The documentation mentions that detailed power consumption information can be found on the Developer Website (1), but the specific values for Partial I/O mode are not included in the provided sources.

Deep Sleep Mode Considerations

The documentation does provide information about Deep Sleep mode limitations and peripheral control. During Deep Sleep mode on the Verdin AM62 V1.2, there are important considerations for GPIO control (2):

Key Deep Sleep Limitations

  • GPIO State Changes: Devices controlled by SoM GPIOs may experience unintended state changes when transitioning to Deep Sleep mode (2)
  • High-Z State: Output buffers of GPIO pins are disabled, placing pins in High-Z state (2)
  • Internal Pull Resistors: The SoC’s internal pull-up and pull-down resistors (ranging from 15 kΩ to 30 kΩ) are enabled to preserve GPIO state (2)
  • CTRL_SLEEP_MOCI# Signal: This signal is also affected by the Deep Sleep limitations (2)

Workaround Solutions

For optimal Deep Sleep functionality, the documentation suggests (2):

  1. Voltage Calculation: Estimate output voltage on I/O pins under worst-case conditions with internal 30kΩ pull resistors
  2. Component Selection: Choose peripheral components with suitable I/O voltage thresholds and low pin bias currents
  3. I2C GPIO Expander: Use as an alternative solution to drive peripherals’ reset and power-gating GPIOs during Deep Sleep state (2)

Hardware Specifications

The Verdin AM62 V1.2 datasheet is the most current version available in the sources (3). The module supports various power management features, but specific power consumption values for different low-power modes would need to be referenced from the complete power consumption documentation on the Developer Website.

For comprehensive power consumption data and specific commands/overlay settings for disabling peripherals, I recommend checking the complete power consumption documentation referenced in the datasheet, as the provided sources don’t contain the detailed peripheral control commands you’re looking for.

Best regards, Toradex AI Assistant.

3

Dear @dm-andreapedica,

Unfortunately we do not test the deep sleep mode ourselves, which is the reason you could not locate any specific numbers.
What I did find however was a document by TI about the SoC power consumption itself.

image
image676×127 16.2 KB

This number only includes the power consumption of the SoC, not the whole SoM.
A list of non-necessary peripherals depends on your application, therefore you will need to check what is not needed for your specific use case. Different peripherals may have different ways to disable them.

Another noteworthy topic that came to mind is the following:
If you are using the Verdin AM62 Dual, it would be possible to limit the maximum frequency to 1.25 GHz and use a lower VCORE (0.75V) to decrease the power consumption.
Should you be using a solo version, it already uses a lower VCORE.

Best regards,
Collin

1 Like
4

Dear Collin,

thanks a lot for your reply, the data you shared will be precious for my HW colleagues.

Relating to my needs, I can confirm we are using the single core version, more precisely the Verdin AM62 512MB WB IT v1.2A.

Now, my concern is actually understand which is the right command linked to the lowest low power level “MUC only”.

As per my experiments, but please confirm my understanding, the command

systemctl suspend

is equivalent to

echo mem > /sys/power/state

that triggers the deep sleep.

The other available power states are:

freeze mem disk

While freeze relates to standby and mem to deep sleep, I’m unsure if disk is related to “MCU only” or not.

The only nearest command I may imagine is

systemctl poweroff

but experimentally that triggers the same flow of the “forced power off” and sends the KILL signal thorugh FORCE_OFF_MOCI, disabling completely the power that is not what we want.

So please could you gather some more information and clarify to me how to trigger and test the MCU Only low power (assuming that it is managed from current Toradex Linux BSP).

Thanks a lot for your support!

Andrea

5

Dear @dm-andreapedica,

I am not certain if our BSP supports setting the precise power level modes, however I found the following article, which describes how you could be able to set it on the SoC level: 3.3.7. S/W Architecture of System Suspend — Processor SDK AM62x Documentation
You are indeed correct in a sense that systemctl suspend is functionally equivalent to echo mem > /sys/power/state.

I found some further information on runtime power management on the AM62. 3.3.4. Runtime PM — Processor SDK AM62x Documentation

Best regards,
Collin

1 Like
6

Thanks for the suggestions, I’ve read the documentation you shared, but it’s not helping with obtaining an acceptable power consumption in deep sleep, even following the suggestions in the documentation and creating a very basic project with all peripherals disabled via device tree overlay.

I’ve created anyway another topic Verdin AM623 - deep sleep configuration and power consumption verification - Technical Support - Toradex Community to collect in one point the progress (and hopefully, hints from your team) to try to find the root cause of my inconsistent measures.

Thanks for the support