Orin Nano and NX Power-On Issues with Custom Carrier Board

Issue Overview

Users are experiencing power-on issues when designing a custom carrier board for Jetson Orin Nano and Orin NX modules. The power-up sequence that works for Jetson Nano and Xavier NX fails to properly boot the Orin Nano and Orin NX. Specifically:

• The carrier board supplies power and the power LED lights up
• After a certain time, the power LED turns off, but carrier board supplies remain on
• The Orin NX and Orin Nano modules appear unable to enter the bootloader

This issue is occurring during the initial setup and testing of a custom carrier board designed to be compatible with multiple Jetson modules (Nano, Xavier NX, Orin Nano, and Orin NX).

Possible Causes

1. Incorrect power-on sequence: The power-up logic circuit designed for Jetson Nano and Xavier NX may not meet the specific requirements for Orin Nano and Orin NX.

2. Timing discrepancies: There might be inconsistencies in the timing of power-on signals, particularly regarding the SYS_RESET signal.

3. Interface incompatibilities: The interfaces for Orin NX/Nano may differ from those of Nano and Xavier NX, causing communication issues.

4. Missing ID EEPROM: The absence of an ID EEPROM on the I2C2 bus could prevent the Orin modules from booting properly.

5. Outdated design guide information: Conflicting information in design guides regarding timing specifications could lead to incorrect implementations.

Troubleshooting Steps, Solutions & Fixes

1. Verify power-on sequence:

   • Probe the power-on sequence on your board to ensure it matches the sequence specified in the latest Design Guide.
   • Pay special attention to the timing between VDD_IN and POWER_EN signals.

2. Adjust timing components:

   • If necessary, modify component values to achieve the correct timing. For example, changing C303 to 10 µF altered the delay between VDD_IN and POWER_EN to approximately 1.8s.

3. Check SYS_RESET timing:

   • Ensure SYS_RESET is released 80ms after POWER_EN, as per the latest documentation.
   • Note that SYS_RESET is controlled by the module, not the carrier board.

4. Review interface compatibility:

   • Consult the Interface Comparison & Migration Application Note and the Orin NX/Nano Design Guide to verify that your board’s interfaces are compatible with Orin NX/Nano modules.
   • Pay close attention to any differences between Nano, Xavier NX, Orin NX, and Orin Nano interfaces.

5. Add ID EEPROM:

   • If not already present, attach an ID EEPROM to the I2C2 bus on your carrier board.
   • This step resolved the boot issue for some users.

6. Configure system without ID EEPROM:
   If designing a custom carrier board without an ID EEPROM, follow these steps:

   • Modify the EEPROM configuration as described in the Jetson AGX Orin Series documentation.
   • Use the following command to configure the system:

     sudo /opt/nvidia/jetson-io/jetson-io.py
     

   • Select "Configure Jetson AGX Orin" and choose the appropriate carrier board option.

7. Update to latest documentation:

   • Always refer to the most recent version of the Jetson Orin NX Series and Nano Series Design Guide for accurate timing and design specifications.

8. Probe PMIC power:

   • Verify that the module PMIC powers on correctly after SYS_RESET is released.

9. Isolate the issue:

   • Test the carrier board with different Jetson modules to identify if the problem is specific to Orin NX/Nano or affects all modules.

10. Seek official support:

    • If issues persist after trying these solutions, consider reaching out to NVIDIA’s official support channels for further assistance.