All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tom Evans <tom_usenet@optusnet.com.au>
To: "François Beaulier" <fbeaulier@orange.fr>, linux-can@vger.kernel.org
Subject: Re: Linux board with 10 CANs
Date: Sat, 16 May 2015 01:24:20 +1000	[thread overview]
Message-ID: <55560FA4.4090300@optusnet.com.au> (raw)
In-Reply-To: <5555A6A3.7090206@orange.fr>

On 15/05/2015 5:56 PM, François Beaulier wrote:
> Hi,
>
> I'm starting the design of a CPU board, based on a computer on module
> with a very common SOC like i.mx6 or am335x.

There are SOCs with 8 CAN ports built in, like the Freescale MPC574X 
chips. That should be a lot easier to work with, and should be supported 
without any extra drivers.

The following Selector Guide tells me the Vybrid SVFxxxR has *FIFTY* CAN 
ports. That may have multiple typos, as Freescale's web site doesn't 
admit to that part.

http://cache.freescale.com/files/microcontrollers/doc/roadmap/BRAUTOPRDCTMAP.pdf

> CAN bitrate needed is quite low (50kbps)

So at about 110 bits for a minimum sized Standard ID packet, that gives 
you 450 messages/second max. That gives you a maximum service latency of 
2.2ms for as many buffers as the chip has. If your data has 8 
bytes/packet then that drops to 3.5ms/buffer (7ms for a chip with 2).

That wouldn't be impossible with MCP2515s, just inadvisable. Especially 
with Linux as it isn't good at any service guarantees.

But I've successfully run three MCP2515's on a Coldfire part. The QSPI 
helps a lot. There are a lot of parts with multiple QSPI ports, and that 
makes it less onerous (or DSPI or ECSPI). The i.MX6D has 5 on it. So two 
"real" CAN ports and two MCP2515's on each of the SPI ports, with a 
spare SPI port. Or three per port.

> I don't want to use MCP2515, i had trouble with it on a previous
 > design because of the lack of buffer in the chip.
> I can't imagine putting 8 MCP2515 and not missing any frame, but may be
> i'm wrong ?

Did you turn the BUKT bit on? If you spread them across lots of SPI 
interfaces it should get easier as they should all be accessed in parallel.

Tom


  parent reply	other threads:[~2015-05-15 15:24 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-15  7:56 Linux board with 10 CANs François Beaulier
2015-05-15  8:20 ` Yegor Yefremov
2015-05-15  8:50   ` François Beaulier
2015-05-15  9:11   ` Marc Kleine-Budde
2015-05-15  9:33     ` François Beaulier
2015-05-15 10:24       ` Andri Yngvason
2015-05-15 12:40         ` François Beaulier
2015-05-15 12:47           ` Marc Kleine-Budde
2015-05-15 13:04             ` AW: [BULK]Re: " Uwe Wilhelm (PEAK-System)
2015-05-15 13:17               ` Marc Kleine-Budde
2015-05-15 13:20                 ` AW: " Uwe Wilhelm (PEAK-System)
2015-05-15 14:18               ` François Beaulier
2015-05-15 12:38       ` Gerhard Uttenthaler
2015-05-15 12:48         ` Marc Kleine-Budde
2015-05-15 13:54 ` Bernd Krumboeck
2015-05-18  9:07   ` François Beaulier
2015-05-18 13:31     ` Bernd Krumboeck
2015-05-20 11:35       ` Gediminas Simanskis
2015-05-21  3:19         ` Bernd Krumboeck
2015-05-15 15:24 ` Tom Evans [this message]
2015-05-18  9:25   ` François Beaulier
2015-05-18  9:40     ` Gerhard Bertelsmann
2015-05-18 11:13       ` François Beaulier
2015-05-18 12:56       ` Tom Evans

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=55560FA4.4090300@optusnet.com.au \
    --to=tom_usenet@optusnet.com.au \
    --cc=fbeaulier@orange.fr \
    --cc=linux-can@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.