* MCP2515 implementation is slow
@ 2014-11-25 16:19 Pankajkumar Misra (RBEI/EEA2)
2014-11-27 7:33 ` David Jander
0 siblings, 1 reply; 2+ messages in thread
From: Pankajkumar Misra (RBEI/EEA2) @ 2014-11-25 16:19 UTC (permalink / raw)
To: linux-spi@vger.kernel.org, linux-can@vger.kernel.org
Hello Guys,
I have compiled MCP251x.c kernel driver module for Olimex A20-Olinuxino Micro.
The device is working fine for one frame at a time at 500ms. If I send two or more frame at the same time,
CAN is going to bus-off due to overrun errors.
Even if I send one frame at faster rate say, 100ms,results in bus-off.
I am communicating with module with ip commands, cansend & candump.
Also my SPI module is working only at 250K baud, not any other baud.
Any suggestions.
Best Regards,
Pankaj
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: MCP2515 implementation is slow
2014-11-25 16:19 MCP2515 implementation is slow Pankajkumar Misra (RBEI/EEA2)
@ 2014-11-27 7:33 ` David Jander
0 siblings, 0 replies; 2+ messages in thread
From: David Jander @ 2014-11-27 7:33 UTC (permalink / raw)
To: Pankajkumar Misra (RBEI/EEA2)
Cc: linux-spi@vger.kernel.org, linux-can@vger.kernel.org, gianluca
On Tue, 25 Nov 2014 16:19:33 +0000
"Pankajkumar Misra (RBEI/EEA2)" <Pankaj.Kumar@in.bosch.com> wrote:
> I have compiled MCP251x.c kernel driver module for Olimex A20-Olinuxino
> Micro.
>
> The device is working fine for one frame at a time at 500ms. If I send two
> or more frame at the same time, CAN is going to bus-off due to overrun
> errors. Even if I send one frame at faster rate say, 100ms,results in
> bus-off.
I tend to think there is something other wrong with your setup. Maybe you are
missing bus-termination/biasing? Chip-clock?
The device should never go in bus-off mode if there are RX-overruns. If it
goes into bus-off, there is something wrong in the hardware.
> I am communicating with module with ip commands, cansend & candump.
> Also my SPI module is working only at 250K baud, not any other baud.
We use a MCP2515 with this driver at 250kbit/s receiving back-to-back messages
without loss on a i.MX51. Please note, that it won't work reliably at any
higher bitrate and system load is quite high.
The MCP2515 is a very bad design, but the driver performance has improved a lot
since spi-bitbang started using a kthread instead of a work-queue.
> Any suggestions.
>
> Best Regards,
> Pankaj
> --
> To unsubscribe from this list: send the line "unsubscribe linux-can" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
Best regards,
--
David Jander
Protonic Holland.
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2014-11-27 7:33 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2014-11-25 16:19 MCP2515 implementation is slow Pankajkumar Misra (RBEI/EEA2)
2014-11-27 7:33 ` David Jander
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).