SSH Connectivity Issue with Nvidia Jetson Orin Nano on Custom Carrier Board

Issue Overview

The user is experiencing connectivity problems with their Nvidia Jetson Orin Nano development board after flashing it with JetPack 5.1.1 SDK. While the device boots up and displays output via HDMI, it fails to be detected by the user’s laptop when connected via a micro-B USB cable. This issue appears to be specific to the Orin Nano module, as the user reports no problems when using other System on Modules (SoMs) like the Orin NX on the same custom carrier board.

The primary concern is the inability to establish an SSH connection to the device using the expected IP address (192.168.55.1), which is typically used for development and debugging purposes. This problem potentially hinders the user’s ability to interact with and develop for the Orin Nano module efficiently.

Possible Causes

1. Custom Carrier Board Compatibility: The issue may stem from compatibility problems between the custom carrier board and the Orin Nano module. While the board works with other SoMs, it might not be fully compatible with the Orin Nano’s specific requirements.

2. USB Driver Issues: There could be problems with USB drivers on the host laptop, preventing it from recognizing the Orin Nano when connected via micro-B USB.

3. Flashing Process Errors: Incomplete or incorrect flashing of the JetPack 5.1.1 SDK might have resulted in missing or corrupted components necessary for USB connectivity.

4. Hardware Defect: Although less likely, there’s a possibility of a hardware defect in the micro-B USB port or related circuitry on either the Orin Nano module or the custom carrier board.

5. Network Configuration Issues: The problem could be related to network configuration on either the host laptop or the Orin Nano, preventing the establishment of the expected 192.168.55.x network.

Troubleshooting Steps, Solutions & Fixes

1. Verify UART Connectivity:

   • Confirm that you can log in to the device via UART. This helps isolate whether the issue is specific to USB/SSH or if it’s a more general connectivity problem.

2. Check Network Configuration:

   • When connected via micro-B USB, verify if the expected network is created on your host laptop:

     ip addr show
     

   • Look for a network interface with IP 192.168.55.100.
   • On the Orin Nano (via UART), check if the device has the correct IP:

     ip addr show
     

   • Look for an interface with IP 192.168.55.1.

3. Test with Official Nvidia DevKit:

   • If possible, test the Orin Nano module on an official Nvidia DevKit to determine if the issue is specific to your custom carrier board.

4. Update USB Drivers:

   • Ensure your host laptop has the latest USB drivers installed, particularly any specific drivers for Nvidia Jetson devices.

5. Reflash JetPack SDK:

   • If the issue persists, consider reflashing the JetPack 5.1.1 SDK to rule out any corruption during the initial flashing process.

6. Check Carrier Board Design:

   • Review your custom carrier board design, focusing on the USB connectivity components. Ensure they meet the specifications required by the Orin Nano module.

7. Test Alternative SSH Methods:

   • If USB SSH remains unavailable, consider setting up SSH over Wi-Fi or Ethernet as an alternative development method.

8. Contact Nvidia Support:

   • If the issue persists and you’ve confirmed it doesn’t occur with the official DevKit, consider reaching out to Nvidia support for further assistance with your custom board implementation.

Remember that while the SSH issue via micro-B USB appears to be specific to your custom setup, the Orin Nano itself is capable of this functionality when used with the official DevKit. This suggests that the root cause is likely related to the interaction between your custom carrier board and the Orin Nano module.