Jetson Orin Nano Boot

My Jetson Orin Nano won’t boot. It started when I was using it and I think I may have unplugged it while something was downloading or installing. I plugged it back in, it booted but ended up on a black screen with just a flashing underscore in the top right, kind of like a shell but I can’t type anything in. I tried to go into the boot menu and make sure to boot from the ssd but nothing worked. I decided to re-flash the board. I didn’t realize that the SDK manager no longer flashes directly and that you need to use a usb iso img. So, I downloaded the iso, burnt it on to the usb and went through the boot process and selected boot from usb, then install on nvme. Still nothing, still a black screen with the flashing underscore. I then tried to flash directly from the sdk mngr but realized that does not work any more. I even took the nvme, removed all partitions then put it back in. I have asked claude and gemini what to do but neither are of any help. I feel like I just lost one of my favorite computers so any help would me much appreciated.

Hello @gistgraydon66!

Based on the title and content of your topic, it looks like it may receive better visibility and feedback in a different category. We took the liberty of moving it for you.

If this was an incorrect assessment, please send me a direct message.

Disclaimer: this moderation suggestion and message were generated with AI assistance.

Hi,

Could you please help confirm the following?

  • Is the host PC a virtual machine or a physical machine?

  • SDK Manager supports flashing the Orin Nano. Could you please provide the failure log and the serial console log for further investigation?

Thanks

Hi,

Thanks for your quick response. I am using a physical machine running the latest Ubuntu. I could not find any option for flashing directly on the sdkmngr app, I only saw that I could headless and headed ISO boot. Whenever I try to boot from ISO, I usually get this, then a bunch of text (too fast to read) and then a black screen with the blinking underscore. I don’t really know what serial logs you would like to see, but I would be more than happy to send them you you if you could give me a little more direction.

Thank you so much

Hi,

Please access /home/$your_name/nvidia/nvidia_sdk/*/Linux_for_Tegra and run the below commands as the developer guide show

  1. super mode
sudo ./l4t_initrd_flash.sh --erase-all jetson-orin-nano-devkit-super internal
  1. normal mode
sudo ./l4t_initrd_flash.sh --erase-all jetson-orin-nano-devkit internal

Thanks

Hello @gistgraydon66,
Before flashing, put the Orin Nano into Force Recovery Mode and confirm that the host can see it over USB with:

lsusb | grep -i nvidia

You should see an NVIDIA device listed. If nothing appears, the flashing tool will not be able to communicate with the module, so check the USB cable, recovery-mode procedure, and host connection first.

After USB recovery detection is confirmed, use the appropriate l4t_initrd_flash.sh command for your board configuration as mentioned previously.

If the board still does not boot afterward, please share the serial console log so we can see where the boot process stops.

Regards,
Pedro

Embedded SW Engineer at RidgeRun
Contact us: support@ridgerun.com
Developers wiki: https://developer.ridgerun.com
Website: www.ridgerun.com

Hey,

I have the sdkmgr installed, but when I try to go to that filepath, I only have iso image, not linux for tegra. I really appreciate your help

I am in force recovery mode, just am having a bit of a hard time flashing

Hi,

Please download the Driver Package (BSP) and Sample Root Filesystem from JetPack SDK Downloads and Notes Archive | NVIDIA Developer.

And follow the Quick Start — NVIDIA Jetson Linux Developer Guide to flash your device.

Thanks

Could you please share the full serial console boot log from power-on until the blinking cursor appears?

Also, please confirm:

  • Exact JetPack/ISO version

  • Host Ubuntu version (lsb_release -a)

  • Host architecture (uname -m)

  • lsusb output while the Jetson is in Force Recovery mode

  • Whether this board successfully ran JetPack 6.x before attempting JetPack 7.x

The serial log is the most important next step, as it should show whether the boot is failing in UEFI, kernel startup, or while mounting the root filesystem.