Are there any kernel builds to make CAN communication?

Autonomous Machines Jetson & Embedded Systems Jetson TX2
1

Are there any kernel builds to make CAN communication?

I’d appreciate it if you could teach me how to do it.

For example, you need to modify the source or install something…

Currently connected via Transylver and sent to CANSAND, there is no response to CAMDUPM.

There is no response to a waveform with the oscilloscope.

When you shoot with a tester, you get a voltage of 3.3V.

CAN-UTILS is also installed, and CAN0 and CAN1 are also visible.

Is there a kernel build that allows CAN communication? Please let me know if you have details.

2

Assuming you’re using the latest JetPack kernel, it already supports CAN.
All you need to do is to add a CAN transciever to the CAN TX and CAN RX pinx (and power/ground,) and configure the interface using ifconfig.

3

can0 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
UP RUNNING NOARP MTU:16 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:10
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
Interrupt:171

can1 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
UP RUNNING NOARP MTU:16 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:10
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
Interrupt:172

Module Size Used by
can_bcm 15298 0
can_gw 10262 0
can_raw 9004 0
can 46782 3 can_gw,can_bcm,can_raw
mttcan 60323 0
can_dev 13416 1 mttcan
vfat 10579 1
fat 63477 1 vfat
fuse 89760 2
bcmdhd 7633912 0
pci_tegra 75137 0
bluedroid_pm 13564 0

It is currently my state. help me!!!

4

can0: <NO-CARRIER,NOARP,UP,ECHO> mtu 16 qdisc pfifo_fast state DOWN mode DEFAULT group default qlen 10
link/can promiscuity 0
can state BUS-OFF (berr-counter tx 248 rx 0) restart-ms 0
bitrate 5000000 sample-point 0.750
tq 25 prop-seg 2 phase-seg1 3 phase-seg2 2 sjw 1
mttcan: tseg1 2…255 tseg2 0…127 sjw 1…127 brp 1…511 brp-inc 1
mttcan: dtseg1 1…31 dtseg2 0…15 dsjw 1…15 dbrp 1…15 dbrp-inc 1
clock 40000000
re-started bus-errors arbit-lost error-warn error-pass bus-off
0 0 0 1 1 0
RX: bytes packets errors dropped overrun mcast
24 3 0 0 0 0
TX: bytes packets errors dropped carrier collsns
0 0 0 0 0 0

can1: <NO-CARRIER,NOARP,UP,ECHO> mtu 16 qdisc pfifo_fast state DOWN mode DEFAULT group default qlen 10
link/can promiscuity 0
can state BUS-OFF (berr-counter tx 248 rx 0) restart-ms 0
bitrate 500000 sample-point 0.875
tq 25 prop-seg 34 phase-seg1 35 phase-seg2 10 sjw 1
mttcan: tseg1 2…255 tseg2 0…127 sjw 1…127 brp 1…511 brp-inc 1
mttcan: dtseg1 1…31 dtseg2 0…15 dsjw 1…15 dbrp 1…15 dbrp-inc 1
clock 40000000
re-started bus-errors arbit-lost error-warn error-pass bus-off
0 0 0 1 1 0
RX: bytes packets errors dropped overrun mcast
24 3 0 0 0 0
TX: bytes packets errors dropped carrier collsns
0 0 0 0 0 0

please explain what the current state is. I do not know.

cansend can0 123#abcdabcd
candump can1>>>>>> nothing appears!!!

can0>>>>>can1 I do not know how to communicate.

5

Have you connected the interfaces with appropriate transcievers? Which transcievers are you using?

Also, I suggest you learn about how CAN drivers on Linux work:
https://elinux.org/CAN_Bus
http://socket-can.996257.n3.nabble.com/Getting-started-with-Linux-amp-SocketCAN-td973.html