The board was created (main controller ESP32-wroom) and we started the code. We figured out the library, but do not fully understand how it can work.
We're having a problem connecting to the SPI.
The fact is that we have the following connection for our esp32 board (it has 2 SPI - VSPI and HSPI):
The screen is connected to the pins:
e-ink HSPI
cs-15
mosi-13
dc-12
clk-14
bysy-27
another sensor module VSPI
ss-5
sck-18
mosi-23
miso-19
busy-17
When I use the Native to Heltec eink library I get problems because the library uses the call to SPI.** which by default uses pins VSPI.
But my physical connection is different.
I found out that GxEPD is very friendly and can contain specified contacts, i.e. if I create an object SPIClass mynamespi(HSPI); and I will transfer the object to the library, then maybe everything will work? Another good person suggested to me that the creator of the library is often here.
Yes, with GxEPD you can pass an instance of SPIClass to the constructor of GxIO_SPI.
This makes GxEPD easy to adapt to hardware with multiple SPI channels.
With the recent version of GxEPD2 you also have a similar option. See README.md.