• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Subscribers 30 subscribers
  • Views 592 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/TMS570LC4357: Hardware Tracing Not Working

James Kiessling
Intellectual 380 points
Part Number: TMS570LC4357
Other Parts Discussed in Thread: TMDX570LC43HDK

Tool/software: Code Composer Studio

Hello,

We've purchased the XDS560v2 Pro Trace emulator tool, and we've been successful in using it to program and debug our application. We would also like to use the tool for hardware tracing/code coverage, however we're running into problems. Specifically, I get the following error when I attempt to perform tracing:

The procedure I'm following to attempt hardware tracing is as follows:

1) Create a target configuration file for the Spectrum Digital XDSPRO USB Emulator connection with the TMS570LC43xx board/device selection:

2) Saving/testing the configuration

3) Right-clicking the target configuration .ccxml file just created in the Target Configurations view, and selecting Launch Selected Configuration

4) Right-clicking the processor target in the Debug window and selecting Connect Target

5) Selecting the same target again, but now going to Load -> Load Program... and uploading/running my application binary

6) Going to Tools -> Hardware Trace -> Code Coverage, switching the Transport Type to Pro Trace and taking the rest of the settings at default

7) Starting the hardware trace from here (Leads to error)

At this point, I get stuck at "XDSPRO is establishing the communication link for CortexR5" for about ~1-2 minutes, before I receive the error message

Everything up to the start of the hardware tracing (a.k.a. flashing/debugging the application) works perfectly.

Hardware wise, we have a fully-designed PCB that utilizes the TMS570LC4357 processor. It has the same 60-pin connector as the TMDX570LC43HDK, and we used the same routing as that board in our PCB. I thought that we might have made a mistake in the routing and/or did not properly lay out the traces on the PCB, so I went back to the HDK and attempted to do code coverage/hardware tracing on that board - no luck. Am I setting up the configuration file or CCS incorrectly for this functionality?

Thank you,

James

  • 0
    TI__Guru**** 171044 points

    James, 

    Thanks for sending such thorough post. Unfortunately I can't reproduce the issue here; both CCSv9.1, TMDX570LC43HDK and the XDS ProTrace work well. 

    One difference is that in my setup the calibration frequency stabilizes at 37MHz - in other more advanced devices I have seen 67.5MHz or the maximum of 92~93MHz. I don't recall seeing 110MHz as you are seeing. 

    In this case, I wonder if there is some sort of temporary configuation in your software setup or your board.

    For the setup, can you do the folloiwng: close CCS, go to the directory %HOMEPATH%\.TI-Trace and delete everything inside. This directory contains the temporary files used by the Trace engine. 

    For the board, you mentioned this happening with your HDK as well. I wonder if there is an external agent that could be causing this - I have seen ground loops between the host and the board cause issues with the communications - especially due to the fact the XDS560v2-class probes usually have circuitry to probe the lines and set the appropriate clock speed. In your particular case, 110MHz is three times (3rd harmonic) of ~37MHz, which is the frequency I get with my setup here - perhaps reflections on unterminated lines? It is hard to guess from here. 

    Hope this helps,

    Rafael

  • 0 in reply to desouza
    Intellectual 380 points

    Rafael,

    Thank you for the reply. Deleting the contents of the %HOMEPATH%\.Ti-Trace folder didn't seem to have any effect on the problem. Going off of your theory about harmonic disturbances, I've tried swapping power/USB cables to no effect. 

    This seems like it may be a complex problem, so to start I have two questions:

    1) The TMDX570LC43HDK is expected to work with the XDS ProTrace "out of the box" without any additional configuration or hardware modifications, correct?

    2) Is there a possibility of JTAG/Trace pin conflict in the software-defined pin muxing? Or, is there a sample application that you've used to test the probe that I could test with my setup?

    Thank you,

    James

  • 0 in reply to James Kiessling
    TI__Guru**** 171044 points

    James,

    Please apologize; I missed your reply. 

    1) Yes, you are correct. The board I have here works "out of the box" with the XDS ProTrace. 

    2) I am not very familiar with the device itself, but looking at its datasheet I can spot that the JTAG pins are not multiplexed with any other functions. However, the ETM pins are multiplexed with the EMIF. 

    https://www.ti.com/lit/ds/spns195c/spns195c.pdf 

    Hope this helps,

    Rafael