Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

kuksa-dbc-feeder does not bring up CAN interface if it is not vcan0

Description

As I understand kuksa-dbc-feeder relies on can-dev-helper to bring up CAN interface (in non-vcan case too?).

But "can-dev-helper.sh" will bring up only in case interface is VCAN.

If it is not VCAN but is down, it won't be upped.

Or there something else which could bring up CAN interface for kuksa-dbc-feeder?

Environment

None

relates to

Activity

Show:

Vasyl Vavrychuk 
September 13, 2022 at 1:20 PM

Well, I've just removed bitrate and left whatever is there

I plan to upstream something togather with VIRTIO CAN driver.

Jan-Simon Moeller 
September 13, 2022 at 12:59 PM

Can you paste your configuration values so we have a reference ?

Vasyl Vavrychuk 
September 13, 2022 at 11:34 AM

Thanks for help!

I missed about this systemd-networkd configuration file. Actually, I am working with VIRTIO CAN which apparently does not support bitrate setting. So, removing "BitRate=500K" helped me.

I'm resolving this issue so far.

Jan-Simon Moeller 
September 12, 2022 at 3:57 PM

Try changing /lib/systemd/network/60-canbus-can.network  :

 

[Match]
Name=can*

[CAN]
BitRate=500K
SamplePoint=75%
DataBitRate=4M
DataSamplePoint=80%
FDMode=yes

[Link]
ActivationPolicy=up

 

 

Scott Murray 
September 12, 2022 at 3:55 PM

I was discussing this with today as he was testing the new steering wheel demo setup with the reference hardware, please try the tweak in his reply to you on the mailing list.  In a nutshell, the can0 interface is supposed to be brought up by the systemd network unit that's in place, but it's set up for non-FD CAN so it fails on the reference hardware or other boards with FD interfaces.  Jan-Simon is looking into how we can manage this wrt different systemd network units, the other possibility is we switch to some other configuration scheme.

Fixed

Details

Assignee

Reporter

Hardware Platform(s) Affected

Renesas H3

Components

Affects versions

Priority

Created September 9, 2022 at 11:53 AM
Updated November 16, 2022 at 10:45 PM
Resolved September 13, 2022 at 11:34 AM