Target SSH Access from the Linux Host

The target should have an IP address assigned automatically by the network or the host system to which it is connected. For more information about enabling the DHCP server on your development host to connect the target directly, see the NVIDIA DRIVE® OS 6.0 SDK Developer Guide section in Setting Up Networking on the Host and Target.

During the initial setup of the target device, you are prompted to choose an SSH profile. If you choose the DRIVE OS Linux Secure Login profile, see the DRIVE OS 6.0 SDK Developer Guide section in SSH Key-Based Authentication from Clients to Server to create a key on the Linux host to connect to the target.

The DRIVE AGX Devkit is pre-flashed with the SSH server installed and enabled by default. If you flash with base DRIVE OS SDK Debian build, which uses the driveos-core-rfs filesystem, the SSH server will not be installed by default. Therefore, you need to install and set up by following the instructions as described in DRIVE OS Linux SSH Server. If you install the driveos-oobe-desktop filesystem by following the instructions in the Finalize DRIVE AGX System Setup (Linux) section, the SSH server will be enabled by default.

To confirm the overall network and SSH installation, follow these steps:

  1. Verify that the target can communicate to the host by using the ping command.

    $ ping <target-IP>
  2. Launch the SSH client.
    $ ssh <user>@<target-IP>
    Use the username and password that were set for the system setup during the initial boot process. Verify that same terms are used here. Follow the steps in the software guides found at

If the ping or ssh command is not successful and the target does not respond, you can launch the UART terminal (Minicom) to access the target.

  • Ensure that only one DRIVE AGX platform is connected to the USB port on the host system.
  • On the host system, verify that ttyACM0 and ttyACM1 are listed under the /dev/ folder.
  • Run Minicom.
    $ minicom -D /dev/ACM0
  • Check the IP address.
    $ ifconfig eqos_0