Category: Hardware/Software
Hello,
I am currently working on a project that involves the integration of the ESP IoT Bridge. I have encountered some issues and would appreciate any assistance or insights from the community. Below are the details of my setup and the problems I am facing:
Setup Details:
ESP IoT Bridge Model: Wi-Fi Router
Development Board: ESP32 with LAN8720, and RJ45
Firmware/SDK Version: V5.2.2
Development Environment: VS code with ESP IDF extension, framework version 5.2.2
Operating System: Windows 10
Issue Description:
There are two models for our project: a master board having different modules with specific features, and a prototype which is a self-developed PCB board integrated with all the different modules used for the master board.
after making some changes for "error, init mac failed" using menuconfig I am not getting that error anymore but facing some new error
Connection Problem:
As per our understanding, there are no major changes in the master and prototype boards, but the problem is that the Ethernet is not initializing properly, giving errors like "eth init fail," "pwrctl timeout," or "reset timeout."
Flashing Method:
We are using UART for flashing the ESP32 with the prototype.
Error Messages with Log:
E (1018) eth_phy_802_3: esp_eth_phy_802_3_pwrctl(250): power up timeout
E (1018) eth_phy_802_3: esp_eth_phy_802_3_basic_phy_init(433): power control failed
E (1023) lan87xx: lan87xx_init(341): failed to init PHY
E (1029) esp_eth: esp_eth_driver_install(229): init phy failed
E (1035) esp_eth: esp_eth_increase_reference(515): ethernet driver handle can't be null
E (1044) esp_eth: esp_eth_update_input_path(341): ethernet driver handle can't be null
E (1052) esp_eth: esp_eth_ioctl(409): ethernet driver handle can't be null
I (1060) esp_eth.netif.netif_glue: a8:59:10:40:dc:78
I (1066) esp_eth.netif.netif_glue: ethernet attached to netif
E (1072) esp_eth: esp_eth_start(282): ethernet driver handle can't be null
Unexpected Behavior:
The same code is working after flashing on the master board but generates errors while flashing on the prototype.
Steps Taken:
We have gone through the hardware connections of both the master and prototype boards with reverse engineering and have ensured the required configuration through the menuconfig and via the ESP IoT Bridge provided code on the Espressif GitHub platform.
Request for Assistance:
I would greatly appreciate any guidance or suggestions to resolve these issues. If anyone has experience with similar setups or has encountered and resolved similar problems, your input would be invaluable.
Thank you in advance for your help!
Best regards,
Aditya Nijave
Issue with ESP IoT Bridge Integration in Project
-
- Posts: 3
- Joined: Tue Jul 30, 2024 10:48 am
Issue with ESP IoT Bridge Integration in Project
- Attachments
-
- Untitled.png (73.94 KiB) Viewed 1314 times
-
- Posts: 200
- Joined: Sun Jun 23, 2024 6:18 pm
Re: Issue with ESP IoT Bridge Integration in Project
Inspect the solder joints under a microscope for cold solder joints, especially around the LAN8720 and associated passive components.
There should be no broken traces or manufacturing defects on the prototype PCB.
There should be no broken traces or manufacturing defects on the prototype PCB.
-
- Posts: 211
- Joined: Fri May 07, 2021 10:35 am
Re: Issue with ESP IoT Bridge Integration in Project
Check if MDIO and MDC GPIOs are properly configured.
Check the PHY address is correctly set in code and in PHY device via it's bootstraps or set PHY address to -1 (auto) in menuconfig.
Probe the MDIO and MDC with oscilloscope if you see any signal.
Check the PHY address is correctly set in code and in PHY device via it's bootstraps or set PHY address to -1 (auto) in menuconfig.
Probe the MDIO and MDC with oscilloscope if you see any signal.
Who is online
Users browsing this forum: Bing [Bot] and 138 guests