Thor Controller Area Network (CAN) Testing Issues


According to the developer guide, Thor does not require pinmux configuration. It is already set to the CAN function by default.

So, does it mean that we no longer need to use busybox to write the values of the corresponding registers?

We have independently developed a board that can output 4 channels of CAN.

During the test using the external CAN analyzer, it was found that the CAN0 transmitter and receiver were functioning normally, but CAN1, CAN2, and CAN3 were unable to receive data.

Additionally, how can I obtain Thor’s TRM manual?

Hi chen.xi,

Correct, you do not need to configure those pinmux register for CAN manually on Thor.
Actually, those registers can not be read as they are from FSI.

Please share the steps how did you verify them.

The operation steps for the Thor end are as follows:

nvidia@tegra-ubuntu:~$ sudo modprobe can
nvidia@tegra-ubuntu:~$ sudo modprobe can_raw
nvidia@tegra-ubuntu:~$ sudo modprobe mttcan
nvidia@tegra-ubuntu:~$ sudo ip link set can3 type can bitrate 500000 loopback off
nvidia@tegra-ubuntu:~$ sudo ip link set up can3
nvidia@tegra-ubuntu:~$ cansend can3 123#11223344aabbccdd
nvidia@tegra-ubuntu:~$ candump can3

The CAN analyzer terminal receives data through the software and then sends it out.

Could you please give me some good suggestions?

Please run the following command to receive CAN data before you sent.

# candump -x any &

The problem has been resolved. There is no need to support this current post anymore.

Could you share your solution for the benefit of the wider developer community?

It was a problem with our hardware. After the modification, it worked properly. There was no issue with the CAN function of the Thor module itself.

1 Like

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