SHUTDOWN_REQ* may not be asserted when the module initiates a software system shutdown

Robotics & Edge Computing Jetson Systems Jetson Orin NX
1

We designed a carrier board，in ubantu22.04.5，when the module initiates a software system shutdown，the SHUTDOWN_REQ signal may probabilistically fail to be asserted and system hang；

module p/n：900-13767-0010-001

2

*** Please note that this reply is generated by LLM automatically ***

The issue you’re experiencing with the Jetson Orin NX module (PN 900-13767-0010-001) on your custom carrier board, where the SHUTDOWNREQ signal may probabilistically fail to be asserted and the system hangs during a software system shutdown, is likely related to the specific configuration and design of your carrier board.

To troubleshoot this issue, let’s consider the following:

  1. Carrier Board Design: Ensure that your carrier board design is compatible with the Jetson Orin NX module. Verify that the power management and shutdown circuitry are correctly implemented and meet the requirements specified in the Jetson Orin NX module datasheet.
  2. Software Configuration: Check the software configuration on your Ubuntu 22.04 system to ensure that the shutdown process is properly configured. Verify that the SHUTDOWNREQ signal is being asserted correctly by the software.
  3. Module Configuration: Check the configuration of the Jetson Orin NX module to ensure that it is set up correctly. Verify that the module is configured to assert the SHUTDOWNREQ signal during a software system shutdown.
  4. Signal Integrity: Verify that the SHUTDOWNREQ signal is being transmitted correctly from the module to the carrier board. Check the signal integrity and ensure that there are no issues with the signal transmission.

Comparing this to the Jetson AGX Orin Developer Kit (P3730-0000), which consists of a P3701 System on Module (SOM) connected to a P3737 carrier board, we can see that the Developer Kit has a specific thermal solution designed for the kit, and the SOM can be used without any software configuration modifications.

In contrast, your custom carrier board design may require specific configuration and design considerations to ensure proper functionality, including the shutdown process.

To resolve the issue, you may need to:

  • Review and modify your carrier board design to ensure compatibility with the Jetson Orin NX module.
  • Update your software configuration to ensure proper shutdown process.
  • Verify the module configuration to ensure correct assertion of the SHUTDOWNREQ signal.
  • Check the signal integrity to ensure correct transmission of the SHUTDOWNREQ signal.

If the issue persists, it may be helpful to consult the Jetson Orin NX module datasheet and the NVIDIA Jetson Linux Developer Guide for further guidance on designing and configuring a custom carrier board.

*** Please give the thumbs up if you get answers you like. Or provide feedback to help us improve the answer. ***

4

Can you please provide scope captures of the behavior of the SHUTDOWN_REQ and your carrier board’s power down sequence, including the POWER_EN and SYS_RESET signals, when this happens?

5

When system hangs，SHUTDOWN_REQ is always high，so POWER_EN and SYS_RESET held high level，system would not shutdown

7

Hi jason.chen,

How did you trigger the software shutdown?
Could you share the full serial console log for further check?