- Because we dont (yet) have enough drivers for this chip.. :-)
These Drivers have methods for both SPI
and I80
(I8080
) busses, using the inbuilt MicroPython driver for spi
or the I80
library from Brad Barnett's mpdisplay.
They were (originally) created to be used with my microPyEZfonts system in an existing project that I was adapting with a vibrant color display to replace a faded monochrome OLED one.
They have been well tested on 3 devices now; a T-Display Touch (ESP32-S3, I80), a T-Watch 2020 (ESP32, SPI) and a loose IPS display module attached to a ESP32-C3 devboard via SPI.
Note: If you have a 240x24 or 320x170 display these drivers really need a firmware with SPIRAM (PSRAM) enabled; these are available in the main download site where the generic firmwares have additional SPIRAM builds available on the same page. Although these drivers will just about load and run without it, the framebuffer will be using over 100K of memory; there simply is not enough left over for any meaningful program.
- Photos dont really do justice to how good the IPS panel on the T-Display looks in reality.
There is a history to this driver, and the micropython st7789 drivers in general..
- @devbis originally published a pure micropython driver supporting a limited range of displays here: https://github.com/devbis/st7789py_mpy/
- They then refined that into a fast firmware based driver: https://github.com/devbis/st7789_mpy
- @russhughes took this and extended it for other screens and features at: https://github.com/russhughes/st7789_mpy; they have actively maintained and developed that driver, and it is a good choice for SPI based displays.
- In parallel to this @bdbarnett was developing https://github.com/bdbarnett/mpdisplay; which incorporates elements from the the above drivers as part of a much larger, more versatile and generally excellent display subsystem supporting many different graphics hardware combos (not just st7789); it also has touchscreen, multiple font systems and graphics primative support.
- More recently the ESP32-S3 arrived with hardware I8080 bus support, as well as some devices that use this; eg the Lilygo T-Display. Russ Hughes then developed https://github.com/russhughes/s3lcd, a hardware driver that takes advantage of this. It requires custom firmware, but I have tested it and it is fast.. very fast.
- Work from the above has also landed in the micropython LVGL ecosystem.
- And, filling the slots in-between, others have also developed and published variations on this theme, such as I do here.
I'm being serious; The drvers given here were made for my own very simple projects, and they do not scale very well for more complex use.
If you need speed or lots of free memory; and using a custom firmware is practical for you:
- S3LCD is an excellent driver; if you have a i80 bus.
- LVGL and other projects also have good st7789 support via frmware drivers; Russ has also contributed to those; if you are building a full GUI check them out.
MPDisplay does not (necesscarily) need custom firmware, and supports the I80 bus version of the st7789. It also has touchsecren drivers and lots of font utilities incorporated into it. I have used it and it works very well, but is a bit complex to set up and understand. And you may be installing a lot of code for feature you will never use.
Both support SPI and I80 busses; one is smaller and more basic than the other.
- support for PWM backlight is also added to both
- Fully supports MicroPython's built in frameuffer, with no additional drawing, scrolling or font writng features.
- Essentially a drop-in replacement for any other framebuffer driver; and is aimed at people adapting code from simpler monochrome displays such as SSD1306's etc.
- https://github.com/echo-lalia/st7789fbuf
- This is in turn a modified version of Russ Hughes st7789py driver(s).
- There are a number of additional drawing and font handling features provided for this that can make use for GUI and large displays more convenient
- I do not document the additional drawing methods, see the documentation for this in the site above and the MPDisplay site.
- Very heavy on memory; pretty much requires having PSRAM enabled
- Not very extensively tested.
Both of these divers use a lot of memory for the framebuffer; for 320x170 and 240x240 displays this is just over 100K of memory; with these large displays it may prove impossible to use these unless you have PSRAM (SPIRAM) enabled in the micropython firmware.
- SPI RAM enabled versions of the generic micropython firmware are available on the main MicroPython download site.
- The smaller (240x135) display I tested with only uses 60K and did not have any memory issues on a ESP32-C3 with the generic esp32-c3 (non SPIRAM) firmware.
The more advanced driver has additional useful methods for use with large color displays; it is derived (via a third party) from the main MPDisplay driver; these are documented here
See the examples (demo's) for a good example of using these.
First; import the driver you will be using:
import st7789_purefb as st7789
or
import st7789_fb_plus as st7789
The init()
methods for both the basic and full drivers are identical.
This will be dictated by your hardware; when this was written the only common i80 bus device is the Lilygo t-display touch
This driver uses the (fast) machine.SPI
inbuilt bus interface.
Init with:
display = st7789.ST7789_SPI(spi,
width, height,
reset=None,
cs=None,
dc=None,
backlight=None,
bright=1,
rotation=0,
color_order=BGR,
reverse_bytes_in_word=True)
The I80 bus driver needs to be added to your project; to do this simply copy the whole i80
folder to the root of your device.
- This bus driver is rather nice; it was written by @bdbarnett and the home repo for it is here. I use a older version bundled into a single library.
Init with:
display = st7789.ST7789_I80(i80,
width, height,
reset=None,
cs=None,
backlight=None,
bright=1,
rotation=0,
color_order=BGR,
reverse_bytes_in_word=True)
The only difference between SPI and I80 init is that for SPI the DC
pin can be supplied, but is not defined for I80 use.
spi OR i80 (bus): bus object **Required**
width (int): display width **Required**
height (int): display height **Required**
reset (pin): reset pin
cs (pin): cs pin
dc (pin): dc pin
backlight (pin) or (pwm): backlight pin
- can be type Pin (digital), PWM or None
bright (value): Initial brightness level; default 'on'
- a (float) between 0 and 1 if backlight is pwm
- otherwise (bool) or (int) for pin value()
rotation (int): Orientation of display
- 0-Portrait, default
- 1-Landscape
- 2-Inverted Portrait
- 3-Inverted Landscape
color_order (int):
- RGB: Red, Green Blue, default
- BGR: Blue, Green, Red
reverse_bytes_in_word (bool):
- Enable if the display uses LSB byte order for color words
After init you draw on the framebuffer as appropriate using the stock framebuffer methods (and extended methods for fb_plus
)
To write the framebuffer contents to the display you need to call:
display.show()
You can also use:
display.rotation(int; 0->3)
This will dynamically change the screen rotation (orientation) using the same values as documented for init()
.
- You cannot swap between portrait and landscape modes. If the display width and height differ you can only rotate by a full half turn.
Finally there is a display.inversion_mode(bool)
that can invert the display colors resulting in a 'negative' image; probably not very useful.
The backlight
pin is optional; if value is None
no attempt will be made to use it.
Control it via the backlight
method:
display.backlight(brightness)
if brightness
evaluates to a boolean the backlight will be set to either 0
(off) or 1
(on) as appropriate.
If using a PWM pin you can set brightness
to a float between 0
and 1.0
to set the backlight brightness (PWM factor).
The bright
init() argument allows the initial backlight state (brightness; bool/float) to be defined.
There are several demo examples; please make sure to read the comments in them.
- See also the 'marquee' and 'nametag' examples in the
doc
folder.
- Again; photographing these displays is hard; this also looks better in real life.
A video of the marquee demo running on a T-Display touch is on Youtube at: