1. Requirements for Your Development Environment

1.1. Getting Started

Follow these high-level steps in order to set up your development environment – host machine and target DRIVE AGX Developer Kit:

  1. Verify you meet the system requirements for installing software on your DRIVE AGX Developer Kit.

  2. Review the Important Installation Information section.

  3. Review other important documentation, such as:

    • DRIVE OS 5.2.6 Release Notes

  4. Download SDK Manager.

  5. Finally, review the SDK Manager installation section of this guide to install DRIVE OS with DriveWorks on your host machine, and flash the target device.

  Note:  

Please try our new "Beta" DRIVE OS Docker containers on NVIDIA GPU Cloud. For more information, see Install DRIVE Docker Containers from NVIDIA GPU Cloud (NGC).  

Note that you still need to install DRIVE OS via SDK Manager for source and sample code.  

2. System Requirements

 Category   Requirement 

Host Machine 

  • Ubuntu Desktop 18.04 LTS

  • Working Internet connection

Architecture 

X86_64

Memory  

8GB

Free Disk Space 

A minimum of 40GB and up to 120GB (during flash) free disk space on the system volume is needed for each full (host and target) deployed SDK version.

GUI 

X11 must be enabled on the host.

Graphics Driver 

The most recent graphics driver for your GPU needs to be installed on the host system. To update your driver, use one of the following methods: 

WARNING: Do not mix both the download and apt-get methods, as this is not supported.

The CUDA version and minimum Linux x86_64 graphics driver for the DRIVE OS  5.2.6.0 release is:

 CUDA Toolkit     Linux x86_64 Driver Version  
 CUDA 10.2.526    >=450.102.04  

Target Device 

The following supported development platform:

Additional Hardware 

A2A USB cable to connect the host machine to the target

3. Important Installation Information

  Note:  

We care about the safety and security of your data; therefore, you will be prompted to enter a new Linux username and password during the installation process.

For DRIVE OS users, SDK Manager will prompt you via the target Linux console to enter a new Linux username and password before flashing.  

  Note:  

Beginning with this DRIVE OS Linux 5.2.6 release username, password, and security profile/setup will remain persistent on later flashes once they are set the first time after flashing the 5.2.6 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 when downgrading to an earlier release. See the DRIVE OS 5.2 Linux Developer Guide sections on Persistence across Bootburn Flashing for information on removing the persistent data, and User Management for information on adding/deleting/changing users or changing the security profile and settings.   

  Note:  

MCU Power Good LED Notification

The Aurix MCU controls the board power-up sequence on the DRIVE AGX Developer Kit. An error was found in some power devices for 5V rails on the DRIVE AGX board such that they may not provide proper voltage output if enabled when voltage is in a certain range. To work around this, the Aurix MCU FW in the release implements a feature to monitor these voltage rails and not power up these rails until the existing voltage is in the proper range. However this will increase the time required for the board to boot or for the board or Xavier devices to reset (i.e., aurixreset or tegrareset commands) to ~14 sec in the average case. In addition, if voltage rails never fall to a valid level after 30 seconds, then the rails will be powered up and the board will boot, but board functions may be affected.

Because of this, the Aurix MCU indicates the board status using one LED located next to the debug USB port. For healthy boot with no error, the LED will blink once every four seconds (i.e., Power Good indication); for error timeout, the LED will blink three times rapidly every four seconds (i.e., Power Bad indication). More information on this is given in the Development Guide section "MCU LED Notification."

In order to verify that networking is properly configured for the DRIVE AGX Developer Kit, please review the DRIVE AGX board setup information found here.

Also note the Additional Resources section of this document, which provides links to useful information for configuring your NVIDIA DRIVE AGX Developer Kit.

3.1. Valid Migration Paths

If you are installing NVIDIA DRIVE™ OS on DRIVE AGX Xavier or DRIVE AGX Pegasus System for the first time, please skip to the Download and Run SDK Manager section.

If you previously installed a different version of DRIVE OS or DRIVE Software, this section provides important information about supported migration paths between DRIVE OS (with and without DriveWorks) and DRIVE Software releases.

Each release of NVIDIA DRIVE OS provides increasing levels of capability and reliability. Additionally, each release provides slightly different features that may be more suitable for your application. In most cases, you will install newer DRIVE OS versions as they are released. However, in some cases, you may decide to install an earlier release.

The tables below describe the supported DRIVE OS and DRIVE Software migration paths. For example, before you install another product version over another product version, please ensure that migration path is supported. If a desired migration path is unsupported, you may need to install another product version first before installing the desired product version.

The specific order or product versions allows the installer to address product version differences, such as VBIOS, PCIe, and Aurix.

For information on the features added in each release, ask your NVIDIA representative for the release notes for DRIVE OS or DRIVE Software for the releases under consideration.

3.1.1. Update Matrix: DRIVE OS and DRIVE Software

To update to DRIVE OS 5.2.6.0, you must have a previous release on your host development environment and flashed on your target DRIVE AGX System, which is noted as supported for upgrade to DRIVE OS 5.2.6.0 in the table below.

Once your host development environment and DRIVE AGX System are updated to DRIVE OS 5.2.6.0, you may only downgrade to previous releases noted as supported in the table below.

 From:  To: 
 DRIVE Software 10.0   DRIVE OS 5.1.12   DRIVE OS 5.1.15   DRIVE OS 5.2.0   DRIVE OS 5.2.3.0   DRIVE OS 5.2.6.0 
