Best posts made by veryalien

I had exactly the same problem on the outlook app on android.
Luckily I also use the built-in android email app with the same account (i get everything twice), the URL worked immediately, so my email is now verified.

This problem seems to be caused by the esp32 2.0.5 update.

I don't think M5Stack are to blame, this was not a mandatory setting before.

After this update was installed I had the same problem with some of my M5Stack boards, but not all of them. A menu setting for erasing flash before upload or not must now be set. It seems that this menu setting must be sent to esptool, if this is not provided then esptool fails with the Address "{upload.erase_cmd}" must be a number error
There is a simple fix, if you can find your hidden arduino boards.txt file.
The path to the file will be different on Windows, Linux and OSX.
You need to add the following to boards.txt for ALL types of M5Stack/M5Stamp boards and then uploads should work again:

<board_name>.menu.EraseFlash.none=Disabled
<board_name>.menu.EraseFlash.none.upload.erase_cmd=
<board_name>.menu.EraseFlash.all=Enabled
<board_name>.menu.EraseFlash.all.upload.erase_cmd=-e

Replace <board_name> with the correct name for each type of board in the complete list. You can see what the name should be in the section for each M5Stack board.

After editing and saving boards.txt in the correct place, you need to restart the arduino IDE. You will then see in the Tools menu Erase All Flash Before Sketch Upload: Disabled/Enabled. This is the missing required setting for esptool.

Make a copy of your boards.txt before you make any edits so you can recover from any incorrect changes.

Good Luck!

@felmue
Thanks for the info, with the bus power mode set to 0, it's all working, including RGB strips and units on ports A, B and C!
You don't need to do a custom neopixel setup as there are already RGB blocks under Hardwares, which now work with the RGB Bars on the Core2.

Have you got a bluetooth speaker?

If so, you could try using your M5Paper to send audio using a bluetooth a2dp connection to your speaker.

I found this arduino project:

https://github.com/pschatzmann/ESP32-A2DP

After making my own audio sample files, I can send audio from my M5Paper to my M5 Atom Echo (running the default factory firmware). I can also send to my other Urban Revolt bluetooth speaker, so it seems to be working correctly.

I just tried one of my SD cards in my M5Paper, using the factory test firmware from M5Burner. Everything works without any problems.
I copied over a couple of text files in different folders, a jpg and a mp3 (just for the sake of it).
The files in the folders were shown correctly, with all the correct details.
I could also open the text files and jpg by tapping on them to see the text and the picture. It doesn't recognise mp3 files to open them, but it reads the file size correctly.
Don't misunderstand this but, you have plugged the SD card in properly? It is upside down, the pins are facing upwards when you insert it. It is fully inserted so it clicks into place. It needs to be pushed right inside with your fingernail, otherwise it's not really in. Sorry if that's blatantly obvious, but you never know.

@kevindtimm Up to 16GB should work. I don't know why there is a relatively low SD card limit in the M5Stack hardware (all models). It might be a limit with the ESP32 itself, but I don't know.
My SD card is a 16GB SanDisk Ultra. It was a random selection from my 16GB cards.

@mwenghi I've worked out that set_checked does actually work. It changes the internal state of the checkbox from unchecked to checked, but it's not changing the visible state of the checkbox on the screen, so it doesn't appear to do anything!

If you add a set_checked_color call (in blockly it's the block set selectedColor) after your set_checked it will then show the relevant checkbox as checked in your desired color.

I've got a problem with M5Burner 2.2.7 on my Ubuntu mate system running on a hp laptop. The M5Burner window is too large for the display.

I can move/scroll it around to find all of the buttons and systems, but it is really annoying. I actually have to move the window using the to see the erase button and the 'X' close button! The maximise window button doesn't do anything at all, I can only minimise the window.

My full laptop display resolution is 1366 x 768 which might be non-standard but it doesn't seem too small.

Is the M5Burner display resolution fixed?

Is there any way that I can change some configuration settings for M5burner so that everything fits more comfortably on my display?

I have the problem that I cannot currently connect to any of my devices with UIFlow from flow.m5stack.com
For example core2 and atom devices can connect to the cloud server as usual and show a green connection.
When I try to connect to a device from my browser, it just says that the connection failed, maybe your device is offline..... All of the API keys I am using are correct. I've recently updated most of my devices to version 1.7.8. and everything was working until today.

Everything works perfectly fine locally via USB.

I cannot run the latest M5Burner with Ubuntu 18.04. It complains that glibc 2.28 is not found.
Unfortunately glibc 2.27 is the most up-to-date version on my system. I cannot upgrade to a newer Ubuntu.
Earlier versions of the M5Burner worked OK. I upgraded to be able to burn firmware on the latest M5 boards like M5Stamp.

This exact problem has been fixed before, see below. Can you please rebuild the M5Burner depending on earlier versions of the system libraries?

Re: Cant run M5Burner in Linux

I'm trying a few little UIFlow tests on my core2 and I noticed that when I touch the display it always gets cleared to the background colour set in the uiflow.
I wrote a simple test program to print the current rtc time as a clock.
Here is the python:

from m5stack import *
from m5stack_ui import *
from uiflow import *
import time

screen = M5Screen()
screen.clean_screen()
screen.set_screen_bg_color(0x070707)

lasttime = None
time = None

lcd.clear()
lcd.fill(0x000000)
lcd.rect(50, 50, 50, 50, color=0xff0000)
lasttime = ''
while True:
  time = rtc.printRTCtime()
  if lasttime != time:
    lcd.print(lasttime, 0, 0, 0x000000)
    lasttime = time
    lcd.print(time, 0, 0, 0xffffff)
  wait_ms(500)
  wait_ms(2)

If I touch the display, it gets cleared to the black background.
The red square that I draw only once disappears, so I know the display is being cleared.
When my program writes to the display again, when the time changes after one second, it updates correctly and shows the time in white on a black background.

How can I disable or change the behaviour of this 'automatic' touch display clear?

I've solved the problem myself. When I use a label the screen clear does not affect it, so only the red square disappears.

from m5stack import *
from m5stack_ui import *
from uiflow import *
import time

screen = M5Screen()
screen.clean_screen()
screen.set_screen_bg_color(0x000000)

label0 = M5Label('Text', x=0, y=0, color=0xffffff, font=FONT_MONT_26, parent=None)

lasttime = None
time = None

lcd.clear()
lcd.fill(0x000000)
lcd.rect(50, 50, 50, 50, color=0xff0000)
lasttime = ''
while True:
  time = rtc.printRTCtime()
  if lasttime != time:
    lasttime = time
    label0.set_text(str(time))
  wait_ms(500)
  wait_ms(2)

I suppose this has something to do with which layers on the display are being cleared by the touch? But this still seems strange default behaviour to me.

If I download the original program to the Core2 (without using a label) and run it from the app menu, any touches do not clear the display at all. If I then reset the Core2 and the app runs automatically, it then clears the display when I do a touch. What is going on?