W6100 (IDFGH-5966)

[MadsHHLund]

Driver for w6100

I have had big problems with the stability of w5500, getting hot and unstable, and have been focusing og then w6100 chip.

I have modified then esp_eth_mac_w5500, to esp_eth_mac_w6100, and esp_eth_phy_w5500 to esp_eth_phy_w6100.

I have testet it, and in my application it's working, but I would be happy, if someone would test on, and perhaps make it an integrated part of EPS-IDF version x.x

w6100.zip

[0xjakob]

@MadnessASAP Could you please create a pull request for this?

[MadnessASAP]

As much as I'd love to help I believe you have the wrong guy. However @MadsHHLund may be willing to help.

[david-cermak]

Hi @MadnessASAP

As we try to make ESP-IDF more compact, less monolithic and mainly related to Espressif chip-sets only, we generally advice supporting any other device which doesn't directly depend on the SoC itself as an external component. (this is mainly true for all standard on-board components which communicate over I2C, SPI or similar, defined in our BSP), but also true for SPI Ethernets. It's becoming very hard for ESP-IDF to support such devices directly in IDF, due to maintenance and testing effort.

That's why I'd suggest creating an external component. It should be soon possible to use IDF component manager for managing such components and it will become very easy to download and deploy these component in user projects.

I have created a demo repository to show how easy it is to implement an IDF component: https://github.com/david-cermak/MadsHHLunds_esp_idf_eth_w6100
Please note this commit showing the transition from your sources to the actual component.

Note that it is possible to add such component to your project easily even without the component manager. You simply add this line to your project makefile:

set(EXTRA_COMPONENT_DIRS path_to_MadsHHLunds_esp_idf_eth_w6100)

in a similar way as it's done in some of our examples:

esp-idf/examples/protocols/mdns/CMakeLists.txt

Line 7 in 4e03a9c

set(EXTRA_COMPONENT_DIRS $ENV{IDF_PATH}/examples/common_components/protocol_examples_common)

[david-cermak]

@MadsHHLund Any comment from you about the suggested approach? This driver won't be an integral part of IDF, but could be made an external component.

[MadsHHLund]

I think its at good solution.

[david-cermak]

@MadsHHLund Thanks for the feedback! Could you close this issue then?