Jetson Orin Nano won't power up

[ngaraycoaia]

Bought the developer kit on Amazon in late July. Tried booting today but device fails to power on. Green LED does not illuminate with official power supply. Tried Force Recovery pins and button header; device is not detected by host PC via USB.

[carolyuu]

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

Based on the provided context, it appears that the Jetson Orin Nano Developer Kit is not powering on, and the green LED is not illuminating. The user has tried using the official power supply and attempting a force recovery using the pins and button header, but the device is not detected by the host PC via USB.

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

1. Power supply: Ensure that the official power supply is functioning correctly and providing the required voltage (12V, 5A) to the device. Try using a different power supply or a multimeter to verify the voltage output.
2. Power button and MCU: The Jetson Orin Nano Developer Kit features a Button Power MCU (EFM8SB10F2G). It’s possible that the power button or the MCU is faulty, preventing the device from powering on. Compare the connections from the reference design to ensure that the power button and MCU are properly connected.
3. USB connection: Verify that the USB connection between the device and the host PC is secure and functioning correctly. Try using a different USB cable or port on the host PC.
4. Force Recovery mode: The user has attempted to enter Force Recovery mode using the pins and button header. However, it’s possible that the device is not entering this mode correctly. Compare the connections from the reference design to ensure that the Force Recovery pins and button header are properly connected.
5. Device detection: The device is not detected by the host PC via USB. This could be due to a faulty USB connection, a malfunctioning device, or incorrect configuration. Try using a different USB connection or a different host PC to rule out any issues with the host PC.

In comparison to other Jetson Orin Nano Developer Kit issues, this problem seems to be related to the power supply or the power button/MCU. The user can try to troubleshoot the issue by verifying the power supply, checking the connections from the reference design, and attempting to enter Force Recovery mode.

To resolve the issue, the user can try the following steps:

1. Verify the power supply and ensure it’s functioning correctly.
2. Check the connections from the reference design to ensure that the power button and MCU are properly connected.
3. Attempt to enter Force Recovery mode using the pins and button header.
4. Try using a different USB connection or a different host PC to rule out any issues with the host PC.
5. If the issue persists, consider contacting NVIDIA support or a professional for further assistance.

In terms of the provided context, the following topics might be relevant to this issue:

• Jetson Orin Nano Developer Kit – Black Screen and Fan Stops After Boot (JetPack 5.1.3)
• Booting issue Jetson Orin Nano boot, jetson
• Jetson nano usb uart isn’t booting Jetson Orin Nano boot

These topics suggest that there might be issues with the device’s boot process or power supply, which could be related to the problem at hand.

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

[DavidDDD]

Hi,

What is your host PC?

Please prepare a native ubuntu and install the sdk manager to flash your device.

Thanks

[ngie]

I ran into similar problems with the prescribed Jetson Linux install process. I ended up giving up on that and just “installed” stock Ubuntu instead: Install Ubuntu on NVIDIA Jetson | Ubuntu . I don’t have the UART/SPI connected so I cannot determine why the CPU reset after trampolining from the bootloader to the kernel.

PS I say “install” Ubuntu 22.x (Jammy) – because I’m having to jump through tons of hoops configuring it for first boot use, then upgrading to 24.x (Noble). I’m kind of surprised that the end-user experience is this bad (this reminds me of the days of eval board bring up on Cavium/Freescale systems back in the late ‘00s/early ‘10s). I’ll be slightly surprised if it takes less effort to boot FreeBSD 15.0-RELEASE on the board, but not shocked.