How to install cuda-toolkit on DRIVE OS 5.2.0 DRIVE AGX platform?

Please provide the following info (check/uncheck the boxes after clicking “+ Create Topic”):
Software Version
[*] DRIVE OS Linux 5.2.0
DRIVE OS Linux 5.2.0 and DriveWorks 3.5
NVIDIA DRIVE™ Software 10.0 (Linux)
NVIDIA DRIVE™ Software 9.0 (Linux)
other DRIVE OS version

Target Operating System
[*] Linux

Hardware Platform
[*] NVIDIA DRIVE™ AGX Xavier DevKit (E3550)
NVIDIA DRIVE™ AGX Pegasus DevKit (E3550)

SDK Manager Version

Host Machine Version
[*] native Ubuntu 18.04


Is there a way to manually install the cuda-toolkit-10-2 package or an equivalent package on DRIVE OS 5.2.0?

I have tried "sudo apt search cuda" command but I did not see this package. Here is the output:

nvidia@tegra-ubuntu:/usr/local/cuda-10.2/lib64$ sudo apt search cuda
[sudo] password for nvidia: 
Sorting... Done
Full Text Search... Done
caffe-cpu/bionic 1.0.0-6 arm64
  Fast, open framework for Deep Learning (Meta)

cuda-cudart-10-2/now 10.2.187-1 arm64 [installed,local]
  CUDA Runtime native Libraries

cuda-cufft-10-2/now 10.2.187-1 arm64 [installed,local]
  CUFFT native runtime libraries

cuda-cuobjdump-10-2/now 10.2.187-1 arm64 [installed,local]
  CUDA cuobjdump

cuda-curand-10-2/now 10.2.187-1 arm64 [installed,local]
  CURAND native runtime libraries

cuda-cusolver-10-2/now 10.2.187-1 arm64 [installed,local]
  CUDA solver native runtime libraries

cuda-cusparse-10-2/now 10.2.187-1 arm64 [installed,local]
  CUSPARSE native runtime libraries

cuda-gdb-10-2/now 10.2.187-1 arm64 [installed,local]

cuda-libraries-10-2/now 10.2.187-1 arm64 [installed,local]
  CUDA Libraries 10.2 meta-package

cuda-license-10-2/now 10.2.187-1 arm64 [installed,local]
  CUDA licenses

cuda-memcheck-10-2/now 10.2.187-1 arm64 [installed,local]

cuda-npp-10-2/now 10.2.187-1 arm64 [installed,local]
  NPP native runtime libraries

cuda-nvdisasm-10-2/now 10.2.187-1 arm64 [installed,local]
  CUDA disassembler

cuda-nvgraph-10-2/now 10.2.187-1 arm64 [installed,local]
  NVGRAPH native runtime libraries

cuda-nvrtc-10-2/now 10.2.187-1 arm64 [installed,local]
  NVRTC native runtime libraries

On DRIVE SW 10 I used to copy the "cuda-repo-ubuntu1804-10-2-local-10.2.19_1.0-1_arm64.deb" from the Host PC where the sdkmanager is installed to the Drive AGX target board. Then execute the following commands:

