• State Resolved
  • Locked Locked
  • Replies 2 replies
  • Subscribers 54 subscribers
  • Views 883 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.

Changing source-code file associations

Jeff Williams
Intellectual 300 points


This ought to be an easy one...

I was stepping through some code, when I got to a SYS/BIOS file.  CCS informed me that it didn't know where to find the source file.  Since I wanted to step into the SYS/BIOS code, I located the source, and informed CCS where it was.  Unfortunately, I located the source file for a different version of SYS/BIOS.  Because of that, the source doesn't match the binary, and CCS displays information a line or so off from where it should be.

At this point, CCS believes that it has the correct source file to match the binary.  I need to change that.

How can I tell CCS to replace the current source-file association with the correct one?

Thanks,
jw 

  • 0
    TI__Guru**** 162895 points

    jw,

    There are a couple of ways you can do this:

    1) If the debugger is not running

    Click the little down arrow beside the bug button.  Click on Debug Configurations.  Select your debug session on the left.  Then click the source tab on the right  This shows the list of paths that are setup, use the Remove button to remove it.  You can use the Add button to add a different path.

    2) if the debugger is running

    In the Debug View right click on your debug session and select "Edit Source Lookup".  Then expand the CPU that the lookup was made for.  If you have a project it should be listed and you can expand it.  Then you should see a list of paths.  There is a button to restore defaults, note that this will clear all extra paths that you have setup.

    Regards,

    John

  • 0 in reply to JohnS
    Intellectual 300 points

    John,

    That seems to have fixed the issue.  Thanks!

    jw