ILI9341 (with and without DMA support)

To use it with the standard repo SPI library comment out these 3 lines in the header file:
#define SPI_16BIT
#define SPI_MODE_DMA 1
#define SPEED_UP 1 // Enables extra calculations in the circles routine to use fastVLine and fastHLine, only in DMA mode.

To use DMA, uncomment those lines, and download the SPI library from my repo:
https://github.com/victorpv/Arduino_STM … es/SPI/src

Once all is tested the changes to the SPI library will be integrated in Roger’s repo.

Please post here if you have any issues with DMA or non-DMA.

Would it be easy to merge ?

(I don’t have ILI8341 yet, maybe I should purchase one … )

I’ve a 3.2″ 320×240 ILI9320

Are they similar to the ILI9341 library ??

I just wanted the screen working first before focusing on the touchscreen…

Thanks

Stanley

TFT320x240-2 by stanley_seow, on Flickr

TFT320x240 by stanley_seow, on Flickr

Got the 2.2″ TFT ILI9341 working on SPI1 pins…
How do I access the SPI2 and SPI3 pins coming from UNO with ONLY 1 SPI sets of pins..

I had to look at the Mini STM32 to lookup the SPI1 pin names..

Thanks

Got the 2.2″ TFT ILI9341 working on SPI1 pins…
How do I access the SPI2 and SPI3 pins coming from UNO with ONLY 1 SPI sets of pins..

I had to look at the Mini STM32 to lookup the SPI1 pin names..

Thanks

Got the 2.2″ TFT ILI9341 working on SPI1 pins…
How do I access the SPI2 and SPI3 pins coming from UNO with ONLY 1 SPI sets of pins..

I had to look at the Mini STM32 to lookup the SPI1 pin names..

Thanks

The DigiX/DUE was 24609 msec , 21secs slower than the STM32 …

Any idea why this happens ??

Try opening the serial terminal window and running the test again

Try opening the serial terminal window and running the test again

Its something we need to fix, but it didnt seem urgent, so I we forgot about it.

I did some investigation into what was causing it, but it wasn’t obvious why it was happening. However I think we have a work around, as it is possible to determine the connection state of the Serial USB.

So the work around is to make the internals of the Serial USB class, ignore any chars that are printed (or written etc) to it, unless the PC terminal is open.

But we have yet to test in practice if this works, and whether it only works on the PC and with the IDE’s terminal or works for other terminal programs and on OSX and Linux…

Things like this are not easy to fix as we need to test on multiple configurations.

To use it with the standard repo SPI library comment out these 3 lines in the header file:
#define SPI_16BIT
#define SPI_MODE_DMA 1
#define SPEED_UP 1 // Enables extra calculations in the circles routine to use fastVLine and fastHLine, only in DMA mode.

To use DMA, uncomment those lines, and download the SPI library from my repo:
https://github.com/victorpv/Arduino_STM … es/SPI/src

Once all is tested the changes to the SPI library will be integrated in Roger’s repo.

Please post here if you have any issues with DMA or non-DMA.

To use it with the standard repo SPI library comment out these 3 lines in the header file:
#define SPI_16BIT
#define SPI_MODE_DMA 1
#define SPEED_UP 1 // Enables extra calculations in the circles routine to use fastVLine and fastHLine, only in DMA mode.

To use DMA, uncomment those lines, and download the SPI library from my repo:
https://github.com/victorpv/Arduino_STM … es/SPI/src

Once all is tested the changes to the SPI library will be integrated in Roger’s repo.

Please post here if you have any issues with DMA or non-DMA.

data 16 pins + 4? 6800/8080 + 4 sdcard + 4 or 5 touch + 1 backlight + power 2 ==> 32 as a minimum?

there seems to be choice in the data format though.
sdcard and touch are likely to be spi interfaces
shield types – uno maybe 8 bit data, i suspect mega shields may well be 16 bit data, again sdcard and touch on spi

connector pin layout – Oh let me count the ways matching a display to a board to the fsmc pinnings to software – i’m still working on that, try a google image search for “tft connector”

reading sources of utft, u8glib or adafruit libraries may give you some insight about initialisation and use of the display, minimally what needs supplying is the init command sequence and plot(x,y).
the rest is fonts and graphics

stephen