• State Resolved
  • Locked Locked
  • Replies 6 replies
  • Subscribers 53 subscribers
  • Views 856 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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/RM48L952: Debug configuration for multiple out files

Will Treharne
Intellectual 270 points
Part Number: RM48L952

Tool/software: Code Composer Studio

Hello,

I currently have two separate CCS projects - one for the bootloader, and another for the firmware. Currently when I want to test/debug the the firmware, I first have to launch a debug session for the bootloader so it is flashed onto the microcontroller, then load the firmware out file (ensuring the debug configuration is set to only erase necessary flash sectors). I then have to add the bootloader symbols to the debug session again as they are dropped when loading in the firmware.

All of this is a bit of a hassle. Is it possible to automate the above steps so when I launch a debug session for the firmware, it automatically loads the bootloader too?

Many thanks

  • 0
    TI__Guru**** 420520 points
    Hello Will,
    All of that can be automated using the scripting solution available with CCS - DSS:
    dev.ti.com/.../

    While the most common case for using DSS is automation from the command-line, you can also run DSS scripts from within the Scripting Console in CCS:
    dev.ti.com/.../

    You can also have DSS scripts auto-executed when launching a debug session by specifying it as an initialization script for your debug configuration (see the section for Debug Overview -> Debug configurations):
    dev.ti.com/.../

    Thanks
    ki
  • 0 in reply to Ki
    Intellectual 270 points

    Hi Ki,

    Thanks for the suggestions. I've been able to write a .js script and successfully flash both .out files.

    When adding the initialization script to the debug configuration, is there any way to specify the file without using an absolute path? From other posts I've seen, it appears project variables like PROJECT_LOC cannot be used.

    Thanks

  • 0 in reply to Will Treharne
    TI__Guru**** 420520 points

    Will Treharne said:
    When adding the initialization script to the debug configuration, is there any way to specify the file without using an absolute path? From other posts I've seen, it appears project variables like PROJECT_LOC cannot be used.

    Yes, variables like PROJECT_LOC are Eclipse variables that are not supported in the initialization script. I suppose you can use the getCurrentDirectory() API (which i believe is the path to the running js script) and pass that to a variable which you can use to avoid absolute paths. Or you can use the Java System.getenv(String) to use an existing system environment variable

    Hope that helps

    ki

  • 0 in reply to Ki
    Intellectual 270 points
    Hi Ki,

    Thanks for the information. That probably would have been my next question, but actually I was referring to the field where you specify which initialisation script to use in the debug configuration window. It appears this does not accept CCS variables unlike most other options. Is there anywhere to specify the script without using an absolute path?

    Thanks
  • 0 in reply to Will Treharne
    TI__Guru**** 420520 points
    I believe you can use a relative path (from the location of the ccxml file). Something like ..\..\..\file.js. Let me know if that works for you.

    Thanks
    ki
  • 0 in reply to Ki
    Intellectual 270 points
    Thanks for the suggestion. Unfortunately that only allows you to enter a path relative to the Eclipse home path (C:\ti\ccsv7\eclipse), rather than relative to the project location.