This is great news! The old MicroPython in M5Stack firmware was the last remaining obstacle holding me from removing some ugly workarounds in Thonny's MicroPython backend.

I also like the decision to use common firmware for all M5 devices and the fact that now one can use the same esptool arguments as for other ESP32 devices. This means Thonny users can use the built-in flashing dialog for M5 devices.

According to my quick initial test Thonny is happy with the new firmware. I tried the original gray M5Stack and Atom Lite. With the gray M5Stack even the "paste" communication mode, which for some reason did't work with M5 earlier firmwares, now seems to work without problems. With Atom Lite it still causes problems, which I'll investigate later.

I'm considering adding a separate "MicroPython (M5Stack)" back-end in the upcoming Thonny 4.0, but this is warranted if it came together with M5-specific MicroPython stub files (.pyi) for autocompletion and static analysis (one of the main theme of Thonny 4.0 will be improved autocompletion).

This is where you could help me. Most likely I don't find time for compiling the stubs from the scarce documentation myself, but if you created the pyi-files describing M5-specific modules, I would include them in Thonny 4.0 under "MicroPython (M5Stack)" back-end.

Keep up the good job!

Aivar
(the main author of Thonny IDE)

This is great news! The old MicroPython in M5Stack firmware was the last remaining obstacle holding me from removing some ugly workarounds in Thonny's MicroPython backend.

I also like the decision to use common firmware for all M5 devices and the fact that now one can use the same esptool arguments as for other ESP32 devices. This means Thonny users can use the built-in flashing dialog for M5 devices.

According to my quick initial test Thonny is happy with the new firmware. I tried the original gray M5Stack and Atom Lite. With the gray M5Stack even the "paste" communication mode, which for some reason did't work with M5 earlier firmwares, now seems to work without problems. With Atom Lite it still causes problems, which I'll investigate later.

I'm considering adding a separate "MicroPython (M5Stack)" back-end in the upcoming Thonny 4.0, but this is warranted if it came together with M5-specific MicroPython stub files (.pyi) for autocompletion and static analysis (one of the main theme of Thonny 4.0 will be improved autocompletion).

This is where you could help me. Most likely I don't find time for compiling the stubs from the scarce documentation myself, but if you created the pyi-files describing M5-specific modules, I would include them in Thonny 4.0 under "MicroPython (M5Stack)" back-end.

Keep up the good job!

Aivar
(the main author of Thonny IDE)

@devros Thanks! Flow firmware works nicely!

I'm able to use display.TFT, but I'm looking for the API described at https://github.com/m5stack/M5Cloud#micropython-api and https://github.com/m5stack/M5GO

I'm trying to get "offline" (ie. no-flow, no-cloud) MicroPython working in Core dev kit (gray).

I tried esp32 and esp32_all from here: https://github.com/m5stack/M5Stack_MicroPython/tree/master/MicroPython_BUILD/firmware. With these I can connect to MicroPython REPL but I can't import neither m5stack.lcd nor simply m5stack.

I also tried v0.4.0 from here https://github.com/m5stack/M5Cloud/tree/master/firmwares/OFF-LINE, but with this I was not able to connect to the REPL over serial. Is this firmware supposed to present the REPL?

Which firmware should I use? Or should I add the module for LCD (and other extras) separately?