What is DRIVE Software?

NVIDIA DRIVE Software is a software package used for developing autonomous vehicles. DRIVE Software contains modular SDKs (DriveWorks, DRIVE IX), System Software (DRIVE OS), Reference application (DRIVE AV Roadrunner) and developer tools.


What is DRIVE OS?

NVIDIA DRIVE™ OS is a foundational software stack consisting of an embedded Real Time OS (RTOS), hypervisor, NVIDIA® CUDA® libraries, NVIDIA Tensor RT™, and other modules that give you access to the hardware engines. DRIVE OS offers a safe and secure execution environment for applications such as secure boot, security services, firewall, and over-the-air updates. Plus, it offers a real-time environment with an RTOS and a hypervisor for Quality of Service (QoS). The RTOS, AUTOSAR, and hypervisor are ASIL-D components.


What is DriveWorks?

NVIDIA® DriveWorks is an SDK that consists of a library of software modules, sample applications and tools to enable software development for autonomous vehicles. DriveWorks leverages the computing power of the DRIVE AGX platforms and is designed to be open, modular and compliant with automotive industry software standards such as ISO26262 and MISRA-C. DriveWorks can be downloaded as part of the DRIVE Software releases.


What is DRIVE IX?

NVIDIA DRIVE™ IX is an SDK used for developing in vehicle applications for safety, comfort and enhancing the user experience. For more information on how to get started, refer to our DRIVE IX developer page.


Where can I buy a DRIVE AGX Developer Kit?

The DRIVE AGX Developer Kit is available exclusively for members of the NVIDIA DRIVE Developer Program for DRIVE AGX. Your company or university must have current legal agreements on file. Please contact your NVIDIA Representative (or contact us) to ensure necessary agreements have been signed before requesting to join the program. Users may only join with a corporate or university email address.


How can I get started with the DRIVE AGX DevKit?

Congratulations for getting your NVIDIA DRIVE AGX DevKit! The Onboarding Guide for NVIDIA DRIVE AGX DevKit provides an overview of all resources relevant to help you start your development.


Where can I find the list of DRIVE AGX compatible sensors and other peripherals?

The DRIVE AGX Platforms are compatible with a number of sensors and peripherals from different vendors. A full list is available on the DRIVE Ecosystem Hardware and Software Components.


What are the differences between the DRIVE AGX and the Jetson AGX Developer Kits?

While both the Jetson AGX and DRIVE AGX kits use the same Xavier SoC, DRIVE is built for automotive applications. The following table highlights the differences between the two platforms.

Jetson AGX
DRIVE AGX
Hardware
DL Inference INT8 (TOPS)
32
60 (Xavier)/320 (Pegasus)
GMSL Interface
Needs external board
Integrated SerDes
CAN Interface
2
6
Flexray Interface
No
2 Flexray interfaces to MCU
MCU
No
Infineon Aurix TC397
Auto-Grade Memory
No
Yes
ECC Enabled
No
Yes
Input Voltage Range
5V (Medium), 9V to 20V (High)
7V to 28V
Operating Temperature
-25C to 80C
0 to 45C
Automotive Sensors Support
No
Cameras, lidars, radars, GNSS/IMU
Full list on DRIVE Ecosystem Hardware and Software Components
Software
Operating System
Linux4Tegra (Ubuntu)
DRIVE OS Linux (Ubuntu)/QNX
Bootloader
Cboot
Quickboot
Computer Vision
VisionWorks/OpenCV
NvMedia (VPI)
Multimedia
MM API/V4L2 API/Gstreamer (Running up to 6 cameras simultaneously of 30 frames/second)
NvMedia (Capture up to 16 cameras for simultaneous processing with hardware acceleration)
Imaging
Librargus (Multimedia, ISP access)
NvMedia SIPL
Autonomous Dev SDK
No
DriveWorks (Interoperability with ROS and deterministic scheduler capabilities coming later)
Autonomous Dev Tools/Framework
CUDA
TensorRT
DriveWorks: Sensor abstraction (Pre-Flight_Checker, Rig_Viewer, SIPL_Query, Sensors_Initialization), image/point cloud processing, vehicle I/O, DNN framework (TensorRT_Optimizer for Caffe, UFF and ONNX models), recorder (Recording_Chopping, Post-recorder_Checker, Video_Exporter, Replayer, CAN_Recording), calibration (Static camera & IMU calibration), egomotion
DRIVE OS: NvMedia, NvSteams, CUDA, TensorRT, Nsight Systems (Performance analysis), Nsight Graphics (Debug, profiler and export with Direct3D), Nsight Eclipse Edition (IDE), Nsight Compute (Interactive kernel profiler for CUDA applications)
Production
Automotive Grade
No
Yes
ASIL Target*
-
ASIL-D (QNX)
AEC-Q100 qual
No
Yes
Nvidia Design Support
-
Available
*Intended for production platform only.

