Hello Pavel,
Thanks a lot for the quick response. went through the shared references !
now facing the CAN bus-off error.. below are the CAN communication details..
On first SoloX target:
:~# ip link set can0 up type can bitrate 125000
:~# dmesg -c
[ 80.008830] flexcan 2090000.can can0: writing ctrl=0x0e312005
[ 80.019421] flexcan 2090000.can can0: flexcan_set_bittiming: mcr=0x5980000f ctrl=0x0e312005
[ 80.019493] flexcan 2090000.can can0: flexcan_chip_start: writing mcr=0x7de2020d
[ 80.019543] flexcan 2090000.can can0: flexcan_chip_start: writing ctrl=0x0e31ac55
[ 80.021531] flexcan 2090000.can can0: flexcan_chip_start: reading mcr=0x64e2020d ctrl=0x0e31ac55
:~#
:~# cansend -e can0 0 1 2 3 4 5 6 7 --loop=2
interface = can0, family = 29, type = 3, proto = 1
:~# dmesg
[ 167.440742] flexcan 2090000.can can0: Error Warning IRQ
[ 167.440814] flexcan 2090000.can can0: Error Passive IRQ
[ 167.443903] flexcan 2090000.can can0: bus-off
:~# ip -details -statistics link show can0
2: 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 0 rx 0) restart-ms 0
bitrate 125000 sample-point 0.875
tq 500 prop-seg 6 phase-seg1 7 phase-seg2 2 sjw 1
flexcan: tseg1 4..16 tseg2 2..8 sjw 1..4 brp 1..256 brp-inc 1
clock 30000000
re-started bus-errors arbit-lost error-warn error-pass bus-off
0 0 0 1 1 1
RX: bytes packets errors dropped overrun mcast
16 2 0 0 0 0
TX: bytes packets errors dropped carrier collsns
0 0 0 0 0 0
:~#
On second SoloX target:
:~# ip link set can0 up type can bitrate 125000
:~# dmesg -c
[ 142.380312] flexcan 2090000.can can0: writing ctrl=0x0e312005
[ 142.392468] flexcan 2090000.can can0: flexcan_set_bittiming: mcr=0x5980000f ctrl=0x0e312005
[ 142.392504] flexcan 2090000.can can0: flexcan_chip_start: writing mcr=0x7de2020d
[ 142.392529] flexcan 2090000.can can0: flexcan_chip_start: writing ctrl=0x0e31ac55
[ 142.392871] flexcan 2090000.can can0: flexcan_chip_start: reading mcr=0x64e2020d ctrl=0x0e31ac55
:~#
:~# candump can0
interface = can0, family = 29, type = 3, proto = 1
^C
:~# dmesg
:~# ip -details -statistics link show can0
2: can0: <NOARP,UP,LOWER_UP,ECHO> mtu 16 qdisc pfifo_fast state UNKNOWN mode DEFAULT group default qlen 10
link/can promiscuity 0
can state ERROR-ACTIVE (berr-counter tx 0 rx 0) restart-ms 0
bitrate 125000 sample-point 0.875
tq 500 prop-seg 6 phase-seg1 7 phase-seg2 2 sjw 1
flexcan: tseg1 4..16 tseg2 2..8 sjw 1..4 brp 1..256 brp-inc 1
clock 30000000
re-started bus-errors arbit-lost error-warn error-pass bus-off
0 0 0 0 0 0
RX: bytes packets errors dropped overrun mcast
0 0 0 0 0 0
TX: bytes packets errors dropped carrier collsns
0 0 0 0 0 0
:~#
I am facing a bus-off error on the first target can0 interface. from where I am sending CAN messages.
The CAN cables I used in two sets are in good connectivity mode.. checked with multimeter..
Any pointers or references on debugging the bus-off error... will be a great help! Thanks!
Thanks
Shrikant