I have the impression that your network is set up for J1939 or CANOpen (CAN
2.0B)

when you send a message to a short address (CAN 2.0A) it doesn't get
acknowledged, and this might crash your bus, as the BB will try to send it
till the message is acknowledged..
Try to send a message to  a 29bit address, or add a second can interface
that will acknowledge your messages. (CAN1 on the BB).

I'm a bit stuck on moving over to J1939, as that requires at least kernel
5.4, which results in boot issues due the overlay approach as applied in
the Beaglebone OS
You can stop this boot failure, but then I failed to have my network coming
up, which was another issue. (I had to work through the debug port)

If you have some advancements in that domain? I am bit time constraint to
solve it in the near future.
I hope the next release will have the latest kernel.

Prepare to learn a lot about working with micro controllers and OS
environments when working in the CAN domain.

Regards,

Gwen


Op di 19 mei 2020 om 17:02 schreef <klim....@gmail.com>:

> I tried to do as indicated in this instruction
> <https://processors.wiki.ti.com/index.php/AM335X_DCAN_Driver_Guide#ip>,
> but it is outdated and does not produce results on new linux kernels. What
> I have to do to make the can interface work?
>
>
> Board: custom board am3359 (almost like beaglebone black)
>
> Target: linux kernel 4.14 , debian 9.9
>
> Target: linux kernel 5.6.4 , debian 10 - same result
>
>
> Problem: Can-bus working just *listen-only-mode*
>
>
> *listen-only mode is ok, messages comes:*
> ? <https://e2e.ti.com/support/processors/f/791/t/906552#>
> 1
> 2
> 3
> 4
> 5
> 6
> 7
> sudo ifconfig can0 down
> sudo ip link set can0 type can bitrate 125000 listen-only on
> sudo ifconfig can0 up
> candump -cae can0,0:0,#FFFFFFFF
>   can0  1FE4F1DC   [8]  01 64 00 00 00 00 00 00   '.d......'
>   can0  1FE4F1DC   [8]  01 64 00 00 00 00 00 00   '.d......'
>   can0  1FE4F1DC   [8]  01 64 00 00 00 00 00 00   '.d......'
>
> *normal mode bus crashes:*
> ? <https://e2e.ti.com/support/processors/f/791/t/906552#>
> 1
> 2
> 3
> 4
> 5
> 6
> sudo ip link set can0 type can bitrate 125000
> sudo ifconfig can0 up
> [13210.377469] c_can_platform 481cc000.can can0: setting BTR=1c0b
> BRPE=0000
> [13210.391464] IPv6: ADDRCONF(NETDEV_CHANGE): can0: link becomes ready
> cansend can0 123#DEADBEAF
> [13220.749607] c_can_platform 481cc000.can can0: bus-off
>
> --
> For more options, visit http://beagleboard.org/discuss
> ---
> You received this message because you are subscribed to the Google Groups
> "BeagleBoard" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to beagleboard+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/beagleboard/9673987a-f2a0-4a5f-8b48-d34a2aae61d9%40googlegroups.com
> <https://groups.google.com/d/msgid/beagleboard/9673987a-f2a0-4a5f-8b48-d34a2aae61d9%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
>

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/CAFfeaG-7TS1HU1-jVbzwFZ7J%3DSL%2BtGu9OHLnuvFzEh-FYTYYyQ%40mail.gmail.com.

Reply via email to