Connection refused
Board not fully booted yet
Wait 60–90 seconds after power-on and retry
No route to host
Host PC interface not configured
Check ip addr on host, assign 192.168.55.x address manually
Connection timed out
USB cable not connected or wrong port
Try a different cable or USB port; verify USB Ethernet interface appears in ip addr
USB interface does not appear
Driver issue or cable fault
Try a different cable; verify the USB connection is data-capable (not charge-only)
Verify the power supply voltage matches the VDD_MAIN specification for your extension board.
Check that the Jetson compute module is fully seated.
Try connecting HDMI to a monitor to see boot messages.
If the board previously had a failed flash, enter Recovery Mode and re-flash.
lsusb shows nothing)Ensure the USB cable is connected before entering recovery mode.
Verify you are using a data-capable USB cable (not a charge-only cable).
Try a different USB port on the host PC (prefer USB-A 3.0 ports).
On some systems, the device may enumerate briefly - run watch -n 1 lsusb to catch it.
tegrastats returns an errorEnsure the system is running a JetPack-based image.
If using a custom image, verify that the BSP and L4T packages are correctly installed.
Flash the correct image using dcs-deploy. See Flashing a New System Image.
Last updated