Open paulvk2 opened 6 months ago
Need more information to understand what plugins you're using etc.
For example, the TFT-eSPI plugin uses the libraries internal interrogator, and therefore would be configured within that library. So does the BSP touch plugin.
The only other plugin is the ArduinoLibrary based plugin, I am assuming that. However, someone will need to determine how the plugin needs to change in order to pass in other than the default bus, is it in the variable definition, here in the plugin:
Using the XPT2046 and the example code that works with the library is `` // Touchscreen pins
SPIClass touchscreenSPI = SPIClass(VSPI); XPT2046_Touchscreen touchscreen(XPT2046_CS, XPT2046_IRQ); `` So the option to fill in these details would be helpful This is for the CYD display (ESP32-2432S028) which has the touch IC on the forth spi bus VSPI they are very inexpensive and a number of sizes exist Regards Paul and thank you for such a quick reply.
If you add GFX_Library_for_Arduino for the ESP devices as selection it will simplify things as many displays are preconfigured for use . In the PDQgraphicstest example are Arduino_GFX_databus.h , Arduino_GFX_dev_device.h , Arduino_GFX_display.h , Arduino_GFX_pins.h . Arduino_GFX_dev_device.h contains a large number of displays by uncommenting the used display the configuration is taken care of and in the TouchCalibration example touch.h just needs the GPIO numbers used Regards Paul
With the ESP32-2432S028 and other similar displays the touch control chip is on the second buss of the ESP32 but tcMenu has no options when the TFT and touch are on different bus.