Adding investigation, this seems to happen only if you upload to the core2 an empty project.

@world101 hi!

Well linux is a wide word. I am on chromebook, it does have linux, but it is arm architecture. Also wont run on raspberry as far as i know. Pops out a lot of errors, i tried installing as much support libraries as i could.

Would it be possible to get the firmware from M5Burner as to make possible for those of us that can not run m5burner on our machines?

That way we could load them with esptool or similar.

Thanks

Hi M5Stack,

The Core2 uiflow 1.7.2 firmware has following problem:

Description: The menu for ui flow on the m5core2 (the one to switch applications or go into setup) Its speed is too fast, making it imposible to make a selection on time.

Version: 1.7.2

Expected behavior: The time before uiflow starts running the selected mode should take longer so the user can make a selection.

Tested Hardware: M5stack Core2 for AWS, with defaul base.

Thanks.

I do not think you have a defective unit.

The thing is that uiflow is kept running in loops and when you try to flash with estool, or connect with rshell that unit does it in pauses. The same thing happens if you connect to a StickC (uiflow loaded) with rshell.

If you flash a generic Micropython and then try to flash again with esptool this should not happen as Micropython with out running any heavy app is not interrupting.

Hi! I flashed mine with uiflow and then micropython, all worked.
Core2 for AWS is just a normal Core2 but wth the base for AWS that also works perfectly with uiflow. I can control the leds and everything. the only difference with the other Core2 is the color and the base for AWS witch has a secure "element" that you can use or not use.

StickC/Plus do not have BLE option because of the limitations, remember your are loading a big chunk of code called uiflow into it, and besides that you are trying to add BLE.

All this is accessible directly by Micropython code directly. It is not that the StickC/Plus can not do it. It can, is just that the BLE libraries are not included in the StickC/Plus firmware.

The problem i think is that last uiflow mode selection is too quick and does not wait enough for the menu to make a change. I liked how on the StickC, you coul press button B and reset. that way you could force to change mode option.

Hope they fix this. it is just matter of adding time to the menu or as you said a cancel or back option.