TMDXRM57LHDK: I cannot configure the profile of the Trace Analyzer XDS560V2

Jerome,

I will likely need to pass this on to an expert but I wanted to ask a couple questions first.

You mentioned you are using an XDS560v2 in the title.  Is this the PRO TRACE version?  It looks like this:

The reason I ask is that a normal XDS560v2 does not support PC trace over pins.

Assuming you are using a PRO TRACE did you happen to install an update into CCS?  As based on the error message it could be something where the trace software has an issue with this device.

Regards,
John

Hello,

Can you lower the JTAG speed to make sure the target is connected?

Hello John
Thanks you very much for your fast reply.
Yes the PRO TRACE version looks exactly like it.
I tried to install a new version of components on CSS and the update has finished with errors.
I tried to reinstall CSS but the problem is still there.
What can I do?
Thanks for your help.

Jerome

Hello Wang
Thanks for your help
I’m not sur to well understand what it means; “lower the JTAG speed”.
But I think the target is connected because I can debug without the trace analyzer.
Run, halt, breakpoint, step by step, all work perfectly.
Jerome

Jerome,

Can you give me more details on the CCS version from the fresh install.  Is this 10.1.1?

We will need to try to setup the same environment.  PRO TRACE + TMDXRM57LHDK + CCS.  I assume this is on Windows?

Regards,

John

John

Thanks you very much for your reply,

The CCS version is the following: 10.1.1.00004

 Regards

Jerome

Thanks Jerome.

I am in the process of setting up the same environment to try to reproduce the issue. It may take a bit of time to get all the pieces together. I will keep you posted of my progress.

Thanks

ki

Hello Ki

I can confirm that the issue comes from the last update of the CSS software.

I have another PC on which the same version of the CCS is installed but without the last update.

I tried with this PC and the trace analyzer works very well, I can configure it very well.

For your information I have also a laptop on which the same version of CSS is installed and the last update was successfully installed. On this machine the issue does not look the same. When I want to profile the trace analyzer nothing happen. No error, no windows to configure the trace analyzer.

Is it possible to cancel the last update?

Thanks very much for your help.

Jerome Beauvais said:

I can confirm that the issue comes from the last update of the CSS software.

I have another PC on which the same version of the CCS is installed but without the last update.

What is the last "update" you refer to? Could it be the TI Emulators pack (v9.2.1.00042)? If so, then you may be getting impacted by an known endianness issue that impacts only TMS570 Cortex-R devices. This issue is resolved in the Emulators pack that comes with CCS 10.2.0.

ki

Hello Ki
I did not remember the components which were updated; it was in the little window at the bottom right of the screen. I uninstalled the CCS 10.1.1.0004 to install the latest version I found on internet : 10.2.0.00009. But with this version the problem is still there.
Thanks for your help

Jerome

Thanks for trying 10.2.0. At least we can rule out that potential cause.

I should have a local environment set up soon. Sorry for the delay.

ki

Hi Ki,

Thank you for keeping me informed.

I can wait a few days without any problem.

Regards,

Jerome

I was able to set up my environment and I can reproduce the issue. I tried various CCS version (8.3.1, 9.3.0. 10.1.0, 10.2.0), they all exhibit the same issue.

I'm curious how you had it working in the first place. You had it working with CCS 10.1.1, correct?

Thanks

ki

Can you try both the custom core trace and the PC trace options to see if those work for you?

Thanks

ki

Hello Ki,
Thank you for your research.
I bought the trace analyzer in October 2014.
I started using it with CSS version 6 then versions 7, 8, and 10.1.1.00004
I have never encountered this problem before.

Regards

Jerome

Hello Ki,
The PC Trace is working but the trace on not so well documented.
There is a lot of line with the text Source file not found> instead of the source files with comments.
I can profile the trace analyzer with the custom Trace but the trace is always empty.
Thanks for your help
Regards
Jerome

The mystery deepens... I have been having all sorts of issues getting HW trace to work on any of my targets so I moved over to another PC. Everything works there... including Function Profiling with my TMDXRM57LHDK and ProTrace Pod! I'm using the same exact CCS versions on both (10.2.0). 

There is likely something specific to the environment on my laptop that is impacting Trace. And it appears to be the same issue on your end. I am continuing investigation and will keep you posted.

Thanks

ki

Hello Ki,
Thanks a lot for your help.
I tried and unfortunately the issue is still there for me.
Regards

Jerome

Hello Ki,

You are right, using a new workspace resolve the issue.

I uninstalled CCS, I suppressed all directories you said and I restart with a really new workspace.

I created again the project from scratch and then I transferred only the source code from the old workspace to the new one. And now it’s working well on both machines!

Thanks a lot for your patience and your help.

Jerome

Great! Looks like it requires clearing the workspace cache along with the other directories. I will need to document this in the troubleshooting guide. Thank you for your patience in all of this.

ki