drive

Connection to NVIDIA DRIVE hardware

Description

This object represents a connection from the MATLAB® software to the NVIDIA® DRIVE hardware. To create this object, use the drive function. To interact with the DRIVE hardware, use this object with the functions listed in Object Functions

Creation

drive

Properties

expand all

This property is read-only.

The name of the target DRIVE board, returned as a character vector.

Example: 'NVIDIA Jetson TX2'

This property is read-only.

Version number of the CUDA toolkit installed on the DRIVE board, returned as a character vector.

Example: '9.2'

This property is read-only.

Version number of the CUDA Deep Neural Network library (cuDNN) installed on the DRIVE board, returned as a character vector.

Example: '7.1'

This property is read-only.

The IP address or host name of the Ethernet port on the DRIVE board, returned as a character vector.

Example: '169.254.0.2''gpucoder-drivepx2-1a'

This property is read-only.

Additional information on the GPU of the DRIVE board, returned as a 1-by-N structure, where N is the number of GPU devices. To access this structure use objectName.GPUInfo. The structure contains the following fields:

NameDescription

Name

Name of the CUDA device.

Index

Index of the selected GPU device.

ComputeCapability

Computational capability of the CUDA device.

CUDADriverVersion

The CUDA device driver version on the board currently in use.

CUDAToolkitVersion

Version of the CUDA toolkit on the board.

MaxThreadsPerBlock

Maximum supported number of threads per block during CUDA kernel execution.

MaxSharedMemPerBlock

Maximum amount of shared memory that a thread block can use during CUDA kernel execution.

MaxThreadBlockSize

Maximum size in each dimension for thread block.

MaxGridSize

Maximum size of grid of thread blocks.

AvailableMemory

Total amount of memory (in bytes) available for data.

TotalConstMem

Total amount of constant memory (in bytes) available for data.

MultiprocessorCount

The number of vector processors present on the device.

TotalCUDACores

Total number of CUDA cores available on the target board.

MaxThreadsPerSM

Maximum number of threads per symmetric multiprocessor.

For example, a DRIVE PX2 board has the following values:

hwDrive.GPUInfo(1,1)

ans = 

  struct with fields:

                    Name: 'DRIVE PX 2 AutoChauffeur'
                   Index: 0
       ComputeCapability: 6.1000
       CUDADriverVersion: 9.2000
      CUDAToolkitVersion: 9.2000
      MaxThreadsPerBlock: 1024
    MaxSharedMemPerBlock: 49152
      MaxThreadBlockSize: [1024 1024 64]
             MaxGridSize: [2.1475e+09 65535 65535]
         AvailableMemory: 4.0265e+09
           TotalConstMem: 65536
     MultiprocessorCount: 9
          TotalCUDACores: 1152
         MaxThreadsPerSM: 2048

This property is read-only.

Version number of the GStreamer library installed on the DRIVE board, returned as a character vector.

Example: '1.8.2'

This property is read-only.

The SSH port number on the DRIVE board, returned as an integer.

Example: 22

This property is read-only.

Version number of the SDL library installed on the DRIVE board, returned as a character vector.

Example: '1.2'

This property is read-only.

Version number of the NVIDIA TensorRT library installed on the DRIVE board, returned as a character vector.

Example: '4.0'

This property is read-only.

Version number of the V4L2 library installed on the DRIVE board, returned as a character vector.

Example: '1.10.0-1'

This property is read-only.

A list of the USB web cameras that are available, returned as a cell array of strings.

Example: {'Microsoft(R) LifeCam Cinema (TM)'}

Object Functions

