Can communication fails only through loopback testing, and the system is found to be over frequency

syslog(4) (1.2 MB)
kern(2).log (5.0 MB)
jetpack4.6.1 bsp3271 nxmodule
Using native can loopback test communication, unable to communicate
sudo modprobe can
520 sudo modprobe can_raw
521 sudo modprobe mttcan
522 sudo ip link set down can0
523 sudo ip link set can0 type can bitrate 500000
524 sudo ip link set can0 type can loopback on
525 sudo ip link set up can0
526 cansend can0 123#abcdabcd
527 ifconfig -a
528 cansend can0 123#abcdabcd
529 ifconfig -a

Are you following this instruction t do the setup: Controller Area Network (CAN) — Jetson Linux Developer Guide documentation ( ?
Which JetPack SW?

Yes, based on this, my Jetpack version is 4.6.1, and the L4T version is 3271

“Normal can is enabled, but it suddenly fails during operation. I have sent you the log of the failure, but it will be fine if you power off and restart it. When there is no communication, the device status also appears to be incorrect, such as overclocking.”

Are you able to try Jetpack 4.6.3(r32.7.3) or Jetpack 5.1(r35.2.1)? These are later releases for Xavier NX.

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