: DRIVE AGX Thor: how to access VH1 P9 CAN1/CAN2 (OEM bus) from Linux / DriveWorks? No canX, mttcan finds no device

Software Version: DRIVE OS 7.2.5

Target OS: Linux

Hardware Platform: DRIVE AGX Thor p3960-10-sw03

Kernel: 6.8.12-rt-tegra (PREEMPT_RT, built Jun 24 2026)

Issue description:

I need to read and write CAN frames on a vehicle OEM bus from Linux using the

DriveWorks CAN sensor (protocol=can.socket). The bus is wired to VH1 / DB9

connector P9 (HARNESS_CAN1 / HARNESS_CAN2, per the DRIVE AGX Thor Mechanical

and Installation Guide, DI-12070-001_v1.3, Interface Connectors table).

On the target, no CAN interface exists:

$ ip link show | grep -i can

(no output)

I loaded the stack manually:

$ sudo modprobe can
$ sudo modprobe can-raw

$ sudo modprobe can-dev

$ sudo modprobe mttcan

dmesg shows only “can: controller area network core”, "NET: Registered PF_CAN

protocol family", “can: raw protocol”, “CAN device driver interface”.

mttcan produces no probe messages.

$ lsmod | grep -i mttcan

mttcan 53248 0

can_dev 40960 1 mttcan

nvpps 32768 2 mttcan,nvethernet

$ ls /sys/bus/platform/drivers | grep -i can

mttcan

$ ls /sys/bus/platform/devices | grep -i can

(empty)

$ find /proc/device-tree -iname “*can*”

(empty)

So the mttcan driver is registered but no matching device exists in this

VM’s device tree.

What I found in the documentation and forum:

  • DriveOS Linux SDK 7.2.5, “CAN Driver”: "On Thor, all four CAN controllers

    are in the FSI, and the FSI CAN interfaces are not visible on Linux systems."

    and “Linux TegraCAN is applicable to Orin only.”

  • Forum topics “No canX devices/interfaces” and "Data communication modes from

    MCU to SOC": on Thor there is no CAN in the CCPLEX, so SocketCAN is not

    supported; FSI CAN is dedicated to safety-critical communication.

  • SDK “SoC to MCU Communication”: the Common Interface covers reset, boot

    chain, firmware and network configuration, but does not list CAN data.

Questions:

  1. Is there any supported way for a Linux application on Thor (DriveWorks

    can.socket or plain SocketCAN) to send and receive on the CAN lines of

    VH1 P9?

  2. Where do HARNESS_CAN1 / HARNESS_CAN2 on VH1 P9 terminate on Thor: sMCU

    (RH850), FSI, or elsewhere?

  3. Does the sMCU firmware (AFW) offer any CAN gateway to the SoC (SOME/IP,

    UDP, or other)? The forum says no mechanism exists for arbitrary data; is

    that still true for current AFW versions?

  4. Is FSI CAN usable from Linux once the FSI Integration Guide / DRIVE OS PDK

    is available, and how would frames reach a Linux application?

  5. Is a USB-CAN adapter (gs_usb / PEAK) the recommended approach for Linux

    applications on Thor? If so, are these drivers expected in the DriveOS

    Linux kernel config?

  6. The DriveWorks CAN tutorial (“Receiving and Sending Data”) and CAN Bus

    module pages in the 7.2.5 SDK still describe can.socket with device=can0.

    Could the documentation note that this does not apply to Thor?

Thank you.

Title: DRIVE AGX Thor: how to access VH1 P9 CAN1/CAN2 (OEM bus) from Linux / DriveWorks? No canX, mttcan finds no device

Software Version: DRIVE OS [7.x.x.x – fill in: cat /etc/nvidia/version-ubuntu-rootfs.txt]

Target OS: Linux

Hardware Platform: DRIVE AGX Thor [fill in exact kit/SKU]; /proc/device-tree/model reports “p3960-0010”

SDK Manager Version: [fill in]

Host Machine Version: [fill in]

Kernel: 6.8.12-rt-tegra (PREEMPT_RT, built Jun 24 2026)

MCU AFW: [fill in: run “version” on the sMCU console]

Issue description:

I need to read and write CAN frames on a vehicle OEM bus from Linux using the

DriveWorks CAN sensor (protocol=can.socket). The bus is wired to VH1 / DB9

connector P9 (HARNESS_CAN1 / HARNESS_CAN2, per the DRIVE AGX Thor Mechanical

and Installation Guide, DI-12070-001_v1.3, Interface Connectors table).

