-
Notifications
You must be signed in to change notification settings - Fork 344
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
Upload "Error 2" #228
Comments
It seems really like a software Issue to me since, when the upload of the program fails, the watchy does a reboot and vibrates. By the way the problem occurs in PlatformIO and also with the esp-flash-tool. |
I am having the same issue with my newly purchased Watchy. Cannot upload, the watch appears to reboot but does not vibrate when the esptool step fails |
The issue is all my motherboard USB ports are USB3.0 and while they do work with other USB 2.0 devices, it does not work with Watchy. Like others on Discord, I had to use a USB 2.0 hub (conveniently part of my monitor) to connect the watch and have everything work. |
I have been unable to upload anything on any USB port. I even broke out a 20 year old USB 2.0 hub I had lying around. I get an Error 2 every time. Multiple cables as well. |
I will have to try that. I am getting this weird architecture error as well. I haven't had any luck with Platform or the BLE upload either. I guess I will try 2.0. |
For the bootmode-problem, I've found a better a better solution than messing around with wires and pads every time flashing. It also works to stick in the USB-Port just in the right moment, before the flash command. The time window is about half a second. |
Recently, when flashing via serial connection, I'm getting the well known ESP32-"Error 2". Which means the ESP is not in download-mode. With a normal Board one would now press the EN-Button while downloading. Actually this works also on my Watchy, pulling down the TP0 (GPIO0) to GND. (But of course I don't want do disassemble half of the Watchy every time I want to download a program.)
I guess Watchy is using the automatic bootloader to get in the bootmode. It seems like this is not working anymore, either due to a HW- or a SW-Fault.
Has anyone experienced the same problem?
And does someone know why the automatic bootloader fails? Could it be a hardware issue?
The text was updated successfully, but these errors were encountered: