previously Ubuntu prompted me to update to 20LTS and I did not think well and pressed to update which was a mistake. Now trying to flash it and it’s out of space and SDKManager does not see it neither via USB or Ethernet.
Need more ideas or strategies.
I’m not sure 20 LTS would work on the Jetson itself (possibly with L4T R32.3.1+ since it is using packages now, but I am skeptical without testing), and would quite possibly need flashing even if you were not out of space (I am assuming you mean you mean the Jetson is out of space, not the host PC).
In recovery mode it won’t matter what you have flashed (or missing) on the TX2. With the micro-B USB connected the host should see it with “
lsusb -d 0955:7c18”. If you are using a third party charger cable, then those tend to fail, but usually intermittently.
Use of wired ethernet or virtual USB wired ethernet requires the unit to be booted and functional, at least up to that part of boot (so for example a lack of GUI does not necessarily mean ssh will fail, but if networking never came up, then it is likely boot never got to the GUI stage). In your case I will say it is just easier to flash (and possibly clone first if you have something valuable on it), but if you really want to see what is going on, then you should use serial console:
The next question becomes one of whether you want to clone before flashing, and either way, if you can reach recovery mode and see the device on the host PC with “
lsusb -d 0955:7c18”?
You are right, 20 LTS does not work well on it at all. I checked the USB-cable and it does not look like what I see as a standard cable (with green markers on either side). So I will go ahead and order the standard NVIDIA cable and if that does not work, I will try to re-approach with a serial cable.
Thanks a lot for the prompt response!
Hi! So I have ordered the official micro-USB - USB cables and a serial cable and still when I start the boot, I get flooded b this message:
So, the boot never ends, I can’t interrupt it. However, LT4 appears but the SDKManager does not manage to initiate the flash process. So I am lost on where to start.
During a normal flash with what starts as a stock Ubuntu 18.04 LTS several direct hardware access drivers and libraries are added. Those drivers and libraries probably have dependencies, and some would possibly work under Ubuntu 20.04, but many would fail (e.g., ABI or API differences). I have no way to speculate on the specific failure, but it is highly likely this is something you would have to build some sort of compatibility into 20.04 such that it could use the 18.04 files.