SparkFun Forums 

Where electronics enthusiasts find answers.

Questions &/or issues related to products in the LCDs and OLEDs category should be posted in this forum.

While we do not have a wiring diagram available for this project, it should be fairly straightforward. All the displays in the blog post you are referring to share the same pins on the SPI bus (MOSI, SCLK, D/C, VCC and GND) and then each CS pin is broken out to an individual I/O pin. You can pretty much use any available I/O pin for CS with SPI and D/C is going to D5 in the example code for 10 displays. If you are going to try and follow along with the example code be aware that 1) it requires 10 displays to run that example and 2)the CS pins are defined in an array at Line 133.
Mark, thanks for the response.

I am new to ESP32 and have been struggling with the wiring to make SPI work even for the basic example of 'Drawing Basics' ... wmEALw_wcB

Would it be possible to explain how the Pins are assigned for ESP32 Thing Plus. Say for the

#define CS_PIN 4 // Used only if USE_SPI == 1
#define DC_PIN 5 // Used only if USE_SPI == 1

Which pin do I take from ESP32 ThingPlus for Chip select and DC - ?
The example says 4 and 5 , does that mean A4 and A5 on the break out board? So sorry to ask these basic questions

Thanks again.
To use this display in SPI mode, first, make sure you cut the jumpers shown in this photo from the "Hardware Hookup" section of our Hookup Guide. Next, just connect the SPI lines to their respective pins labeled on the ESP32 Thing Plus or by referencing the Graphical Datasheet.

As for the CS and DC pins, you can run those to (nearly) any available I/O pin on your ESP32 Thing Plus. For example, try using pins 14 and 15 and then adjust the #define functions to reflect those changes like this:
Code: Select all
#define CS_PIN 14 // Used only if USE_SPI == 1
#define DC_PIN 15 // Used only if USE_SPI == 1 
Finally, just make sure you have the USE_SPI function set to 1 for SPI. If you continue to have trouble, please take a few photos of your circuit and attach them to your reply and we can troubleshoot further.