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.

Can't connect to Launchpad (anymore)

I've been playing with the Stellaris Launchpad (EK-LM4F120XL Rev A) for a couple of days now,

compiling and running several of the example projects, without problems. Today however,

I get the dreaded 'Frequency is out of range' message, indicating that the PC can't connect

to the board.

Considering all this did work, i'm suspecting that the installation went correctly, what could

be the cause of the communication problem? dmesg doesn't even detect insertion or

removal of the cable.

Here are some data of the system: CCSv6.1.1, running on Linux X86_64, kernel 4.1.6,

distro is Slackware64 14.1

There is no output to 'dmesg' or to the logs in /var/log on plugging in or removing.

There are no log messages to the terminal where CCS has been started. ICDI is

selected as communication link. The test projects were built correctly.

  • Hi John,

    What was the last program did you load at your Launchpad? Do you see the power led on? Do you see your Tiva Launchpad connections at Device Manager? If you see your device connections at Device Manager, try the LM Flash Programmer Debug Port Unlock Utility. If successful unlock, program a simple example program like "blinky". If the "blinky" example program works, then you have recovered your board.

    I do not know if the LM Flash Programmer works using Linux.

    You posted at the wrong forum. The appropriate forum to post this is at TM4C forum. Luckily, someone will move this post there.

    - kel
  • What was the last program did you load at your Launchpad?

    Not entirely sure - I believe it was 'Project0'.

    Do you see the power led on? Yes

    Do you see your Tiva Launchpad connections at Device Manager? I suspect 'Device Manager' is Windows?

    LM Flash Programmer Debug Port Unlock Utility: I suspect that is also for Windows. The ZIP I downloaded has a .msi extension. Wouldn't be bad if TI would clearly mark it on the LM Flash Programmer page though.

    I wonder what procedure the unlock utility applies. I'm quite capable of writing a Linux version if I knew what the underlying problem is.
     I finally solved the problem rebooting, which I couldn't try yesterday (this machine also acts as a server).

    BTW, I did monitor the USB transactions when plugging in the board, and noticed that, even though the actual plug in is detected, there was no indication a driver was activated (eg. no interrogating the VID/PID of the peripheral)


    Thanks for replying, Markel, particularly in these festive days!

  • "Verify Answer" your reply to mark this post as "Answered".

    - kel
  • Kel,


    It's not really answered. Rebooting is not an acceptable solution.

    I'd also appreciate, if possible, if you could indicate which problem is actually solved by the LM utility. Maybe I could create something similar for Linux.

  • John Coppens said:
    I'd also appreciate, if possible, if you could indicate which problem is actually solved by the LM utility.

    See, link at my signature "JTAG Communication Failures".     

    I have informed a TI Engineer about this.

    - kel