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 Problem!!!

Other Parts Discussed in Thread: EK-TM4C123GXL

Hi there,

I have an EK-TM4C123GXL Evaluation kit which i used several times and things were going great.


Recently i was trying a new program which i downloaded to the board and was debugging it ,then suddenly the debugging crashed with no obvious reason and when i tried to modify the code and run the debugger (simulation) again the program gave me this message (could not initialize target device) and then the program crashes!!!

I googled the problem and tried everything i found but in vain.The things i tried are as follows:

1- I uninstalled keil and then installed it again on my laptop.

2-I tried to install keil on a different pc.

3-I used lm flash programmer to erase the flash of the microcontroller.

Please tell me what also should i do to be able to use my board again.

Finally,these are the screen shots of the error

Thank you for your effort :)

  • Hi Mostafa,

         Try the LM Flash Programmer Debug Port Unlock Utility. See, this post below.

         JTAG Communication Failures

    -kel

  • Hi dude,

    Thank you for your reply but i have already tried that and i stated it above as no. 3

  • Mostafa Mohamed1 said:
    Thank you for your reply but i have already tried that and i stated it above as no. 3

    Erase Flash is different from Debug Port Unlock utility. So, I thought you have not. The Debug Port Unlock Utility is at the "Other Utilities" tab of the LM Flash Programmer

    Do you have ICDI drivers installed at your PC, you can check that at the Device Manager, while your Tiva Launchpad is connected??

    Do you see the power led on at your Tiva Launchpad?

    -kel

  • Hi man,


    I performed the debug port unlock utility exactly as you said but no use.

    Also in the device manager the launchpad is ok and the green led is on. :(

  • Hello Mostafa

    As mentioned by Kel the Unlock Feature should help you to recover the device. BTW, what was the code that caused the device to lock up

    1. Is the JTAG port being used for GPIO

    2. Is the device clock frequency out of range or were you using deep sleep with frequnecy and voltage scaling?

    3. Is the board being detected in the Device Manager?

    Some data would be useful

    Regards

    Amit

  • Hi Amit,

    I downloaded the LM flash programmer and used it to unlock the device but nothing changed at all.

    Considering your requests:

    1- I didn't use the JTAG ports for GPIO.

    2-I used a clock frequency of 80 MHZ using the PLL but didn't use deep sleep at all.

    3-The board is detected by the device manager and the power LED is on.

    The board did that when i downloaded a program on the flash then i was trying to debug it.The hardware i used had 4 switched and when i presses and released one of them many times the debugger crashed and the board didn't accept downloading codes anymore.

  • Mostafa Mohamed1 said:
    The hardware i used had 4 switched and when i presses and released one of them many times the debugger crashed and the board didn't accept downloading codes anymore.

    So, you have an external hardware with 4 switches connected to your launchpad when this happened? Is this external hardware just switches? Provide details.

    Remove this external hardware and try the Debug Port Unlock Utility again.

    By doing a visual inspection at the board, do you see anything damaged?

    -kel

  • The external switches provide 4 inputs for the micro-controller,each input is translated into a different frequency signal.

    I disconnected the external hardware and tried the port unlock utility but also no use.

    I examined the board visually and nothing weird is obvious.

  • So is the board damaged or what guys??!!!!

    No one has any idea to make it flash!!!! :(

  • Hi Mostafa,

        When using the Debug Port unlock utility, "hold reset" and use the debug port unlock utility.

        If by using the Debug Port Unlock Utility several times, you are unable to recover your board, then it is possible that there is something damaged at the board.

        If you don't have the capacity to debug the problem at board level, then I suggest you get a new Launchpad for your project.

        I suspect that this action you did of interfacing an external board caused this.

        Touch the IC's on the board and see if anything is unusually heating up.

    -kel

  • Hello Amit:

    about 2. Is the device clock frequency out of range or were you using deep sleep with frequency and voltage scaling?

    I set the deep-sleep LDO voltage to 0.9V,  Flash in low power mode and SRAM in low power mode when enter deep-sleep mode.

    As the following code:

    HWREG(SYSCTL_LDODPCTL) = SYSCTL_LDO_0_90V;

    HWREG(SYSCTL_DSLPPWRCFG) = SYSCTL_FLASH_LOW_POWER | SYSCTL_SRAM_LOW_POWER;

    When i re-flash the TIVA, CCS show the following message:

    CORTEX_M4_0: Flash Programmer: Timed out while writing to Flash memory

    CORTEX_M4_0: Error: Debug Port error occurred.

    CORTEX_M4_0: GEL: File: C:\Users\3450-2350-s\WorkspaceTM4C123G\CAN_Application\Debug\CAN_Application.out: Load failed.

    Could you any suggest to solve it ?

    Peter.

     

  • Hello Peter,

    The maximum frequency is specified as 16MHz when using LDO at 0.9V. So either you need to drop the system frequency to 16MHz or use 1.2V instead.

    Regards
    Amit