Orin Not Booting Anymore As Well As Giving No Display Output While Still Being Flashable

Robotics & Edge Computing Jetson Systems Jetson AGX Orin
1

Since yesterday, our Jetson AGX Orin 64 GB (dev kit) does not boot properly anymore.

All information that I could retrieve so far:

  • The power LED shows white correctly when powered
  • No display output is given; not via DisplayPort and also not via a USB-C hub with an HDMI cable connected
  • Powering through both USB-C ports and the 12 V port was tested; makes no difference
  • All plugged in cables except power and the DisplayPort cable have been removed; makes no difference
  • The UART debug serial via Micro-USB does not yield any output at 115200 baud rate; tested with 2 different devices and multiple different tools
  • The Orin seems not to boot as it is not reachable via ssh, not connected to the network, no debug output is given, no display output etc.
  • Booting without the SSD connected makes no difference
  • Booting with SSD connected makes no difference
  • Connecting the Orin via USB-C to an Ubuntu 22.04 host machine and using the `sdkmanager` detects the Orin though correctly!
    • It is even possible to flash it without any errors shown
    • But even after that all above problems remain the same and the Orin does not boot as it seems

The weirdest thing: It is not necessary to explicitly let the Orin boot into recovery/flash mode for it to being detected by the `sdkmanager` and able to being flashed. I guess this means that the Orin always boots into the recovery/flash mode instead of booting normally? I don’t see any reason for this though as we didn’t short the corresponding pins. Also I’d expect to receive some UART debug output even when the Orin boots into recovery/flash mode?

Does anyone have any ideas what the possible root problem could be or has someone any ideas on how to proceed debugging?

Thank you very much for your help! If I can provide any useful additional information, please tell :).

EDIT: In this thread the possibility of a burned fuse is discussed which could result as it seems in symptoms similar to mine above? I’m currently flashing the SSD instead of the eMMC, maybe this changes the behavior.

EDIT 2: When trying to flash the SSD, it all seems to go well until a dialog windows is shown that the Orin is not ready. The terminal output logs “Step 3: Start the flashing process” and after that only repeats “Waiting for target to boot-up…” until “Error: timeout”. There’s still no debug UART output, even while flashing.

EDIT 3: To provide more info regarding the flashing to eMMC. It seems to work fine, the `sdkmanager` prints in the end

waiting for device boot up…
waiting for device auto config process…
done.
…
Install completed successfully.

and shows the success dialog which tells to restart the Orin and boot into the OS login screen.
But after that the same problems apply, no display output, no debug output etc.

4
  • The UART debug serial via Micro-USB does not yield any output at 115200 baud rate; tested with 2 different devices and multiple different tools

I wonder few points here

  1. What does that mean 2 devices here? You have 2 Orin AGX that both could not boot up anymore?

  2. As sdkmanager is still flashing, what is the UART log during flash process? If it could flash, then UART must print logs.

6

Thanks for your help!

  1. With the 2 devices I meant to different laptops to read via Micro-USB the UART logs
  2. Absolutely no UART output, even while flashing

But: In the meantime we were able to get a different carrier board and changed them - and now the UART output works and after a new flash to the eMMC the Orin also boots up fine again. So seemingly it is a HW fault on the carrier board.

Still though we are not able to receive any display output from the Orin (even with the replaced carrier board), do you have any ideas what the reason could be? Again tried with DisplayPort as well as a USB-C adapter to HDMI; both without any results.

7

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 ~0325

OK. Let’s forget about the old carrier board.

What is the UART log from new carrier board now?

I would like to check what you could do based on the UART log first.