What are the benefits of the DRIVE AGX Developer Kit compared to DRIVE PX 2?

DRIVE PX 2
DRIVE AGX
Hardware
GPU Architecture
SOC - Pascal
dGPU - Pascal
SOC - Volta
dGPU - Turing
Automotive Grade
Yes
Yes
Architected to achieve
ASIL target for Production
ASIL B
ASIL D
AEC-Q100 qual
No
Yes
DL Inference INT8 (TOPs)
24
30: per Xavier
320: for 2 Xavier SOCs +
2 Turing dGPU modules
Memory
Type
SOC - LPDDR4 @ 1600MHz
dGPU - GDDR5 @ 3GHZ
SOC - LPDDR4X @ 2133MHz
dGPU - GDDR6 @ 6GHZ
Peak Bandwidth
Per Parker - 51 GB/s
Per PG418 (Pascal) - 192 GB/s
Per Xavier - 136 GB/s
Per PG189 (Turing) - 384 GB/s
Automotive Grade Memory
No
Yes
ECC Enabled
Yes
Yes
Software
Operating System
DRIVE OS Linux 5.0.10.3
DRIVE OS Linux 5.1 or later
Compute
CUDA 9.2
CUDA 10.2 or later
Deep Learning
TensorRT 4
TensorRT 5.1 or later
Safety Assessed
No
Yes (DRIVE OS QNX)
Computer Vision
No
NvMedia (VPI)
Developer Experience – Host
Ubuntu 16.04
Ubuntu 16.04 or 18.04
DRIVE Software
DriveWorks 1.2
DRIVE Software 9 and above
Support
EOL
Yes

What I/O does the DRIVE AGX Developer Kit support?

Feature
NVIDIA DRIVE™ AGX Xavier
NVIDIA Xavier SoC
2
NVIDIA dGPU SXM2
2 (Only with DRIVE AGX Pegasus)
System RAM
32GB LPDDR4x per Xavier
QSPI NOR Flash
128MB per Xavier
eMMC
128GB per Xavier
Security Key Storage
8GB eMMC per Xavier
UFS
256GB per Xavier
Camera
Up to 16 cameras: GMSL2 (Aggregators on CIM)
MCU
Infineon Aurix TC397
Ethernet
10 GbE
2x HSD (1 per Xavier), 2x RJ45
1 GbE
7 (3½ HSD)
100 MbE
5 (2½ HSD)
CAN
Up to 6
FlexRay to MCU
2
USB2 / USB3.1
Xavier: 4 (XA:3; XB:1)
Others: 2 (Debug:1, Com Ex:1)
HDMI
6
GPIO
6 (4 for XA, 1 for XB, 1 for CVM)
PCIe
1 x16 (Mini-SAS connectors)
eSATA
4
M.2 code 2280 M-keyed
1 PCIe ×4
Automotive Audio Bus (A2B)
No A2B, but XA DAP ports are connected to headers
Debug and Development
JTAG, USB3.1, USB2, HDMI, UART

How can I get support for my DRIVE AGX Developer Kit?

If you can’t find what you are looking for in the downloads, documentation, or forum, please contact your NVIDIA Representative or reach out directly.


Do you have additional questions?