Alright I have a change when using Torizon 5.0.0 i get physical Can 2 and 3 to work. In Linux they are refereed to as Can0 & Can2
I did a port of my configuration and the changes in the dtsi file are the same as the one above.
I did run a dmesg | grep flexcan and got the following message.
colibri-imx8x-v10b-06614244:~$ dmesg | grep flexcan
[ 422.623602] flexcan 5a8e0000.can can1: bus-off
[ 652.384734] flexcan 5a8e0000.can can1: bus-off
[ 993.029455] flexcan 5a8e0000.can can1: bus-off
suggesting something is not working as intended.
when running ifconfig i get the following
can0: flags=193<UP,RUNNING,NOARP> mtu 16 metric 1
unspec 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 txqueuelen 10 (UNSPEC)
RX packets 26 bytes 159 (159.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 7 bytes 7 (7.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
device interrupt 64
can1: flags=193<UP,RUNNING,NOARP> mtu 16 metric 1
unspec 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 txqueuelen 10 (UNSPEC)
RX packets 9 bytes 72 (72.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 3 overruns 0 carrier 3 collisions 0
device interrupt 65
can2: flags=193<UP,RUNNING,NOARP> mtu 16 metric 1
unspec 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 txqueuelen 10 (UNSPEC)
RX packets 17 bytes 115 (115.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 3 bytes 3 (3.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
device interrupt 66
But if I use cansend can1 500#00000000 i get the following
can0: flags=193<UP,RUNNING,NOARP> mtu 16 metric 1
unspec 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 txqueuelen 10 (UNSPEC)
RX packets 26 bytes 159 (159.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 7 bytes 7 (7.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
device interrupt 64
can1: flags=129<UP,NOARP> mtu 16 metric 1
unspec 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 txqueuelen 10 (UNSPEC)
RX packets 12 bytes 96 (96.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 3 overruns 0 carrier 3 collisions 0
device interrupt 65
can2: flags=193<UP,RUNNING,NOARP> mtu 16 metric 1
unspec 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 txqueuelen 10 (UNSPEC)
RX packets 17 bytes 115 (115.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 3 bytes 3 (3.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
device interrupt 66
It changes state which is the source for the bus-off state in dmesg.
so there is a difference and it works better 2/3 so far ^^
Can i provide any additional information?