Also, even in this situation with UIFlow is running, if I burn factory test firmware, it will work normally.

I feel that there is an unstable part in the display-related HW. Firmware is UIFlow_Core2-v1.7.1.1-core2.bin.

I copied the above library to Core2 and ran the following code from the serial console.

import ili934x
from machine import Pin, SPI
spi = SPI(miso=Pin(38), mosi=Pin(23, Pin.OUT), sck=Pin(18, Pin.OUT))
display = ili934x.ILI9341(spi, cs=Pin(5), dc=Pin(15), rst=Pin(4))
display.fill(ili934x.color565(0xff, 0x11, 0x22))
display.pixel(120, 160, 0)
display.print('1234567890 ABCDEFGHIJKLMNOPQRSTUVWXYZ')
     :     :     :
display.print('1234567890 ABCDEFGHIJKLMNOPQRSTUVWXYZ')

As a result, the characters are displayed as shown in the image below.
I'm not sure what this means, but can it help analyze the problem?

However, it seems running with black screen. I tried connect to Core2 from UIFlow Cloud and run the program. print() can print text to the serial console, but M5Label will show nothing on the Core2 screen. just black screen.

I tried burn with low baudrate (115200), but nothing changed

@NetworkUke : please see your other post. In your case the firmware file size is way to small.

@puzznic : have you tried to reduce the baudrate? Not sure that will help but worth a try.

Thanks
Felix

"Hard resetting via RTS pin...

Burn Successfully"

The m5stack display freezes and in the console output is:

rst:0x10 (RTCWDT_RTC_RESET),boot:0x17 (SPI_FAST_FLASH_BOOT)
invalid header: 0x4f44213c
invalid header: 0x4f44213c
invalid header: 0x4f44213c
invalid header: 0x4f44213c
invalid header: 0x4f44213c
invalid header: 0x4f44213c
invalid header: 0x4f44213c
invalid header: 0x4f44213c
ets Jul 29 2019 12:21:46

on an infinite loop.

Even after re-burning it with the easy loader when I attempt to burn UIFlow_Core2 the same issue occurs. Any advice is greatly appreciated.

after burning UIFlow, what do you see in the COM Monitor log of M5Burner when you reset M5Core2? Any errors?

Thanks
Felix

I just received my first Core2 yesterday, and I had the same problem trying to run the uiFlow 1.7.1 firmware.

After many attempts, I finally tried the 1.7.0 version, and it worked ! Maybe try this version instead of the latest one.

just to be clear, when you run the Factory Test the screen in your M5Core2 works, correct? correct. here's a screenshot of the test running:


After burning UIFlow, have you tried to reset your M5Stack with the reset button?
Also have you tried to fully shutdown your M5Stack by pressing and holding the power button, then power it on again?

the device has been reset and turned off and on multiple times indeed.
so weir, I reckon...

just to be clear, when you run the Factory Test the screen in your M5Core2 works, correct?

After burning UIFlow, have you tried to reset your M5Stack with the reset button?

Also have you tried to fully shutdown your M5Stack by pressing and holding the power button, then power it on again?

Thanks
Felix

• =================
  Erase now
  =================
  esptool.py v2.5.0
  Serial port COM5
  Connecting....
  Detecting chip type... ESP32
  Chip is ESP32D0WDQ6 (revision 1)
  Features: WiFi, BT, Dual Core, 240MHz, VRef calibration in efuse
  MAC: b8:f0:09:c5:b1:34
  Uploading stub...
  Running stub...
  Stub running...
  Erasing flash (this may take a while)...
  Chip erase completed successfully in 35.7s
  Hard resetting via RTS pin...
  =================
  Erase Successfully
  =================~~~~

hmm, that is strange. I've just verified with my M5Core2 and after burning UIFlow_Core2 v1.7.1-core2 it restarted with UIFlow just fine.

Have you tried to re-download the UIFlow firmware? (Although I don't think that is the issue as my burning shows exactly the same amount of data written as yours, and the hash is verified as well.)

Maybe try to erase your M5Core2 from within M5Burner first the burn again?

Thanks
Felix