• State TI Thinks Resolved
  • Locked Locked
  • Replies 3 replies
  • Answers 1 answer
  • Subscribers 31 subscribers
  • Views 519 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.

Compiler/EK-TM4C123GXL: Device no more communicating and LCD Booster Pack Display

Sahil
Expert 1585 points
Part Number: EK-TM4C123GXL

Tool/software: TI C/C++ Compiler

Hi,

I am trying to run the grlib_demo with LCD Booster Pack.

Since the Display was not working so i was searching around to see what is the issue and how to fix. Based on a post on e2e, I tried some modification and flash the device. Since then it has stopped communicating any more.

Here is the snapshot of the code I introduced (From Line #1035 to 1044) and the error is shown as well.

Please advise.

Thanks

  • 0
    Guru 117855 points

    Sahil said:
    Since the Display was not working so i was searching around to see what is the issue

    and

    Sahil said:
    Based on this post, I tried the modification and flash the device...  [failure continues]

    Have you provided "full/proper" data & "chain of events" - so that those here - are best enabled to assist?    

    Your subject line lists,  "No more communicating" - to that you added,  (the always infamous)  "Display NOT Working!"       "Not Working" - applies even more strongly - to those trying to assist you.    it can mean an UNLIMITED NUMBER of Failures - thus proves of (very) little assistance - to your hapless helper crüe.       You do note  "No more communicating" - is (that) the sole failure?    

    • Does the screen initialize - and display the opening screen(s)?     That's important - is it not?
    • You state, "No more communicating" - which suggests that the display - at one time - DID Communicate!    Is that true?
    • Beyond successfully  "communicating" (if it did such) - has your display & MCU (ever) worked to your satisfaction?      
    • If so - what was changed - to disrupt that successful operation?     That's important information - is it not?
    • Your last of the 2 quotes presented notes,   "this post"   - yet no identification of that post - at all - is provided.   [edit:]  poster added (after) my writing!

    Substantial clarification - as outlined herein - appears (very much) needed...

  • 0 in reply to Sahil
    TI__Guru**** 191486 points
    Hi,
    You intent is trying to use the NMI pin as the GPIO, correct? You would've locked the device from JTAG access if you configure the JTAG pins for GPIO. However, this is not what you are doing. Not sure why the debugger is not connecting to the target. Please try to unlock the device by following the below steps.

    1. Unpower the board and press reset

    2. Power the board but do not release the reset

    3. Run the JTAG unlock sequence according to the LM programmer "dialog box"

    4. Power Cycle the board

    5. Do a Flash Erase Check or load a simple program to confirm the debugger can access the MCU again

    Please use below code to configure PD7 for GPIO.

    HWREG(GPIO_PORTD_BASE+GPIO_O_LOCK) = GPIO_LOCK_KEY;

    HWREG(GPIO_PORTD_BASE+GPIO_O_CR) |= GPIO_PIN_7;