• State Resolved
  • Locked Locked
  • Replies 4 replies
  • Subscribers 52 subscribers
  • Views 1750 views
  • Users 0 members are here
Support feedback
Options
Options

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/TMS320C6678: Problem using ${project_loc} in debug configuration

Petr Bouchner
Prodigy 140 points
Part Number: TMS320C6678

Tool/software: Code Composer Studio

Hello,

I use CCS v5.5 on Linux and I have a strange problem on our TMS320C6678 dev kit:

For a reason we need to use ${project_loc}/... path in a debug configuration. We have to load all 8 cores this way. When I close all windows containing any code for a specific project, then try to load out files with this path, I get an error: "Encountered a problem during... ${project_loc}/dbg/... .out". Vice versa, when I do have some of the project's code open, no error occurs and I am able to load the out files to the cores.

Yes, I have always set my project "Active", as seen in the Project Explorer. When all windows with the code are closed, I get this error. Yes, I know of ${PROJECT_LOC}  vs  ${project_loc} difference and stuff.

I use kit6678BH560v2_USB.ccxml config for BH560v2.

Questions:

Did anyone else have to solve this strange problem?

Is this problem connected to CCS, Eclipse, or...?

Why does this happen and is there any solution to this? (besides remembering not to close the code window)

Screens from both example and custom made project below:

1. Debug config:

2. It works when main.c is open:

3. It does not work, when all code is closed:

4. The same situation with (reproducible) client_evmc6678:

Thanks in advance.

  • 0
    TI__Guru**** 173310 points

    Petr,

    Petr Bouchner said:
    When I close all windows containing any code for a specific project, then try to load out files with this path, I get an error: "Encountered a problem during... ${project_loc}/dbg/... .out". Vice versa, when I do have some of the project's code open, no error occurs and I am able to load the out files to the cores.

    It seems strange that having source files open in the editor would impact whether the Program field syntax is accepted or not.

    Are you sure that specifying ${project_loc}/dbg/file.out in the Program field works consistently when source files are open? Does this work also when launching the debugger using the Debug (green bug) button?

    As far as I know, these variables are not supported in the debug configuration. I did some testing with a newer versions of CCS v7.4 and it did not work with paths relative to ${project_loc}. It did work when using path relative to ${workspace_loc} though. 

    We have a request filed for debug configurations to support project variables (see the first thread below), however we may be somewhat limited by functionality that we inherit from Eclipse. 

    Please see these related threads on this topic as well.

    https://e2e.ti.com/support/development_tools/code_composer_studio/f/81/t/569741

    https://e2e.ti.com/support/development_tools/code_composer_studio/f/81/t/145142

  • 0 in reply to AartiG
    Prodigy 140 points

    Yes, I am sure of that, 100% correct during several tests, when I closed windows with any code, problem occured again. I do not use the "green bug" button, since we have many different debug configurations for different uses (debug/release paths etc).

    Usage of  ${project_loc}/ is proved working in CCSv5, e.g. https://e2e.ti.com/support/development_tools/code_composer_studio/f/81/t/164883

  • 0 in reply to Petr Bouchner
    TI__Guru**** 173310 points

    I observed a couple of odd things when trying to use ${project_loc}/ with CCS 7.4, but ignoring that I was able to reproduce the behavior you described.

    I have filed bug # CCSIDE-3296 to track this issue so an engineer can take a closer look. Feel free to track its status using the SDOWP link in my signature. The link will be updated with this bug report in about an hour.

  • 0 in reply to AartiG
    TI__Guru**** 173310 points

    An engineer looked into this issue and here are some additional comments on this topic.

    The variable ${project_loc} is a built-in Eclipse dynamic variable, which should resolve to the current "context" project. However, since it does not work when just the project is selected, it is possible that something else takes focus when a debug session is launched, thereby the project_loc variable is not getting resolved. When a source file is open that serves as current context and then project_loc gets resolved properly.

    An alternative would be to use workspace_loc instead of project_loc. And a few other variables, as shown below, could also work (hello is the name of the project in the examples below):

    ${workspace_loc:/hello}/Debug/hello.out

    ${project_loc:hello}/Debug/hello.out

    ${resource_loc:hello}/Debug/hello.out


    Unfortunately we do not have direct control over this as it is a feature we inherit from Eclipse. Hopefully using one of the above alternate variables is a viable solution for you.