If I understand your use case correctly, it is of course possible. It's the basic use case. W5500 Datasheet specifies: W5500 does not support auto-MDIX feature. Thus, user should use straight-through cables to connect to other switches or routers and crossover cables to connect to devices such as se...

It's strange there are no W5500 errors printed in the log....

Great to see the issue has been fixed!

You were really close to the solution based on your detailed issue description. Hence it implies to me there must be something wrong with documentation. Would you have any suggestion how it could be improved? What would you help during your investigation?

We've already observed that high traffic on Ethernet can also affect the SPI DMA transactions. The same seems to apply for I2S. Try to reduce `dma_burst_len` when initializing Ethernet with `eth_esp32_emac_config_t` config structure.

Try to check https://github.com/espressif/esp-idf/bl ... nect.c#L25

Just recall me, the issue is the W5500 gets completely unresponsive? If so, it's pretty serious and you need to HW restart it. If you have reset pin already mapped to PHY instance, "just" de-initialize the Ethernet interface and its Netif as demonstrated at https://github.com/espressif/esp-idf/blob/...

The SPI Ethernet is much slower. You can achieve more than 90 mbps for Tx/Rx UDP with internal EMAC. With SPI Ethernet is around 17 mbps.

Please share more information about your setup, e.g. IDF version, board you use (custom or modules connected via wires), etc. Are you able to reproduce the issue with Ethernet basic example?

Do you use some devboard or your custom board? Is PHY address correctly set?

Might be HW issue with your board. Could you please try to debug using https://github.com/espressif/esp-eth-dr ... phy_tester ? Ideally, run the pytest script. However, just note it was tested on Linux so far so you need to be on Linux.

Once you done, let me know the results.