All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bill Richardson <william.richardson@sun.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] help for FCC1 ethernet with mpc8248 from embedded planet?
Date: Wed, 08 Sep 2004 11:49:35 -0700	[thread overview]
Message-ID: <413F543F.4000402@sun.com> (raw)

I've been trying to port U-Boot to an 8248-based board from Embedded Planet
(http://www.embeddedplanet.com/products/ep8248.asp). I started with the
MPC8260ADS configuration and made a new board, as suggested in the README. So
far, the SMC1 serial port works, the DRAM controller works, flash works, I can
get to the U-Boot prompt and issue commands, etc.

However, when I try to use the FCC1 ethernet, problems occur. For example:

=> ping 192.168.2.2
Trying FCC1 ETHERNET
Using FCC1 ETHERNET device
sending ARP for c0a80202
ARP broadcast 1
ARP broadcast 2
ping failed; host 192.168.2.2 is not alive
=>


192.168.2.2 is a valid IP, and is alive. Sniffing with tcpdump shows the following:

10:46:58.101158 Broadcast > Broadcast, ethertype Unknown (0xffff), length 60:
         0x0000:  ffff ffff ffff ffff ffff ffff ffff ffff  ................
         0x0010:  ffff ffff ffff ffff ffff ffff ffff ffff  ................
         0x0020:  ffff ffff ffff ffff ffff ffff ffff       ..............
10:47:03.069813 Broadcast > Broadcast, ethertype Unknown (0xffff), length 60:
         0x0000:  ffff ffff ffff ffff ffff ffff ffff ffff  ................
         0x0010:  ffff ffff ffff ffff ffff ffff ffff ffff  ................
         0x0020:  ffff ffff ffff ffff ffff ffff ffff       ..............

The PHY is a Level One (Intel) LXT971A. I can query it with U-Boot's mii
commands, and it looks correct - it autonegotiates, recognizes the link, etc.
The fact that I see the correct packet length and it isn't dropped suggests
that the phy is at least sort-of working.


The ARP packet that's passed to fec_send() (in cpu/mpc8260/ether_fcc.c) is correct:

(gdb) print packet
$9 = (void *) 0xffd2e0
(gdb) x/42xb packet
0xffd2e0:	0xff	0xff	0xff	0xff	0xff	0xff	0x02	0x00
0xffd2e8:	0x00	0x00	0x00	0x02	0x08	0x06	0x00	0x01
0xffd2f0:	0x08	0x00	0x06	0x04	0x00	0x01	0x02	0x00
0xffd2f8:	0x00	0x00	0x00	0x02	0xc0	0xa8	0x02	0x05
0xffd300:	0x00	0x00	0x00	0x00	0x00	0x00	0xc0	0xa8
0xffd308:	0x02	0x02
(gdb)



I'm very new to the whole powerpc/embedded world. Is it a correct assumption 
that the FCC driver in mpc8260/ether_fcc.c will work for the 8248?


Any hints or suggestions will be much appreciated.


Thanks.


Bill
-- 
Art for Art's Sake
Engineering for Money

                 reply	other threads:[~2004-09-08 18:49 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=413F543F.4000402@sun.com \
    --to=william.richardson@sun.com \
    --cc=u-boot@lists.denx.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.