#Execute the following commands on the Drive Target board
sudo dpkg -i cuda-repo-ubuntu1804-10-2-local-10.2.19_1.0-1_arm64.deb
# List the Meta Packages Available for CUDA 10.2
cat /var/lib/apt/lists/*cuda*Packages | grep "Package:"

sudo apt install cuda-toolkit-10-2
sudo apt install cuda-libraries-10-2

But now on the Host Machine where I installed DRIVE OS 5.2.0 through the sdkmanager I could not find any debian packaged for CUDA.

Thanks in advance for any help.

Best regards,

Hi @dgarba ,

Is cuda-repo-ubuntu1804-10-2-local-10.2.19_1.0-1_arm64.deb part of DRIVE Software 10?
As far as I know, DRIVE OS SDK supports cross compilation and that’s how to build the sample application in SDK.

Hi @VickNV,

Yes the cuda-repo-ubuntu1804-10-2-local-10.2.19_1.0-1_arm64.deb package is part of DRIVE Software 10. This file is found on the Host machine DRIVE Software 10 installation directory through the sdkmanager.

This is the path where I found the the .deb file in the host machine:

  • /home/$USER/nvidia/nvidia_sdk/DRIVE_Software_10.0_Linux_OS_DDPX/DRIVEOS/drive-t186ref-cuda/target/cuda-repo-ubuntu1804-10-2-local-10.2.19_1.0-1_arm64.deb

So, there is no way to install the cuda-toolkit-10-2 on DRIVE OS 5.2.0?

Our project is intended to be built natively on the DRIVE AGX platform and has cuda-toolkit-10-2 package as a dependency. On DRIVE SW 10 I was able to install this package with the above steps, but unfortunately, after I upgraded to DRIVE OS 5.2.0 I haven´t been able to install this dependency on the DRIVE AGX platform.

Why does NVIDIA remove the CUDA toolkit package support in DRIVE OS 5.2.0 release, if it is a very useful and necessary package on NVIDIA platforms?

Best regards,

In System Requirements of NVIDIA CUDA Installation Guide for Linux of CUDA Toolkit 10.2, there is no support on arm64. I think that’s why DRIVE OS 5.2.0 Linux SDK doesn’t include it anymore. Thanks.

Hi @VickNV,

I don´t understand why do you say that there is no support on arm64 for CUDA Toolkit 10.2. On DRIVE SW 10 release, CUDA 10.2 toolkit is fully supported for DRIVE AGX. It has to be manually installed with the steps described in the first comment of this post, but it works perfectly. In fact, the cuda-repo-ubuntu1804-10-2-local-10.2.19_1.0-1_arm64.deb package was provided by the sdkmager DRIVE SW 10 build on the host machine, so the developer can copy that file to the DRIVE AGX platform and install CUDA toolkit 10.2 there.

Where can I get the cuda-repo-ubuntu1804-10-2-local-10.2.19_1.0-1_arm64.deb equivalent package supported for DRIVE OS 5.2.0, since the sdkmanager build for DRIVE OS 5.2.0 does not provide this package?

Can I use the cuda-repo-ubuntu1804-10-2-local-10.2.19_1.0-1_arm64.deb package of DRIVE SW 10 on DRIVE OS 5.2.0? Both release versions use CUDA 10.2, the difference is just in the micro number of the CUDA version (10.2.X).

Also, the NVIDIA CUDA Installation Guide for Linux of CUDA Toolkit of older versions doesn´t indicate arm64 support in the System Requirements section but is well known that CUDA since version 8 is fully supported in Jetson platforms for examples that are based on arm64 architecture. Actually, the CUDA 10.2 is fully supported and working fine in DRIVE SW 10 for DRIVE AGX platform (arm64 based architecture) and also for JetPack 4.5.1 in Jetson platforms (arm64 based architecture).

Thanks in advance for any help.

Best regards,

I’m checking with the team and will get back to you. Thanks.

DRIVE OS SDK intends that developers cross compile their applications.
So our team would like to know the reason that your project needs to be built natively.
We will appreciate if you can help to elucidate it. Thanks.

Hi @VickNV,

We compile our project in an ARM docker container on amd64 host (AWS). This is due to project structure and requirements.

We are trying to upgrade from DRIVE SW 10 to DRIVE OS 5.2.0. But on DRIVE OS 5.2.0 installation on a host PC using the sdkmanager, the "cuda-repo-ubuntu1804-10-2-local-10.2.19_1.0-1_arm64.deb" package that we used to install CUDA toolkit on our ARM docker image is not found anymore.

I just want to know if it is possible to obtain the cuda-repo-ubuntu1804-10-2-local-10.2.19_1.0-1_arm64.deb" package equivalent for DRIVE OS 5.2.0, because the CUDA version of DRIVE SW 10 differs in the micro version (CUDA 10.2.X) for DRIVE OS 5.2.0. And, I want to keep the same version intended for DRIVE OS 5.2.0.

For the next SDK OS and SDK SW releases I will suggest to keep the arm64.deb CUDA toolkit package in the generated Image installation directory of the sdkmanager, so in case that the developers want to install CUDA toolkit on the DRIVE AGX they can do it without problems as we was doing it in the previous releases. I understand that by default this package is not installed to reduce the File System size of the generated Image, but you could give a way to install it if it is required by the developer.

Best regards,

Thanks for letting us know. We will discuss internally on your case.

Hi @VickNV,

I was wondering if you have news about this support?


I already brought up this internally and the discussion is still ongoing. But I would suggest you to contact with your nvidia representative for this. Sorry for any inconvenience.

sent a personal message to help on this further.

Thank you VickNV, we will take it from here. I appreciate all your support.

I second this request. Our use case is slightly different but also requires the cuda-repo-ubuntu1804-10-2-local-10.2.19_1.0-1_arm64.deb" package equivalent for DRIVE OS 5.2.0. We want to run our application in a container on Drive AGX. In order to create the container, previously I would install CUDA in the container using cuda-repo-ubuntu1804-10-2-local-10.2.19_1.0-1_arm64.deb". However, since this doesn’t exist on DRIVE OS 5.2.0 anymore, I am stuck.

Hi @kenneth.chu ,

We’ll open up our Docker containers in the next release and we recommend you start using those. Thanks.

Hi @VickNV, thanks for your reply.
I know you mentioned above (and I see from other posts), that the intention is for developers to cross compile their applications on PC. I just wanted to confirm this is this case moving forward with future versions as well. And applies to the docker as well (i.e. the application cannot be built in the docker).
Our build and package management system is designed to be built on target so it is a significant change for us. (We didn’t have any issues with Drive OS Thanks.

As you can see in this post, even current DRIVE OS 5.2.0 doesn’t support building on target. For following versions docker image for cross compilation will be available on NGC. Thanks.