Orin Nano not booting, overheating

I purchased a Jetson Orin Nano Developer Kit and received it last Monday. That night, I successfully flashed it with an SD card on a Windows laptop by etching Jetpack 5.1.3. The next day, I installed the required software for the robotics competition I was competing in. The competition was set outside. Although the Jetson was running in California summer heat, it was never in direct sunlight and ran fine. The next day, we were able to use it as needed until Wednesday night.

We connect to the Jetson using an ethernet NoMachine connection. Our Jetson’s power source had an issue causing it to lose power if the robot moved too much. After connecting to the Jetson, it lost power due to this issue. After turning it back on, the connection no longer worked and pinging it was unsuccessful. We checked the ethernet cable separately and it worked fine.

We attempted several types of connections and all failed, even though the Jetson’s power LED was on at all times. First, an HDMI connection to a monitor showed only a black screen. Connecting through serial to see the logs produced also resulted in no output. Lastly, I tried connecting to it while it was in force recovery mode and it did not appear as a connected device.

It was noted that the fan never turned on. The fan base immediately heated up after receiving power. Plugged in for 10 minutes, the fan stayed off even when the fan base got too hot to touch.

We found this forum. Most of the issue was the same, but I cannot access the logs as directed. I also cannot update using SDKManager.

We only had it for 3 days, so any suggestions would be appreciated

Hi alexandria.joli,

We have to check the serial console log to get the detailed information.
Please refer to the instruction in Jetson Nano & NX Style - Serial Debug Console - JetsonHacks to capture serial console log and share it as file here for further check.

Why you can not flash it through SDK Manager?

Have you referred to the following steps to enter into force recovery state?
Connect Type C port to Host PC → Short REC/GND → Power Up the board
Run lsusb from your host to check if your devkit can be recognized.

I believe it should be noted that I have successfully set up these same connections before on a different Jetson of the same model

Please refer to the instruction in Jetson Nano & NX Style - Serial Debug Console - JetsonHacks to capture serial console log and share it as file here for further check.

I had followed this same tutorial and even had several people check that the pins were correct. I open Putty and turn the Jetson on, but Putty stays a blank screen. I have done this before for a different Jetson so I know that Putty should should show outputs as the Jetson boots. Even though the power light is on, I am thinking it never attempts to boot.

Why you can not flash it through SDK Manager?

The only way I have managed to flash through SDK Manager is by connecting through force recovery mode. Is there another way?

Have you referred to the following steps to enter into force recovery state?

Yes. Again, I had someone else confirm I was using the correct pins. That same day, I flashed another Jetson by going into force recovery mode, so I am aware of the required connections to get it there. But this board never showed up using lsusb so SDK Manager never detected it for me to flash it

Without the serial console log, we won’t know what happened to your board.
Force recovery state is controlled by HW.

Okay, if you’ve confirmed that you use the correct method to enter force recovery mode and also correct connection for serial console log but they both do not work.

Please refer to What if I need an RMA (Return Material Authorization)?.
Sorry for the inconvenience.

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.