Getting Started with DRIVE OS 6.x Linux Development

This guide is for the users of the DRIVE OS Linux operating system running on the NVIDIA DRIVE AGX platforms.

Target SSH Access from the Linux Host

If using a network connection ("Preferred method"), ensure the target and host system are both connected to the same network. Both the target and the host will be assigned an IP address automatically.

If a direct connection between the host and the target is required, refer to the DRIVE OS 6.0 SDK Developer Guide Setting Up Networking on the Host and Target for more information about enabling the DHCP server.

As discussed in Finalize DRIVE AGX Orin System Setup, 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 Developer Kit is pre-flashed with the SSH server installed and enabled by default. If you flash the developer kit with SDK Manager or Docker, the SSH server is also installed and enabled by default. However, if you flash with the 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.

Note: While ping and ifconfig are not installed by default in the DRIVE OS Docker, ssh client and rcp are, so the user will be able to ssh/rcp between the Docker and target using the following procedures.

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 the 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.

  1. Ensure that only one DRIVE AGX platform is connected to the USB port on the host system.

  2. On the host system, confirm the ttyACM0 and ttyACM1 are listed under the /dev/ folder.

  3. Run Minicom.

    minicom -D /dev/ttyACM0
  4. Check the IP address.

    ifconfig eqos_0
Note: eqos_0 is the interface name for the RJ45 interface on the lower center of the Developer Kit backpanel. If other Developer Kit Ethernet interfaces are used, the interface name will vary.