MII - RMII Link status detection
Hello,
i run u-boot on the Embedded Planet EP88xC evaluation board. Like the name indicates the board is equipped with a Freescale MPC885 processor.
On the board are two PHYs connected over MII. With u-boot i am able to see the link status of the PHYs with a slightly modified do_mii function.
My main question is, if anyone knows, if it is also possible to check the link status of the PHYs over RMII, because on our target the PHYs shall be connected over the reduced interface.
My second problem has nothing to deal with u-boot but with Linux:
We want to use the two network devices as one bonding device for high availability.So i configured and compiled the bonding module and the ifenslave command. Transfered it to the eval board and could successfully load (insmod) the module. The problem is that the bonding module do not receive a link down signal from the fec driver and so do not recognize a missing/broken cable or similar.
Best Regards,
Ingo
Signature · 15 lines
Ingo Swieter Tel: 05121/1760-821 Mail: ingo.swieter at brunel.de Brunel GmbH Bereich Communications Daimlerring 9 31135 Hildesheim Fax: 05121/1760-999 Internet: http://www.brunel.de Hauptsitz: Airport City, Hermann-K?hl-Str. 1 a, 28199 Bremen Amtsgericht Bremen HRB 16935 General Manager: Carsten Siebeneich
Ingo,
Quoted 9 lines · Ingo Swieter
Hello,
i run u-boot on the Embedded Planet EP88xC evaluation board. Like the name indicates the board is equipped with a Freescale MPC885 processor.
On the board are two PHYs connected over MII. With u-boot i am able to see the link status of the PHYs with a slightly modifieddo_miifunction.
Quoted 4 lines
My main question is, if anyone knows, if it is also possible to check the link status of the PHYs over RMII, because on our target the PHYs shall be connected over the reduced interface.
The differences between MII and RMII are in the data plane. As you mention, RMII uses a reduced set of DATA pins. As long as you still have the MDIO control plane connected (MDIO and MDC pins), you should be able to get link status.
Quoted 9 lines
My second problem has nothing to deal with u-boot but with Linux:
We want to use the two network devices as one bonding device for high availability.So i configured and compiled the bonding module and the ifenslave command. Transfered it to the eval board and could successfully load (insmod) the module. The problem is that the bonding module do not receive a link down signal from the fec driver and so do not recognize a missing/broken cable or similar.
No experience here. Sorry.
regards,
Ben
Quoted 11 lines · Ben Warren
Ingo,
Quoted 2 lines · Ingo Swieter
[.. difference MII - RMII ..]
The differences between MII and RMII are in the data plane. As you mention, RMII uses a reduced set of DATA pins. As long as you still have the MDIO control plane connected (MDIO and MDC pins), you should be able to get link status.
Thank you for the information, that was what i hoped and thought.
Best Regards,
Ingo
Signature · 15 lines
Ingo Swieter Tel: 05121/1760-821 Mail: ingo.swieter at brunel.de Brunel GmbH Bereich Communications Daimlerring 9 31135 Hildesheim Fax: 05121/1760-999 Internet: http://www.brunel.de Hauptsitz: Airport City, Hermann-K?hl-Str. 1 a, 28199 Bremen Amtsgericht Bremen HRB 16935 General Manager: Carsten Siebeneich
Hi,
u-boot-users-bounces at lists.sourceforge.net wrote on :
Quoted 8 lines
My second problem has nothing to deal with u-boot but with Linux:
We want to use the two network devices as one bonding device for high availability.So i configured and compiled the bonding module and the ifenslave command. Transfered it to the eval board and could successfully load (insmod) the module. The problem is that the bonding module do not receive a link down signal from the fec driver and so do not recognize a missing/broken cable or similar.
Does your fec driver support link status changes? Are there kernel messages generated, if you plug/unplug your ethernet cable? If not, the driver maybe does not support the link status change interrupt. Or the PHY interrupt line is not connected with the cpu on your hardware?
Regards,
Martin Krause
--
TQ-Systems GmbH
Muehlstrasse 2, Gut Delling, D-82229 Seefeld
Amtsgericht Muenchen, HRB 105 018, UST-IdNr. DE 811 607 913
Geschaeftsfuehrer: Dipl.-Ing. (FH) Detlef Schneider, Dipl.-Ing. (FH) Ruediger Stahl
http://www.tq-group.com