@Yan-Yezi
yes it can be coding in UiFlow 1:
https://docs.m5stack.com/en/uiflow/blockly/module/commu

@teastain Today I will try connecting up the 5V piece to it . Thanks for the help

@jarain78 Hello,

I'm currently facing the same pb with my M5dial:

Any idea ?

URL_REFRESH='https://api.netatmo.com/oauth2/token' params={ 'grant_type':'refresh_token', "client_id":'xxx', "client_secret":'xxx', "refresh_token":'xxx' } rep=requests.post(URL_REFRESH, data=params)

=> TypeError: object with buffer protocol required

I have the same problem. It is insanely annoying. I have a new device in my hand and I can't do anything about it.

You need a computer with internet access to configure the M5GO

@toxicavenger now you go to UIFlow2 and create code for it

@camille-chomant
I think it's the same situation as me.
My M5 DinMeter also works using Arduino IDE. Example programs and homemade programs work well.
However, I burn firmware to use UIFLOW, see the message Successful, and nothing appears on the screen. When I run or download the program from UIFLOW, I get a message saying Successful, but it still doesn't work.

For the m5stack fire you need to follow these steps

Remove all modules, leaving only the host Then try to lower the baud rate when burning If there are wires, you can short-circuit G0-GND before powering on the device and then power on again.0_1711007646460_432299571_430472252787300_1867478767739245481_n.jpg

You don’t as there have been so many issues with it that it’s been removed

No, The ESP32S3 does indeed have 2 com ports but you have to put the Core S3 into Boot mode to program it.

https://youtu.be/2K4hHGtskAU

In most cases it's the USB cable or the Host PC that is the problem. Windows has issues with its come port communications with S3's. huh, what, All firmware is available in M5Burner unless you made it yourself then you should be backing up your own files. Never heard of CoreS3 TP Upgrade V0.5.exe
M5Burner is the program for burning firmware.

@rafciuk When the connecting screen appears, Hold the reset button in for around 5 seconds. it takes some practice but the grey is not dead just soft bricked.
Another option is to try using arduino to upload a blank sketch before trying M5Burner again.

I have accidentally uploaded the wrong firmware before and had to reset in the above manner.

The device is not dead it just that the core and core2 use different screens and so you cant see what it is doing.

Have you installed the usb driver for the S3 based devices?