• State TI Thinks Resolved
  • Locked Locked
  • Replies 8 replies
  • Answers 1 answer
  • Subscribers 31 subscribers
  • Views 2382 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

EK-TM4C123GXL: Interfacing with BOOSTXL-K350QVG-S1

Arjun Singh
Prodigy 20 points
Part Number: EK-TM4C123GXL
Other Parts Discussed in Thread: BOOSTXL-K350QVG-S1

Does anyone know how to interface the TM4C123GXL with the BOOSTXL-K350QVG-S1? I have no experience writing graphics libraries but I need to write graphics to this display. I do have a graphics library for the EB-LM4F120-L35 and this microcontroller; however, I don't know what to change. From what I understand we have to remove a resistor from one of the ports and switch out a header file? Where do I get the BOOSTXL header file? Any help would be greatly appreciated. Thank you! 

  • 0
    TI__Guru 72500 points

    Please download TivaWare and look at the examples in: C:\ti\TivaWare_C_Series-2.1.4.178\examples\boards\ek-tm4c123gxl-boostxl-kentec-s1

  • 0 in reply to Bob Crosby
    Prodigy 20 points

    Thank you for your quick response sir. I believe I have solved all of my software; however, my LCD refuses to operate. I have removed R10 but even then the back light won't turn on. How should I trouble shoot this? Thank you

  • 0 in reply to Arjun Singh
    Guru 117855 points

    Arjun Singh said:
    I believe I have solved all of my software; however, my LCD refuses to operate.

    Perhaps it is (just) me - but somehow I find those "items in highlight" - to be (also) high in "Potential Conflict!"

    Is it not possible - perhaps even likely - that such LCD "refusal" results from, "Not quite, "all solved" software?"

    While "refusal" is unlikely - it contrasts well w/the usual, "Does NOT Work!"

  • 0 in reply to Arjun Singh
    TI__Guru 72500 points
    Interesting, can you check the backside with a scope? PF2 (J4-1) is the LED control and PD7 (J4-9) is the LCD reset.
  • 0 in reply to Bob Crosby
    Guru 117855 points

    Bob - perhaps deserving of (almost) equal interest - is not "PD7" one of those (just discovered) pins defaulting into NMI?

    Poster's LCD (may) just have escaped, "Refusal" status/label...

  • 0 in reply to cb1_mobile
    TI__Guru 72500 points

    My understanding is that NMI is an optional configuration for PD7. From the datasheet section 5.1 where it refers to PD7 and PF0: "The NMI signal is the alternate function for two GPIO signals and functions as a GPIO after reset."

    But you may be on to something. The pin must be unlocked to reconfigure and this software needs to reconfigure it from an input to an output. I am not seeing that in the example code. (My life would be easier if I had a Kentec display booster pack to play with.)

  • 0 in reply to Bob Crosby
    TI__Guru 72500 points
    I don't have a display, but when I run the code on my EK-TM4C123 I see both PD7 and PF0 go low and toggle high. Let's see what Arjun gets.
  • 0 in reply to Bob Crosby
    Guru 117855 points

    I am (almost) certain that PD7 requires the same "unlock" treatment as does PF0 - and the supporting fact (LCD Refusal) - raises the "suspect status" of PD7.

    Presented here is the relevant "GPIO Signal Inventory" from the most recent TM4C123 manual we have:

    I am (almost) 100% certain that (both) PD7 & PF0 "Default to NMI."     (I would bet money upon that.)     Now NMI is - as you rightly state - an input configuration - although I suspect that it performs (somewhat) outside of "normal" user expectations.     Those users seeking to employ (either) of those pins as GPIO Output (and possibly to a more "normal" GPIO Input) must perform the "Pin Unlocking Procedure - proper for that pin.

    The Lcd (must) be seeking a GPIO Output (likely active low - I've not RTFM) to bring about a Reset - and the pin's default as NMI/(special) Input - appears outside of proper usage!

    Your discovery of "toggle activity" upon PF0 & PD7 - unless one or both have been "unlocked" - then set to output - is beyond my (and perhaps others') explanation...