Hi,
we have a custom board designed based on LX2160ARDB with same 10G PHY's connected but with the following hardware changes.
"IRQ2 and IRQ3 on CPU are not going to 10G_PHY_1 and 10G_PHY_2.Instead IRQ_10G_PHY1_B goes to IRQ7 and IRQ_10G_PHY2_B to IRQ2"
Please find the image for your reference.
we are getting 'PHY timed out error' while booting.
network is not connected in both u-boot and kernel.
We could not find Ethernet pin muxing in DTB file(fsl-lx2160a-rdb.dts,fsl-lx2160a.dtsi).please help us where to make changes for PHY device detection.
Thnaks,
Bhavani.
I do not see any routine in Linux, at least in NXP-maintained kernel code, that could
output the exact message you mentioned. You either quoted it imprecisely or
it is generated by a non-NXP code. In general, PHY-related errors may indicate
two situations:
1. Link setup timeout. The driver is able to communicate with the PHY but the
PHY can't setup the link to the far end. This is a PHY-specific problem,
consult at the PHY vendor/documentation.
2. The MAC driver can't read the PHY status via the management interface. Try
talking to your PHYs in u-Boot using mdio command:
https://community.nxp.com/t5/QorIQ/help-on-MDIO-commands-in-u-boot/m-p/318550
If the PHYs fail to respond, check MDIO/MDC connection.
If the PHYs do respond, but Linux fails to bring them up, make sure the
connection between the PHYs and MACs is properly described in the Device Tree:
https://source.codeaurora.org/external/qoriq/qoriq-components/linux/tree/Documentation/devicetree/bi...
https://source.codeaurora.org/external/qoriq/qoriq-components/linux/tree/arch/arm64/boot/dts/freesca...
Hope this helps,
Platon