From: Roman Fietze <roman.fietze@telemotive.de>
To: linuxppc-embedded@ozlabs.org
Subject: LocalPlus or XLB-Arbiter Problems, DMA, MPC5200, DENX' 2.4.25
Date: Tue, 21 Nov 2006 10:24:59 +0100 [thread overview]
Message-ID: <200611211025.00412.roman.fietze@telemotive.de> (raw)
[-- Attachment #1: Type: text/plain, Size: 1358 bytes --]
Hello,
We've got the following problem:
MPC5200CBV400 L25R Rev 2
Using the DENX 2.4.25 with FEC and ATA DMA, BAPI 2.2, Prios are set to
FEC 6/5 and ATA 4/3 (RX/TX). This causes the FEC task to interrupt the
ATA task (default).
We try to load both tasks by transferring data from the ATA disk to
the Ethernet, e.g. by using FTP.
At the same time we write to some peripheral on the LocalPlus from
within a cyclic timer tasklet.
From time to time writing to the external peripheral fails, there is a
bus cycle, but we write some wrong data. This only happens if we have
FEC+ATA active at the same time.
Increasing the ATA priorities above the FEC priorities gives us FEC
errors, but the external peripheral works.
I'm sure others have similar problems. Did any of you change the
priority setting of these tasks to be able to run her/his hardware? Is
this related to the XLB pipelining problem as described in the errata
and previous mails in this list? Does anybody know if this problem is
fixed in newer revisions of the chip? Could be disabling pipelining
and waiting for TIP to go away help as well?
Thanks for any help.
Roman
--
Roman Fietze Telemotive AG Büro Mühlhausen
Breitwiesen 73347 Mühlhausen
Tel.: +49(0)7335/18493-45 http://www.telemotive.de
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next reply other threads:[~2006-11-21 9:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-21 9:24 Roman Fietze [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-12-09 10:04 LocalPlus or XLB-Arbiter Problems, DMA, MPC5200, DENX' 2.4.25 Jean-Michel CAPITAN
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=200611211025.00412.roman.fietze@telemotive.de \
--to=roman.fietze@telemotive.de \
--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