[U-Boot-Users] Re: IBM 440GX eval name

[U-Boot-Users] Re: IBM 440GX eval name

[Jarrett Redd]

I also have a 440GX eval board from IBM.  I tried the
ocotea config and it boots up just fine.  However, I
get a message about an I2C read error.  Is this
normal?  In addition, I can't seem to bring up the
network.  However, this is my first shot with u-boot
so probably I am doing something stupid.  The docs I
have found so far are pretty good, but relatively
unclear on the network setup.  Is there something I
have to do besides setting some environment variables?
 Or is there some doc that I missed?  Thanks.

-tc

----------------------------------------------------
IBM PowerPC 440 GX Rev. B
Board: IBM 440GX Evaluation Board
        VCO: 1066 MHz
        CPU: 533 MHz
        PLB: 152 MHz
        OPB: 76 MHz
        EPB: 76 MHz
I2C:   ready
DRAM:  I2c read: failed 4
I2c read: failed 4
256 MB
FLASH:  5 MB
PCI:   Bus Dev VenId DevId Class Int
In:    serial
Out:   serial
Err:   serial
KGDB:  kgdb ready
ready
Net:   ppc_440x_eth0
BEDBUG:ready

=> printenv
bootargs=root=/dev/hda1 
bootcmd=bootm ffc00000
baudrate=115200
loads_echo=1
ethaddr=<macaddr>
ipaddr=<ipaddr>
netmask=<netmask>
serverip=<servip>
gatewayip=<gwip>
hostname=<hostname>
netdev=eth0
stdin=serial
stdout=serial
stderr=serial

Environment size: 278/4092 bytes

=> 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


__________________________________
Do you Yahoo!?
Yahoo! Small Business $15K Web Design Giveaway 
http://promotions.yahoo.com/design_giveaway/

[U-Boot-Users] Re: IBM 440GX eval name

[Travis Sawyer]

On Tue, 2004-04-06 at 22:17, Jarrett Redd wrote:
> I also have a 440GX eval board from IBM.  I tried the
> ocotea config and it boots up just fine.  

Great!  Good to see some mileage from my port!
> However, I
> get a message about an I2C read error.  Is this
> normal?

Yes, and no :)  Normal if you have only one (1) DIMM populated.  If
there are two (2) DIMMs you _*shouldn't*_ see that message.  I don't
have another DIMM handy, so I couldn't test that.  If the message
bothers you that much, you can remove the second SPD_EEPROM address from
the config (do this locally though).

>   In addition, I can't seem to bring up the
> network.  
See below...

> ----------------------------------------------------
> IBM PowerPC 440 GX Rev. B
> Board: IBM 440GX Evaluation Board
>         VCO: 1066 MHz
>         CPU: 533 MHz
>         PLB: 152 MHz
>         OPB: 76 MHz
>         EPB: 76 MHz
> I2C:   ready
> DRAM:  I2c read: failed 4
> I2c read: failed 4
> 256 MB
Looks like you have one DIMM installed.

> FLASH:  5 MB
> PCI:   Bus Dev VenId DevId Class Int
> In:    serial
> Out:   serial
> Err:   serial
> KGDB:  kgdb ready
> ready
> Net:   ppc_440x_eth0
> BEDBUG:ready
> 
> => printenv
> bootargs=root=/dev/hda1 
> bootcmd=bootm ffc00000
> baudrate=115200
> loads_echo=1
> 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

where the 'xx', 'yy', etc are the ethernet mac addresses for your
board.  (Flip it over, they are on stickers on the bottom of the board).


> ipaddr=<ipaddr>
You'll want to set the others as appropriate also...

> netmask=<netmask>
> serverip=<servip>
> gatewayip=<gwip>
> hostname=<hostname>
> netdev=eth0
> stdin=serial
> stdout=serial
> stderr=serial
> 
> Environment size: 278/4092 bytes
> 
> => 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.Good luck,

Travis

[U-Boot-Users] Re: IBM 440GX eval name

[Jarrett Redd]

--- 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/

[U-Boot-Users] Re: IBM 440GX eval name

[Travis Sawyer]

On Wed, 2004-04-07 at 14:17, Jarrett Redd wrote:
> --- 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.
> 
Is your dimm PC3200 DDR?  Speeds match the current dimm?
(It does have a spd eeprom right?)


> An interesting thing to note here is, the 'ethaddr'
> value was automatically set somehow (is there auto
> detection support here?)
Hard coded in the config.  Uses MY mac addresses.

>   So anyway I just entered the ones on the
> stickers.
> 
u-boot has the mac addresses for my board in the config file...
README.ocotea says (I think) change it for your own board.

> > 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.

Normal (autonegotiation that is).  U-boot only init's the net devices
when it needs them.

You won't be able to ping loopback or yourself, as u-boot is single
threaded, only initiates net traffic, and listens for replies.

> 
> 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.
> 
Ensure your switch settings are the following:
U80: 2,3, & 6 on, all others off.

> 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.  :-)
> 
The fpga handling code could use some sprucing up...


If there are any more questions we should probably take this offline.

-travis