... which approach would you start with?

The website you linked to has several examples for Raspi and Arduino. Study the code. Way down on the page are links to a schematic and the ST7789V2 datasheet.

Schematics are primitive, just level converters and a voltage regulator connected between the "public" interface to the outside world and the LCD controller. LCD backlight is PWM controlled by the outside interface (pin 1). Other signals look like I²C (SDA, SCL), there is also a chip select (CS), data/control switch (D/C), and a reset line (RST). Reading the Spec at the top of the web page lists SPI, not I²C as control interface. So SDA should be named MOSI, SCL should be named CLK, and having a CS line makes total sense with SPI. Note that there is no MISO, as usual for many LCDs. They are write-only devices.

On top of the website, you can see a timing diagram sending 16 bit RGB565 pixel data. This is how you write into display memory - pixel by pixel, with D/C set high. With a little bit of luck, there is a way to move to a selected pixel before writing, probably by setting D/C low.

The ST7789V2 datasheet starts with a lot of electrical stuff, the serial interface is documented in chapter 8.4 and following explaining low-level SPI, Commands are in chapter 9. Note that you can not read back from the display, the required data line (MISO) is not available at the outside interface.

So this is how I would start. Read the website, the datasheet, the example code. Example code often stinks and most times lacks any error checks. Datasheets omit little details and sometimes are plain wrong. Get used to it.

Alexander

--
Today I will gladly share my knowledge and experience, for there are no sweeter words than "I told you so". ;-)

In reply to Re: ST7789V2 LCD Controller by afoken
in thread ST7789V2 LCD Controller by Bod

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":



  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.