TTGO T-WATCH-2020

[vlad]

Hi mate, thank you for the prompt response.

I didn't think that metronome itself is a problem, but the accuracy could be an issue

Currently I'm looking for the solution how to send the tempo over socket.io to t-watch.
I have two messages in mind:
1. Start Metronome with specific tempo value
2. Stop Metronome

By the way guys, could anyone please give me a link to some kind of best practice how to upload a project with multiple Python files into ESP32 ? I've spent couple of nights by now and all I found were basic examples only.

Cheers,
Vlad

[vandys]

I'm also getting this after flashing Micropython:

rst:0x10 (RTCWDT_RTC_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)
configsip: 0, SPIWP:0xee
clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
mode:QIO, clock div:2
load:0x3fff0018,len:4
load:0xffffffff,len:-1
ets Jun 8 2016 00:22:57

I know "thonny" somehow avoids this... could somebody pick out if/how it invokes esptool, so I can flash my watch without being dependent on a particular IDE?

Thanks!
Andy Valencia

Hi,
I don't know if you are on Linux, MacOs or Windows. But if when you connect the watch, you don't see the device, you still need to install drivers.
When you see the device, install esptool at https://github.com/espressif/esptool
Download the firmware http://micropython.org/resources/firmwa ... 3d8e81.bin
and finally execute:
erase flash

Code: Select all

esptool.py --chip esp32 --port /dev/cu.usbserial-4152065289  --baud 115200 erase_flash

write flash

Code: Select all

esptool.py --chip esp32 --port /dev/cu.usbserial-4152065289 --baud 115200 write_flash -z 0x1000 esp32spiram-idf4-20200811-unstable-v1.12-663-g9883d8e81.bin

where / dev /cu.usbserial-4152065289 is your device

Thank you for writing this! It looks like the esptool.py from my esp-idf was causing the problem. Checking out the esptool you named fixed the problem. The actually firmware you listed has faded away, but the latest in that lineage loads and boots just fine.

Game on!

[vandys]

Has anybody played with backlight yet? The pinmap doc doesn't mention a pin 12, but that seems to be what drives it. PWM to get adjustable level. Am I reading the source correctly?

Also, where can I read that side button on the 2020 watch? I know it has a knurled button, but no rotary encoder. But where's the button itself come in?

TIA

[rcolistete]

I have finished version 0.1 of the wasp project adapted to twatch 2020.
It works: clock, stopwatch, flashlight, settings.
in this version the clock wakes up every 5 minutes and tries to connect to the internet to do certain tasks, right now just synchronize the time.
This version will have many errors that I will correct, but it is already a watch that can be used.
https://github.com/sactre/wasp-os/tree/develop/wasp
To test it, load micropython on the clock, then copy the contents of the wasp folder to the clock.

Your Wasp-OS variant works on LilyGo TTGO T-Watch-2020, thanks !
Time from battery full to empty, about 40 hours, idle, not connected to USB cable, pressing the button to turn the screen 2-3 times a day.

It would be :
- useful to document where the WiFi/Internet connection is configured;
- a lot faster if the repository "ST7789 Driver for MicroPython", which has firmware for TTGO T-Watch-2020 with ST7789 screen driver in C could be used. There are some differences with respect "wasp/drivers/st7789.py", like arguments order of ST7789, no attribute 'linebuffer', etc.

[vandys]

I have finished version 0.1 of the wasp project adapted to twatch 2020.
It works: clock, stopwatch, flashlight, settings.

Your Wasp-OS variant works on LilyGo TTGO T-Watch-2020, thanks !

Your wasp work is a treasure trove for showing how many of the HW components are accessed. Thank you very much!

[uraich]

I also managed to get the wasp-os to work on my t-watch. However, as soon as I take the USB cable away from the watch it does not do anything any more. Strangely enough it still works if I remove the USB cable from the computer but leave it connected to the watch. What am I doing wrong? Do yours behave the same way?

[uraich]

Sorry, I need help!
When I take off the USB cable from the watch it shuts down and there is no means to get anything to work. Is this a problem only with my watch?
Do your watches work ok with the USB cable removed?

[rcolistete]

After charging via USB cable, my TTGO T-Watch-2020 works without the microUSB cable, no problems at all.
As I've said in the above post :

Time from battery full to empty, about 40 hours, idle, not connected to USB cable, pressing the button to turn the screen 2-3 times a day.

[uraich]

Thanks for your help.
It looks like I had a problem with charging. Now I left it one the charger for the night and I can finally take of the USB cable.
I will play with the hardware and see how far I can come
Man thanks again.
Uli

[husky]

I have finished version 0.1 of the wasp project adapted to twatch 2020.
It works: clock, stopwatch, flashlight, settings.
in this version the clock wakes up every 5 minutes and tries to connect to the internet to do certain tasks, right now just synchronize the time.
This version will have many errors that I will correct, but it is already a watch that can be used.
https://github.com/sactre/wasp-os/tree/develop/wasp
To test it, load micropython on the clock, then copy the contents of the wasp folder to the clock.

Your Wasp-OS variant works on LilyGo TTGO T-Watch-2020, thanks !
Time from battery full to empty, about 40 hours, idle, not connected to USB cable, pressing the button to turn the screen 2-3 times a day.

It would be :
- useful to document where the WiFi/Internet connection is configured;
- a lot faster if the repository "ST7789 Driver for MicroPython", which has firmware for TTGO T-Watch-2020 with ST7789 screen driver in C could be used. There are some differences with respect "wasp/drivers/st7789.py", like arguments order of ST7789, no attribute 'linebuffer', etc.

Thanks for the feedback. I really have to do documentation of how to configure the wifi and how to make applications that need internet and background tasks.
Regarding the use of the ST7789 driver, I have used the wasp-os driver for application compatibility. But I think I can make a proxy to use the official ST7789
But every time I do things in this fork I find it more difficult to maintain compatibility with the original wasp-os project. I have already separated a lot from the Core, to the way of managing the apps and the battery management. At first I was going to do a PR on the main project. But now I think it is better to keep this project independent.
opinions?
Next things I want to do:
I would like the battery to last 72 hours.
I am working on a weather app.