Hello,
I seem to have the same problem on an imx7 colibri using flexcan1 (pins 55 and 63). The state goes to BUS-OFF as soon as I try to send the first message.
# ip -details link show can0
4: can0: mtu 16 qdisc pfifo_fast state UP mode DEFAULT group default qlen 10
link/can promiscuity 0 minmtu 0 maxmtu 0
can state ERROR-ACTIVE (berr-counter tx 0 rx 0) restart-ms 0
bitrate 250000 sample-point 0.875
tq 250 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 24000000numtxqueues 1 numrxqueues 1 gso_max_size 65536 gso_max_segs 65535
# cansend can0 123#deadbeef
# ip -details link show can0
4: can0: mtu 16 qdisc pfifo_fast state DOWN mode DEFAULT group default qlen 10
link/can promiscuity 0 minmtu 0 maxmtu 0
can state BUS-OFF (berr-counter tx 0 rx 0) restart-ms 0
bitrate 250000 sample-point 0.875
tq 250 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 24000000numtxqueues 1 numrxqueues 1 gso_max_size 65536 gso_max_segs 65535
# dmesg | fgrep -i can
[ 12.015535] CAN device driver interface
[ 12.045204] flexcan 30a00000.can: 30a00000.can supply xceiver not found, using dummy regulator
[ 80.563886] IPv6: ADDRCONF(NETDEV_CHANGE): can0: link becomes ready
[ 116.604819] can: controller area network core (rev 20170425 abi 9)
[ 116.616042] can: raw protocol (rev 20170425)
[ 116.618702] flexcan 30a00000.can can0: bus-off
#
I’m running this from a docker image with these numbers:
# cat /etc/issue
Debian GNU/Linux 10 \n \l
# cat /etc/os-release
PRETTY_NAME="Debian GNU/Linux 10 (buster)"
NAME="Debian GNU/Linux"
VERSION_ID="10"
VERSION="10 (buster)"
VERSION_CODENAME=buster
ID=debian
HOME_URL="https://www.debian.org/"
SUPPORT_URL="https://www.debian.org/support"
BUG_REPORT_URL="https://bugs.debian.org/"
And the Torizoncore version:
~$ cat /etc/os-release
ID=torizon-upstream
NAME="Torizoncore Upstream"
VERSION="5.1.0+build.1 (dunfell)"
VERSION_ID=5.1.0-build.1
PRETTY_NAME="Torizoncore Upstream 5.1.0+build.1 (dunfell)"
BUILD_ID="1"
ANSI_COLOR="1;34"
~$ cat /etc/issue
Torizoncore Upstream 5.1.0+build.1 \n \l
Hope this is relevant.
Has any solution to this issue been found?