CAN Interface

Please provide the following info (tick the boxes after creating this topic):
Software Version
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
1.9.3.10904
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

Hi community,

we are trying to set up the CAN interface on the Orin Drive.

Following the steps similar to Controller Area Network (CAN) — Jetson Linux Developer Guide documentation we are able to see CAN messages on wireshark created by cansend or cangen.
candump also displays messages when the loopback flag is set to ‘on’ when configuring the can interface.

When connecting a real device via the H2 CAN interface though, we are not able to see any transmitted message or any sort of hint that something was connected to the system.

Are there any additional steps required or options/configs that can be checked on the Orin before trying to debug the connected hardware?

We also tried to recompile the kernel on docker to check and to explicitly set the CAN modules as described in Enabling CAN Driver in Linux Kernel | NVIDIA Docs .

Including the mttcan module in the defconfig is not reflected/respected in the final .config, but apparently the module is present and loadable after flashing the rebuilt kernel.

Are we misinterpreting the documentation here or missing another aspect?

Thank you very much for your support.

Please refer to Setting Up CAN Loopback for instructions, and run candump and cansend using different CAN interfaces to test non-software loopback.

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.