I bought a Jetson orin nano development kid last week. After I received it, burned JP513 image on a microSD, boot the system, upgraded firmware, no problem. After I have firmware 365xxxxx on the box, I burn JP62 on a NVME SSD. When I tried to boot from the SSD, it failed. Right now, even I boot from the old JP 513 microSD, it does not work. Fan is spinning, indicator light is on, but no any video output at all. I have tried to redownload the images a couple of times and recreated the microSD a couple of times, it did not help. Is it possible to “RESET” the box?
Hi,
Please try burn JP6.2 on a microsSD to check whether the issue exist.
If you want to flash with NVMe, you need a sdk manager (native ubuntu required) to flash your device.
Thanks
Thank you very much, DavidDDD. I have tried both JP5.1.3 and JP 6.2 on MicroSD, I got the same problem. I have tried to use SDK manager to flash the NVMe this afternoon, at the end I got an error “could not detect a board”. I have to skip the flash. Not sure if there is any special requirement for the USB-A/USB-C cable connect the PC and Jetson (I did connect the 2 pins and disconnect them, it did not help. I keep getting the “board” error)? I have bought some new cables today. when they come, I will try to boot it with new cable and new monitor. If there is anything else I can try, please let me know…Thank you again…Ben
Hi,
Since you are using sdk manager, is your host environment a native ubuntu or a virtual machine(e.g. VMware)?
If you are using native ubuntu with sdk manager, you could execute below commands to check whether device in recovery mode.
lsusb
After the commands, you might see the similar result like Quick Start — NVIDIA Jetson Linux Developer Guide 1 documentation show.
Thanks
Hi David,
My Ubuntu environment is on a physical machine. It is Ubuntu 24 (not 20 or 22) on an old Mac.
“lsusb” cannot find any nvidia devices. I have tried to connect/disconnect Jetson to the Mac, “lsusb” gave the same output, no nvidia device.
If a PC’s motherboard has problem, it will beep during boot time. From the sound, we can figure out if CPU or memory have problems. Is there a similar diagnostic mechanism for Jetson devices that provides feedback during the boot process?
As a newcomer to the NVIDIA ecosystem, I apologize if these questions are common. I appreciate any guidance or pointers to relevant resources. Thank you for your assistance.
Have a great day,
Ben
The problem has been fixed by SDK manager! After flash JP 6.2 image from SDK manager to Jetson, boot is OK. Even with the old JP 6.2 microSD created by Etcher.
When I tried to work on the issue, I encountered some Etcher related problems. On Windows 10 PC, Etcher cannot read JP 6.2 image file, “Error: (0, h.requestMetadata) is not a function” was returned. On MAC, the following message was returned. “Something went wrong. if it is a compressed image, please check that the archive is not corrupted. the writer process ended unexpectedly”. On Windows 11 PC, no problem. Etcher finished successfully. I guess the problem I encountered may be caused by the bad microSD I created with Etcher.
Connect a PC and Jetson does not need special cable. USB-A to USB-A cable plus a USB-A/USB-C adapter works fine. But when you choose the Jetson target, you have to choose the match one. Otherwise, SDK manager may not be able to find the target.
1 Like
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.