From: "Mark Chambers" <markc@mail•com>
To: "Stefan Nickl" <Stefan.Nickl@kontron•com>
Cc: linuxppc-embedded@ozlabs•org
Subject: Re: All-ones problem with FCC1 on MPC8541
Date: Thu, 28 Oct 2004 14:02:46 -0400 [thread overview]
Message-ID: <006301c4bd18$59cfc570$0301a8c0@chuck2> (raw)
In-Reply-To: 1098984003.11434.12.camel@lucy.pep-kaufbeuren.de
> I checked port configuration and clock routing registers in
> cpm2_io/fcc_enet.c again and again, but all I get in and out is ones.
>
> The packet sizes I receive look reasonable, but the buffers are
> filled only with 0xff. The same goes for sending, the contents
> of the buffers are OK (dhcp discover...), but when capturing
> the output on the other side with ethereal, the packet is again
> all 0xff.
>
> We just discovered that apparently preamble, frame delimiter and FCS go
> out over the MII (at least TxD[0:3] change state), so I don't suspect a
> hardware bug.
>
I would guess the problem is at the DMA level, that the FCC is
reading/writing
ffs to/from memory for some reason. The preamble and FCS come from the
FCC itself, not memory, so that's why you see them. I'd guess some kind
of mismatch with the kind of cycles generated by the FCC DMA and the
memory controllers.
Mark Chambers
next prev parent reply other threads:[~2004-10-28 18:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-28 17:20 All-ones problem with FCC1 on MPC8541 Stefan Nickl
2004-10-28 18:02 ` Mark Chambers [this message]
2004-10-29 12:50 ` Stefan Nickl
2004-10-29 13:29 ` Mark Chambers
2004-10-29 14:22 ` Kumar Gala
2004-10-29 14:47 ` Stefan Nickl
2004-11-18 10:13 ` Stefan Nickl
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='006301c4bd18$59cfc570$0301a8c0@chuck2' \
--to=markc@mail$(echo .)com \
--cc=Stefan.Nickl@kontron$(echo .)com \
--cc=linuxppc-embedded@ozlabs$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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