Beginning with svn version 438 can4linux can be used on the RaspberryPi when a Microchip MCP1515 is connected to the SPI pins. Tested on kernel 3.12.32+
can4linux for the CPC-PCI and the CAN FD board IB-500 was successful tested to run with kernel 3.16. It is assumed that all other targets which were used under kernel 3.11 and higher will run as well with 3.16.
The BananaPi is a small credit card size computer. But different to the RaspberryPi the used Allwinner A20 CPU has a CAN controller on chip.
There is now already some code in the repository as a first starting point. The project leader hopes to have a working version within the next days.
This entry shows how many processes are currently using a physical(or virtual) CAN channel and how many are allowed to share a CAN controller. The format is:
/proc/sys/dev/Can/OpenCount: 2(4) 1(4) 0(4) 0(4)
where the first number shows the number of processes currently using the CAN and the number in parenthesis shows the max number allowed.
Tested can4linux TARGET=CPC_PCI successfully with the newly installed Kubuntu 14.04.
Of course, other TARGETs should work as well.
The first ready to use version with CAN FD support fort the IXXAT IB500 is available now. On board are two CAN channels based on the IFI CAN FD implemented in a FPGA. The driver is able to be used in classic CAN or CAN FD mode.
Starting with svn version 286 two targets can be used which are using the kernel coding style.
Its the native PC based EMS_PCI, a two channel PCI board, and
The EtherCAN3.0 ecan9 for the Freescale i.MX28
Please test and have fun
can4linux for the CPC-PCI board was successful tested to run with kernel 3.11. It is assumed that all other targets which were used under kernel 3.0 and higher will run as well with 3.11.
From now on the sources in the SourceForge repository will be changed to conform to the Linux kernel coding style. For historical reasons only that was not the case up to now.
The two LEDs, red and green, per CAN channel and the CAN termination can be controlled via ioctl().
can4linux compiles on OpenSuse 12.3 which was released recently.
Linux kernel version is 3.7.10.
Already some month ago we followed the advice of SourceForge to upgrade to the new project structure. With this change, the URL of the repository did change as well.
Unfortunately the most changes on the can4linux project were still made on the old URL, and therefore not visible on the SourceForge can4linux project pages.
This was corrected now. https://sourceforge.net/projects/can4linux/ is up to date.... read more
We are pleased to announce the first released version for this modern target. Check out README.xcanps.zynq for more information about features and some restrictions we have still to work on.
Please test.
Alex has added a scripting interface for Python. Check out
can4linux-examples/pyCan-example.py.
The latest svn version 139 contains code to support CAN FD.
Because currently no hardware CAN controller is available,
this can only be used and tested in the virtual CAN mode.
can4linux can be used without any hardware if the module is loaded with
/sbin/insmod $(CAN_MODULE).ko virtual=1
The module is compiled anyway for a specific hardware. Therefore it is possible to switch at load time between real hardware support or the simulation mode. In simulation mode no hardware access will take place and the module can be loaded without the board installed for which the module is compiled.... read more
The CAN TX and RX error counters are now available in
/proc/sys/dev/Can.
Independently of any CAN application the error counters can now be read out to get an impression on the communication quality.
This is only available for the SJA1000 so far.
Please provide patches for other CAN controllers.
Some functions, like ioctl(... CMD_STOP ...) are only available for the first process which has opened the CAN device.
Created can4linux-3.6.tgz from svn release 118 which at least should work with Linux kernels up to kernel 3.1
the i.MX28 based module is now supported with can4linux