-
Notifications
You must be signed in to change notification settings - Fork 329
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
How to update ESP32-S3 model (from CrowdSupply campaign) #252
Comments
Hey there, it looks like you have the latest hardware which is V3 and uses the ESP32-S3. You will need to update to the latest arduino-esp32 (v3.0.2) and the latest Watchy library (v1.4.12). In the Arduino IDE, select the following options:
To enter bootloader mode:
To reset Watchy:
Enter bootloader mode, select the serial port, upload sketch, reset Watchy We'll be updating the official docs shortly. |
Thanks for the clarification. It did work (verifying and uploading) as I am now on the right timezone and can thus use NTP. When I do use "Update Firmware" though and go on Chromium on https://watchy.sqfmi.com/watchfaces and select another watchface, e.g |
The "Update Firmware" functionality is deprecated and will be updated with a new version with OTA soon. For now, please select example watchfaces in the Arduino IDE and upload them over USB. |
Hi, just received my Watchy and it works well. Unfortunately the timezone is on GMT -5 and I'm on GMT +2. I didn't find a way to change that via the interface on the watch. I did learn via #235 that I have to compile the firmware. I'm a bit lazy so I thought I'd try first via https://watchy.sqfmi.com/watchfaces using Chromium but it didn't work.
I thought maybe my USB cable was wrong so I tried
espflash board-info
which did show mefrom
Serial port: '/dev/ttyACM0'
and thus both the watch and cable are working.Consequently I'm wondering what's the status of support for this model. Is it a new one? Can I follow https://watchy.sqfmi.com/docs/getting-started or is it for V2.0 which might be an older version?
The text was updated successfully, but these errors were encountered: