I'm currently having the exact same problem as this post here: https://e2e.ti.com/support/processors/f/791/t/723318
The main noticeable issue is that the device will work just fine in loopback mode (ip link set can0 type can bitrate 50000 loopback on), with candump and cansend working just fine and the device returning the following as status when ip -details link show can0 is run:
2: can0: <NOARP,UP,LOWER_UP,ECHO> mtu 16 qdisc fq_codel state UNKNOWN mode DEFAULT group default qlen 10
link/can promiscuity 0 minmtu 0 maxmtu 0
can <LOOPBACK> state ERROR-ACTIVE (berr-counter tx 0 rx 127) restart-ms 100
bitrate 50000 sample-point 0.850
tq 1000 prop-seg 8 phase-seg1 8 phase-seg2 3 sjw 1
c_can: tseg1 2..16 tseg2 1..8 sjw 1..4 brp 1..1024 brp-inc 1
clock 25000000numtxqueues 1 gso_max_size 65536 gso_max_segs 65535
However, when I try and follow most tutorials on setting up the canbus, with "triple-sampling on" the program responds with "RTNETLINK answers: Operation not supported".
When the interface is set up without loopback mode enabled, ip -details link show can0 returns the following:
2: can0: <NOARP,UP,LOWER_UP,ECHO> mtu 16 qdisc fq_codel state UNKNOWN mode DEFAULT group default qlen 10
link/can promiscuity 0 minmtu 0 maxmtu 0
can state ERROR-ACTIVE (berr-counter tx 0 rx 127) restart-ms 100
bitrate 50000 sample-point 0.850
tq 1000 prop-seg 8 phase-seg1 8 phase-seg2 3 sjw 1
c_can: tseg1 2..16 tseg2 1..8 sjw 1..4 brp 1..1024 brp-inc 1
clock 25000000numtxqueues 1 gso_max_size 65536 gso_max_segs 65535
However in this mode, nothing is sent on the bus and the can_tx and can_rx lines from the processor are forced low (rather than being normally pulled up).
Any help would be much appreciated.
