• Locked Locked
  • Replies 7 replies
  • Subscribers 55 subscribers
  • Views 917 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.

CCS v4.1 not debugging

NickG
Prodigy 220 points

Other Parts Discussed in Thread: CCSTUDIO

I am trying to debug code (any example stellaris code) on a DK-LM3S9B96 via CCS v4.1.3.00034 on my work computer with Windows XP. The code will build successfully, however, when I debug an example project like 'hello', it never connects to the target (I've waited as long as 35 minutes before having to end CCS via Task Manager). The following screenshot is all the farther it gets.

 

On the same machine, however, Code Red v2.0 can successfully debug projects to the same board. Also, my home computer with Windows 7 can debug projects to the same board using the same CCS version and Stellaris code installed from the same two discs that came with the Development Kit.

I've tried uninstalling CCS and reinstalling. I've also tried updating within CCS via Help>Software Updates>Find and Install. Once done installing the updates, I get this:

I click 'Install All'. After following the prompts I get the following Install Error:

I click OK and get:

The computer with the trouble also has CCS v3.1 and CCS v3.3. Could that have anything to do with it?

Any suggestions or thoughts as to why it won't connect to the target?

Thanks,

Nick

  • TI__Guru**** 173310 points

    Nick,

    Have you ever been able to connect and load code to this board on the WinXP machine, (ie) did this problem start recently or has it always occured? I would first suggest following the troubleshooting steps at http://processors.wiki.ti.com/index.php/Troubleshooting_CCS#Debugger, specifically deleting the debug launch and target cache files. Also try creating a new workspace, importing the project again and try to connect again.

    I'm not quite sure what went wrong with the update. The 1st screenshot shows the update to Spectrum Digital drivers which should not really matter in your case anyway since you are not using a Spectrum Digital emulator.

    There should not be a problem having CCS 3.1 and 3.3 on the same PC as CCS4. Please try the troubleshooting steps suggested above and let us know if you still have problems.

  • in reply to AartiG
    Prodigy 220 points

    Hi Aarti,

    Thanks for the reply. Yes, at one time I was able to load code to this board using the WinXP machine, several weeks ago. I had switched to Red Suite temporarily because for me it was quicker to load code than CCS. However, since our company uses CCS, I need to get it to work.

    I followed the steps in the link you provided (except step one, I'm using USB). I deleted the debug 'launch', deleted the contents of the .TI folder, deleted the targetdb.cache file, created a new workspace, imported the project again, did a 'rebuild all', and debugged. I waited for 30 minutes - never connected to the target.

    Nick

  • in reply to NickG
    TI__Guru**** 171809 points

    Nick,

    Just an idea: since you installed the Codered did you manage to connect to the board using CCS? The reason is that Codered may have installed an incompatible emulation driver for the embedded Stellaris emulator.

    With the board connected to the PC you can try to update the drivers to the ones installed by CCSv4 - they are under the directory <CCS_INSTALL_DIR>\ccsv4\emulation\drivers\stellaris\ftdi

    Hope this helps,

    Rafael

     

  • in reply to desouza
    TI__Genius 16510 points

    Nick,

    A couple more comments on this:

    1) The warning about the SD signing certificate having expired can be ignored. It will have no impact on what you need to do.

    2) The error message printed during the update is worrisome. If you are able to zip up the contents of the C:\Program Files\InstallJammer Registry\4F9A85D9-5F0E-E538-D71C-621DF59F81FA folder and attach them to this thread, there might be something in the log that will provide a hint as to the underlying problem.

     

  • in reply to AndyW
    Prodigy 220 points

    Ok, here are the contents of that folder:

    5164.New WinZip File.ZIP

  • in reply to NickG
    TI__Genius 16510 points

    The install error is occurring due to a permissions error on file com.ti.ccstudio.scripting.environment_3.1.0.jar. I thought the log file might add more info, but it does not help with what is causing the permission error. A common cause would be that the file is in use, but this seems unlikely given that most of the other files were updated correctly.

    Perhaps the most straight forward route to proceed with would be to download the latest full CCS install image (available here) and install this to a different folder name. With the fresh copy we can be sure there are no install issues to overcome.

  • in reply to AndyW
    Prodigy 220 points

    Ok thanks Andy. I'll give this a try on Monday and let you know how it works out.

    Nick