Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Ethernet ESP32 support broken with latest IDF44 (fixed) #6318

Closed Answered by Jason2866
Jason2866 asked this question in Q&A
Discussion options

compiled Arduino s3 branch with Arduino lib builder.
Somewhere between the relased core 2.0 2 and the actual one is "something"
which brokes ethernet for ESP32 (thinking a IDF change did)

You must be logged in to vote

Adding this settings to sdkconfig

CONFIG_ETH_RMII_CLK_OUTPUT=y
CONFIG_ETH_RMII_CLK_OUT_GPIO=17

solved

Replies: 5 comments 3 replies

Comment options

Hi @Jason2866, thanks for your report.

Can you provide more info?

Board, what exactly doesn't work and so on. I would suggest to open new issue and fill out issue template.

Thanks!

You must be logged in to vote
0 replies
Comment options

Jason2866
Feb 21, 2022
Collaborator Author

@VojtechBartoska We are investigating. Boards which do not use gpio 17 for Ethernet are working.
If we can provide relevant info we are going to open a issue.
A log

00:00:00.250 Project tasmota - Olimex ESP32-PoE-Iso Version 11.0.0.2(theo)-2_0_2_3(2022年02月21日T12:12:39)
I (363) gpio: GPIO[0]| InputEn: 0| OutputEn: 0| OpenDrain: 0| Pullup: 1| Pulldown: 0| Intr:0 
I (364) gpio: GPIO[0]| InputEn: 1| OutputEn: 0| OpenDrain: 0| Pullup: 0| Pulldown: 0| Intr:0 
I (370) gpio: GPIO[17]| InputEn: 0| OutputEn: 0| OpenDrain: 0| Pullup: 1| Pulldown: 0| Intr:0 
I (378) gpio: GPIO[17]| InputEn: 0| OutputEn: 1| OpenDrain: 0| Pullup: 0| Pulldown: 0| Intr:0 
I (386) gpio: GPIO[17]| InputEn: 0| OutputEn: 0| OpenDrain: 0| Pullup: 1| Pulldown: 0| Intr:0 
I (395) gpio: GPIO[17]| InputEn: 0| OutputEn: 0| OpenDrain: 0| Pullup: 0| Pulldown: 0| Intr:0 
E (514) lan87xx: lan87xx_pwrctl(409): power up timeout
E (514) lan87xx: lan87xx_init(491): power control failed
E (514) esp_eth: esp_eth_driver_install(223): init phy failed
00:00:00.413 ETH: Bad PHY type or init error
You must be logged in to vote
0 replies
Comment options

FYI, I also had problems with GPIO17 and 18 when using them with UART1.
I had to send a PR to use other pins by default.
The issue happens when the pins are left floating.
Maybe it has to be pulled up/down externally?

You must be logged in to vote
0 replies
Comment options

Jason2866
Feb 21, 2022
Collaborator Author

@SuGlider Thank you, for the hint. Adding a resistor is not a solution. We use different ready made devices which are working fine with there factory firmware (for example https://templates.blakadder.com/ewelink_ZB-GW03.html or https://templates.blakadder.com/sonoff_SPM.html) and replace this firmware with a custom firmware (Tasmota). All fail which uses GPIO17 for clock which is build with actual Arduino version. Core 2.0.2 did work.

You must be logged in to vote
0 replies
Comment options

Jason2866
Feb 21, 2022
Collaborator Author

Adding this settings to sdkconfig

CONFIG_ETH_RMII_CLK_OUTPUT=y
CONFIG_ETH_RMII_CLK_OUT_GPIO=17

solved

You must be logged in to vote
3 replies
Comment options

Comment options

Jason2866 Feb 22, 2022
Collaborator Author

Comment options

Jason2866 Feb 23, 2022
Collaborator Author

Better fix #6340

Answer selected by Jason2866
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

AltStyle によって変換されたページ (->オリジナル) /