Hello,
tryed you example code on my ESP32D0WDQ6.

display.pixel(120, 120, st7789py.RED)

display.pixel(120, 120, st7789py.YELLOW)

But display always green.

It is a ST7789V not a ST7789 Display

http://www.lilygo.cn/claprod_view.aspx?TypeId=21&Id=1128&FId=t28:21:28

How to fix this ?
Thanks

Hi @devbis

While using this driver with the T-WATCH S3 I ran into the problem that the display is rotated 180 degrees.
Reading your code and the datasheet of the device, I tried to set MADCTL_MX and MADCTL_MY in the MADCTL register, however while in this way I can see the device oriented correctly, there is a odd offset: it shows only 2/3 of the display 240x240 area. I don't know if it's some issue with the scrolling feature of the chip or what. I wonder if you know anything about it. Thanks.

Currently:
def write(self, command=None, data=None):
"""SPI write to the device: commands and data"""
self.cs_low()
if command is not None:
self.dc_low()
self.spi.write(bytes([command]))
if data is not None:
self.dc_high()
self.spi.write(data)
self.cs_high()

Was able to fix it to work by changing to:
if data is not None and data != b'':

Both regular nulls and empty byte strings are passed to the function.

I'm trying to display Bitmaps on the Raspberry Pi Pico using the Waveshare display (https://www.waveshare.com/wiki/Pico-LCD-1.14).
I convert a 240x135 image to BMP (24 bits) and then I convert it using imgtobitmap.py.
Image appears always yellowish: I mean image looks like the BLUE is missing.
I edited the library (st7789py.py) at row 803, maybe it would be

buffer[i + 1] = color & 0xff

instead of

buffer[i + 1] = color_index & 0xff

?

Anyway images still not looks good, even if I chose the maximum value for Bit x Pixel (5, values greater than 5 causes a memory error in Thonny since the generated file is too large).

Hello, thank you for writing this driver. Initially I used it with MicroPython SoftSPI, and performances where terrible. I did some profiling and found that it was the SoftSPI implementation itself that is so show, but at least with the ESP32-S3, if we switch to the hardware SPI, it goes from 1100 ticks to fill the screen to... 53! Basically more or less the performance of the C driver if I understand correctly.

Now the trick is that sometimes you can use the SPI() constructor and still use the SoftSPI() thing (and get a deprecation message). This depends on the first parameter, that must be a number, the hardware SPI identifier basically. To really use the hardware SPI, you need to do something like that when constructing the object:

    # Our display does not have a MISO pin, but the MicroPython
    # SPI implementation does not allow to avoid specifying one, so
    # we use just a not used pin in the device.
    spi = SPI(1, baudrate=40000000, polarity=1, sck=18, mosi=13, miso=37)
    display = st7789.ST7789(
        spi, 240, 240,
        reset=False,
        dc=Pin(38, Pin.OUT),
        cs=Pin(12, Pin.OUT),
    )
    display.init()

Note that the S3 seems able to use any pin for hardware SPI! I don't think that before ESP32-S3 it was like that, but I'm not sure.

I hope this helps! And I believe it would be cool to document this in the project README file. Others may benefit from this information.

File "", line 28, in
ImportError: no module named 'fonts'

Hi. Thanks you so much for post this "slow" MicroPython module. Is enough quick for my modest project with on ESP32.

So, I can't understand to use the blit_buffer method. What is the image format for the buffer. Do you have a exemple or a link please?

Thanks you!!

Hello Ivan
I am using an ESP 32 TTGO T Display board and the screen stay black
I have to add before calling display.init() these 2 instructions:

backlight= machine.Pin(4)
backlight.value(1)

to get the display visible
I have looked inside your driver and i don't see any backlight set

Kindly
Dan