Forum Rule: Always post complete source code & details to reproduce any issue!
Results 1 to 4 of 4

Thread: LCD ITDB18SP TFT with T3.0

  1. #1

    LCD ITDB18SP TFT with T3.0

    I got one of these lcd's lying around.

    http://robotics.org.za/index.php?rou...product_id=584

    How difficult would it be to use it with a teensy3?

  2. #2
    Senior Member PaulStoffregen's Avatar
    Join Date
    Nov 2012
    Posts
    21,467
    Did you try compiling the code? Are there errors?

  3. #3
    Yes i did.

    This report would have more information with
    "Show verbose output during compilation"
    enabled in File > Preferences.
    Arduino: 1.0.5 (Windows NT (unknown)), Board: "Teensy 3.0"
    C:\Program Files (x86)\Arduino\libraries\UTFT\UTFT.cpp:76:4: error: #error "Unsupported ARM MCU!"
    C:\Program Files (x86)\Arduino\libraries\UTFT\UTFT.cpp: In constructor 'UTFT::UTFT(byte, int, int, int, int, int)':
    C:\Program Files (x86)\Arduino\libraries\UTFT\UTFT.cpp:218:10: error: cannot convert 'volatile uint8_t* {aka volatile unsigned char*}' to 'volatile uint32_t* {aka volatile long unsigned int*}' in assignment
    C:\Program Files (x86)\Arduino\libraries\UTFT\UTFT.cpp:220:10: error: cannot convert 'volatile uint8_t* {aka volatile unsigned char*}' to 'volatile uint32_t* {aka volatile long unsigned int*}' in assignment
    C:\Program Files (x86)\Arduino\libraries\UTFT\UTFT.cpp:222:10: error: cannot convert 'volatile uint8_t* {aka volatile unsigned char*}' to 'volatile uint32_t* {aka volatile long unsigned int*}' in assignment
    C:\Program Files (x86)\Arduino\libraries\UTFT\UTFT.cpp:224:11: error: cannot convert 'volatile uint8_t* {aka volatile unsigned char*}' to 'volatile uint32_t* {aka volatile long unsigned int*}' in assignment
    C:\Program Files (x86)\Arduino\libraries\UTFT\UTFT.cpp:228:12: error: cannot convert 'volatile uint8_t* {aka volatile unsigned char*}' to 'volatile uint32_t* {aka volatile long unsigned int*}' in assignment
    C:\Program Files (x86)\Arduino\libraries\UTFT\UTFT.cpp:242:11: error: cannot convert 'volatile uint8_t* {aka volatile unsigned char*}' to 'volatile uint32_t* {aka volatile long unsigned int*}' in assignment
    C:\Program Files (x86)\Arduino\libraries\UTFT\UTFT.cpp:244:11: error: cannot convert 'volatile uint8_t* {aka volatile unsigned char*}' to 'volatile uint32_t* {aka volatile long unsigned int*}' in assignment
    C:\Program Files (x86)\Arduino\libraries\UTFT\UTFT.cpp:246:10: error: cannot convert 'volatile uint8_t* {aka volatile unsigned char*}' to 'volatile uint32_t* {aka volatile long unsigned int*}' in assignment
    C:\Program Files (x86)\Arduino\libraries\UTFT\UTFT.cpp:248:11: error: cannot convert 'volatile uint8_t* {aka volatile unsigned char*}' to 'volatile uint32_t* {aka volatile long unsigned int*}' in assignment
    C:\Program Files (x86)\Arduino\libraries\UTFT\UTFT.cpp:252:11: error: cannot convert 'volatile uint8_t* {aka volatile unsigned char*}' to 'volatile uint32_t* {aka volatile long unsigned int*}' in assignment

  4. #4
    Member Dawnmist's Avatar
    Join Date
    Nov 2012
    Location
    Australia
    Posts
    51
    You may find this thread useful: http://forum.pjrc.com/threads/18002-...1289-with-utft

    It's the UTFT library with a few modifications to get it compiling/using the teensy 3 pins. While the thread is discussing a different end display, the modifications should work to make it usable by any of the 8/16 data line displays supported by UTFT (but not the serial ones - you'd need to provide the teensy3-equivalent functions that were not yet written for those).

    It isn't well optimised yet - while we could use Port D/Port C for the 16-bit parallel lines and reduce the write to 2 cycles, using pins 0-7 of Port C means we lose access to the SPI pins for SDCard access.

    Paul - Would it be possible to write B0-3,B16-19 in a single write cycle - if so, how would we do that? Using D0-7,B0-3,B16-19 for the data lines would leave access to an SDCard for storing images to be displayed on the TFT, while still allowing a drop to 2 writes instead of 16. If not, then what would be involved in writing to the two segments in a pair of cycles (letting it drop to 3 writes)? Or would B0-3+C0-3 be better (still leaves the first of the SPI CS lines available)? Note: I did see this post here: http://forum.pjrc.com/threads/23950-...ll=1#post34168 - but it loses the SPI port pins...I would like to duplicate that but without losing access to SPI.
    Last edited by Dawnmist; 08-12-2013 at 08:04 AM.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •