After a while, Hello to all in Toradex .
I’d like to consult strange behavior of Colibri imx6ull we use in our new product carrier board. To be more specific, Colibri imx6ull 512MB IT without Wifi + Yocto 6.8.
I found similar topics here, but with different possible solution.
On few modules we found problem on PHY startup, Micrel KSZ8041.
Sometimes, usually on cold start of our carrier board, PHY is
1] not available
dmesg | grep fec
[ 002.817703] fec 20b4000.ethernet eth0: registered PHC device 0
[ 0020.391388] fec 20b4000.ethernet eth0: Unable to connect to phy
2] available, but eth0 does not start
PHY is found Ok
[21.473686] Micrel KSZ8041 20b4000.ethernet-1:02: attached PHY driver (mii_bus:phy_addr=20b4000.ethernet-1:02, irq=POLL)
But it never starts, even we are able to test it over ethtool or phytool.
While on Toradex Colibri evaluation it work without problem all the time, we found out warning in Colibri carrier board schematics of Ethernet part about ETH_LINK and ETH_SPEED signals.
As comes out, those signals on our board were not connected. After connection to proper load ( LED + R ), PHY starts to behave correctly.
So, Id like to ask
1] Is it possible to confirm such behavior, when we did not put proper load on LED outputs ? If so, fix is on our side in BSP, we found problem and that’s good.
2] Is it possible to do any change in configuration of device tree ( or other software change ) to fix this issue ?
I presume LED signals comes from PHY KSZ8041 and not from imx6ull itself, so its not – but I have to ask
Thanks for any response or advice, it will be handy for others too.
Have a nice day.