PEAK-System Forum

BTW: the upcoming peak-linux-driver-8.x will be able to handle ip link set commands with SocketCAN devices, so there is no need to use the echo commands anymore

Michael, do you have any time frame of when the upcomming driver will be available to us.

Regards,
Benno

For me it is also not posible to use the Peak USB dongle on the "Linux version 4.1.13-v7+" kernel.
Only downgrading the kernel back to "Linux version 3.18.0-trunk-rpi" I can see the Peak USB can0 device.

Other downside is you have 2 different kernels for the PI and the PI2, so if you have a PI 2 ...

Yes I woud like to use the Peak-CAN dongle on this PI to use both CAN and our hardware at the same time.

Benno

Our CAN Hardware is not using SPI (to slow!!!)
You need a CAN-USB Interface with our own USB Drivers to work with CAN


Yes I know, but our other hardware is using SPI from the device tree option in the 4.x kernel
Also the 2 different kernels for PI en PI2 is solved with the device tree solution ...

Is there already a solution to use the drivers on 4.1.13 kernel.
This version of the kernel is using devicetree drivers for the SPI bus.

The 3.18.0 kernel is not using DT.

Benno

As always the solution is simple
then the controller auto recovers from bus-off errors.

Benno

I am working on a SocketCAN implementation in C / C++

When the Peak USB CAN dongle is in a error state (BUS-OFF in below example), I can not send messages on the bus anymore.
Receiving of messages is no problem.

# ifconfig -a
can0 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00 ...