This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

CCS/EK-TM4C1294XL: Working with FT800 EVE display

Part Number: EK-TM4C1294XL
Other Parts Discussed in Thread: BOOSTXL-K350QVG-S1

Tool/software: Code Composer Studio

Hi, 

i have a TM4C1294XL launchpad, and i want to work with a FT800 EVE screen,

but there are no support libraries,

can i get help with this?

  • Raynard Omongbale said:

    want to work with a FT800 EVE screen,  but there are NO support libraries 

    Perhaps this should have been noted (prior) to your (assumed) selection of the FT800 series.    Had you noted that (other) ARM MCUs offer varying degrees of 'FT800 support?'

    My firm HAS Succeeded in this effort - but w/this vendor's simpler (and lower cost) 'TM4C123' device!   (we have no interest in the TM4C129 family.)

    If/when interested - contact us via this forum's 'PM' option (accessible via your forum sign-on/editing page) as such discussion proves 'outside' accepted forum practices/guidelines...   (to which - we always - comply!)

  • Hello Raynard,

    We don't have any related collateral on our end, but it looks like there is an application note on the product page for how to use the FT800 with ARM cores. From what I read, the interface to the ARM MCU for the system would just be SPI in the end, so you should be able to use the TM4C instead if you want to take the effort to port the provided example software over. The MCU used in that app note is another M4F so it shouldn't be too hard (and clearly can be done per cb1's testimony!). That's the best advice I can give from our end, as our focus for support is on the various BoosterPacks we provide such as the BOOSTXL-K350QVG-S1 as a display example.

  • Ralph Jacobi said:
    ...the interface to the ARM MCU for the system would just be SPI in the end

    Pardon - but the words, 'Just, Never, Always' must be chosen w/great care.    Indeed the interface to our 'ME812A' (that's an FT-800 assembled & produced as a 'Bezeled TFT Module') does employ 'SPI' - yet the FT-800 itself includes an, 'Interrupt, & 2 other signal lines, 'AL_PWM & PD#.'    Those added signals appear to conflict w/'Just SPI.'    (Indeed - a minor point - unless user's App benefits from those signals - and being 'outside SPI' - they have been 'excluded!'

  • I also own a TM4C123 device.

    I tried to work with the TM4C123 ARM MCU  with code composer but I keep getting the gmake *** target “all”

  • Feel your pain - is it not becoming clear that your 'issue' is primarily the 'Basic Operation of the MCU' w/in the Vendor's IDE?

    Any attempt to 'Deal w/the 'FT800' - at this (so early) stage - appears premature - thus misguided.

    Your path to success (usually) is composed of small steps - each one building your confidence & capability - while you further approach your main objective.

    My firm employs the 'PRO IDE' (IAR) thus can offer no insights into your (apparent) IDE quandry.   It may better serve you to:

    • experiment w/several of the vendor supplied projects - especially created for the TM4C123
    • once you've got them working - you can move to the SPI Peripheral examples.   My firm always recommends that you acquire a 'simple/small SPI-based EEProm' - with which you can build & test/verify your mastery of the SPI operation.
    • only then - is it believed that you are (almost) ready to 'do battle' w/the (bit demanding) FT800 SPI (w/'benefits') challenge.

    I'm in attendance only sporadically here - staff reviews 'PM Status' fairly regularly.   

    As earlier noted - that's the best means to continue our link.    (as/if you desire... we have produced full 'Turn-Key' FT800 Designs for others - that's yet another option for your consideration...)