STM32MP157C-DK2 Ethernet network is not working

[JSomi]

We brought stm32Mp157C-DK2 board for our prototype testing. I can able to work on the A7 and M4 also ran examples. After 3 days of our work the Ethernet communication is not working. The LED's on the connector is not glowing. I check in Linux terminal with dmesg there is no controller detection . When I reboot the system and check the initial dmesg the output is like this on my linux host sytem using minicom:

root@stm32mp1:~# dmesg | grep eth

[  0.000000] psci: probing for conduit method from DT.

[  1.575436] stm32-dwmac 5800a000.ethernet: PTP uses main clock

[  1.579819] stm32-dwmac 5800a000.ethernet: no reset control found

[  1.586023] stm32-dwmac 5800a000.ethernet: No phy clock provided...

[  1.601232] stm32-dwmac 5800a000.ethernet: User ID: 0x40, Synopsys ID: 0x42

[  1.606799] stm32-dwmac 5800a000.ethernet:  DWMAC4/5

[  1.611707] stm32-dwmac 5800a000.ethernet: DMA HW capability register supported

[  1.619050] stm32-dwmac 5800a000.ethernet: RX Checksum Offload Engine supported

[  1.626354] stm32-dwmac 5800a000.ethernet: TX Checksum insertion supported

[  1.633237] stm32-dwmac 5800a000.ethernet: Wake-Up On Lan supported

[  1.639476] stm32-dwmac 5800a000.ethernet: TSO supported

[  1.644814] stm32-dwmac 5800a000.ethernet: Enable RX Mitigation via HW Watchdog Timer

[  1.652625] stm32-dwmac 5800a000.ethernet: TSO feature enabled

[  1.692950] usbcore: registered new interface driver cdc_ether

[  2.186587] optee: probing for conduit method from DT.

[  8.406969] stm32-dwmac 5800a000.ethernet eth0: Could not attach to PHY

[  8.441252] stm32-dwmac 5800a000.ethernet eth0: stmmac_open: Cannot attach to PHY (error: -19)

[  9.402998] using random self ethernet address

[  9.404040] using random host ethernet address

I tried of changing cable and checked switch everything is ok. Please suggest how to debug in this case to resolve the issue.

[PatrickF]

Hello,

did you use started package or your own SW?

Maybe it is a good idea to Flash SD-Card with latest STM32MP15 ecosystem release v1.1.0

See https://wiki.st.com/stm32mpu/wiki/Getting_started/STM32MP1_boards/STM32MP157C-DK2/Let%27s_start/Populate_the_target_and_boot_the_image

If still not working, I suspect a faulty board.

Note that Ethernet LEDs behavior is the PHY (RTL8211F) default one:

Here is my log, connected to a 100M network:

root@stm32mp1:~# dmesg | grep eth

[   0.000000] psci: probing for conduit method from DT.

[   1.521047] stm32-dwmac 5800a000.ethernet: PTP uses main clock

[   1.525439] stm32-dwmac 5800a000.ethernet: no reset control found

[   1.531693] stm32-dwmac 5800a000.ethernet: No phy clock provided...

[   1.548969] stm32-dwmac 5800a000.ethernet: User ID: 0x40, Synopsys ID: 0x42

[   1.554493] stm32-dwmac 5800a000.ethernet:  DWMAC4/5

[   1.559548] stm32-dwmac 5800a000.ethernet: DMA HW capability register supported

[   1.566776] stm32-dwmac 5800a000.ethernet: RX Checksum Offload Engine supported

[   1.574129] stm32-dwmac 5800a000.ethernet: TX Checksum insertion supported

[   1.581016] stm32-dwmac 5800a000.ethernet: Wake-Up On Lan supported

[   1.587283] stm32-dwmac 5800a000.ethernet: TSO supported

[   1.592580] stm32-dwmac 5800a000.ethernet: Enable RX Mitigation via HW Watchdog Timer

[   1.600449] stm32-dwmac 5800a000.ethernet: TSO feature enabled

[   1.635628] usbcore: registered new interface driver cdc_ether

[   2.133548] optee: probing for conduit method from DT.

[   8.637902] stm32-dwmac 5800a000.ethernet eth0: No Safety Features support found

[   8.698158] stm32-dwmac 5800a000.ethernet eth0: IEEE 1588-2008 Advanced Timestamp supported

[   8.760343] stm32-dwmac 5800a000.ethernet eth0: registered PTP clock

[   8.792495] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready

[   9.604900] using random self ethernet address

[   9.623627] using random host ethernet address

[  11.938258] stm32-dwmac 5800a000.ethernet eth0: Link is Up - 100Mbps/Full - flow control off

[  11.945364] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready

[JSomi]

Thanks Patrick for your reply.

I used starter package and flashed. Starting the board is working fine I can able to connect to network. But after three days of working on the board, when I connect my Ethernet cable none of the LED's are blinking and no communication. Again I re-flashed the starter package but the issue remains unsolved.

How come Ethernet damages if its working already? I checked with multi-meter all the voltages and connections on the Ethernet controller and connector. But nothing seems to be faulty.

[PatrickF]

I don't know how it could occur, could be a board manufacturing issue (weak solder joint) or a short circuit somewhere during your tests.

As far as I know, we did not experience any reliability issues with this board. I think you were unlucky.

I suggest you to ask your reseller if he could manage a product exchange.