Ok, guess that means the default ethernet example (that uses GPIO17) needs to be configured differently for the D2WD.

Robin

In the latest ESP32 datasheet (esp32_datasheet_en) version 1.3, the notes at the bottom of pages 9 and 12 state that GPIO16 and GPIO17 should not be used since they are part of the embedded flash circuit. The other docs and schematics show those pins should actually be SD_DATA_2 and SD_DATA_3 (GPIO9...

Yes, lan8720 with 50Mhz crystal. I use GPIO17 from the stock master tree used in phy_device_power_enable() to connect to the enable pin on the crystal. I also had to add a 100 ohm resister between the crystal and the ESP32 to prevent current drain that lowered the clock voltage.

Robin

Made a little "ESP32 Etherbase" ethernet proto board for the devkit-c. Working well with the LAN8720A.

Robin

I suppose one could use another free area within efuse to store the mac and point the mac read functions there. This would prevent people from changing the mac.

Robin

I was also trying to determine how to use our IEEE allocated MAC block for the devices. The docs seemed to indicate that once you change the efuse bits from 0 to 1, they could not be changed back to 0. How would you go about changing the factory programmed efuse MAC bits if the 1's cannot be changed...

Good details Rudi. Guess Olimex needs to do a new spin on the board.

Robin

Have you verified the 8710 is working with an external crystal or oscillator? I didn't get an IP until I connected crs/dv to gpio27. Are you seeing the DHCP request on your server?

Robin

Very cool Rudi. How are you generating the clock?

Hi Rudi. The 50MHz oscillator on the lan8720 eval board is there but not used. The onboard 25MHz crystal is used and the 8720 has the functionality to double the clock for it's reference and output so that a cheap crystal can be used. I did have to remove the 25MHz crystal and add a 50MHz oscillator...