My Jetson Orin Nano Dev Kit splash screen displays the following errors on boot:
L4TLauncher: Unable to locate L4T Support protocol: Not Found
L4TLauncher: Using legacy interface. Support would be deprecated soon!!
L4TLauncher: Failed to get PlatformResourceInfo
Error: Could not detect network connection.
This occurs after both:
Using the following dd command (on an inserted, unmounted microsd card in an sd card reader).
And also after using Balena Etcher to copy and verify the sd image.
Notes:
i. I tried both methods on separate troubleshooting attempts.
ii. Firmware version is 36.2.0-********, so I shouldn’t need to update the firmware.
iii. I was previously successful with the dd command on jp61.
iv. To boot up the Jetson Orin Nano Dev Kit, I insert the microsd and plug in the power cord. I don’t run any commands.
What can I do to troubleshoot next?
a. My next best guess would be a new microsd card and sd card reader, however Balena Etcher did successfully verify the copied image so I’m not positive this is an issue with my sd card.
Hi,
I bought my Jetson Nano last month and was faced with exactly the same problem.
To solve the problem I only had to follow the steps as described in this document https://www.jetson-ai-lab.com/initial_setup_jon.html
In the meantime everything works perfect with JetPack 6.2 which runs from SDCard.
Good luck!
@WayneWWW Ubuntu recognizes something was plugged into /dev/ttyUSB0 but I haven’t been able to get any sort of logs show up with minicom nor w/ the program screen.
What I did:
I connected the following on the Jetson Orin Nano Dev Kit:
Green wire → RXD
White wire → TXD
Black wire → GND
I used sudo dmesg | tail to view which /dev/***I was connecting to.
I set minicom settings to what was mentioned.
I tried setting software control flow to both on/off.
And I tried powering the jetson orin nano dev kit off and on a few times.
What I did notice:
minicom will complain that it “cannot open /dev/ttyUSB0” IF I unplug the USB, but this message goes away as soon as I plug it back in. This happens regardless of whether Jetson Orin Nano Dev Kit is on or off (or even connected at all).
minicom has a persistant “offline” label at the bottom of the terminal
What else can I do to troubleshoot this?
I have quadruple checked that my pins are connected to the correct locations. Their labels are slightly above the pins themselves.
My next best guess is was to wiggle the connected wires a bit to see if there is a bad connection. Unfortunately this doesn’t seem to affect anything.
Exact same problem. On booting, after the error that @zdilly described the Orin drops into a simple shell mode. I followed the instructions at NVIDIA’s 🚀 Initial Setup Guide - Jetson Orin Nano - NVIDIA Jetson AI Lab with care. I tried both a 64 Gb and 128Gb sd card. Under Jetpack 5.13, I was able to update the firmware to 5.0-36585864 verified by the Orin’s UEFI. The board’s hardware worked BEFORE the firmware update under Jetpack 5.13 on the same 64Gb sd card noted above. So I believe the hardware and the sd card are sound. For those of us without a second PC running Ubuntu, the SDK Manager approach is unavailable. What else could be the boot problem?
Yes, I tried but with no luck at all.
sdkmanager went from step 1 to step 3 without any problem but when I got ready to flash the sd card, it compains the USB cable connecting the Ubuntu machine and Jetson Orin nano is not good enough and ask me to change to another one. I tried more teen different cables including usb 2, 3.0,3.1 3.2 (including 3.2 gen 2x2 the guide wants), and usb 4.0. None of them works with sdkmanager. Sometimes, the sdkmanager could not even detect the Jetson. All of these cables have been good to connect to defferent devices (Monitors, keyboards, usb SSD,) At the end, I gave up sdkmanager.
When I try the sd card method the setup window always complains nable to locate L4t support protocol Not found.
The next step, I think i wil buy a ttl-USB convert cable to check the boot log to see what is happening there. I also tried to set up a larger RAMdsik (say, 8000000), it does not help either.
I realy have very tough with this little board. It would very nice if there is anyone out there can tell me what to do?
@zdilly I think you are right, but how frustrating that the SD method described by NVIDIA does not work for many buyers of the Orin Nano. I’d like to know if the L4T error message implies a firmware issue or not. Surely NVIDIA pros can speak to that?? @wenwx I sympathize with your frustration. Based on what I read, you definitely need a TTL-USB cable to use the SK Manager. @zdilly : which USB port on the Orin did you use when you successfully ran the SDK Manager?
I come from software world so troubleshooting with physical hardware is quite different for sure. Stick with it and your frustrations will be worth it!
I used USB-C when connecting Jetson Orin Nano to computer and SDK Manager in order to flash.
Yes, this is still an issue. A lot of us do not have access to a standalone Ubuntu PC to run SDK Manager. If having one is a hard requirement, then NVIDIA should advertise that fact, or help us pinpoint the boot error and help find a workaround. Surely somebody at NVIDIA can interpret the L4T boot error?
I finally found my way through! The usb problem for sdkmanager was caused by my ubuntu notebook usb auto suspend. I just disabled the autosuspend setting, everything is now ok thanks for the suggestions from both ChatGpt and Gemini. However, i still have not found a way to solve the l4t problem,