wiki/ CanBusLinuxDriver

CAN Bus Linux Driver

News 7-Dec-2004

Now we are tuning for efficiency.

News 5-Sept-2004

Many reliablility problems were solved:

Thank you, ?KeithPackard!

News 18-August-2004

Uncanny has been installed and tested on the launch tower and the Flight Computer! In practice, Phase 1 (interruptless) was not completed, and we moved directly into Phase 2.

The main limitation that was uncovered was the inability to detect arbitrary RTR messages. Instead, the Intel chip is designed for the user to set up message buffers with data to send automatically when the matching RTR message is received, without having to involve the higher level software. We have adapted the PIC nodes not to send RTR messages to work around this limitation.

News 5-Feb-2004

Freenix paper accepted! The paper will be refereed with a final submission deadline of March 25th. The referee is Ralf Nolden (kde.org). Now I'll have to decide whether it's worth a trip to Boston in the summer.

Since the paper is supposed to be about developing a working driver, hopefully this will be a kick in the butt to get working on this more regularly. There might be a test on the LTC this weekend at Andrew's house. (In the meantime, small amounts of the interrupt handler have been written.)

News 31-Dec-2003

Freenix paper submitted! The ?LaTeX source will be attached to AbstractFreenix2004 presently.

Not much else has been done on the driver recently. It is in suitable shape to install and test on the LTC, but Ted has been working on the LTC electronics all month.

News 2-Dec-2003

Bart suggested we do a writeup of the CAN driver work for Freenix in July 2004 in Boston. The deadline for submission of an abstract is 16-Dec-2003. An outline is on AbstractFreenix2004.


The Flight Computer and ?Launch Tower Computer MOPS/520 boards contain a built-in Intel i82527 CAN interface chip. We found an open source Linux driver which handles this chip, which we modified to work on the MOPS board.

Capabilities

Problems

CAN Driver Rewrite

The problems outlined above along with the "one device per message object" design decision were found to be too limiting. The current driver is overly general in order to deal with lots of settable parameters, two types of CAN chips, and a multitude of different boards and architectures.

The proposed driver rewrite features:

Phase 0 user mode chip driver for easier experimentation [DONE 18-Nov-2003]

Phase 1 (started 11 Nov 2003, suitable for low bandwidth commands to LTC):

Phase 2 (suitable for high bandwidth telemetry from FC):

-- IanOsgood - Sept 5, 2004

Other useful pages

Chip references

-- IanOsgood - 03 Oct 2003