ESP32-2432S028-R

[henry25005]

Hi,
even if I am a newbie, I would appreciate some help..
I have stuck up with this named board and activating the display, touch and sd-card. While setting HSPI in hardware section, and CS-Pin to 15 and DC to Pin 2 in the display-device, the display works fine. But I am not able to activate neither the touch nor the sd-card. In some posts I have read, the SPI can handle up to three devices, only the CS Pin has to be adapted. One tutorial names GPIO5 for the sd-card, and another GPIO-0 for the touch, but it does not work at all...
Every help is welcome..
If I have overlooked same posts, please be patient, I 'll promise to improve...
Greetings, Henry

[Ath]

Do you have a link to the (exact) board you are using?

[TD-er]

Maybe there is some more info in this discussion by the Tasmota team?
https://github.com/arendst/Tasmota/discussions/17939

[Ath]

This Reddit link has a reply by im-ptp (have to scroll down a bit) that quite accurately lists all GPIO pins used. It shows that the 3 SPI devices all use different SPI pins, and currently ESPEasy only supports a single SPI bus...
The display controller seems to be a somewhat special variant of the ILI9341, you could try using the ILI9342 setting of the ILI934x/ILI944x plugin.

[henry25005]

Maybe there is some more info in this discussion by the Tasmota team?
https://github.com/arendst/Tasmota/discussions/17939

HI,
thank you for your quick response. In fact, I tried this source before. The problem is, with ESP-EASY, I do not find the possibility to configure the second SPI. In my opinion, ESP-EASY wants to run several devices, display and touch, on the same SPI.. Only adapting the named CS-Gpio does not work..

Thanks..

[TD-er]

Yep, I have not yet added the functionality to select which SPI bus to use as that wasn't really needed upto now.
But with the newly added support for other ESP32 variants and also some products being sold recently (like the Shelly pro 4PM) there is for sure a need to select which SPI bus to use.

However this is not yet included and it might need quite some code changes to add it as you really need to take care of what calls can be made when certain SPI busses are being addressed.
I know Theo Arends from Tasmota has spent quite a lot of time to re-implement GPIO extender support for the Shelly pro 4PM as this one is also used to select CS signals for various SPI devices.
So you need to address a SPI device during low-level SPI communications.