I’m using the Drive PX 2 as target platform and a PC with Ubuntu 14.04 as host, DriveWorks SDK v0.3 and PDK v220.127.116.11.
My host PC has a NVS 510, which has only 3.0 compute capability (shouldn’t be a problem, right?).
I can cross-compile the DriveNet application and even run my compiled sample directly on the Drive PX 2 without problems.
When I try to run it on the Drive PX 2 using a remote debugging session with Nsight-Eclipse on my host PC, I am able to step the sample until dwInitialize, but when it goes inside this function the application ends abruptly and I cannot debug it.
Within the gdb traces I can see the following error:
error,msg=“fatal: No CUDA capable device was found. (error code = CUDBG_ERROR_NO_DEVICE_
The remote shell shows the following:
Warning: Adjusting return value of linux_common_core_of_thread (pid=1391, tid=1391).
core = 17 >= num_cores = 6!
Initialize DriveWorks SDK v0.3.400
Release build with GNU 4.9.2 from v0.3.0-rc8-0-g3eeebea against PDK v18.104.22.168
SDK: Resources mounted from /usr/local/driveworks/data/resources
Killing all inferiors
Do you know what is the cause this problem?