N/A See Note #1 NO NO NO See Note #1  DRIVE Software 10.0 
See Note #1 N/A YES NO NO NO  DRIVE OS 5.1.12 
NO YES N/A YES NO NO  DRIVE OS 5.1.15 
NO NO YES N/A YES YES  DRIVE OS 5.2.0 
NO NO NO YES N/A YES  DRIVE OS 5.2.3.0 
YES NO NO YES YES N/A  DRIVE OS 5.2.6.0 

 

  YES  

Supported   

  NO  

Not supported   

  Note #1  

Not directly supported. Contact your NVIDIA representative for details.    

 

Previous | Next

  Previous Topics     Next Topics  

Home    

Download and Run SDK Manager    

Install DRIVE with SDK Manager    

 

Notices

Notice

THE INFORMATION IN THIS GUIDE AND ALL OTHER INFORMATION CONTAINED IN NVIDIA DOCUMENTATION REFERENCED IN THIS GUIDE IS PROVIDED “AS IS.” NVIDIA MAKES NO WARRANTIES, EXPRESSED, IMPLIED, STATUTORY, OR OTHERWISE WITH RESPECT TO THE INFORMATION FOR THE PRODUCT, AND EXPRESSLY DISCLAIMS ALL IMPLIED WARRANTIES OF NONINFRINGEMENT, MERCHANTABILITY, AND FITNESS FOR A PARTICULAR PURPOSE. Notwithstanding any damages that customer might incur for any reason whatsoever, NVIDIA’s aggregate and cumulative liability towards customer for the product described in this guide shall be limited in accordance with the NVIDIA terms and conditions of sale for the product.

THE NVIDIA PRODUCT DESCRIBED IN THIS GUIDE IS NOT FAULT TOLERANT AND IS NOT DESIGNED, MANUFACTURED OR INTENDED FOR USE IN CONNECTION WITH THE DESIGN, CONSTRUCTION, MAINTENANCE, AND/OR OPERATION OF ANY SYSTEM WHERE THE USE OR A FAILURE OF SUCH SYSTEM COULD RESULT IN A SITUATION THAT THREATENS THE SAFETY OF HUMAN LIFE OR SEVERE PHYSICAL HARM OR PROPERTY DAMAGE (INCLUDING, FOR EXAMPLE, USE IN CONNECTION WITH ANY NUCLEAR, AVIONICS, LIFE SUPPORT OR OTHER LIFE CRITICAL APPLICATION). NVIDIA EXPRESSLY DISCLAIMS ANY EXPRESS OR IMPLIED WARRANTY OF FITNESS FOR SUCH HIGH RISK USES. NVIDIA SHALL NOT BE LIABLE TO CUSTOMER OR ANY THIRD PARTY, IN WHOLE OR IN PART, FOR ANY CLAIMS OR DAMAGES ARISING FROM SUCH HIGH RISK USES.

NVIDIA makes no representation or warranty that the product described in this guide will be suitable for any specified use without further testing or modification. Testing of all parameters of each product is not necessarily performed by NVIDIA. It is customer’s sole responsibility to ensure the product is suitable and fit for the application planned by customer and to do the necessary testing for the application in order to avoid a default of the application or the product. Weaknesses in customer’s product designs may affect the quality and reliability of the NVIDIA product and may result in additional or different conditions and/or requirements beyond those contained in this guide. NVIDIA does not accept any liability related to any default, damage, costs or problem which may be based on or attributable to: (i) the use of the NVIDIA product in any manner that is contrary to this guide, or (ii) customer product designs.

Other than the right for customer to use the information in this guide with the product, no other license, either expressed or implied, is hereby granted by NVIDIA under this guide. Reproduction of information in this guide is permissible only if reproduction is approved by NVIDIA in writing, is reproduced without alteration, and is accompanied by all associated conditions, limitations, and notices.

Trademarks

NVIDIA, the NVIDIA logo, and cuBLAS, CUDA, CUDA-GDB, CUDA-MEMCHECK, cuDNN, cuFFT, cuSPARSE, DIGITS, DGX, DGX-1, DGX Station, NVIDIA DRIVE, NVIDIA DRIVE AGX, NVIDIA DRIVE Software, NVIDIA DRIVE OS, NVIDIA Developer Zone (aka "DevZone"), GRID, Jetson, NVIDIA Jetson Nano, NVIDIA Jetson AGX Xavier, NVIDIA Jetson TX2, NVIDIA Jetson TX2i, NVIDIA Jetson TX1, NVIDIA Jetson TK1, Kepler, NGX, NVIDIA GPU Cloud, Maxwell, Multimedia API, NCCL, NVIDIA Nsight Compute, NVIDIA Nsight Eclipse Edition, NVIDIA Nsight Graphics, NVIDIA Nsight Systems, NVLink, nvprof, Pascal, NVIDIA SDK Manager, Tegra, TensorRT, Tesla, Visual Profiler, VisionWorks and Volta are trademarks and/or registered trademarks of NVIDIA Corporation in the United States and other countries. Other company and product names may be trademarks of the respective companies with which they are associated.