You’d want to get the serial console log from a normal boot without recovery mode. You should be able to get some debug information if you start logging serial console prior to applying power to the Orin Nano. It is useful to see serial console log during flash itself whenever flash is failing, but just seeing what goes on during normal boot is where you would start. Also, if the system is just failing at graphics the serial console would allow first boot setup and logging in to access on command line (which in turn would offer the GUI log).
I should not have mentioned the TTL cable, which is still useful with the serial UART on the header, but if the USB-C has serial console (I don’t know for sure if it is that or the pins 8 and 10 which have this), then you wouldn’t need the TTL cable (I don’t have an Orin Nano to look at).
Now something which does look wrong is on the
lsusb output I see this:
Bus 001 Device 017: ID 0955:7523 NVIDIA Corp. APX
APX” usually shows up with a VM. If the host PC is a VM, then I’d expect flash failure, and although it could work well for serial console or other purposes, a VM often has incorrect default USB setup which will cause USB to fail. Make sure to always use a native Ubuntu (18.04 or 20.04 will work, 20.04 being preferable).
I’m going to suggest checking serial console again during boot (not recovery mode), but check with
gtkterm. You’ll probably need to “
sudo apt-get install gtkterm”. Since the port is
ttyUSB0, this should work:
sudo gtkterm -b 8 -t 1 -s 115200 -p /dev/ttyUSB0
If you get no log from that, it is time to use JetPack/SDK Manager to flash the QSPI memory on the Nano module. You’d want to use the most recent release (L4T release and JetPack releases are tied together, so if you pick one or the other it leads to the same thing). You can find the releases here:
Note for NVIDIA: I don’t see the Orin Nano listed in in the L4T listing, but I do see it in the JetPack 5.1.1 listing. Probably the L4T release page needs to have the Orin Nano added.
For reference, Jetpack 5.1.1 matches L4T R35.3.1 and shows it works with Orin Nano.
I want to emphasize that although a VM can work, VMs often fail because they need the USB properly configured to keep the USB even when it disconnects and reconnects. WSL2 is particularly problematic because, if an image is being created, it needs loopback to be added. If you see
APX you should suspect a VM.