[U-Boot-Users] PPC 440EP Ethernet question

[Jacob Simu]

Hello!

I've managed to port U-boot for our board with a 440EP processor. But I 
have problem to get the ethernet working. We use a Altima AC104Z PHY. I 
can read out all PHY register and they seem to be correct.
I have tried both RMII mode with the 405gp_enet.c and SMII mode with the 
440gx_enet.c implementation.

The PHY initiation looks fine. But when trying to ping or tftp I get no 
connection.

I can see that I enter the eneInt interrupt handler.

If anyone has a hint or tips on any diffrences on the 440EP regarding 
ethernet please let me know.

Below I send the serial output from a SMII run.

Best regards,

Jacob.


/*********************************************************/

U-Boot 1.1.2 (Jun 17 2005 - 16:09:33)

IBM PowerPC 440 GUNKNOWN (PVR=422218d3)
Board: IBM 440EP Board (OPVDR)
        VCO: 800 MHz
        CPU: 400 MHz
        PLB: 100 MHz
        OPB: 50 MHz
        EPB: 50 MHz
I2C:   ready
DRAM:  128 MB
Top of RAM usable for U-Boot at: 07fff000
Reserving 179k for U-Boot at: 07fd2000
Reserving 132k for malloc() at: 07fb1000
Reserving 144 Bytes for Board Info at: 07fb0f70
Reserving 48 Bytes for Global Data at: 07fb0f40
Stack Pointer at: 07fb0f28
New Stack Pointer is: 07fb0f28
Now running in RAM - U-Boot at: 07fd2000
FLASH: mfg_code 39
dev_code 79
FLASH ADDR: fff80000
FLASH MANUFACT: 1

FLASH DEVICEID: 4f
512 kB
PCI: CPC0_STRP1[PISE] not set.
PCI: Configuration aborted.
In:    serial
Out:   serial
Err:   serial
U-Boot relocated to 07fd2000
Net:   ppc_440x_eth0, ppc_440x_eth1
=> ping xxx.xxx.xxx.xxx
Trying ppc_440x_eth0
About preceeding transfer (eth0):
- Sent packet number 0
- Received packet number 0
- Handled packet number 0
devnum:0 ZMII_FER:c0000000
Waiting for PHY auto negotiation to complete.. done
TX_BUFF 0 @ 0x07fb24a8
RX_BUFF 0 @ 0x07ffce80
RX_BUFF 1 @ 0x07ffd480
RX_BUFF 2 @ 0x07ffda80
RX_BUFF 3 @ 0x07ffe080
Installing IRQ handlers //Own debug output
Using ppc_440x_eth0 device


###########################################This message has been scanned by F-Secure Anti-Virus for Microsoft 
Exchange.Formore information, connect to http://www.f-secure.com/