Boot issue under an ambient temperature of −40°C

We are using a custom board based on Jetson AGX Orin Industrial (JetPack 6.2 / Ubuntu 22.04).

Test conditions:
After being placed in an ambient temperature of −40°C for 4 hours, the system was powered on. After shutdown, it was powered on again every 1 hour.

Two units were used for testing. After power-on, one unit stopped at the UEFI screen, while the other encountered an error after loading the kernel and failed to enter the root filesystem (rootfs).

Additional information:

  1. The system operates normally once returned to room temperature.
  2. This issue does not occur during repeated power on/off testing performed continuously under an ambient temperature of −40°C.

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

The issue you’re experiencing with your custom board based on Jetson AGX Orin Industrial, where the system fails to boot after being exposed to high temperatures, is likely related to the thermal management and power-on sequencing of the board.

The Jetson AGX Orin series, including the Industrial version, has a thermal management system that is designed to protect the device from overheating. However, it appears that the system is not able to recover from the high temperature exposure in your test scenario.

Comparing this to other Jetson modules, the Jetson Orin NX and Jetson Orin Nano series also have thermal management systems, but they may behave differently under similar test conditions. The Jetson Orin NX, for example, has a slightly different thermal management system than the Jetson AGX Orin, which may affect its behavior in high-temperature environments.

In terms of power-on sequencing, the Jetson AGX Orin has a specific boot flow that involves the BootROM, PSCROM, MB1, MB2, and UEFI. Any issues with the power-on sequencing can cause the system to fail to boot.

To troubleshoot this issue, you may want to try the following:

  1. Verify that the thermal management system is functioning correctly. Check the thermal sensors and ensure that they are reporting accurate temperatures.
  2. Review the power-on sequencing and ensure that it is correct. Check the BootROM, PSCROM, MB1, MB2, and UEFI logs to see if there are any errors or issues during the boot process.
  3. Try to reproduce the issue with a different Jetson module, such as the Jetson Orin NX or Jetson Orin Nano, to see if the issue is specific to the Jetson AGX Orin Industrial.
  4. Check the system’s power management settings and ensure that they are configured correctly. The Jetson Orin series has various power management features, such as dynamic voltage and frequency scaling, that can affect the system’s behavior in different power states.

In terms of documentation, you can refer to the Jetson Linux Developer Guide, which provides information on the thermal management system, power-on sequencing, and power management features of the Jetson Orin series.

Additionally, you can also refer to the following topics:

  • “Jetson Orin NX low temperature limit” which discusses the low temperature limit of the Jetson Orin NX.
  • “Automatic shutoff at temp extremes” which discusses the automatic shutoff feature of the Jetson Orin NX at temperature extremes.
  • “Is the lowest system bootable temperature settable?” which discusses the lowest system bootable temperature of the Jetson Orin NX.
  • “Low temperature Limit” which discusses the low temperature limit of the Jetson AGX Orin.
  • “Orin NX can’t cold boot at -25℃” which discusses the issue of the Jetson Orin NX not being able to cold boot at -25℃.
  • “Jetson Orin 200T module’s minimum operating temperature is only -20℃” which discusses the minimum operating temperature of the Jetson Orin 200T module.

These topics may provide additional information and insights into the thermal management and power-on sequencing of the Jetson Orin series, which can help you troubleshoot and resolve the issue you’re experiencing.

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

There is no update from you for a period, assuming this is not an issue anymore.
Hence, we are closing this topic. If need further support, please open a new one.
Thanks
~0603

Could you share the full uart log as text log instead of such picture? Log sharing as an image is actually not quite good.