M5 tough..getting started issue...
-
Hi,
I just bought my first m5 tough (first m5 device every), so everything is new to me.
Installed the driver : ok (device connected on COM4)
Could write the firmware to UIflow2.0 (2.0.5-Tough) with M5 burner (logged in to my account).I can't get write any program to the device via web uiflow2. It's possible to connect, but when writing a program a just hangs.
Also the device is not bound to my account.
On the M5 tough device itself, I am seeing "Tough Tools" and serveral menu-items on the bottom of the screen wirfi, touch, I2C,etc...)
Searched for many hours , but documentation is not very basic and unclear. Getting frustrated...not a fluent start...
Who can help me ? -
Did you erase find and bind to your account because it doesn’t appear so.
Did you check the website, google or YouTube? But documentation is available -
Hello @wouter
I don't think your M5Tough is actually running UIFlow2 since you are writing that you're seeing "Tough Tools" and several menu-items on the bottom. I think it is still running the Tough Tools firmware it came with (which is different from UIFlow2 firmware).
When UIFlow2 is running on your M5Tough it does say so on the screen. On screen at the top from left to right you should see: UIFlow2 / Time / WiFi signal / Cloud connection state / Battery state.
Thanks
Felix -
@felmue
Hi, yes you are correct, I already suspected something like this.But I can't figure out why UIFlow is not running.
When I look in the M5 burner, and I search for "Tough" I do find "tough_tools" and the display currently looks exactly like this.(as you mentioned).I can also find UIFlow_Tough, this is for the V1 uiflow I suppose.
For the UIFlow2.0 I can find "Uiflow2.0 (core2/tough/Core2 v1.1).
Here I select V2.0.5-Tough. Then Download.
Then Configure -> COM4, I add the wifi settings, and time zone.
I select : show startup menu and network setup
Powermode : USB IN BUSOUT
Then Next -> It says Burning.
Detecting chip type...
ESP32
Chip is ESP32-D0WDQ6-V3 (revision v3.1)
Features: WiFi, BT, Dual Core, 240MHz, VRef calibration in efuse, Coding Scheme None
Crystal is 40MHz
MAC: 08:f9:e0:d2:66:f4
Uploading stub...
Running stub...
Stub running...
Changing baud rate to 1500000
Changed.
Configuring flash size...
Auto-detected Flash size: 16MB
Flash will be erased from 0x00009000 to 0x0000efff...
Compressed 24576 bytes to 503...
Writing at 0x00009000... (100 %)
Wrote 24576 bytes (503 compressed) at 0x00009000 in 0.3 seconds (effective 663.5 kbit/s)...
Hash of data verified.Leaving...
Hard resetting via RTS pin...
"Burn Sucessfully"Did a long press on the side button to turn it off, turn it back on via the button.
Turned off the power by removing the usb cable and put it back in.And then.....everything stays the same on the device ?
What am I missing ? -
@ajb2k3
Hi thank your for your answer. Yes I read the m5stackwebsite, google, youtube... but not many things about the M5 tough, or how to get started. I understood quickly I needed to do a firmware flash to uiflow2, but that doesn't seem to work for some reason. If you can point me to some usefull info I would certainly appreciate this.
I think find and bind will only work if I get the UIflow2 firmware working ? -
I've just started working with M5 Tough (about a month). I can execute some code and tinker with the basics as I attempt to do something more advanced. I can answer some basic things I have tried.
The simple stuff:
I flashed the UIFLow 2.0 firmware using m5burner
Used the web uiflow software to write a basic program and pushed it onto the device.
Then, I connected to the device using Thonny. I can now write code in main.py (using UIFlow web IDE to figure out some code blocks and copy it into the main.py)The things I am working on: (the documentation is terrible)
- Connect the device to a Bluetooth speaker
- Read a music file from an SD card and play it over Bluetooth
-
Hello @wouter
that is strange indeed. I have no idea as to why after as successful burning of V2.0.5-Tough your device would still boot up with the previous factory installed firmware. Maybe try to erase first?
Thanks
Felix -
You have missed a step there, you must Erase the existing firmware before burning new firmware.