I bought this device recently, successfully upgraded to JetPack 6.2, and was using it since last couple of days. Then suddenly on one day it was not working and I followed the solution of a very similar topic on this forum, provided as below:
I was also seeing the bootup screen saying ‘L4TLauncher: Attempting Recovery Boot’ exactly as same as shown in the above topic. Following these instructions, I selected ‘Jetson Linux’ and ‘Jetson Runtime Components’ to install in the Target Device in SDK Manager using my Ubuntu 22.04 host machine.
Then at the end of Step02 in SDK Manager, when I continue, a screen showing many logs appear in SDK manager and it got stuck. See the attached image below:
In the next try, I checked the option ‘Download now and install later’ at the end of Step02 in SDK Manager and downloaded all the files in my host machine. Then I manually tried to re-flash the board using ‘sudo ./flash.sh jetson-orin-nano-devkit mmcblk0p1’ command in the terminal and it flashed the board. But when I try to power on the board and connect it to a display, I see the usual boot up screen showing the following information, but this screen just gets stuck and nothing happens afterwards.
Jetson System firmware version 36.4.3-gcid-38968081 date 2025-01-08T01:18:20+00:
00
ESC to enter Setup.
F11 to enter Boot Manager Menu.
Enter to continue boot.
L4TLauncher: Attempting Direct Boot
EFI stub: Booting Linux Kernel…
EFI stub: Using DTB from configuration table
EFI stub: Loaded initrd from LINUX_EFI_INITRD_MEDIA_GUID device path
EFI stub: Exiting boot services…
Please help me resolve this issue. Thank you for your time.
Thank you DaneLLL for your reply. I used an SD card with a new JetPack 6.2 image and now the Orin Nano is working. But I can’t see the “2:MAXN SUPER” power mode now. Please refer to the image below.
I spent the week looking at a similar issue. Eventually I found a setting page for the boot ROM that had the L4T showing as disabled. When I enabled it, I was then back to getting an image loading from the SD Card. I had noticed that the USB Cable connection was not causing a device to be noticed by any PC. What I see in the flash process, is the L4T Software changing the device type the usb connection is, and if that ends in an undesirable spot, It may not reset the system to nominal.
I do not recall what I mistyped from the UEFI page to get to the devices list. Maybe someone smarter knows what that command sequence is.
It appears that your only flash SD card Image, but not flash the qspi.
We suggest follow the Dane mentioned manual flashing method to full flash your device.
Other option is to use sdk manager to flash.
It appears that your apt server has some issue.
Please only choose Jetson Linux and rerun the sdk manager again.
Thank you for your suggestion. I tried this. I flashed the board for “Jetson Orin Nano Developer Kit with Super Configuration (NVMe)” configuration form my Ubuntu host machine and at the end of the process, I encounter an error as shown in the attached image.
To go into the ‘Force Recovery’ mode, I shorted the ‘FC REC’ and ‘GND’ pins of the device. But during the flashing process, the device never booted up, but was always powered on. After seeing this error, I disconnected the power to Jetson Orin Nano, disconnected it from Ubuntu host machine, and powered it on again with a connecting display. Now I still only see the same power modes and am not able to see the 2:MAXN SUPER mode.
I could not use the SDK manager because when I try to install software from that, I see another issue as I posted at the start of this topic.
Please suggest me further steps to resolve this. Thank you for your time.