Hi KingAlex1985 1. The can utilities are from socketcan. I build them using my cross-compiler by doing: mkdir socketcan;cd socketcan svn co http://svn.berlios.de/svnroot/repos/socketcan cd can-utils export CC=/opt/xtools/chain/arm-unknown-linux-gnueabi/bin/arm-unknown-linux-gnueabi-gcc export CPPFLA...

I noticed that the clock value I was using was not appropriate for the PICAN board as the PICAN has a 16Mhx crystal. With arch/arm/mach-bcm2708/bcm2708.c patched appropriately - .oscillator_frequency = 20000000, + .oscillator_frequency = 16000000, - .max_speed_hz = 10000000, + .max_speed_hz = 800000...

OK perhaps I spoke too soon about having a solution with the raspberryPi and the PICAN board. The driver now works well in loopback mode, i.e. ip link set can0 type can bitrate 500000 loopback on ifconfig can0 up and I can use cangen and candump with data coming through just fine. However, connectin...

The solution is an updated mcp2515.c which can be found at http://lnxpps.de/rpie/mcp2515_mod.c With the new mcp2515.ko installed, I now get: # ip link set can0 type can bitrate 500000 restart-ms 100 # ip -details link show can0 5: can0: <NOARP,ECHO> mtu 16 qdisc noop state DOWN mode DEFAULT qlen 10 ...

I have the same symptoms as KingAlex1985. I am able to talk to my device on the CAN bus using the RaspberryPi and a Peak-USB Can device. When I use the pican nothing is transmitted as the link is always in the state STOPPED. ie. ip -details link show can0 3: can0: <NOARP,UP,LOWER_UP,ECHO> mtu 16 qdi...