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/TDA2PXEVM: How to run "Hardware Trace Analyzer - Function Profiling" on A15 with XDS560v2 Pro Trace

Part Number: TDA2PXEVM
Other Parts Discussed in Thread: TDA2

Tool/software: Code Composer Studio

Hello,

When I tried "Hardware Trace Analyzer - Function Profiling" on CCS 8.3.0 with XDS506V2 Pro Trace, CCS crashed. I tried several time but CCS always crashed or no response. How to solve this problem?

Best regards,

Wilson.

  • Hi Wilson,
    When does the crash happen? When you start Trace Analyzer? Or when you halt the program while Trace Analyzer is running?

    Thanks
    ki
  • Hi Ki-Soo,
    Crash happened at stop. Crash disappeared after increasing heap size of CCS.
    Now I can run hardware trace on A15, but I tried on C66 below error message appeared.
    "Could not run analyzer on C66xx_DSP1. Cause: This device is not supported by the receiver". Board is TDA2 Plus EVM.
    Best regards,
    Wilson.
  • That is odd. I am using a similar setup - CCSv8.3.0 w/my XDS560v2 PRO on a DRA74x EVM. HW Trace works fine on the C66x. Your EVM is J6 Plus, which is the equivalent of DRA74xP - slight difference. Other than trace, everything else with C66x works fine (you can connect, load run, etc)?
  • No problem in loading/running C66 with XDS560v2 PRO and CCSv 8.3.0.00009. I installed "auto_rvp_rsp_devices_support_1.0.9" CCS CSP.

    One thing I changed from default target configuration is "JTAG TCLK Frequency"  in connection properties. Default was "Adaptive" and it didn't work. I can connect with "TCLK looped-back with user specified limit". Could you guide right setting also?

  • user4836286 said:
    One thing I changed from default target configuration is "JTAG TCLK Frequency"  in connection properties. Default was "Adaptive" and it didn't work. I can connect with "TCLK looped-back with user specified limit". Could you guide right setting also?

    Yes that is correct. I did that also. You need that setting for the PRO TRACE pod as well as the Spectrum Digital XDS560v2 STM probes. 

    I will need to pull in some of the trace experts. I will keep you posted as I get updates.

    ki

  • My apologies for the delay on this. I am currently trying to get access to a J6 Plus target to reproduce the issue.
  • Thanks for keeping attention. I'm doing manual profiling. It's too difficult and not efficient.
  • Again, my apologies for the delay. The issue is trying to secure this particular target to test with. We are waiting to borrow it. I hope to have an update soon.

    ki
  • Update: My colleague was able to get access to a AM574x (J6 Plus) target and is also having issues was processor trace with the C66x. We had some overall trace issues on J6 Plus targets (no issue with J6) in the past and looks like there are still some issues remaining. We are still investigating and sorry for all the inconvenience.
  • Ki-Soo,
    When HW trace on TDA2px can be ready? I'm trace with TDA2x EVM but my target is TDA2Px. Profiling on TDA2x has limitation due to different clock and DDR.
    Best regards,
    Wilson.
  • Sorry, I don't have an estimate on when it will be fixed. The issue has been escalated and it is under investigation by the trace experts.
  • The issue has been fixed. The fix will be available in the upcoming CCSv9.0 release next month.

    Thanks
    ki