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

ESP32 Windows - Device not ready. #192

Closed
ghost opened this issue Apr 1, 2017 · 4 comments
Closed

ESP32 Windows - Device not ready. #192

ghost opened this issue Apr 1, 2017 · 4 comments

Comments

@ghost
Copy link

ghost commented Apr 1, 2017

I have a Win10 hosted VMWare Workstation (11.1.2) that works perfectly when programming Arduino ESP-8266, that fails when trying to program an ESP32. To get setup I followed the Arduino ESP32 instructions here: https://github.com/espressif/arduino-esp32/blob/master/doc/windows.md I'm using Python 3.6.0 64-bit and Arduino 1.8.15. This WMWare virtual machine and USB port works fine when programming ESP-8266. When I try to upload to an ESP-32 it says "This device is not ready." I have checked that nothing else is using the port. Any suggestions?

Sketch uses 115459 bytes (11%) of program storage space. Maximum is 1044464 bytes.
Global variables use 9488 bytes (3%) of dynamic memory, leaving 285424 bytes for local variables. Maximum is 294912 bytes.
esptool.py v2.0-dev
Traceback (most recent call last):
  File "esptool.py", line 2177, in <module>
  File "esptool.py", line 1954, in main
  File "esptool.py", line 153, in __init__
  File "site-packages\serial\__init__.py", line 88, in serial_for_url
  File "site-packages\serial\serialwin32.py", line 62, in open
serial.serialutil.SerialException: could not open port 'COM5': WindowsError(21, 'The device is not ready.')
Failed to execute script esptool
the selected serial port Failed to execute script esptool
 does not exist or your board is not connected
@ghost ghost changed the title ESP32/VMWare - Device not ready. ESP32 Windows - Device not ready. Apr 1, 2017
@moxy-bc
Copy link

moxy-bc commented Apr 2, 2017

Not sure if this is related to this, or not...
#136 (comment)

@projectgus
Copy link
Contributor

Hi @CodeFreak604,

I don't think this is related to the issue @moxy-bc linked, that failure happens at a later stage than this.

A couple of questions/suggestions:

  • Can you verify COM5 exists and is shown in Windows Device Manager? Are there are warnings shown for COM5 in Device Manager?
  • Is the serial port shared from the host to the guest at the serial port level, or as a USB device? If shared as a serial port, we have had reports of problems with VM serial port emulation before - try sharing the entire USB device from the host to the guest.

@projectgus
Copy link
Contributor

@CodeFreak604 , did you make any more progress with this issue?

@projectgus
Copy link
Contributor

Closing due to a lack of information to follow up, but feel free to reopen if you have more information.

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

2 participants