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?
DRIVE IX is a software 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; register for the NVIDIA DRIVE Developer Program for DRIVE AGX.
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 here.
How can I get support for my DRIVE AGX Developer Kit?
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.
What are the benefits of the DRIVE AGX Developer Kit compared to DRIVE PX 2?
|GPU Architecture||SOC - Pascal
dGPU - Pascal
|SOC - Volta
dGPU - Turing
|Architected to achieve
ASIL target for Production
|ASIL B||ASIL D|
|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|
|Operating System||DRIVE OS Linux 18.104.22.168||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|
What I/O does the DRIVE AGX Developer Kit support?
|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)
|GPIO||6 (4 for XA, 1 for XB, 1 for CVM)|
|PCIe||1 x16 (Mini-SAS connectors)|
|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|