Firefly Open Source Community

   Login   |   Register   |
New_Topic
Print Previous Topic Next Topic

[Hardware] AIO-3568j CAN Bus RX Errors

17

Credits

0

Prestige

0

Contribution

new registration

Rank: 1

Credits
17

【Hardware】 AIO-3568j CAN Bus RX Errors

Posted at 1/27/2023 16:12:58      View:1403 | Replies:1        Print      Only Author   [Copy Link] 1#
Last edited by CAN_user10 In 1/27/2023 16:17 Editor

Hi, we are testing out integrating an AIO-3568j board into our product. Our product has a CAN with a 500,000bps bus, but when we attempt to connect this board to our bus we are receiving packets but almost all of them are being received as errors (we only need to receive messages). We are also testing a Debix SOM A + IO board, when we connect this Debix board it is working correctly with no errors, we are connecting both boards to our bus in the same way with the same cables.

We noted that both boards seem to have a 120 olm resistor, so this shouldnt be the problem.

We are running the official ubuntu: AIO-3568J_Ubuntu18.04-MLU220-r21199_v1.3.0a_220817

To setup the CAN bus in Ubuntu we run these commands
'ip link set can0 type can bitrate 500000'
'ip link set can0 up'
we also tried setting the qdisc to default as we noticed the Debix board uses the default, while this firefly defaults to fq_codel.
'tc qdisc replace dev can0 root pfifo_fast'
We tested both can0 and can1 with the same settings and received the same results.

I will attach a screen shot showing the ifconfig read out. It shows both can bus interfaces with lots of errors but note they weren’t connected at the same time, the interfaces were tested separately.

We also tested building our own ubuntu image to change the CAN clock rate, we tested 300M and 400M clock rates but achieved the same result.

Do you have any ideas on what the issue could be?
Thanks!





errors.png (95.78 KB, Down times: 131)

errors.png
Reply

Use props Report

18

Credits

0

Prestige

0

Contribution

new registration

Rank: 1

Credits
18
Posted at 2/10/2023 11:27:30        Only Author  2#
Update the sdk to the latest version and then make the following changes,
Change the can module when using it in the device tree:
-compatible = "rockchip,can-1.0";
+compatible = "rockchip,rk3568-can-2.0";
Reply

Use props Report

You need to log in before you can reply Login | Register

This forum Credits Rules

Quick Reply Back to top Back to list