Please provide the following info (tick the boxes after creating this topic):
Software Version
DRIVE OS 6.0.10.0
DRIVE OS 6.0.8.1
DRIVE OS 6.0.6
DRIVE OS 6.0.5
DRIVE OS 6.0.4 (rev. 1)
DRIVE OS 6.0.4 SDK
other
Target Operating System
Linux
QNX
other
Hardware Platform
DRIVE AGX Orin Developer Kit (940-63710-0010-300)
DRIVE AGX Orin Developer Kit (940-63710-0010-200)
DRIVE AGX Orin Developer Kit (940-63710-0010-100)
DRIVE AGX Orin Developer Kit (940-63710-0010-D00)
DRIVE AGX Orin Developer Kit (940-63710-0010-C00)
DRIVE AGX Orin Developer Kit (not sure its number)
other
SDK Manager Version
2.1.0
other
Host Machine Version
native Ubuntu Linux 20.04 Host installed with SDK Manager
native Ubuntu Linux 20.04 Host installed with DRIVE OS Docker Containers
native Ubuntu Linux 18.04 Host installed with DRIVE OS Docker Containers
other
Hello Nvidia!
Iām following up on my previous post made a while ago: How to gather CAN data using external CAN sensor
Now I finally have the H2A vehicle harness connected to my VBOX 3iSL using the P3 DB9 connector (since that has SMCU_CAN signals as explained in the mechanical and installation guide documentation).
To add some context about what the VBOX does, it is currently set up to send GPS/CAN data out through its serial port.
I checked the VBOX to make sure it was sending signals correctly (which it was), and I ran the following sample to try and see the output on the terminal:
sudo ip link set can0 type can bitrate 500000
sudo ip link set can0 up
ifconfig -a (to confirm that can0 was up and running)
./sample_canbus_logger --driver=can.socket --params=device=can0
The final result only showed this output, with no CAN messages coming into the terminal:
user@tegra-ubuntu:/usr/local/driveworks/bin$ sudo ./sample_canbus_logger --driver=can.socket --params=device=can0
Program Arguments:
ādriver=can.socket
āfilter=
āhwtime=1
āoffscreen=0
āparams=device=can0
āprofiling=1
āsend_i_understand_implications=0
āsend_id=6FF
āsend_size=8
[29-10-2024 13:29:20] Platform: Detected Drive Orin P3710
[29-10-2024 13:29:20] TimeSource: monotonic epoch time offset is 1730216012399566
[29-10-2024 13:29:20] TimeSourceVibranteLinux: detect valid PTP interface mgbe2_0
[29-10-2024 13:29:20] TimeSource Nvpss : PTP ioctl returned error. Synchronized time will not be available from this timesource.
[29-10-2024 13:29:20] TimeSource: Could not detect valid PTP time source at nvpps. Fallback to mgbe2_0
[29-10-2024 13:29:20] PTP Time is available from Eth Driver
[29-10-2024 13:29:20] Adding variable DW_Base:DW_Version
[29-10-2024 13:29:20] Added variable DW_Base:DW_Version
[29-10-2024 13:29:20] Platform: number of GPU devices detected 1
[29-10-2024 13:29:20] Platform: currently selected GPU device 0, Resource Data Dir: trt_08_05_10_03, Arch: ga10b
[29-10-2024 13:29:20] Platform: currently selected GPU device integrated ID 0
[29-10-2024 13:29:20] CUDLAEngine:getDLACount: CUDLA version is = 1003000
[29-10-2024 13:29:20] CUDLAEngine:getDLACount: Number of DLA devices = 2
[29-10-2024 13:29:20] Context::mountResourceCandidateDataPath resource FAILED to mount from ā./resourcesā: VirtualFileSystem: Failed to mount ā./resources/resources.pakā
[29-10-2024 13:29:20] Context::mountResourceCandidateDataPath resource FAILED to mount from ā/usr/local/driveworks-5.10/bin/dataā: VirtualFileSystem: Failed to mount ā/usr/local/driveworks-5.10/bin/data/resources.pakā
[29-10-2024 13:29:20] Context::findDataRootInPathWalk data/DATA_ROOT found at: /usr/local/driveworks-5.10/bin/ā¦/data
[29-10-2024 13:29:20] Context::mountResourceCandidateDataPath resource FAILED to mount from ā/usr/local/driveworks-5.10/bin/ā¦/dataā: VirtualFileSystem: Failed to mount ā/usr/local/driveworks-5.10/bin/ā¦/data/resources.pakā
[29-10-2024 13:29:20] Context::findDataRootInPathWalk data/DATA_ROOT found at: /usr/local/driveworks-5.10/data
[29-10-2024 13:29:20] Context::mountResourceCandidateDataPath resource FAILED to mount from ā/usr/local/driveworks-5.10/dataā: VirtualFileSystem: Failed to mount ā/usr/local/driveworks-5.10/data/resources.pakā
[29-10-2024 13:29:20] Context::findResourcesPackageInPathWalk: Could not find ./resources/resources.pak in upto 7 parent directories from /usr/local/driveworks-5.10/bin/ā¦/lib/libdw_base.so.5.10
[29-10-2024 13:29:20] Context::findResourcesPackageInPathWalk: Could not find ./resources/resources.pak in upto 7 parent directories from /usr/local/driveworks-5.10/targets/aarch64-Linux/lib/libdw_base.so.5.10
[29-10-2024 13:29:20] SDK: No resources(.pak) mounted, some modules will not function properly
[29-10-2024 13:29:20] egl::Display: found 1 EGL devices
[29-10-2024 13:29:20] egl::Display: use drm device: drm-nvdc
[29-10-2024 13:29:20] TimeSource: monotonic epoch time offset is 1730216012399566
[29-10-2024 13:29:20] TimeSourceVibranteLinux: detect valid PTP interface mgbe2_0
[29-10-2024 13:29:20] TimeSource Nvpss : PTP ioctl returned error. Synchronized time will not be available from this timesource.
[29-10-2024 13:29:20] TimeSource: Could not detect valid PTP time source at nvpps. Fallback to mgbe2_0
[29-10-2024 13:29:20] PTP Time is available from Eth Driver
[29-10-2024 13:29:20] Initialize DriveWorks SDK v5.10.87
[29-10-2024 13:29:20] Release build with GNU 9.3.0 from buildbrain-branch-0-g9a5b4670e12 against Drive PDK v6.0.6.0
[29-10-2024 13:29:20] SensorFactory::createSensor() ā time.nvpps, nvpps-device=/dev/nvpps0
[29-10-2024 13:29:21] TimeSensor: failed to set NVPPS parameters. Error: Invalid argument
[29-10-2024 13:29:21] This platform does not support NVPPS GPIO mode. Fallback to timer mode
[29-10-2024 13:29:21] TimeSensor: initialized with no UTC time reference.
[29-10-2024 13:29:21] SensorFactory::createSensor() ā can.socket, device=can0
[29-10-2024 13:29:21] EndpointNVPPS: started on /dev/nvpps0
[29-10-2024 13:29:21] CANSocket: use SW based timestamps for can0
[29-10-2024 13:29:21] CANSocket: started can0
Am I missing some setup steps somewhere (ie. do I need to use can.aurix instead, and would that work with my Vbox)? Or do I have the wrong harness?
Thank you