I am trying to boot the nano by flashing jetson-nano-sd-r32.1.1-2019-05-31 using etcher.
Whatever i do, and however i write that image, I am getting this error.
Direct firmware load for tegra21x_xusb_firmware failed with error -2
Any one knows what is the problem and how it can we fixed ?
I have read in the forum that we can boot from usb sticks but that is something that i don’t want to do for my setup.
Any help will be appreciated.
Thanks,
Hi sundeep.ec.aimt,
Are you using Etcher tool to flash image into SD card?
Your host machine is Ubuntu 16.04? or Windows?
Reference guide:https://developer.nvidia.com/embedded/learn/get-started-jetson-nano-devkit#write
I am using etcher as mentioned above.
I am using Ubuntu 16.04.
Hi sundeep.ec.aimt,
Can you download Etcher tool again?
And insert SD card to USB card reader try again. Thanks!
Hi,
What is the exact error here? One line error from UART? Could you share the full log?
Is your usb device working after boot up?
I have already tried this.
When i am inserting the memory card in Jetson and powering it on, i see NVIDIA Logo. after that it says that HDMI is plugged and i get this error. I am attaching a screenshot for reference.
Direct firmware load for tegra21x_xusb_firmware failed with error -2
How can i do get the log in this case ?
Thanks.
Hi,
I think you have similar issue with this one:
https://devtalk.nvidia.com/default/topic/1054926
Actually, if it boots up normally, there should be ubuntu GUI showing up on your HDMI monitor and ask you to use keyboard + mouse to configure your user account. The other user then hit usb error and cannot configure account and stuck.
Could you
enable the uart debugger to dump full log
go to the #37 of that thread and use that script to bypass the account configuration of ubuntu?
Also, since you miss both gui and usb firmware, could you help go to below folder of your host and check whether usb firmware exists or not?
-> nvidia/nvidia_sdk/JetPack_4.2_Linux_P3448/Linux_for_Tegra/rootfs/lib/firmware/tegra21x_xusb_firmware
I have the same problem, and I can’t see how this solves it.
I have tried flashing several versions of the sd card image, all gives me the same error. The #37 mentioned seems to use the jetpack on host which is very inconvenient in my situation. If this is the only way, I’ll do it but would much prefer just using sd card image in this instance.
Can you please clarify if I got this wrong? Does this works for sd card flashing as well?
I have tried the image from https://developer.nvidia.com/jetpack-422-archive, the last image from https://developer.nvidia.com/embedded/jetpack
I flash tried two different cards (32gb) that are known to work, flashed with etcher and dd. Nothing works
my current jetpack is… very old. I have no idea how to find out which one exactly but 3.x
Hi,
Since I don’t get response from previous user, I cannot tell you what happened.
Sometimes the firmware takes few retry to get loaded. If your usb device is working fine, then no need to worry about this error.
The boot does not complete and I get no UI, also can’t connect headless…
so something is going wrong.
let me know if you need any more information. It is strange I am the only one getting this.
And I don’t get your statement here.
I flash tried two different cards (32gb) that are known to work, flashed with etcher and dd. Nothing works
my current jetpack is… very old. I have no idea how to find out which one exactly but 3.x
What is 3.x ??
Sorry, since then I installed jtop and my jetpack is 4.2 (L4T 32.1.0). I thought it was older.
If you already tried quite times of re-flash, then I think you are free to erasing the data on sd, right?
If so, why not just upgrading the jetpack version?
This is a production system (well, sort of) and I don’t want to face upgrading and then having nothing to boot from
currently, I just switch back to my original card and can re-run my system while pondering the wonders of software engineering…
I will give it another try with yet another card that arrived fresh yesterday, and another card reader for the flashing.
will keep you posted…
btw, please check the serial console log.
It will tell us what is going on.
I need to dig my ttl to usb cable… have it somewhere.
New card, new card reader and all is well now! Thank you for all your help
