DMA on ESP-WROOM-32

[Driver55]

Hello everyone.
I've been using this library for a few days and I wonder if anyone has managed to get DMA communication working with this library.
I'll start by saying that the examples without DMA works all , but none of the ones that require DMA works.
(eg SpriteRotatingCube.ino or BouncyCircles.ino).

I use the following configuration:
Library TFT-eSPI Ver. 2.5.43
Arduino IDE Ver. 2.3.4
ESP-WROOM-32
Display ST7789 SPI-Interface (without CS and only SDA for I/O).
Using VSPI as interface

#define TFT_MISO -1
#define TFT_MOSI 23
#define TFT_SCLK 18
#define TFT_CS -1 // Chip select control pin
#define TFT_DC 2 // Data Command control pin
#define TFT_RST 4 // Reset pin (could connect to RST pin).

Can anyone help me??

[Basitadam]

Currently for ESP32, DMA works only on -S3 (with a small modification to s3 processor source file)

[Driver55]

Currently for ESP32, DMA works only on -S3 (with a small modification to s3 processor source file)

thanks for the reply.
I will try to integrate a solution and if positive, I will report it

[Basitadam]

Take a look at this post : https://github.com/Bodmer/TFT_eSPI/discussions/3652

[roelvan]

Take a look at this post : https://github.com/Bodmer/TFT_eSPI/discussions/3652

404 link

[Tawank]

#3652
this should work

[Driver55]

I'm back on the topic to update the problem:

The 1st use of the library I did it on a low-cost 1.3" display with ST7789 controller. (see image).
Originally this display does not have a CS pin. Inside the printed circuit board this pin is set directly to 0V.
In addition it only has the SDA signal for data communication.
In this configuration the library works well except for the DMA.
For my personal curiosity, I modified the display by bringing out the CS signal.
see:
https://www.instructables.com/Adding-CS-Pin-to-13-LCD/

By doing this it also works with the use of the DMA. All the other displays used in the tests (ST7789V and ILI9341) with CS signal have never presented any problem.
I have only one doubt about this behavior related to the CS signal, and I think it may be linked to the revision of the display controller, although this doesn't explain everything.

Does anyone have other explanations?