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/CODECOMPOSER: Using the MSPDebugStack

Part Number:

Tool/software: Code Composer Studio

Operating System: Windows 10 64-bit

CCS Version: 7.2.0.00012

Board: MSP430F2619

Emulator: MSP-FET430UIF

I am trying to figure out how to run the example program (\ApplicationExamples\Example) found in the MSP Debug Stack Developer's Package (http://www.ti.com/tool/mspds?amp ) There is a lot of documentation given in the developer's guide but as a beginner I still can't understand how to run the program on my device. I would appreciate a quick rundown of how to do it. In the future I would like to be able to use some of the functions in the MSP430_EEM header file.

Thanks!

  • Hi James,

    The MSP430 DLL Developer's Guide gives a little bit more information on the examples and can be found in the \Doc folder of the MSPDS download. Before we get too far into modifying and running the examples, can I ask what your end goal is?

    There may be other tools the we provide that perform what you're looking for.

    Best regards,
    Caleb Overbay
  • Sure, I am trying to automate the trace window functionality in code composer so that I can get the address bus, data bus, and control signal for all of the instructions in my code as it runs, not just 8 lines.

    It seem to me that if I could integrate the functions found in the MSP340_EEM header file into my code or vice versa, I would be able to extract and then clear the data from the trace buffer. I did ask another question ( https://e2e.ti.com/support/development_tools/code_composer_studio/f/81/t/610050 about the possibility of doing the above and the answer so far seems to be it is not possible. Now I am wondering how to use the MSPDebugStack because it looks like it could be a solution.

    Please ask any more questions you might have and thanks for responding so quickly.

  • Hi James,

    I'll need to speak with some other team members to see if this is possible so i can provide some better guidance. I'll keep you updated on the progress. Thanks for your patience.

    Best regards,
    Caleb Overbay
  • Thanks a lot for your time.

    Today I've been able to use breakpoints to refresh the trace buffer and then I can just copy and paste the window to an excel file. This is adequate but I would still like to know like I've said if it would be possible to completely automate the process by either accessing through the gui the trace window (which another ti employee said was impossible in the question I linked) or using the MSPDebugStack.

    I don't want to take up so much of your time trying to see if it is possible to do it that way. My original hope was that someone could help me understand the steps behind running the example program in the MSPDS download and then I could figure out if I can access the trace buffer in the EEM.

    I will defer to your judgement if you want to see if it is possible first although I would still like some guidance on how that example works :)

**Attention** This is a public forum