• State Resolved
  • Locked Locked
  • Replies 7 replies
  • Answers 2 answers
  • Subscribers 53 subscribers
  • Views 1337 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: Cannot use system variable ${PROJECT_BUILD_DIR} in debug configuration in CCS6.13

Gui-Jia Su
Prodigy 100 points


Tool/software: Code Composer Studio

Hi,

I am working on a project that generates two different .out files (say file1.out and file2.out) using a custom makefile for debugging simultaneously on two F28335 dsp boards in CCS6.13. I tried to create a debug configuration using the system variable ${PROJECT_BUILD_DIR} in the program path for specifing which file to load into which board. So the paths are ${PROJECT_BUILD_DIR}/file1.out and ${PROJECT_BUILD_DIR}/file2.out. Even though the variable is shown to point to the correct folder, it didn't work and an error message says "Specified Program (Spectrum Digital XDS510USB Emulator/C28xx) does not exist." While it worked with absolute file paths, the reason to use the system variable is to make the debug configuration file portable and able to work with either "Debug" or "Release" configuration. I also tried with the other variable ${BUILDDirectory} and it didn't work either. Have I not done it correctly? Please help.

Best regards,

  • 0
    TI__Guru**** 173310 points

    user122609 said:
    So the paths are ${PROJECT_BUILD_DIR}/file1.out and ${PROJECT_BUILD_DIR}/file2.out. Even though the variable is shown to point to the correct folder, it didn't work and an error message says "Specified Program (Spectrum Digital XDS510USB Emulator/C28xx) does not exist."

    Unfortunately the debug configuration does not support the use of variables such as ${PROJECT_BUILD_DIR}. However, you could use something like ${build_artifact:nameofmyproject}.

    Here is a related thread on this topic. Portability of debug configurations is also summarized in this wiki section: 
    http://processors.wiki.ti.com/index.php/Portable_Projects#Portable_target_and_debug_configurations

  • 0 in reply to AartiG
    Prodigy 100 points

    Thanks for the clarification and additional information. May I suggest it as a feature request to make the Build Variables available for use in Debug/Launch configurations?

  • 0 in reply to Gui-Jia Su
    TI__Guru**** 173310 points

    user122609 said:
    May I suggest it as a feature request to make the Build Variables available for use in Debug/Launch configurations?

    I'm not sure about the technical feasibility of this request (the debug/launch configurations feature is inherited from Eclipse and has been this way for a long time), but before I file the request may I ask: does using ${build_artifact:nameofmyproject} not satisfy your portability requirement?

  • 0 in reply to AartiG
    Prodigy 100 points

    Since ${build_artifact:nameofmyproject} resolves to projectname.out, I can use it for only one of the two .out files.

  • 0 in reply to Gui-Jia Su
    TI__Guru**** 173310 points

    So do you have both the .out files in the same build configuration subdirectory? Because if they were in different build config directories such as "Debug" and "Release" then ${build_artifact:nameofmyproject} would work for both, it would just pick the .out file in the configuration subdirectory of the active configuration of project.

  • 0 in reply to AartiG
    Prodigy 100 points

    Right. Two .out files are generated for each build configuration. So I need a path variable, like ${PROJECT_BUILD_DIR}, that points to the build output folder and can be used in debug/launch configurations.

  • 0 in reply to Gui-Jia Su
    TI__Guru**** 173310 points

    user122609 said:
    So I need a path variable, like ${PROJECT_BUILD_DIR}, that points to the build output folder and can be used in debug/launch configurations.

    Although this may be entirely within Eclipse control, I have filed a feature request so the CCS team can review the request and analyze its feasibility. The tracking # for the request is CCSIDE-3063.