Hi,

hmm... actually there is no network related stuff in my board specific code, only early init code. I assumed that - because I'm using a PPC405EP cpu - the networking should already be handled by U-Boot itself, e.g. in 'common/miiphyutil.c'. Am I wrong?

Here is, what the 'mii' command returns:

==> mii device MII devices: 'ppc_4xx_eth0' Current device: 'ppc_4xx_eth0' ==> mii info 0x0c PHY_PHYIDR2 @ 0xc = 0x1619 PHY_PHYIDR[1,2] @ 0xc = 0x00221619 PHY 0x0C: OUI = 0x0885, Model = 0x21, Rev = 0x09, 100baseT, FDX

Reto

-----Original Message----- From: Matthias Fuchs [mailto:matthias.fuchs@esd-electronics.com] Sent: Freitag, 16. Juni 2006 17:26 To: Stalder, Reto Cc: u-boot-users@lists.sourceforge.net Subject: Re: [heur] Re: [U-Boot-Users] PPC405EP ethernet problems

Hi,

is it possible that you use miiphy_read/write() somewhere in your

board

specific code? If so, in which function? Which board is it?

Can you post the code from your board setup that does any network related stuff?

Matthias

...

Stalder, Reto schrieb: Hi Matthias

Thank you for your quick response! I've tried out your suggestion. Unfortunately U-Boot stops while booting, without reaching the

command

...

prompt. The output is:

... U-Boot 1.1.4 (Jun 16 2006 - 16:45:43)

CPU: AMCC PowerPC 405EP Rev. B at 266.666 MHz (PLB=133, OPB=66,

EBC=33

...

MHz) I2C boot EEPROM disabled 16 kB I-Cache 16 kB D-Cache DRAM: 8 MB FLASH: 16 MB In: serial Out: serial Err: serial Net: ...

Enabled debug outputs (with defined DEBUG and ET_DEBUG constants) do not tell me anything more. What else could I try?

Best regards, Reto