MicroPython Forum (Archive)

Thanks. The problem went away when I woke up this morning. This is not the first time I have found one of these kinds of devices to "settle down" over night. It doesn't make sense from my limited understanding of electronics, but whatever.

Thanks again.

PyBoard running 1.14. I copied ssd1306.py from latest to the board (not from 1.14 since I can't figure out how to download files from a tag on Github without downloading the entire source as a zip). Then I tried the following and got this error: MicroPython v1.14 on 2021-02-02; PYBv1.1 with STM32F40...

The Tile36 manual documents its included font, which offers all characters between 'space' and 'delete' (ASCII values 32-127). However, the exclamation point and the 'delete' solid box (as documented) don't appear on the device, despite the manual. Has anyone else noticed this?

Thanks.

The Tile36 has a command to set the RGB mode to either CREE or WE. I realize CREE is a brand, and in some fashion a particular hardware technology of LED, but what does it mean to choose between CREE and something else at the software level, and what does WE mean with respect to LEDs? As far as I ca...

The Tile36 manual describes how you can scroll the text buffer one of two ways, either with the init command anytime after initialization (\x01) or with a typical two-byte command (\x02\x2e). As far as anyone knows, is there any practical difference between these two commands that seemingly accompli...

The Tile36 manual specifies a command \x02\x11? where ? is a single parameter (a single byte), with the description "set scroll text". I have experimented with a variety of values here and recognize that it alters both the value of the text buffer and the behavior of the scrolling, but I can't reall...

Okay, thanks.

Is there any sort of guide or documentation to assist with installing MicroPython on a stand alone ARM processor? I'm not sure where or how to start. I realize it's a fairly broad and general question. I'm not asking for specifics here, rather a pointer to any preexisting writing on the subject, if ...

IT WORKED! Your command differed from mine in two ways. It explicitly stated the firmware size and it indicated a different firmware mode. So I tried it again, reverting each of those parts to my original command, and the part that is relevant is the -fm change. I can still use --flash_size=detect a...

Thanks!