PEAK-Linux Driver on Raspberry Pi

[M.Maidhof]

Hi,

when you like to use the PCAN-USB with the Netdev interface, you don´t need to install our chardev driver anymore. Since kernel version 3.4 and higher, the SocketCAN Netdev driver is available in the kernel. But when you install our chardev driver, the kernel driver will be blacklisted. So please do the following steps:

- uninstall our driver in the peak-linux-driver directory: sudo make uninstall
- reboot your system.
- after the next boot, check for can0,1 with ifconfig -a
- configure the devices with ip link set

regards

Michael

[roB3AR]

Hi Michael,

Thanks for the quick response. I tried what you said, but can0 and can1 aren't listed under 'ifconfig -a', even with running 'sudo modprobe can' before. Using another microSD card, I copied/installed Raspbian 4.1.13-v7+ onto it, installed can-utils, and then ran 'config -a', but I don't see the pcans anywhere represented as can0 or can1. I'll continue to look for them, but I was wondering if I'm still missing a step not using the chardev?

UPDATE: I'm currently trying to follow the guide you outlined here, but I can't figure out what to add to /boot/config.txt. I've tried a few things, but each time the Raspberry Pi didn't come back online after reboot.

Thanks again,
Rob

[bennog]

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 use the right 3.18 kernel.

Benno

[M.Maidhof]

it looks like the SOCKETCAN option is not enabled in your kernel config.

Please check cat /boot/config-4.xxxxxxx |grep -i can

(replace xxxxxx with your kernel version)

If you don´t like to recompile the kernel with that option, you can also use the peak-linux driver, and compile it for Netdev use. Than you will see canX devices again.

see: http://www.peak-system.com/forum/viewto ... t=256#p723

Or try a different 4.x kernel which has the SocketCAN option enabled by default.

regards

Michael

[roB3AR]

bennog,
What git commit id did you use to downgrade to "Linux version 3.18.0-trunk-rpi"? I tried this one, but it only took me to 3.18.3 from 4.1.13-v7+ and "uname -r" lists 4.1.13-v7+ still.

Michael,
I don't have any file within my image that starts with "config-4*" (ran sudo find -iname "config-4*"). I'm still determined to get a version of raspbian running without the peak-linux driver. I've gotten the peak-linux driver running with netdev support, but it lacks the ability for me to set the bitrate via ip link, which is my main problem. I know I can still set it with echo command, but I was really hoping to get this set up using the full range of netdev tools.
I was trying to get this example you wrote running, but when it appears the image 2014-01-07-wheezy-raspbian.img that raspberrypi.org hosts is corrupt (sha1 doesn't match that of the site, and it won't boot), which is disappointing because that seemed pretty failsafe. Do you know of any other builds version of raspbian that have socketcan enabled, and you've tested the pcan with?
As always, thanks for taking time to help me get this set up!
Thanks,
Rob

[M.Maidhof]

Hi Rob,

do you have a RPI or RPI2? The image was for a RPI1, and I still have a copy of this image (2014-01-07-wheezy-raspbian.img) here available. Please contact me by email, using our support email address for more details.

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.

regards

Michael

[bennog]

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

[M.Maidhof]

Hi Benno,

it should be ready for release until end of this month.

regards

Michael

[felgo]

Is support for 4.* kernel also included in the upcomming driver? Is there another way to use pcan with this kernel and socketcan?

[M.Maidhof]

Hi,

simply use the Netdev driver which is included in the 4.x kernel. The kernel driver is always a SocketCAN driver. You only have to configure your kernel, to have the SocketCAN option enabled, if it is not enabled by default.

Do you have any issues with our peak-linux driver and kernel 4.x?

regards

Michael