Show Posts
Pages: [1]
1  Products / Arduino Due / Re: Building a CAN communication protocol interface for Arduino DUE on: February 07, 2013, 09:43:47 am
Palliser, I did  not mean to be critical. People are ready to go on this, and I think it's time we start working towards a goal. It sounds like the Atmel engineer may have higher priorities or slowed down on progress, maybe we should start working on our own CAN API. What would we need outside of the datasheet to do this?
2  Products / Arduino Due / Re: Building a CAN communication protocol interface for Arduino DUE on: February 06, 2013, 05:21:18 pm
I would have to agree with AdderD. Why can't preliminary code be posted up for people to start digesting/optimizing/learning/testing/developing? Also, this API that's being 'developed'. There hasn't even been any discussion on how this API will utilize the CAN peripheral and other necessary peripheral features on board the micro.

Let me elaborate: From my experience with micros and peripherals, there are many ways to configure the drivers. Sometimes you can use DMA, sometimes there is dedicated RAM on board for the specifc peripheral, or you might not use either. There's all kinds of Low Power Mode Options just for CAN. What events will be generating CAN interrupts to the uC?
What exactly is this API establishing? A bare bones CAN driver or are there more layers of software queuing on top?

So why are driver configuration options not up for discussion? The driver is the foundation upon which everything else will be running. It seems as though there should be discussion on this, unless Palliser wants only his CAN driver ideas implemented..
3  Products / Arduino Due / Re: Building a CAN communication protocol interface for Arduino DUE on: December 13, 2012, 05:36:45 pm
To clarify my last post, I suggest we don't use Atmel's CAN drivers and instead work them from scratch. But if they are really good, then no need to mess with them. In reality, it will probably be a task of looking what they did and seeing if we can improve upon their driver implementation. If it's anything like the CAN processing on the PIC24/PIC32, you can probably offload much of the CAN receiving messages to a DMA channel, which will be key for efficiency. This could be done with TX too, but may not benefit too many applications. I should probably start reading the Atmel uC manual to see how they implement this stuff.
4  Products / Arduino Due / Re: Building a CAN communication protocol interface for Arduino DUE on: December 13, 2012, 05:20:06 pm
I see. I haven't looked at the Atmel CAN example drivers yet, but from my experience, chip manufacturer's code is generally pretty rubbish. If we want legitimate CAN applications for the Arduino, we will need to have an extremely solid base driver interface to work off. Don't want to build a house on a weak (inefficient) foundation.
5  Products / Arduino Due / Re: Building a CAN communication protocol interface for Arduino DUE on: December 13, 2012, 12:08:55 pm
Palliser, are you developing the base CAN drivers based on Atmel example code at the moment? My plan was to write the CAN drivers from scratch, with different configurations options. After that is up and working, integrate that code into an Arduino library.
6  Products / Arduino Due / Re: Building a CAN communication protocol interface for Arduino DUE on: December 05, 2012, 09:58:07 am
Hey guys. I'm interested in getting on board with the CAN protocol as well. I've done a lot of low level CAN drivers on the pic24, dspic, and pic32 along with the MCP2551 transceiver at work. I have a DUE coming in next week and just put in my order for TI samples of the two transceivers mentioned earlier in this thread (234 and 235).
What is the scope of this CAN library? I'd be more than willing to work the low level driver stuff and different implementations of it (interrupt based, polling based, different modes).
Pages: [1]