Application failed after Driveworks 0.6 updates (Solved)

After Driveworks 0.6.67 Update,
an application cannot start. It was developed at Driveworks 0.3.

I attach library info as follow;

nvidia@nvidia:~$ patchelf --print-needed test_app
libdriveworks.so.0
libcudart.so.8.0
libcublas.so.8.0
libnvmedia.so
libEGL.so.1
libpthread.so.0
libX11.so.6
libXrandr.so.2
libXinerama.so.1
libXi.so.6
libXcursor.so.1
libGLESv2.so.2
libudev.so.1
libusb-1.0.so.0
libnv_extimgdev.so
libnv_embstatsplugin.so
librt.so.1
libdl.so.2
libdrm.so.2
libstdc++.so.6
libm.so.6
libgcc_s.so.1
libc.so.6
ld-linux-aarch64.so.1

I tested “patchelf --replace-needed” for libcudart and libcublas.
Reference link:
https://devtalk.nvidia.com/default/topic/1028385/driveworks/couldn-t-launch-cameras-after-upgrading-to-driveworks-0-6/


nvidia@nvidia:~$ ./test_app --csi-port=ab --camera-type=ar0231-rccb
nvrm_gpu: Bug 200215060 workaround enabled.
Cannot initialize SAL: DW_INVALID_ARGUMENT

Any idea about it?

Thanks

Dear ddpx2,

Driveworks 0.6.67 is using CUDA 9.0
Driveworks 0.3 is using CUDA 8.0
It appears to be a problem because the CUDA version is not correct.

One more thing, did you update Aurix FW?

We’ve posted new PDK and DW on developer.com.
Could you please check if this symptom is reproduced after updating with new PDK and DriveWorks? Thanks.

Dear SteveNV,

TRUE. CUDA version 8!

Then I replaced “libcudart and libcublas” to new ones by patchelf tool.

As for AURIX, I checked new FW was installed for 0.6.67 DriveWorks.

Thanks,

Hi ddpx2,

Please check if this symptom is reproduced after updating with new PDK and DriveWorks?

Thanks.

Kay,

New PDF and Driveworks you mean are newly released Drive OS?

“5.0.10.3”

Thanks,

Yes

Kay and SivaRamaKrishna,

I installed to test new Driveworks, 5.0.10.3 version on Drive PX2 AutoChauffeur.

Failed!

Since this application involves parameters in itself, it conflicts with new DriveWorks and its parameters.
e.g --camera-type, --csi-port

Thanks