P4080 Random Communication Problem

[ali_erceylan]

HI,
We are developing a powerpc which contains P4080, 2x KSZ9031 phyical and KSZ8999 ethernet switch,

currently we see two problem;

1: when %20 of the start ups we see this error on u-boot console:"couldn't get PHY for P4080DS_MDIO0 addr0 failed to connect". but not all cards,only a few of them.

2:There is a second device which is communicating with P4080 and PC over KSZ8999 but sometimes we can't see as online second device and we can ping to P4080 but when we use exernal switch, there is no problem.

and also there is a warning which is :"Serdes bank1 expect refence clock 100 Mhz but actual is 125 Mhz " is this couse any problem?

[bpe]

Both the PHY problem and the warning about SerDes clock appear
most likely because you did not remove or improperly modified the board
initialization code specific to NXP P4080DS development system.
P4080DS has a CPLD that implements additional logic to monitor
clocks and warn if they don't match RCW settings. Your board most likely
doesn't have it, hence the message 'SERDES bank X expects reference
clock...'.

The message about not being able to get the PHY is generated when
u-Boot is unable to identify the model of the PHY connected the MDIO.
This can happen either because  the PHY does not respond to MDIO cycles
or phy_find_by_mask() was called with invalid parameters. Note that
P4080DS has a multiplexer on MDIO bus which is typically not necessary
on a production board.

Suggestions:

1. Review your board initialization code. If you copied from board/freescale/corenet_ds/,
   eliminate all code that: (a) accesses CPLD features not implemented
   on your board; (b)manipulates MDIO multiplexer. Make sure you correctly
   initialize mdio and phy-related structures, take initialization for a board
   that has no MDIO multiplexer as a reference (P2041RDB, P1023RDS).
   
2. Verify MDIO operation by initiating transactions manually. Make sure your
   PHYs respond at the addresses you expect. See DPAARM, Sections 3.6.3.4.6
   through 3.6.3.4.11.
   
   
As of the Ethernet switch problem, consult at it's manufacturer for
troubleshooting recommendations.