On the target, no CAN interface exists:

$ ip link show | grep -i can

(no output)

I loaded the stack manually:
$ sudo modprobe can
$ sudo modprobe can-raw
$ sudo modprobe can-dev
$ sudo modprobe mttcan
dmesg shows only “can: controller area network core”, “NET: Registered PF_CAN
protocol family”, “can: raw protocol”, “CAN device driver interface”.
mttcan produces no probe messages.

$ lsmod | grep -i mttcan
mttcan 53248 0
can_dev 40960 1 mttcan
nvpps 32768 2 mttcan,nvethernet

$ ls /sys/bus/platform/drivers | grep -i can
mttcan
$ ls /sys/bus/platform/devices | grep -i can
(empty)
$ find /proc/device-tree -iname “*can*”
(empty)

So the mttcan driver is registered but no matching device exists in this

VM’s device tree.
What I found in the documentation and forum:

  • DriveOS Linux SDK 7.2.5, “CAN Driver”: “On Thor, all four CAN controllers
    are in the FSI, and the FSI CAN interfaces are not visible on Linux systems.”
    and “Linux TegraCAN is applicable to Orin only.”
  • Forum topics “No canX devices/interfaces” and “Data communication modes from
    MCU to SOC”: on Thor there is no CAN in the CCPLEX, so SocketCAN is not
    supported; FSI CAN is dedicated to safety-critical communication.
  • SDK “SoC to MCU Communication”: the Common Interface covers reset, boot
    chain, firmware and network configuration, but does not list CAN data.

Questions:

  1. Is there any supported way for a Linux application on Thor (DriveWorks
    can.socket or plain SocketCAN) to send and receive on the CAN lines of
    VH1 P9?

  2. Where do HARNESS_CAN1 / HARNESS_CAN2 on VH1 P9 terminate on Thor: sMCU
    (RH850), FSI, or elsewhere?

  3. Does the sMCU firmware (AFW) offer any CAN gateway to the SoC (SOME/IP,
    UDP, or other)? The forum says no mechanism exists for arbitrary data; is
    that still true for current AFW versions?

  4. Is FSI CAN usable from Linux once the FSI Integration Guide / DRIVE OS PDK
    is available, and how would frames reach a Linux application?

  5. Is a USB-CAN adapter (gs_usb / PEAK) the recommended approach for Linux
    applications on Thor? If so, are these drivers expected in the DriveOS
    Linux kernel config?

  6. The DriveWorks CAN tutorial (“Receiving and Sending Data”) and CAN Bus
    module pages in the 7.2.5 SDK still describe can.socket with device=can0.
    Could the documentation note that this does not apply to Thor?

Thank you.

Dear @yaswanthkumar.karunakaran ,
CAN is not accessible for tegra on Thor devkit only accessible via FSI CAN. So DW can’t use CAN interface. There is no method(function) to send CAN data from MCU to tegra.

Thank you for the clarification.

To make sure I understand correctly: on the DRIVE AGX Thor devkit, SocketCAN
and the DriveWorks CAN sensor (can.socket) cannot be used, and there is no
function to forward CAN data from the MCU or FSI to the Tegra/Linux side.

I have a few follow-up questions about the roadmap:

  1. Is Linux (CCPLEX) CAN access on DRIVE AGX Thor planned for a future DRIVE OS
    release (for example an FSI-to-Linux CAN forwarding path, a virtual SocketCAN
    interface backed by FSI CAN, or a CAN gateway in the MCU firmware)? If so,
    which release or timeframe is targeted?

  2. If it is not planned, what is NVIDIA’s recommended architecture for a Linux
    application that must read and write a vehicle CAN bus on Thor? Is a USB-CAN
    adapter (gs_usb or PEAK) the recommended approach, and will those kernel
    drivers be included in the DriveOS Linux image?

  3. Is FSI CAN usable from Linux with the DRIVE OS PDK and the FSI Integration
    Guide? If so, how are frames exchanged between the FSI and a Linux
    application (for example over the FSI-CCPLEX communication path), and where
    can we request access to that documentation?

  4. Could the DriveWorks CAN documentation (CAN Bus module and “Receiving and
    Sending Data” tutorial in the 7.2.5 SDK) be updated to state that can.socket
    is not available on Thor? The pages currently show device=can0 without
    mentioning this limitation.

Thank you.

Dear @yaswanthkumar.karunakaran ,
No CAN usage is supported from tegra in future and accessed only via FSI CAN. You need to reach out to your NVIDIA representative to get access to FSI integration guide.