linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Alex BASTOS <alebas@televes.com>
To: linuxppc-embedded@ozlabs.org
Subject: CPM2 reports CRC errors in FCC2 for good packets
Date: Tue, 28 Jun 2005 15:59:09 +0200	[thread overview]
Message-ID: <1119967149.42c157ad7a74e@webmail.televes.com:443> (raw)


Hi guys,

I am working with a MPC8248 custom board. On this, we have mixed
interfaces, with Ethernet on FCC1 working in Full Duplex 100Mbps,
and MII-generic on FCC2, working in Half-Duplex 100Mbps.

On FCC2, CPM2 reports CRC error for each received packet, but
ignoring it, packets arrive correctly. We have tested it with
a known packet (ARP broadcast) through both interfaces, and this
packet reports and CRC error on FCC2, but not in FCC1 ... but the
received packet is the same in both cases !!! (taken from buffer
pointed by RxBD):

# FCC2 : Generic-mii Half Duplex
# ARP Broadcast Packet received on board!!!
FF FF FF FF FF FF 00 10 5A A7 8A F3 08 06 00 01 08 00 06 04 00 01
00 10 5A A7 8A F3 0A 00 00 03 00 00 00 00 00 00 0A 00 00 01 00 00
00 00 00 00 00 00 00 00 00 0000 00 00 00 00 00 E7 E0 E9 46
... len: 64
CBD_SC = 1C84 (crc_error)


# FCC1 : ETHERNET Full Duplex
# ARP Broadcast Packet received on board!!!
FF FF FF FF FF FF 00 10 5A A7 8A F3 08 06 00 01 08 00 06 04 00 01
00 10 5A A7 8A F3 0A 00 00 03 00 00 00 00 00 00 0A 00 00 01 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 E7 E0 E9 46
... len: 64


So, packet is received ok, but CRC error is reported.
Any idea? May it be a Hardware problem, even if packets are received
OK by the driver?


Thanks,

Alexandre BASTOS

             reply	other threads:[~2005-06-28 12:50 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-28 13:59 Alex BASTOS [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-07-08  6:37 CPM2 reports CRC errors in FCC2 for good packets Bastos Fernandez Alexandre

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='1119967149.42c157ad7a74e@webmail.televes.com:443' \
    --to=alebas@televes.com \
    --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).