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.

Issue browsing source files when debugging with CCS 5.2

Other Parts Discussed in Thread: CCSTUDIO

Hi,

i recently switched from CCSv5.1 to v5.2, and I experience an issue while debugging:

1. I build an executable from a CCS RTSC project that is created with com.ti.ccstudio.apps.projectCreate (Project is imported first in the workspace)

2. I load the executable in the Debug perpective using: Run -> load -> load program (Browse Project)

3. PC goes automatically to main as expected.

But it looks like the source file the Debugger opens is not linked to my CCS project. Hence, I cannot browse the code while debugging, for instance, with a Ctrl + mouse left Click to go to the definition of a constant.

Am I missing something in the workspace settings?

Is that an issue with the projectCreate?

Any help is welcome to get rid of this annoyance.

Best rgds/Seb.

  • Seb,

    Some additional information could be helpful here:
    - do you mean that the same procedure to create and build the project (via command line) is used for both CCS 5.1 and 5.2, but the debug issues only appear with 5.2?
    - did you try after making sure the source file is linked to the project when creating the project?
    - are you able to browse to the source file and open it during the debug session and get back the source file association that way?

  • Aartig,

    - do you mean that the same procedure to create and build the project (via command line) is used for both CCS 5.1 and 5.2, but the debug issues only appear with 5.2?
    [Seb] Correct. 
    - did you try after making sure the source file is linked to the project when creating the project?
    [Seb] Yes, and this is fine. I can build the project with CCSv5.2 without problem.
    - are you able to browse to the source file and open it during the debug session and get back the source file association that way?
    [Seb] Yes, that is the case.

    Best Rgds/Seb.

  • Seb,

    I have a few more questions to understand the issue clearly.

    Was the project originally created with CCS 5.1 using command line projectCreate and then imported into CCS 5.2 with command line projectImport? If so, was it copied/not copied to new workspace?
    Or was the project created itself using CSC 5.2?

    Would you be able to attach a test project that reproduces this behavior? Ideally this would be best to help us reproduce and analyze the issue. Also if you could please include the exact sequence of steps/commands used to create, import and build the project and which version of CCS was used for each, that would be extremely helpful.