Waveshare Ethernet Module, High-Performance 10/100 Ethernet Physical Layer Transceiver (PHY)

Product Information

ESD Protected MII/RMII Fast-Ethernet PHY with HP Auto-MDIX and SMSC flexPWR TM in a Small Footprint BLE_ESP32 (xdrv_79): Start scan as soon as we are connected to a device - saves missing a few adverts. Add commands ``ZbNameKey``, ``ZbDeviceTopic``, ``ZbNoPrefix``, ``ZbEndpointSuffix``, ``ZbNoAutoBind``, ``ZbNameTopic`` as synonyms for ``SetOption83, 89, 100, 101, 110 and 112`` respectively

Microchip's LAN8710A/LAN8710Aiarehigh-performance, small-footprint, low-power 10BASE-T/100BASE-TX transceivers specifically designed for today's consumer electronics, industrial and enterprise applications. The LAN8710A/LAN8710Aiarethe industry's smallest footprint solution with up to 40% lower power consumption than existing Microchip transceivers. The LAN8710A/LAN8710Ai have an integrated voltage regulator and ESD protection components to help reduce Bill of Material (BOM) costs. Higher frequencies come with reduced available bit depth (as by https://esphome.io/components/output/ledc.html). Remove the two jumpers from CN2, and place them at the two outermost empty jumper pins marked CN11 and CN12. I will add my opinion. Rejecting a RMI support in new ESP32 series like S3 is a very bad decision. Now I cannot to achieve high network performance. When I used LAN8720 with old chip, I could achieve up to 60Mbit/s in useful throughput. But now if I forced to use some SPI bridges like Wiznet W5500, it allows me only 15Mbit/s throughput. Of course, I can use Wiznet W5300 with parallel interface, that gives me 80Mbit/s network performance, but this chip is enough expensive in comparison with W5500 or LAN8720 and much bigger in their case. emac: Timed out waiting for PHY register 0x2 to have value 0x0007 (mask 0xffff). Current value 0xffff emac: Timed out waiting for PHY register 0x3 to have value 0xc0f0 (mask 0xfff0). Current value 0xffffI made a small prototype for the eBox ESP32-T and the Waveshare LAN8720 ETH Board which already has an 50MHz oscillator. The entry: #define D_ZIGBEE_NOT_STARTED "Zigbee not started" is duplicated in i18n.h from all language files. This produces a warning while compiling due to redefinition if changing the language in my_user_config.h I also find this https://esp32.com/viewtopic.php?t=5732 but before removing the crystal I prefer to be sure I'm not missing something else. Rejecting a RMI support is very very bad decision. Now I m forced to search some another solutions, that allows me to stay in low price for bill electronics components and sufficient LAN network performance. Example configuration entry ethernet : type : LAN8720 mdc_pin : GPIO23 mdio_pin : GPIO18 clk_mode : GPIO0_IN phy_addr : 0 # Optional manual IP manual_ip : static_ip : 10.0.0.42 gateway : 10.0.0.1 subnet : 255.255.255.0 Configuration variables: ¶

Microchip'sLAN8720A/LAN8720Aiarehigh-performance, small-footprint, low-power 10BASE-T/100BASE-TX transceivers specifically designed for today's consumer electronics, industrial and enterprise applications. The LAN8720A/LAN8720Aiare the industry's smallest footprint solutions with up to 40% lower power consumption than existing Microchip transceivers. The LAN8720A/LAN8720Ai have an integrated voltage regulator and ESD protection components to help reduce Bill of Material (BOM) costs. Power and mode must be individually controllable. Some devices may not function properly if the mode is also turned off when the power is turned off. the advantage could be that if wifi is not good we can use lan cable, maybe it could be PoE powering?I have a little problem with Tasmota and Ethernet (in summary – Ethernet doesn’t work without wifi connection): Actually the board has two STM32 chips. One is the target of the demo board, and the other is the STLINK. iBeacon (xdrv_52): Clean up BLE_ESP32 based driver; add commands and advert timing. Remove HM10 code - it's in the other one..... BUT when I turn wifi off (wifi 0 in console or changing wifi configuration to non existing wifi), I also loose Ethernet connection.

ESD Protected MII/RMII 10/100 Ethernet Transceiver with HP Auto-MDIX Support and flexPWR Technology in a Small Footprint Installing using the ZIP file and then updating using the Library Manager will result in duplicate libraries.

10/100 Base-T/TX Ethernet Transceiver with RMII Interface

Add commands ``ChannelRemap``, ``MultiPWM``, ``AlexaCTRange``, ``PowerOnFade``, ``PWMCT``, ``WhiteBlend``, ``VirtualCT`` as synonyms for ``SetOption37, 68, 82, 91, 92, 105 and 106`` respectively Raspberry Pi Pico has a lot of interesting and unique features, but it doesn’t have networking. Of course this was only ever going to be a temporary inconvenience, and sure enough, over Pi Day weekend we saw both USB Ethernet and Ethernet PHY support released for Pico and RP2040. Raspberry Pi Pico and RMII Ethernet PHY Go grab your Raspberry Pi Pico board and a micro USB cable. Plug the cable into your Raspberry Pi or laptop, then press and hold the BOOTSEL button on your Pico while you plug the other end of the micro USB cable into the board. Then release the button after the board is plugged in. For using the thermostat function, publication of the measured temperature was using the wrong name. Changed to the common used name.

Pin# of the enable signal for the external crystal oscillator (-1 to disable for internal APLL source) EMAC_TXD0, EMAC_TXD1, EMAC_TX_EN, EMAC_RXD0, EMAC_RXD1, EMAC_RX_DV and EMAC_TX_CLK are fixed and can't be rerouted to other GPIOs. HP Auto-MDIX eliminates the need for special "crossover" cables when connecting LAN devices together. While we're certainly not thinking of dropping Ethernet for future products, at this point we do not have any publicly announced upcoming chips with Ethernet in it. (I cannot comment on if the feature is in not-yet-announced chips, sorry for that.) Note that you could always add e.g. a SPI Ethernet chip to an ESP32-S3 to get Ethernet connectivity, although I agree that is not as optimal as simply having an integrated MAC.I have successfully flashed WT32-ETH01 using FT232RL FTDU module, ESP_Flasher and tasmota32-ethernet.bin (from https://github.com/tasmota/install/raw/main/firmware/unofficial/tasmota32-ethernet.bin) If a non-standard BootLoader has already been written to STM32, connection of nRTS pin and RESET pin is required. EDIT: After reading that the lenght of wires can be an issue at 50MHz, I wired it with 10cm wires (instead of 20cm on the photo), still the same. I have copy and pasted template {"NAME":"WT32-ETH01","GPIO":[1,1,1,1,1,1,0,0,1,0,1,1,3840,576,5600,0,0,0,0,5568,0,0,0,0,0,0,0,0,1,1,0,1,1,0,0,1],"FLAG":0,"BASE":1}