From: Jarrett Redd <coin068_redd@yahoo.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Re: IBM 440GX eval name
Date: Wed, 7 Apr 2004 11:17:05 -0700 (PDT) [thread overview]
Message-ID: <20040407181705.32787.qmail@web21510.mail.yahoo.com> (raw)
In-Reply-To: <1081342892.5520.10.camel@pavement.sandburst.com>
--- Travis Sawyer <tsawyer+u-boot@sandburst.com>
wrote:
> I don't have another DIMM handy, so I couldn't
> test that.
Ok, just out of curiousity, I found another DIMM to
try and test, but with 2 it hangs at the "DRAM: "
message.
> > In addition, I can't seem to bring up the
> > network.
> See below...
>
> > ethaddr=<macaddr>
> There's your problem. Do the following:
> setenv ethaddr XX:XX:XX:XX:XX:XX
> setenv eth1addr YY:YY:YY:YY:YY:YY
> setenv eth2addr ZZ:ZZ:ZZ:ZZ:ZZ:ZZ
> setenv eth3addr AA:AA:AA:AA:AA:AA
>
Well, the '<macaddr>' in the above output was edited
by me for the email purposes. Sorry about that. I
have the actual mac addr in there but was masking it
out since this list is archived on the internet.
Similarly for the other masked settings.
An interesting thing to note here is, the 'ethaddr'
value was automatically set somehow (is there auto
detection support here?), but it was incorrect in the
final byte, at least compared to any of the 4
stickers. I rebooted under PIBS and unfortunately got
4 more different mac addresses that also do not match
the stickers in the last 2 bytes. So, they all seem
to be valid IBM mac values for this board, but I'm not
really certain which mac addresses are really mine for
this board. So anyway I just entered the ones on the
stickers.
> > => ping <address>
> > Waiting for PHY auto negotiation to complete..
> > done
> > ENET Speed is 100 Mbps - FULL duplex connection
> > ping failed; host <address> is not alive
> >
> Hmmm... since your setup is using EMAC0, ensure
> you have the cable in port 0. Also, the only enet
> group supported is group 4, so ensure you have the
> jumpers set that way. (J79, J80, J29, J31, J76,
> J81) are all 1-8 and 3-6.
>
Yes, I checked and they are correct. Still no joy.
Other ideas? The network comes up just fine under
PIBS with the same settings. Also, is loopback
supported? I cannot ping loopback or the board's own
ip address either. In addition, every time I try to
ping, it always waits for auto negotiation. That
doesn't seem normal.
Another thing I noticed that doesn't seem normal is
that the board seems to hang on the 'reset' command or
after using the reset button on the board.
Incidentally, just for fun, I tried burning the image
into the 4MB alternate flash and booting from that.
It works just fine, other than flash detection getting
a bit confused. :-)
-tc
__________________________________
Do you Yahoo!?
Yahoo! Small Business $15K Web Design Giveaway
http://promotions.yahoo.com/design_giveaway/
next prev parent reply other threads:[~2004-04-07 18:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-07 2:17 [U-Boot-Users] Re: IBM 440GX eval name Jarrett Redd
2004-04-07 13:01 ` Travis Sawyer
2004-04-07 18:17 ` Jarrett Redd [this message]
2004-04-07 18:42 ` Travis Sawyer
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=20040407181705.32787.qmail@web21510.mail.yahoo.com \
--to=coin068_redd@yahoo.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.