@arno well already 8 months since zigbee was on sale and guess what ;) still no UIFlow
@m5stack i hope ZigBee will born nice and shine after 9 month's of development.

About C3 - you can use pure micropyhon its already there:
https://github.com/micropython/micropython/releases/tag/v1.17

@ajb2k3 said in UIFlow 1.8.6:

@mati said in UIFlow 1.8.6:

@m5stack said in UIFlow 1.8.6:

we will update the tutorial as soon as possible

in my case all is working fine on core2 LCD module is connected over PortA

Have you updated the firmware on the colour lcd?
I get the framebuf error if I don't add the init screen block

Nope, just out of the box and go. First try with Atom lite fail but on core2 and init in the setup all looks legit.

@m5stack said in UIFlow 1.8.6:

we will update the tutorial as soon as possible

in my case all is working fine on core2 LCD module is connected over PortA

LCD color vs Atom lite
Traceback (most recent call last):
File "flow/m5cloud.py", line 82, in _exec_fun
File "<string>", line 20, in <module>
File "units/_lcd.py", line 128, in fill
AttributeError: 'Lcd' object has no attribute 'frame_buf'

Traceback (most recent call last):
File "flow/m5cloud.py", line 82, in _exec_fun
File "<string>", line 20, in <module>
File "units/_lcd.py", line 128, in fill
AttributeError: 'Lcd' object has no attribute 'frame_buf'

Traceback (most recent call last):
File "flow/m5cloud.py", line 82, in _exec_fun
File "<string>", line 22, in <module>
File "units/_lcd.py", line 169, in show_on
File "i2c_bus.py", line 101, in write_mem_list
MemoryError: memory allocation failed, allocating 64800 bytes

ahh one more think with i just recall :D
when my core 2 was at home by using M5Burner by mistake i just preload UIflow for Core not for Core2 and this was a same loop as you can see

@edawen said in Product failed. Burning, Downloading, finding where to get API get.:

@mati said in Product failed. Burning, Downloading, finding where to get API get.:

a

Putty doesnt do any good. I did find, by accident, that if i went into monitor, and pressed Reset instead of Send, it would print out this ;

=================
COM8
=================
ets Jul 29 2019 12:21:46

rst:0x1 (POWERON_RESET),boot:0x17 (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:DIO, clock div:1
load:0x3fff0018,len:4
load:0x3fff001c,len:1044
load:0x40078000,len:8896
load:0x40080400,len:5816
entry 0x400806ac
ets Jul 29 2019 12:21:46

rst:0x1 (POWERON_RESET),boot:0x17 (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:DIO, clock div:1
load:0x3fff0018,len:4
load:0x3fff001c,len:1044
load:0x40078000,len:8896
load:0x40080400,len:5816
entry 0x400806ac
M5Core2 initializing...axp: vbus limit off
axp: gpio1 init
axp: gpio2 init
axp: rtc battery charging enabled
axp: esp32 power voltage was set to 3.35v
axp: lcd backlight voltage was set to 2.80v
axp: lcd logic and sdcard voltage preset to 3.3v
axp: vibrator voltage preset to 2v
[E][sd_diskio.cpp:739] sdcard_mount(): f_mount failed 0x(3)
OK
[E][sd_diskio.cpp:739] sdcard_mount(): f_mount failed 0x(3)
Addr:0x34 - Name:Axp192
I2C Axp192 Found
Addr:0x38 - Name:CST Touch
I2C CST Touch Found
Addr:0x68 - Name:IMU6886
I2C IMU6886 Found
Addr:0x51 - Name:BM8563
I2C BM8563 Found

I'm not sure what to Send, in monitor or Putty. This doesn't show up in Putty, as text or as garbage. There is no SD card inserted and it is at the red "SDCard Find failed" prompt on the Core2.

This is after I shutdown the PC, removed and deleted the driver and installed CP210xVCPInstaller_x64_v6.7.0.0, the same driver installed bu UIflow. M5Burner will still not work. I have not followed the Cold Start Method yet. That will be tomorrow.

Regards.

this proof there is a communication, with is fine but core2 is in the boot loop.
What about opening or to be more precision remove bottom where is a battery.
After opening inspect both buttons maybe one stuck and this is a problem with loop.

Hey @Edawen
bit strange, what about open COM8 via putty the is any output ?
In case on Core2 please open it and disconnect internal battery and try again.

But more or less this could be a service tickate case.

@kylecat1 Hey,

yes its could be old FW burned, i think i was the same with my unit,
go to https://docs.m5stack.com/en/quick_start/unitv2/update
and follow the guide.

@m5stack said in UIFlow 1.8.4:

We are very sorry, we are working hard to supplement the support of related modules

thx for reply, maybe all will be happy if we can see some roadmap with HW implementation.

@m5stack what about zigbee ? soon we gonna celebrate 5th month of waiting ;)