Verdin AM62P reset state behavior

Technical Support
,
1

Hi,

When I try to reboot the verdin am62p (1.0B) from inside Torizon OS 7.4.0 (b28), it goes into the reset state, then instead of powering up afterwards, it continues to shutdown. I have tried it on the Mallow (1.1c) and the development board (1.1f).

Am I forgetting / missing something?

Thanks!

2

Hi, I’m the Toradex AI Assistant.

I might make mistakes or occasionally get you wrong. Our support team will step in if needed.

Based on the available sources, I don’t have specific information about the reboot issue you’re experiencing with the Verdin AM62P on Torizon OS 7.4.0. The sources confirm that the Verdin AM62P is supported on Torizon OS(1) and is compatible with the Mallow Carrier Board(2), but don’t address this specific reboot behavior.

Potential Areas to Investigate

Since this appears to be a power management issue during the reboot cycle, here are some general areas that might be relevant:

Power Supply Verification

  • Ensure adequate power supply capacity for both boards
  • Check power connections and stability during the reset cycle

Hardware Configuration

  • Verify that both the Mallow 1.1c and Development Board 1.1f are properly configured for the AM62P module
  • Check for any hardware-specific settings that might affect the power cycle

Software Configuration

  • Review any custom device tree overlays or system configurations that might affect power management
  • Check for any specific Torizon OS settings related to power management

Next Steps

For this specific issue with the reboot behavior, I’d recommend:

  1. Check the power supply specifications and connections
  2. Review any custom configurations that might affect the boot process
  3. Test with a minimal system configuration to isolate the issue

If you’d like more detailed troubleshooting guidance, could you provide additional information about your power supply setup and any custom configurations you’re using?

**

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

If I answered your question, please tick the “Solution” checkbox.

For follow-up questions to me, please use @ToradexAI in your post.

3

Aditionally, when I try the same with the verdin AM62 (1.2A) on both carrier boards, it works as expected.

Also, to clarify, I have no customizations at all.

4

Thank you for the additional details. This clarifies that the issue is specific to the Verdin AM62P (1.0B) module, while the Verdin AM62 (1.2A) works correctly on the same carrier boards with the same OS version.

Module-Specific Issue Analysis

Since you’re experiencing this only with the Verdin AM62P 1.0B and not with the Verdin AM62 1.2A, this suggests a module-specific behavior difference. The Verdin AM62P is powered by the TI AM62P5 processor with different power management characteristics compared to the AM62 series (1).

Key Differences Between Modules

The Verdin AM62P features (1):

  • TI AM62P5 applications processor with up to 4x Cortex-A53 cores and 1x Cortex-R5F core
  • More powerful GPU with 50 GFLOPs
  • Different power management architecture

While the Verdin AM62 uses (2):

  • TI AM625/623 processor with up to 4x Cortex-A53 cores and 1x Cortex-M4F
  • Different power dissipation characteristics

Potential Hardware-Specific Considerations

Since this occurs on both the Mallow 1.1c and Development Board 1.1f with the same AM62P module, but works fine with the AM62 module, this points to:

  1. Module Revision Specific Behavior: The 1.0B revision of the AM62P might have specific power management characteristics
  2. SoC Power Sequencing: The AM62P5 may have different power-down/power-up sequencing requirements
  3. Firmware/U-Boot Differences: Different bootloader behavior between the two module types

Recommended Next Steps

  1. Verify Power Supply: Ensure your power supply can handle the AM62P’s power requirements, which may differ from the AM62
  2. Check Module Revision: Confirm if this behavior is consistent across other AM62P 1.0B modules
  3. Serial Console Monitoring: Monitor the serial console during the reboot attempt to capture any error messages or boot sequence information

Since this appears to be a module revision-specific issue with no custom configurations involved, this would benefit from direct technical support investigation to determine if this is a known characteristic of the AM62P 1.0B revision.

Best regards, Toradex AI Assistant.

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

If I answered your question, please tick the “Solution” checkbox.

For follow-up questions to me, please use @ToradexAI in your post.

5

Just found that it is a known errata, found here: Errata #1 HAR-12163 Verdin AM62P Errata.

Is there any new information available on this?

1 Like
6

Hi @jippeheijnen,

As you have found, we have a known issue. I am checking with our product management to see if this will be fixed in a newer version of Hardware (or through any other workarounds). I will update you soon.

7

Hello @jippeheijnen,

I have an update for you. This errata will be corrected in the next version of AM62P. It is a work in progress, and the expected timeline for release is Q1 2026.

1 Like