[U-Boot-Users] MPC83xx Ethernet bug

[Ben Warren]

Joakim Tjernlund wrote:
> Ping?
>
> Jocke 
>
>   
ACK. Another reason it would be nice to have a PHY library that handles 
fixed connections. Stay tuned...
>> -----Original Message-----
>> From: u-boot-users-bounces at lists.sourceforge.net 
>> [mailto:u-boot-users-bounces at lists.sourceforge.net] On Behalf 
>> Of Joakim Tjernlund
>> Sent: den 20 november 2007 08:52
>> To: Liu Dave
>> Cc: U-BOOT
>> Subject: Re: [U-Boot-Users] MPC83xx Ethernet bug
>>
>> On Tue, 2007-11-20 at 13:29 +0800, Liu Dave wrote:
>>     
>>> Hello Joakim,
>>>
>>> I did the test u-boot-1.3.0 wolfgang just released on mpc832xemds
>>> board, I did not see the issue that you said.
>>>       
>> But you did, see below
>>
>>     
>>> U-Boot 1.3.0 (Nov 20 2007 - 13:30:24) MPC83XX
>>>
>>> Reset Status:
>>>
>>> CPU:   e300c2, MPC8323E, Rev: 10 at 264 MHz, CSB:  132 MHz
>>> Board: Freescale MPC832XEMDS
>>> I2C:   ready
>>> DRAM:  128 MB
>>> FLASH: 16 MB
>>> In:    serial
>>> Out:   serial
>>> Err:   serial
>>> Net:   UEC: PHY is Davicom DM9161A (181b8a0)
>>> FSL UEC0: Full Duplex
>>> FSL UEC0: Speed 100BT
>>> FSL UEC0: Link is up
>>> UEC: PHY is Davicom DM9161A (181b8a0)
>>> FSL UEC0, FSL UEC1
>>>       
>> Here it is, the network i/f is initialized without any 
>> network activity.
>> This adds several extra seconds before prompt or boot as the
>> mdio code has big delays in it.
>>
>>     
>>> Hit any key to stop autoboot:  0
>>> => ping 10.193.20.133
>>>       
>> I should have been here as this is the first network operation.
>>
>>     
>>> Using FSL UEC0 device
>>> host 10.193.20.133 is alive
>>> =>
>>>
>>> Thanks,
>>> Dave
>>>
>>>       
>>>> -----Original Message-----
>>>> From: u-boot-users-bounces at lists.sourceforge.net 
>>>> [mailto:u-boot-users-bounces at lists.sourceforge.net] On Behalf 
>>>> Of Joakim Tjernlund
>>>> Sent: 2007?11?19? 11:51 PM
>>>> To: U-BOOT
>>>> Subject: [U-Boot-Users] MPC83xx Ethernet bug
>>>>
>>>> Just tried to move my 83xx based board to latest u-boot and
>>>> noticed an old problem. u-boot tries to bring up the
>>>> ethernet at startup, not the first time it is used:
>>>>
>>>> U-Boot 1.3.0-rc3-g992742a5-dirty (Nov 19 2007 - 16:45:18) 
>>>>
>>>> Reset Status: External/Internal Soft, External/Internal Hard
>>>>
>>>> CPU:   e300c2, MPC8323E, Rev: 10 at 266.664 MHz, CSB:  133 MHz
>>>> Board: Transmode CU
>>>> I2C reset sequence.
>>>> I2C:   ready
>>>> DRAM:  
>>>>    DDR RAM: 256 MB
>>>> FLASH: 128 MB
>>>> In:    serial
>>>> Out:   serial
>>>> Err:   serial
>>>> Net:   read wrong value : mii_id 3,mii_reg 2, base e0102320
>>>> read wrong value : mii_id 3,mii_reg 3, base e0102320
>>>> UEC: PHY is Generic MII (ffffffff)
>>>> read wrong value : mii_id 3,mii_reg 1, base e0102320
>>>> read wrong value : mii_id 3,mii_reg 5, base e0102320
>>>> FSL UEC0: Full Duplex
>>>> FSL UEC0: Speed 100BT
>>>> FSL UEC0: Link is up
>>>> read wrong value : mii_id 4,mii_reg 2, base e0103320
>>>> read wrong value : mii_id 4,mii_reg 3, base e0103320
>>>> UEC: PHY is Generic MII (ffffffff)
>>>> read wrong value : mii_id 4,mii_reg 1, base e0103320
>>>> read wrong value : mii_id 4,mii_reg 1, base e0103320
>>>> read wrong value : mii_id 4,mii_reg 5, base e0103320
>>>> FSL UEC1: Full Duplex
>>>> FSL UEC1: Speed 100BT
>>>> FSL UEC1: Link is up
>>>> FSL UEC0, FSL UEC1
>>>> read wrong value : mii_id 3,mii_reg 1, base e0102320
>>>>
>>>> => 
>>>>         
I don't know why the calls to init_phy() and phy_change() are in 
uec_initialize() instead of uec_init(). Moving them should at least 
prevent this stuff at boot-up.

regards,
Ben