Thanks for the contribution. The addition of KSZ8081 is good. But I don't think the new board definition is needed, instead one can use the GENERIC_UNICORE board, which was just added via #8365.

The support for KSZ8081 was merged in 30db33d

I can confirm that using the ESP32 GENERIC nightly builds (tested with v1.20.0-379-ga18d62e06) works as expected with the KSZ8081 on the Espoir board.

The docs from Connaxio work unmodified to bring up the Ethernet, i.e. this is all that is needed:

from machine import Pin
import network

lan=network.LAN(mdc=Pin(32),mdio=Pin(33),power=None,phy_type=network.PHY_KSZ8081,phy_addr=0)
lan.active(1)

Oh and also the Espoir does not need a unicore build, the ESP32-U4WDH processor used in the board was changed to be dual-core (see Espressif PCN-2021-021).

The Connaxio docs do say dual-core as expected, although this pull request initially seems to have been targeting uni-core.

Hi Sean, you are right; when I initially designed Espoir, The MINI-1 was a single-core module (I still have a bunch of them on a shelf...), but by the time I launched it on Crowd Supply, I managed to get my hands on the newer, dual-core modules. It appears I forgot to fix that afterwards. Thankfully the generic build works, so nothing needs to be done except for me to update the docs.

@ma-lalonde , are you able to confirm that all shipped Espoir boards used the newer dual-core parts?

I'm looking into reviving this board definition, I think it's justified to be it's own board because it has specific hardware and has named pins on the silkscreen, for which I've created a pins.csv file for so that e.g. I2C on the Mikro Bus can be used with Pins.board.SDA instead of needing to know that it's actually Pins(23)

@dpgeorge what's the threshold for when a separate board definition makes sense? My thinking is that the labelled pins on the silkscreen are much more usable as named pins rather than needing GPIO numbers in the generic build.

Also I'm going to see what I can do to have some kind of convenience function that does the Ethernet init rather than needing the boilerplate line of:

lan=network.LAN(mdc=Pin.board.EMAC_MDC,mdio=Pin.board.EMAC_MDIO,power=None,phy_type=network.PHY_KSZ8081,phy_addr=0)

@seanlano yes, all shipped boards have a dual-core processor. I kept the single-core modules here to support my own low-power personal projects, since most platforms (Arduino, tasmota) cna be compiled for single core, but for the average user, that's a bit over the top. And it would have made things complicated with managing many board branches

@seanlano Does this need to be reopened? Do you think you'll be able to pull together a useful board definition?

Do you think you'll be able to pull together a useful board definition?

Yeah I reckon I can - would be very handy to have. It's on my to-do list!