Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Timed out waiting for PHY register #13

Open
Gnubsch opened this issue Apr 15, 2020 · 9 comments
Open

Timed out waiting for PHY register #13

Gnubsch opened this issue Apr 15, 2020 · 9 comments

Comments

@Gnubsch
Copy link

Gnubsch commented Apr 15, 2020

Hello,
I have bought three ESP32-POE-ISO boards With two copies the demo for the ethernet interface works. With the third board I get the timeout error.
It has probably something to do with the clock.

I used the ESP32_PoE_Ethernet_Arduino file for this.
Any tips how I can solve the problem?
I have already tried it on different PC's with different USB cables and ports.

Thanks a lot.

Error: Timed out waiting for PHY register 0x2 to have value 0x0007(mask 0xffff). Current value 0x0000[0m

Arduino 1.8.12 / Board-Lib esp32 1.0.4

@DanKoloff
Copy link
Contributor

DanKoloff commented Apr 15, 2020

What operating system are you using? What is the baud rate selected?

Edit: It can be driver related.

@Gnubsch
Copy link
Author

Gnubsch commented Apr 15, 2020

OS: Windows 10 Pro / 10.0.18363
Board: Olimex ESP32-POE-ISO Rev.C
Uploadspeed: 115200
Flash Frequency: 80 Mhz
Partition Scheme: Standard
Programmer: AVRSIP mkII
Driver: CH341Ser.INF 01/30/2019, 3.5.2019

`esptool.py v2.6
Serial port COM3
Connecting.....
Chip is ESP32D0WDQ5 (revision 1)
Features: WiFi, BT, Dual Core, VRef calibration in efuse, Coding Scheme None
MAC: 24:0a:c4:25:99:2c
Uploading stub...
Running stub...
Stub running...
Configuring flash size...
Auto-detected Flash size: 4MB
Compressed 8192 bytes to 47...

Writing at 0x0000e000... (100 %)
Wrote 8192 bytes (47 compressed) at 0x0000e000 in 0.0 seconds (effective 6553.6 kbit/s)...
Hash of data verified.
Compressed 15856 bytes to 10276...

Writing at 0x00001000... (100 %)
Wrote 15856 bytes (10276 compressed) at 0x00001000 in 0.9 seconds (effective 139.7 kbit/s)...
Hash of data verified.
Compressed 706784 bytes to 393190...

Writing at 0x00010000... (4 %)
Writing at 0x00014000... (8 %)
Writing at 0x00018000... (12 %)
Writing at 0x0001c000... (16 %)
Writing at 0x00020000... (20 %)
Writing at 0x00024000... (25 %)
Writing at 0x00028000... (29 %)
Writing at 0x0002c000... (33 %)
Writing at 0x00030000... (37 %)
Writing at 0x00034000... (41 %)
Writing at 0x00038000... (45 %)
Writing at 0x0003c000... (50 %)
Writing at 0x00040000... (54 %)
Writing at 0x00044000... (58 %)
Writing at 0x00048000... (62 %)
Writing at 0x0004c000... (66 %)
Writing at 0x00050000... (70 %)
Writing at 0x00054000... (75 %)
Writing at 0x00058000... (79 %)
Writing at 0x0005c000... (83 %)
Writing at 0x00060000... (87 %)
Writing at 0x00064000... (91 %)
Writing at 0x00068000... (95 %)
Writing at 0x0006c000... (100 %)
Wrote 706784 bytes (393190 compressed) at 0x00010000 in 34.7 seconds (effective 163.0 kbit/s)...
Hash of data verified.
Compressed 3072 bytes to 128...

Writing at 0x00008000... (100 %)
Wrote 3072 bytes (128 compressed) at 0x00008000 in 0.0 seconds (effective 1536.0 kbit/s)...
Hash of data verified.

Leaving...
Hard resetting via RTS pin...`

@DanKoloff
Copy link
Contributor

@Gnubsch
Copy link
Author

Gnubsch commented Apr 15, 2020

Correct.

@DanKoloff
Copy link
Contributor

DanKoloff commented Apr 15, 2020

When you get the error, what happens if you press the on-board reset button? Does the same error appears?

@Gnubsch
Copy link
Author

Gnubsch commented Apr 15, 2020

The error occurs after restarting the device or when I press the hardware button. The same error occurs.

19:09:12.348 -> ĽP⸮⸮&⸮{⸮=�c�א⸮⸮⸮ets ⸮]��⸮�⸮016⸮0:2⸮⸮⸮⸮H⸮HH⸮⸮⸮0x1 ⸮⸮]�I=N_RE⸮QU⸮I⸮ot:0⸮b (ӕ}��MT_FLP*⸮%==T) 19:09:12.348 -> ⸮˙⸮⸮⸮ip:⸮⸮ SPR�⸮⸮�e 19:09:12.348 -> ⸮k⸮E⸮⸮:0x0bq_d⸮⸮⸮0,d_d.⸮⸮⸮⸮0,cs0E⸮⸮⸮0x00,h⸮E⸮⸮⸮0x00⸮�}⸮⸮⸮:0x0j 19:09:12.382 -> mo⸮Y'T⸮ �⸮⸮⸮⸮ di⸮⸮j 19:09:12.382 -> l+⸮⸮0Mfff⸮⸮8,lYK⸮j 19:09:12.382 -> load⸮⸮⸮ff�⸮⸮�⸮len:⸮⸮4 19:09:12.382 -> ⸮+⸮⸮0x400⸮⸮00,⸮⸮⸮8⸮6 19:09:12.382 -> ⸮+⸮⸮0⸮008⸮�⸮bb⸮n:58LSH⸮⸮⸮ry 0⸮008⸮ac ⸮E (1046) emac: Timed out waiting for PHY register 0x2 to have value 0x0007(mask 0xffff). Current value 0x0000 19:09:14.637 -> E (2046) emac: Timed out waiting for PHY register 0x3 to have value 0xc0f0(mask 0xfff0). Current value 0x0000 19:09:14.637 -> E (2046) emac: Initialise PHY device Timeout 19:09:18.521 -> etsRչ⸮ 8 20⸮�⸮⸮Ғ⸮:57C⸮⸮r⸮⸮⸮ (POWQ⸮⸮}I�SET)I⸮⸮⸮⸮0x1b⸮i�⸮}�AST_⸮*M!} OOT)C⸮⸮⸮˥gsip'⸮b�⸮⸮IWP⸮�⸮5 19:09:18.521 -> clk_⸮⸮⸮0⸮⸮,q_⸮⸮⸮0A0,dߖ⸮⸮0⸮0,c.⸮⸮⸮⸮⸮0x00 ⸮}⸮⸮⸮:0x⸮⸮wp_⸮⸮⸮0A0 19:09:18.556 -> 틕⸮DR⸮��⸮⸮ck ⸮Z⸮⸮j 19:09:18.556 -> load⸮⸮⸮ff�⸮⸮⸮bb⸮⸮⸮C!⸮+⸮:0x3⸮⸮�⸮⸮�⸮len⸮⸮⸮⸮j 19:09:18.556 -> loa⸮'⸮⸮0⸮800blen⸮⸮96 !녑⸮0x40⸮⸮400⸮⸮⸮⸮5816 ⸮Y⸮⸮⸮0x40⸮06acC⸮E (1046) emac: Timed out waiting for PHY register 0x2 to have value 0x0007(mask 0xffff). Current value 0x0000 19:09:20.811 -> E (2046) emac: Timed out waiting for PHY register 0x3 to have value 0xc0f0(mask 0xfff0). Current value 0x0000 19:09:20.846 -> E (2046) emac: Initialise PHY device Timeout

@DanKoloff
Copy link
Contributor

Please drop an e-mail at support@olimex.com with short introduction and link to this GitHub issue, I will tell you how to proceed with the return.

We don't have this problem here and each board's Ethernet is tested empirically so I have no idea what might be wrong. The clock comes from the ESP32, so I don't think it is clock issue.

@Gnubsch
Copy link
Author

Gnubsch commented Apr 16, 2020

Thank you for your efforts. I am writing the email to the support.

@danieltang3434
Copy link

Hi @Gnubsch, did you get any feedback from Olimex? I'm facing the same problem also.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants