• State TI Thinks Resolved
  • Locked Locked
  • Replies 1 reply
  • Answers 1 answer
  • Subscribers 55 subscribers
  • Views 419 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.

How to use CCS as debug environment only?

Uwe Brackenhoff
Prodigy 10 points


Hallo,

because our business is within the automotive sector, we have to fulfill a wide range of process activities. To be able to do this, we are using our own build environment, which is deeply connected with a lot of third party tools to match those process activities.
We have some new projects were TI microcontroller derivatives (from TSM320C28xxxx line) are to be used so I got the task to integrate the TI CGTs into our build environment. I managed to use the compiler to build and link. Also binary post processing is not a problem.

My question is now: Can the CCS be set-up to just flash an existing binary and have a debug session afterwards?

We don't want to use the CCS gui for editing and compiling, because it is hard to automate project setup for every developer this way. We just need a debug environment for the XDS110.

If this is not possible to achieve: Starting from a list of source files, include paths, libraries, defines, compiler and linker options what would be the best way to setup a CCS environment in an automated way, which can be synchronized with the parameters from our build system (adding/ removing source files / include paths etc.).

Kind Regards

  • 0
    TI__Guru**** 473721 points

    Hello,

    Uwe Brackenhoff said:
    My question is now: Can the CCS be set-up to just flash an existing binary and have a debug session afterwards?

    Yes, absolutely. In fact, this is a common environment for many customers. The CCS debugger is launched and the executable/binary is loaded/flashed manually. 

    When the debugger is launch manually, it is called a "Manual launch". Please see Section 7.3.2 of the CCS User's Guide for more infomration:

    https://software-dl.ti.com/ccs/esd/documents/users_guide/ccs_debug-main.html#manual-launch

    The below video is an example of using CCS to debug a program generated (and flashed) from outside the CCS environment. It shows how to start a manual CCS debug session, load the debug symbols, and debug:

    https://dev.ti.com/tirex/explore/node?node=AE-5HKkgK7JaKD4KtMHLgA__FUz-xrs__LATEST

    Note that in the above video, the program is already flashed. But as noted in the video, instead of loading symbols you can also load/flash the program there also.

    Note that there are few caveats when trying to debug a program without a CCS project. Most of them revolve around source file look up. It is not an issue if the debugging is taking place on the same machine that built the program and if the all the files (program file and all source files) are left in their original location. If this is not the case, then the debugger may not be able to find the location of the source files needed for source level debug. In these cases, please refer to Slides 53-58 of the following presentation: https://software-dl.ti.com/ccs/esd/training/CCSv6-TipsAndTricks.pptx

    Note that the above presentation is for an older CCS version, however the concepts regarding debugger source lookup should still be relevent.

    Hope this helps

    ki