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
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 DRIVE™ OS 6.0 SDK Developer Guide section on Setting Up Networking on the Host and Target.
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 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.
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:
Verify that the target can communicate to the host by using the
ping
command.ping <target-IP>
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 developer.nvidia.com/drive/start.
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, confirm the
ttyACM0
andttyACM1
are listed under the/dev/
folder.Run Minicom.
minicom -D /dev/ttyACM0
Check the IP address.
ifconfig eqos_0
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.