From: Txema Lopez <tlopez@aotek.es>
To: linuxppc-embedded@ozlabs.org
Subject: MPC5200B SPI codec error when there is a heavy ethernet traffic.
Date: Tue, 15 Jan 2008 17:44:12 +0100 [thread overview]
Message-ID: <478CE2DC.5040309@aotek.es> (raw)
[-- Attachment #1: Type: text/plain, Size: 1285 bytes --]
Hi all,
We have a MPC5200B based custom board running a 2.4.25 Denx linux
kernel. We use the PSC6 in SPI-codec mode to exchange some bytes
periodically in full-duplex with a peripheral.
In 'normal' conditions this communication runs fine. But when we start
sending packets over the Ethernet as a background activity, we see on
the oscilloscope that one of the SPI transfers is interrupted. Not only
that the SPI clock stops, something that could happen in the case that
the transmission Fifo is empty, or the reception Fifo is full, but that
the chip select actually goes high for an instant, causing the
peripheral to abort the communication.
We have reproduced the same bug in a Lite5200B using the spi-dev driver
and a user application, so it seams it's not a problem of our hardware.
The problem only arises if there is some heavy Ethernet traffic (a big
file ftp transfer or a big file copy by nfs) , so we think the error is
related with the Bestcomm activity. We have contacted freescale to check
if it's a microprocessor bug and they are looking into it. But we think
it could be also a bug in the Bestcomm programming of the FEC tasks.
Could be it possible? At this point, we really need some help. Any clue
will be welcomed.
Best regards,
Txema
[-- Attachment #2: tlopez.vcf --]
[-- Type: text/x-vcard, Size: 324 bytes --]
begin:vcard
fn:Jose Maria Lopez
n:Lopez;Jose Maria
org:Fagor Automation S. Coop.
adr:;;San Andres 19. Apdo. 144;Arrasate-Mondragon;;20500;Spain
email;internet:tlopez@aotek.es
title:Sotware engineer
tel;work:(34) 943719200
tel;fax:(34) 943791712
x-mozilla-html:FALSE
url:http://www.fagorautomation.es
version:2.1
end:vcard
reply other threads:[~2008-01-15 17:07 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=478CE2DC.5040309@aotek.es \
--to=tlopez@aotek.es \
--cc=linuxppc-embedded@ozlabs.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 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).