• State TI Thinks Resolved
  • Locked Locked
  • Replies 3 replies
  • Answers 1 answer
  • Subscribers 53 subscribers
  • Views 1493 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/CODECOMPOSER: Accessing Trace Window or Buffer

James Scholl
Prodigy 60 points
Part Number: CODECOMPOSER
Other Parts Discussed in Thread: MSP430F2619

Tool/software: Code Composer Studio

Operating System: Windows 10 64-bit

CCS Version: 7.2.0.00012

Board: MSP430F2619

Emulator: MSP-FET430UIF

I am a code composer and embedded programming beginner, so please bear with me. I am trying to automate the trace functionality in CCS so that I can get the trace information (address, data bus, and control signals) for all my code as it runs, not just 8 lines. Is there any way to access the data within the trace window and send it to a text file as well as automate it so I can get the trace data for my whole program?

I've looked into the DSS and GEL file documentation but I can't find any way to access the data within the trace window GUI. Would the GUI composer be able to do that? I read that the trace buffer in the EEM is inaccessible to the CPU otherwise I was thinking that you could access the memory locations where the trace buffer data is stored.

Thanks!

  • 0
    TI__Guru* 78091 points
    Hi James,

    There is no way to do this in CCS or using DSS. I am working to see if there is any other way to do this, but my suspicion is that there is not.

    Can you share more information about what you are trying to do specifically with this trace? Are you working to debug an issue with your code, or maybe you are hoping to do some sort of code profiling? What is your goal? Maybe we can help you to find an alternate path to help.

    Regards,
    Katie
  • 0 in reply to Katie Pier
    Prodigy 60 points
    Thanks for the quick reply.

    My goal with the trace is to be able to track each CPU instruction (i.e. see what the CPU is doing in real time) similar to what the disassembly view shows.

    If it were possible to access the CCS GUI and for example, continually start and stop the trace window, sending the 8 lines to a text file, that would solve the problem but I suppose like you said that is not possible.

    I have found documentation on the MSPDebugStack that seems promising especially in the MSP_EEM.h file. Could you give your opinion on whether that could be a solution? From what I can tell so far those functions would allow you to run a trace and access the trace buffer.

    I am trying to be clear but please ask any questions you might have.

    Thanks again.
  • 0 in reply to James Scholl
    TI__Guru* 78091 points
    It looks like this discussion continued here: e2e.ti.com/.../2251474