Hi,
Where can I find the MicroPython screen driver for M5stickC and Plus?
I need numpy/ulab so I am using this firmware with good success.
Problem is, the only access to the screen I can get easily is via low-level ST7735 access, which only allows for the tiniest of characters in portrait mode only. Where is the LCD driver for MicroPython, with similar functionality to that in UIFlow?
Thanks!
Yes, @ajb2k3, it was you I was looking for! :-)
Now 1.6.5 is there in my original download, so I guess we don't have to download a new M5 burner any time there is a new release, thank you.
I should mention that M5Burner says that Base Micropython is v1.11 while os.uname() says it is in fact v1.12
Jack
Related to this request would be having the possibility of burning bare MicroPython from source, bringing in all M5Core drivers, and adding any user made apps, tables and pre-cooked code.
Where are they? You know, the exact same ones used in the Uiflow firmware? They are critical for byte code and freezes.
Plus clear instructions on how to compile the whole lot.
Thanks!
@m5stack said in micropython flowlib missing sources:
@tialm we has plan to open source all Unit code. but maybe it need wait the UIFlow2.0 version finish
How are you doing with this @m5stack?
The promise to be able to use MicroPython on bare metal is what attracted me to your gadget in the first place, I certainly wasn't expecting to have to start from scratch. You do realize that for those of us in this predicament the cores without input/output libs are just nice looking tiny plastic bricks, right? Based on this thread patience is wearing thin and you are losing customers.
You can share with a click of the mouse those drivers that already work well in the current UIFlow (1.6.4), start with the basics (axp192, lcd, buttons,...) - and some instructions on how to build/freeze them in.
No need to get them perfect, just do it.
Thanks!
+1 for Thonny, works great. Only drawback is that it does not yet have debug functionality for MicroPython.
No, it's one of the main reasons why those who would like to run bare metal MicroPython are instead forced to use the bloated UIflow firmware, which has the relative unexposed 'lcd' driver within it in module 'm5stack'.
Over a year and still waiting for independent MicroPython versions of such modules ...
No, it's one of the main reasons why those who would like to run bare metal MicroPython are instead forced to use the bloated UIflow firmware, which has the relative unexposed 'lcd' driver within it in module 'm5stack'.
Over a year and still waiting for independent MicroPython versions of such modules ...
Is it possible that lcd.image expects an image smaller than the lcd? Perhaps it needs to be resized.
Have you tried displaying a small image?
+1 for Thonny, works great. Only drawback is that it does not yet have debug functionality for MicroPython.
Related to this request would be having the possibility of burning bare MicroPython from source, bringing in all M5Core drivers, and adding any user made apps, tables and pre-cooked code.
Ok, so after 10 days we have:
I'd be interested to hear from more people. M5Stack, do you have an idea of the distribution of operating systems for the community at large?
A good mix so far, interesting. Feel free to add your own, oh silent reader ;-)
I'll start. I use
2 = MicroPython
OK it works. So for future reference this is what I did:
From now on whenever you turn it on the Stick will run boot.py and then main.py in the /flash directory.
If when it's so running you attach the device to a computer via the USB cable, you can interrupt whatever it is doing by starting Thonny and hitting ctrl-F2 (Stop/Restart Backend), which will bring up the MicroPython REPL prompt. Cool.
I am curious about software platform usage in M5Stack devices, so here is my poll, just reply with the number that applies to you:
The figures on each line are the number of posts shown for each in the forum today.
Thanks for participating
Jack
Excellent, I will try that, thank you very much.