getFileTransfer file from NVIDIA hardware to host computer
putFileTransfer file from host computer to target hardware
deleteFileDelete file on target hardware
openShellOpen terminal on host computer to use a Linux shell on NVIDIA hardware
systemRun commands in a Linux shell on the NVIDIA hardware
getL4TVersionGet the L4T version of the NVIDIA Jetson hardware
getPdkorSdkVersionGet the version number of the DriveWorks SDK installed on the DRIVE hardware
setupCodegenContextSelect the target hardware to build code for from multiple live connection objects
webcamCreate webcam object to acquire images from an USB webcam attached to the NVIDIA hardware
getCameraListGet a list of available cameras on the NVIDIA hardware
updatePeripheralInfoScan for and update the list of peripherals connected to the target hardware
getLinuxVersionGet information about the Linux environment on the target
imageDisplayCreate an imageDisplay object for displaying images on NVIDIA targets
getPILPortGet the TCP/IP port number used by the PIL execution
getPILTimeoutGet the timeout value that PIL uses for reading data
setPILPortSet the TCP/IP port number used by the PIL execution
setPILTimeoutSet the timeout value that PIL uses for reading data
killApplicationKill an application on the NVIDIA target by name
killProcessKill a process on the NVIDIA target by ID
runApplicationLaunch an application on the NVIDIA target by name
runExecutableLaunch an executable on the NVIDIA target by name
getDisplayEnvironmentGet the display environment value used for redirecting the display on the target
setDisplayEnvironmentSet the display environment value used for redirecting the display on the target

Examples

collapse all

This example shows you how to create a connection from the MATLAB software to the NVIDIA DRIVE hardware. The DRIVE hardware is connected to the same TCP/IP network as the host computer. This example uses the device address, user name, and password settings from the most recent successful connection to the DRIVE hardware.

Create a connection, hwDRIVE, from the MATLAB software to NVIDIA DRIVE hardware.

hwDRIVE = drive
Checking for CUDA availability on the Target...
Checking for 'nvcc' in the target system path...
Checking for cuDNN library availability on the Target...
Checking for TensorRT library availability on the Target...
Checking for prerequisite libraries is complete.
Gathering hardware details...
Checking for third-party library availability on the Target...
Gathering hardware details is complete.
 Board name         : NVIDIA Jetson TX2
 CUDA Version       : 9.2
 cuDNN Version      : 7.1
 TensorRT Version   : 4.0
 GStreamer Version  : 1.8.2
 V4L2 Version       : 1.10.0-1
 SDL Version        : 1.2
 Available Webcams  : Microsoft® LifeCam Cinema(TM)
 Available GPUs     : DRIVE PX 2 AutoChauffeur,NVIDIA Tegra X2

hwDrive = 

  jetson with properties:

       DeviceAddress: 'gpucoder-drivepx2-1a'
                Port: 22
           BoardName: 'NVIDIA Jetson TX2'
         CUDAVersion: '9.2'
        cuDNNVersion: '7.1'
     TensorRTVersion: '4.0'
          SDLVersion: '1.2'
         V4L2Version: '1.10.0-1'
    GStreamerVersion: '1.8.2'
             GPUInfo: [1×2 struct]
          WebcamList: {'Microsoft® LifeCam Cinema(TM)'}

The GPU Coder™ Support Package for NVIDIA GPUs establishes an SSH connection to the DRIVE hardware using the settings stored in memory. It checks for the CUDA toolkit, cuDNN, and TensorRT libraries on the target hardware and displays this information on the MATLAB Command Window. To set up the environment variables on the board for the compiler and the libraries, see Install and Setup Prerequisites for NVIDIA Boards.

To get the PDK/SDK software version on the DRIVE board, use the getPdkorSdkVersion method of the DRIVE connection object.

getPdkorSdkVersion(hwDRIVE);
Drive SDK/PDK version is: 5.0.5.0-10129397

To start a PuTTY SSH terminal session on the DRIVE board, use the openShell method of the DRIVE connection object.

openShell(hwDRIVE);
Using username "ubuntu".
Welcome to Ubuntu 16.04 LTS (GNU/Linux 4.9.38-rt25-tegra aarch64)

 * Documentation:  https://help.ubuntu.com/

594 packages can be updated.
321 updates are security updates.

ubuntu@gpucoder-drivepx2-1a:~$ ls
CamVid.avi  Documents  MATLAB  Pictures  segnetDemo  Videos
Desktop     Downloads  Music   Public    Templates
ubuntu@gpucoder-drivepx2-1a:~$

After logging into the Linux® shell, you execute shell commands such as ls as shown.

To close the connection, use clear to remove hwDRIVE and any other connections that use hwDRIVE.

clear hwDRIVE;
Introduced in R2018b