Shop OBEX P1 Docs P2 Docs Learn Events
TFT LCD with touchscreen breakout board - ILI9325 help needed — Parallax Forums

TFT LCD with touchscreen breakout board - ILI9325 help needed

ohVaNiLLaGoRiLLaohVaNiLLaGoRiLLa Posts: 33
edited 2013-09-30 17:04 in Propeller 1
I have recently gotten a tft lcd screen, http://www.adafruit.com/products/335, but I am having troubles getting it working. I have looked in the obex and have not been able to get any of the tft lcd objects that use the ILI9325 chip to work with this board which i knew would probably happen. I am trying to write my own object to control this board but I am not quite sure what I need it to do =/ There is an arduino tutorial for this board and I have looked over the code for that but I am still having issues understanding what needs to happen to get the screen up and running. The example code given for the arduino is here, https://github.com/adafruit/TFTLCD-Library. I believe the "pin_magic.h" is where most of the magic actually happens for controlling the ILI9325. Could anyone shed some light on what actually needs to happen to get this thing running?

another question I would like to ask is which language I should I attempt to write this in? spin or c++? I have always written my prop programs in spin but now since I can now use c++ to program it and the example code given for the arduino is very very similiar to c++ I was thinking maybe I should try that.

Comments

  • Dr_AculaDr_Acula Posts: 5,484
    edited 2013-09-30 17:04
    Lots of code on this thread http://forums.parallax.com/showthread.php/137266-Propeller-GUI-touchscreen-and-full-color-display?highlight=ili9325 including drivers in spin. We were using the display in 16 bit mode which takes about 20 propeller pins, but it fairly straightforward to change it to 8 bit mode.

    Getting the display to display something is the first challenge. The next problem we faced on that thread is that refreshing the display takes a long time, as the data for a full screen is more than the propeller memory. So sprites and icons need to either be read from an SD card (slow) or stored in external ram. Hence the reason we ended up in 16 bit mode as it was easier to dump data out to the display.
Sign In or Register to comment.