Finalize DRIVE AGX Orin System Setup

Note: If the End User License Agreement (EULA) has not been accepted on the DRIVE AGX Orin Developer Kit, the DP display will not be activated when flashing is completed. The user must connect to the DRIVE AGX platform console via a terminal emulator to determine when flashing has been completed, and to complete the platform setup.

Instructions for connecting a terminal emulator to the platform are in the NVIDIA DRIVE OS Linux SDK Developer Guide sections Using tcu_muxer and Terminal Emulation. You can connect the Developer Kit using the following command:

sudo minicom -w -D /dev/ttyACM(0/1)
Note: The username, password, and security profile/setup will remain persistent on later flashes once they are set the first time after flashing the DRIVE OS SDK release. The user will not be prompted for this information again when flashing this or later releases. However, the user may need to clear the persistent data when downgrading to an earlier release. See the NVIDIA DRIVE OS Linux SDK Developer Guide section on Methods to Reset Persistence Partition for information on removing the persistent data, and User Management for information on adding/deleting/changing users or changing the security profile and settings.   
  1. Accept EULA and Set Admin Username/Password.

    See the NVIDIA DRIVE OS Linux SDK Developer Guide section on DRIVE OS Linux oem-config for more information on these prompts. (This is only needed for the first boot out of the box, and does not apply to SDK Manager or Docker flashed systems, unless persistent data is cleared.)

  2. Select SSH Profile and Other Setup Options.

    DRIVE OS Linux provides two profiles for security setup (including SSH): an NVIDIA enhanced security profile that uses ECDSA-based algorithms for SSH security, or stock Ubuntu 20.04 configuration. The customer must select the profile on the first setup screen. Both profiles will enable SSH server in the target by default.

    The user can follow the other prompts after SSH profile selection to install additional users; see DRIVE OS Linux oem-config for more information [not prompted if already set on DRIVE OS Linux first flashing]. After these prompts are completed, the platform will boot to the prompt to enter the username.

Note: If you flash with NGC Dockers with the bootburn --init_persistent_partitions option, the new login and password is not set on the target on flashing, and the expected system configuration screens do not appear. You can still add/delete user logins or change passwords using the information in the NVIDIA DRIVE OS Linux SDK Developer Guide section on DRIVE OS User Management.
Note: You do not need to use sudo for the following commands:
However, if you choose to use sudo for one, use it consistently with the others. Do not switch between sudo/non-sudo usage.