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.

Trace Analyser

hi,

   How  to implement trace analyser in ccsv5 .  need  some tutorial about Trace analyser. 

  • Hello,

    The level of trace support is highly dependent on the device and emulator. What device and emulator are you using?

    Thanks

    ki

  • hi,

       we start the trace analyser in project using simulator. how to enable the trace analyser in ccsv5

  • Trace Analyzer is for analyzing trace data collected from a hardware target that supports trace. Depending on the type of trace, a specific emulator may be needed.

    Thanks

    ki

  • Hi,

              I am working on C6670. I am not getting , how to start trace analyzer in my project. How to check out inclusive and exclusive function CPU cycles and how to check out function call graph?

    Kindly let me know the procedure to do the above task using Trace analyzer?

    thanks

    shilpa

  • Hi,

    I am using an C6670 EVM that connects to my PC using Blackhawk XDS560v2-USB Mezzanine Emulator connection. I need to enable Traces in my project.

    During my trials, In the debug perspective,under Trace Control menu, I am getting the following message, "Please select a Trace receiver"

    There are four options in the select receiver Tab by the name None, 560 Trace Pod, 560 V2 Trace and ETB.

    I am not sure which one to select for enabling trace.

    My question is

    1. Is this possible to have traces on EVM with USB connection to the PC

    2.If yes, can you please explain the configurations.

    Regards,

    Shilpa

  • The XDS560v2 emulator supports 1) STM trace over the pins (higher performance) or the ETB and 2) CPU trace using the ETB.  Here are the basic sequences to follow for your setup...

    [STM Trace over 560v2]

    1. Launch debug session.
    2. Conect DSP device and load your target application.
    3. Right click in the "Debug" pane and select "Show all cores" to display "Non Debuggable Devices".
    4. Expand "Non Debuggable Devices" node and connect CSSTM device.
    5. Start Tools->Trace Control
    6. From Trace Control select the CSSTM tab, click "Receiver" button, and add "560 V2 Trace".
    7. Adjust port width, trace buffer size, etc, and press "Apply".
    8. Start Tools->Trace Analyzer->Open Trace Connection In New View->CSSTM
    9. Add trace job if necessary (use View->Breakpoints)
    10. Run target application
    11. Data will appear in the CSSTM Trace Analyzer window

     

    [STM Trace over ETB]

    Same as above except in step 6 select the "ETB" receiver

     

    [PC trace over ETB]

    1. Launch debug session.
    2. Conect DSP device and load your target application.
    3. Start Tools->Trace Control
    4. From Trace Control select the DSP tab, click "Receiver" button, and add "ETB".
    5. Press "Apply".
    6. Trace Analyzer view will open automatically
    7. Start View->Breakpoints
    8. In Breakpoints pane, right click and add "Trace" breakpoint
    9. Right click new trace bp and select "Breakpoint Properties"
    10. Expand "Hardware Configuration"->"Type"->"What to Trace", enable Program Address and Time Stamp, and press "Ok"
    11. Enable the Trace breakpoint
    12. Run target application
    13. Data will appear in the c66x Trace Analyzer window
  • Hi
    1)I have a TMDXEVL6678LE with a blackhawk XDS560v2 usb mezzanine emulator .can I use pro trace as transport type in configuration ?or it is just possible with trace emulator?
    2)what is the difference between these two emulators?
    3)would you please give me examples of system analyzer and trace analyzer?(I have mezzanine emolator )
    4)can I use my emulator for system analyze?

    thanks

  • Dariush - I replied to your identical post in the below thread:
    e2e.ti.com/.../2216768

    As mentioned in that thread, it is recommended to start a new thread instead of replying to an old thread. Please do so in the future.

    Thanks
    ki