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.

CODECOMPOSER: Saving trace window content to a file

Part Number: CODECOMPOSER
Other Parts Discussed in Thread: ENERGYTRACE

Tool/software:

Hello,

Is there a way to save trace window content to a file?

Regards,

Eugene

  • Is there a way to save trace window content to a file?

    Is this regarding CCS 20? If so, then there is an option for save EnergyTrace data to a csv file. The option for save Core Trace data is not yet available.

    Thanks

    ki

  • Yes. This is CCS 20.0.1. It is MTB Core trace.

    It basic and very useful feature if debugger GUI.

    When this will be available?

    Regards,

    Eugene

  • It is on the roadmap but there is no firm date as of yet. It will be CCS 21.x at the earliest.

  • Hi Ki,

    How about an option to stream MTB into a file not just export the window content. PC discontinuities would probably suffice. It is relatively easy to restore execution trace offline.

    Regards,

    Eugene

  • How about an option to stream MTB into a file not just export the window content

    This is already on the roadmap. Apparently it is a good amount of work to implement this from the Trace view so the first iteration will likely be using some trace library used by the target application to configure and export captured trace data. We also plan to provide some post processing script to analyze the data and generate some reports like function profiling. Ideally we support this from the IDE also but that will be further down the road.