-
Notifications
You must be signed in to change notification settings - Fork 7.2k
-
Notifications
You must be signed in to change notification settings - Fork 7.2k
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
[TW#15969] make monitor
Error 1
#1136
Comments
The IOError is a Windows-level OS error. I get similar errors if the USB connection is flaky, or the USB/Serial chip is browning out and resetting. If the same board has previously worked in the same situation, try swapping out the USB cable. |
Tried a different board, different USB cable, and different USB port. The problem still occurs with different boards, too. Edit: Just used a multimeter and I'm getting a solid, stable 5V. |
Same issue here on Win 10 64bit. Worked fine about a week ago with the same board, USB port, and cable. Now I get this error 100% of the time with any code for make monitor. The serial monitor in Arduino IDE and Putty work fine for monitoring. |
@adamt80 Have you done the Fall Creator's Update on that machine? My machines have the update. |
@sigwinch28 Yes. Both my machines have the update as well. Probably related because I undid the last couple monitor changes and the issue persists. Update: |
Windows update is definitely responsible for this. I have no issues just before it and after I have same error as you. Quick and ugly fix:
to
|
I came here to say that I had the same issue after installing the Fall Creator's Update and @logmanPL 's workaround allowed me to debug. Thanks! |
Just another quick confirmation that I encountered the issue immediately upon installing the Fall Creator's Update and @logmanPL 's post saved the day for me as well, thank you! |
I have this issue too after Win10 update. simple_monitor gives me same error occasionally too. Wonder esp-idf is to blame or pyserial. |
Hi folks, Sorry for the slow turnaround on this. I (finally) got my Windows 10 box updated to Fall Creators Update and saw the exact same issue. The bug is, oddly enough, in the console display output handling rather than anything to do with serial. It appears to be timing related, somehow. Fix coming shortly (very similar to @logmanPL's above, only I noticed that retrying the write() always seems to succeed so doing this instead.) |
Seems like this is not always the case: |
…lso fails Although in my tests the second write always passes, people have reported different results. Closes #1136 (again)
cf. espressif#1136 for more information
…wice Turns out when IOError is thrown by the console, the character is also successfully displayed. Revisits fix from #1136 As reported https://esp32.com/viewtopic.php?f=14&t=4766&p=20637
…wice Turns out when IOError is thrown by the console, the character is also successfully displayed. Revisits fix from espressif#1136 As reported https://esp32.com/viewtopic.php?f=14&t=4766&p=20637
…lso fails Although in my tests the second write always passes, people have reported different results. Closes espressif/esp-idf#1136 (again)
…wice Turns out when IOError is thrown by the console, the character is also successfully displayed. Revisits fix from espressif/esp-idf#1136 As reported https://esp32.com/viewtopic.php?f=14&t=4766&p=20637
After following the install guide for Windows on a Windows 10 64-bit machine, I receive an error when attempting to run
make monitor
after flashing thehello_world
.I installed the IDF via the "from scratch" method for Windows and the monitor was previously working, but I can't figure out what's changed:
The text was updated successfully, but these errors were encountered: