Not sure if any of this will help, but a few things come to mind…
The micro-OTG connector of a Nano only works as “device mode”, and since it cannot be a host, if you connect any kind of keyboard there, then it won’t work…those are devices too, and it needs a host. When fully booted there are some utility functions associated with that port. When in recovery mode (you have to short the recovery pin to ground while either starting power or resetting power, then let go of the recovery pin short), then the “driver package” recognizes the Nano as a custom USB device (and the driver package runs on the Ubuntu host PC). I assume you are using the full-sized USB port for keyboard/mouse, so this is unlikely an issue, but it is useful to know about the micro-OTG port. You’ll still want to be sure to check you’ve jumpered the correct pins to get to recovery mode.
Note that on the Linux host PC, you can run this command to monitor USB devices with an NVIDIA ID:
watch -n 1 lsusb -d '0955:'
…as you plug in or unplug the USB to the host PC you should see a USB device if (A) the Jetson is fully booted, or (B) the Jetson is in recovery mode.
Also, if you monitor “
dmesg --follow” on the host PC, then as you plug in anything USB there should also be a note there.
Note that there are two ways of applying power to a Nano dev kit. I think there are some differences depending on model, but basically there is also a barrel connector, and if the barrel connector is used, then you must have the jumper installed. If the micro-OTG port is used to power the Nano, then the jumper should be removed. You’ll want to check the jumper for power issues.
Since Jetsons don’t have a BIOS (flashed software essentially flashes what would be a software version of a BIOS every time you flash, even on the SD card model when no SD card is present) you’ll never see early boot messages. If you really want to see what goes on you’ll need to use a serial console. See:
Trivia: Unlike the driver for desktop PC video cards the GPU in the Jetson can only use the custom driver installed from flash because it does not use the PCI bus (and PCI-based video detection schemes fail on a Jetson). The GPU driver will differ because it is directly integrated with the memory controller. Some of the video setup knowledge used for a desktop GPU setup does not apply to a Jetson.