What is this ? (IDFGH-16696)

[savenlid]

Checklist

• [x] Checked the issue tracker for similar issues to ensure this is not a duplicate.
• [x] Provided a clear description of your suggestion.
• [x] Included any relevant context or examples.

Issue or Suggestion Description

WCH CH390H/D Ethernet Driver

Is this mac included physically inside the esp32-p4 ?

[savenlid]

ESP32-P4 internal MAC + IP101 external phy = my physical setup, custom PCBA, no devkit.

[kostaond]

Hi @savenlid, do you use Ethernet init component? If so, what version do you use?

[savenlid]

hi @kostaond

I do 1.0.0

I briefly used the 1.1.0 before it was "yanked" I think i used it a couple of hours at most.

[kostaond]

What IDF version do you use? I noticed v5.5.? from your logs but I'm not able to reproduce with release/v5.5 branch and common_examples/simple-ethernet . Try to run idf.py fullclean and then delete dependencies.lock. You can also try to delete sdkconfig but you will lost all your configuration.

[savenlid]

5.5.1

it is ethernet_init that has all the dependencies on a lot of ethernet chips. it demands the spi include file to compile them. in the end he will not link them in but demands to be able to compile them.

[kostaond]

The issue should have been fixed in ethernet_init v1.1.0. You can force use it, if you specifically define version: 1.1.0 in your manifest. v1.1.0 was yanked because it blocked v5.4.3 release but it was mostly a tooling problem rather than ethernet_init problem. Yanking was the easiest solution at that time.