lsusb simply says one of the following if present:
- A recovery mode Jetson is detected, or
- A booted Jetson with virtual wired ethernet is detected.
No flash can be completed if the unit did not start in recovery mode. A successful flash results in the Jetson rebooting. After reboot, if the account is set up, then ssh is used by SDKM to add packages. I’m not sure if the repo is already installed or not before ssh starts. Examining the repos after a flash would be fairly easy, and you could avoid installing those extras until you’ve examined this since extras can be installed at any time.
When a Jetson is fully booted, and if the defaults have not been changed, then you are correct that
lsusb should show up. If this is not the case, then you’d want to use serial console to see what is going on. Technically you could log in directly at the Jetson and get this same information if basic boot succeeded and first boot setup is complete, but often if something went so wrong that the micro-USB is not showing up, then something else went wrong and you would often not get to log in directly. Serial console boot log is the key to knowing what is going on.