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
other
Target Operating System
Linux
QNX
other
Hardware Platform
NVIDIA DRIVE™ AGX Xavier DevKit (E3550)
NVIDIA DRIVE™ AGX Pegasus DevKit (E3550)
other
SDK Manager Version
1.5.0.7774
other
Host Machine Version
native Ubuntu 18.04
other
We are setting up the Host PC with the Nvidia Drive AGX to run some of the sample code provided. We are using a Host PC with Ubuntu 18.04.5 with Nvidia RTX 3080 GPU. The driver used is Nvidia Driver 460. Initially we were successful in installing the Nvidia SDK Manager and run a couple of sample codes on the Host PC with the configuration of Nvidia Driver 460 and CUDA version 11.2. We went ahead to flash the Dev system, firstly it was not giving the expected pop-up with SDK Manager indicating successful flash. We tried to fix this and in the process did a full CUDA install on host(we have CuDA version 10.2), now we are not able to proceed with the cross-compilation when we wanted to run the sample code on Dev system.
Dear @raghuram.krishnamurthy,
Could you uninstall the CUDA 11.2 toolkit on host and uninstall DRIVE SW using sdkmanager. Remove the sdkm logs(~/.nvsdkm/ folder). After that, reboot the host and check installing on both host and target using sdkmanager. Please share the logs(~/.nvsdkm/logs and sdkm.log files) if in case failed to flash to investigate further.
Hi @SivaRamaKrishnaNV ,
Attaching the logs after doing the above steps. The Flash was successful, however there is no pop-up coming on the Dev system.
As we don’t see any change on the Dev system after the flashing, can you let us know as to how we can validate if the flash was successful apart from the message on the SDK Manager.
We understand that the Dev system and host PC must be connected to the Internet while flashing. We are not sure if the Dev system is connected to the Internet even though a proper Ethernet connection is given to the Dev system via the Dual Gbe dongle via port 1GbE 3/4, since there is no Wired connection that is visible in the Network Settings on the dev system monitor. Kindly advise how to ensure that the Internet is connected to the Dev system.
Logs and bug report:
sdkm.log (11.5 MB)
logs.zip (597.3 KB)
nvidia-bug-report.log.gz (2.3 MB)
Dear @raghuram.krishnamurthy1 ,
As per shared logs, I could see flashing is successful. Could you check running some DW samples on Tegra A to verify. You may check running camera GMSL sample(DW sample) with SF3324 camera module.
Now coming to Host PC, Could you check below things and confirm.
- Run CUDA 10.2 samples are host to confirm if CUDA is setup correctly.
- Run few DW samples on host(Please see Prerequisites and compilation steps at
file:///usr/local/driveworks-2.2/doc/nvsdk_html/dwx_samples_building.html)
- Please check DW cross compilation (Please see Prerequisites and cross- compilation steps at
file:///usr/local/driveworks-2.2/doc/nvsdk_html/dwx_samples_building.html)
Dear @raghuram.krishnamurthy1,
Is there any update?
Hi @SivaRamaKrishnaNV,
Thanks for your support. We were able to do cross-compilation on the host PC from the info that you provided above and we are trying the upload on the dev system.
We are currently facing another issue with regard to remote logging into the dev system. We followed the instructions for this as in the below link, however we are facing the issue as in the attached, could you help here. Please let us know if the dev system can be remotely logged into from outside the network from a different country.
https://developer.nvidia.com/drive/learn/tutorial-remoteogl
Hi @SivaRamaKrishnaNV
Could you help here to resolve the above issue, thanks.
Dear @raghuram.krishnamurthy1,
Could you check leveraging from the steps provided at Remote access with OpenGL support with Drive Software 10.0 . If you still see an issue, please file a new topic as it is not relavant to topic thread
