I am trying to set it up Jeston Nano Orin for the 1st time. Followed all instructions on the NVIDIA website. Flased the SD card using Mac/Linux and even Windows seperately. Not matter what i do when i start the nano after flashing it always goes into some shell mode saying startup.sh and stops there. No commands works after that and i can never make it boot normally. I also read NVIDIA site instructions and put it on recovery mode by connecting pins 3 & 4 still the same issue. How can this be fixed so i can go to next step and use it
Recovery pins only cause the Jetson to become a custom USB device understood by a custom USB driver. The recovery mode itself does nothing without the flash software (which happens to have that custom USB driver). One needs to flash the Jetson itself once, and then several SD card versions will work. The SD card does not contain the boot content.
To clarify, the Orin Nano has QSPI memory on the module itself. Jetsons do not have a BIOS, but they do have the equivalent in software. Flashing the Orin Nano itself means you are simultaneously flashing the equivalent of BIOS and the boot content onto the QSPI memory in recovery mode.
That custom USB driver runs only in desktop Linux PC architecture. You need an actual Linux PC to flash the module in recovery mode.
FYI, what gets flashed is Ubuntu plus NVIDIA drivers. That content, together, is referred to as L4T (“Linux for Tegra”). The command line package is normally downloaded with the GUI flash front end, which is JetPack (there is a network layer on top of that known as SDK Manager).
Note that there are currently two releases of L4T which work on the Orin Nano: R35.x and R36.x. You can look up either of those, and they will lead to the correct JetPack/SDKM to flash this to the module (then your SD card will work). However, the major release version has to be compatible with the SD card. If you flash the Jetson with an R35.x release and the SD card is R35.x, then it should work; similar for R36.x and SD card R36.x. If you cross an R35.x with an R36.x, then it will fail.
A given L4T release tends to be tied to a given JetPack release, and so picking one would more or less pick the other. Note that R35.x is stable, and although R36.x is also stable, it is newer. R36.x migrated to the mainline Linux kernel rather than one customized for Jetsons. I think the optional drivers for R35.x are probably more complete since the mainline R36.x isn’t picked by NVIDIA (the modules and drivers default to what mainline uses; the R35.x modules and drivers have some picked by NVIDIA).
Find either here:
You will need a correct Linux PC to flash since the driver runs only on Linux. The JetPack GUI also restricts things somewhat further. Read the docs to find out the release of JetPack you can use with the L4T or JetPack release. Please note that JetPack itself works on a wider range of Ubuntu PCs than what the Orin will accept (the Orin release chosen further restricts what the Ubuntu host PC version can be).
Also, double-check on your recovery pins. 3 & 4 does not sound correct, but it might be ok. All of the above assumes this is an NVIDIA developer’s kit (if this is using a third party carrier board, then this all changes).
I tried every thing listed above, no luck i still cant make the Nano work. Any thing else i can try ?
What did you try exactly…?
Most of users tell us they tried something but actually some of them don’t know what they are doing.
For example, recovery mode is just a mode to put the board into a state “it can get flashed”. If you just enter recovery mode but then doing nothing, then it won’t change anything.
If you ever tried something, tell us what did you try so that we can tell you next step…
I also must ask, what was it you tried? Did you verify if this is a developer kit, versus a third party carrier board? Was your host PC running Linux natively, and not via a VM? If something did fail during a flash, can you post the log?
Below are all the things I did.
Mac & Windows :
Tried leveraging Jetson Nano Developer Kit SD Card image on microSD card to start Jetson. Use the information from the link Get Started With Jetson Nano Developer Kit | NVIDIA Developer. Downloaded the image and used Etcher to flash the drive with the image.
When all done connected Jetson to a monitor and it never crossed the 1st page.
I read some blog that recommended I jump pins to go to recovery did that and no luck as well.
Based on this issue opened this ticket and followed the instructions.
Used Linux Ubuntu desktop not VM. Ubuntu version is 22.04.4 LTS
Installed SDKManager 2.1.0.11698
Connected Jetson via USB and inside the SDKmanager UI it says Target hardware – Could not detect a board.
See images
Just some clarification…
- Jetson nano and Jetson Orin Nano are different. Jetson nano is a platform that was released for like 5 years ago. And that one with “Orin” is the latest one.
The link you shared here:
this is a Jetson nano document.
For Orin, you have to use this.
And for sdkmanager case, you need to put the board into recovery mode before flashing.
If the board is in recovery mode, your Host PC will see Nvidia corp device in lsusb command.
Thanks for sharing the details. As instructed, i used the Jetson Orin Nano link provided above (Jetson Orin Nano Developer Kit Getting Started | NVIDIA Developer) . Its not working and i am struck at boot up. See attached images.
I also tried the SDK Manager route by puttng board into recovery mode before flashing and the lsusb is not identifying the board and also SDK manager is not recognizing as well ( See attached)
How did you put your board into recovery mode?
I tried connecting pins 9 & 10 and also tried pins 3 & 4 based on information i saw on internet.
See attached images
Do you have other usb cable to test? I am afraid the usb type C cable in use has some issue which makes it not able to detect.
This is using a brand new USB cable i purchased - FEMORO USB to USB Cable 6ft, USB A 3.0 Cables Double Sided Cord Male to Male 5Gbps
If u think i should try with similar cable i can purchase one and give a shot
USB type-A is not capable of male-to-male unless standards are broken. Type-C is similar, but a bit of wiring trickery (“these are not the droids you are after”) which allows mixing of device and host in different ways than something with a type-A connector.
Are you sure this is a USB type-A to type-A?
I don’t know what you saw on the tutorial you saw on the Internet…
The flash port is the type C port… thus, it does not make sense to use a type A- type A cable here…
Tried with Type C Port still not luck SDKManager still doesnt recognize. Any thing else i can try?
Based on previous comment, you better taking a photo for how is your connection exactly.
It seems the tutorial video you are watching didn’t guide you correctly…
I guess the board is not in recovery mode either.
Also, try a native ubuntu host but not VM…
A VM which fails to pass through the USB would always cause the flash software to believe there is no Jetson in recovery mode, so I’ll double down on the VM probably being at fault. If you believe you got the Jetson procedure for recovery mode correct, then that almost has to be the issue since recovery mode hardware is quite reliable.
Incidentally, shorting the pins for recovery is like the shift key on a keyboard, but it modifies either power on or power reset. If recovery is held during power on, or at the moment of a power reset, then you will have it in recovery mode (there is no need to do things like hold it for 10 seconds).
I have been using native ubuntu host not VM
In that case there is only a need to verify the right USB port. On your Ubuntu host PC, if the Jetson is already in recovery mode, but the cable is not connected, monitor “dmesg --follow” on the host. Then plug in the cable and see what the new log lines are as a result of the plug-in. It is possible a cable is bad, but USB-C is not usually a problem; it is also possible that a specific port does not work for some reason on the host PC, so try multiple ports if there is no output to dmesg as a result of the USB plug-in (just make sure the Jetson is in recovery mode prior to plug-in).
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.