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.

Debugging EK-LM4F120XL makes CCS v5.3 crashes

Hi CCS team,

i am having a problem with my CCS v.5.3.00090 which makes the CCS crashes everytime i try to debug EK-LM4F120XL Stellaris Launchpad board with any project. CCS gives first the "Error connecting to the target" error, and when i hit Retry button, i get the "Error connecting to the target: Frequency is out of range" error message, and if i hit Cancel button, CCS crash with the following messages.

It is very strange since yesterday everything was ok, until i had to change my Stellaris board (since i broke the old one), and try to reinstall the driver for the new board, and suddenly i can't work with CCS anymore.

I already tried to reinstall CCS v5.3, reinstall the driver as instructed here: http://processors.wiki.ti.com/index.php/Stellaris_support_in_CCS#Frequency_out_of_range_error (and make sure under "Device Manager" that everything has been installed properly). Here are the screenshot of my device manager:

I tried to activate the "Debug Server Log" and you can find it here (maybe it helps):

http://e2e.ti.com/cfs-file.ashx/__key/communityserver-discussions-components-files/81/7266.debug_5F00_log

6330.dmp.zip

Any other suggestions that might help me solve this problem will be very much appreciated.

  • Hi,

    so finally i solved the problem. To share with others, it seems there are basically two types of ICDI drivers for Stellaris: one is for the older ICDI with FTDI chip as emulator (found on many LM3S dev kits), and one is for the newer ICDI with LM4F chip as emulator (found for example on the EK-LM4F120XL Stellaris Launchpad). 

    Somehow you can install the ICDI driver for the Stellaris Launchpad (it didn't fail as shown above). But this is the problem. Got a CD from a friend which comes with EKS-LM4F232 (also comes with LM4F chip as emulator) , forced to re-install the driver from the CD solves the problem for me..