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.

XDS560 V2 Pro Trace, Failed to calibrate the circuit for C66xx_0

Hi,

Can somebody from the emulation team help with the following trace error. I can find out more information if needed.

I am trying to use the XDS560-V2 Pro trace emulator to debug a crashing problem that occasionally happens on our 6678. My problem is that when I try to apply the trace control, I get the following error:

 

 

I have looked on the forums and wiki and the only thing I see is that there may be a pin manager problem that requires a gel file to configure. I have attempted running what I think would be the right file for this with no change.

Any ideas what I am missing?

  • Brad,

    I can't help focus on the word "occasionally": are you experiencing this with what frequency?

    I could imagine this issue being caused by software if it happens all the time (or the most number of times), or even if that a fix for this issue can only be solved by a PC restart, but a hardware glitch or a flaky connection or connector if it happens infrequently.

    Also, which versions of software are you using? CCS, TI Emupack and the SD emulators?

    BTW, if the issue only is solved after a restart, try to search for a process called <TraceServer.exe> or, in the latest emupack releases, <xds_ecom_server.exe> that may be left orphaned after CCS is closed. You will need enable show processes from all users to see that.

    Also, if you are using the TI 60-pin connector, be extra careful as these tiny damn pins are easily bent, especially closer to the connector edges.

    Cheers,

    Rafael

  • Rafael, let's not mix what the customer is trying to debug in their code (the occasional crash) and the trace related error dialog box. The trace error dialog box is consistent and happens 100% of the time. They cannot perform any trace regardless if they reset, power cycle, etc. I'm working on getting the tool versions you requested.

    Until then, do you know what does that error dialog box indicates?
  • We are using CCS 5.3.0.0090, TI Emulators 5.1.275.0 and Spectrum Digital Emulator 5.2.0.09
  • Brad,

    I thought the "occasionally" was referenced to the Trace error, not to an application error.

    Given it happens all the time, the error is probably due to a hardware failure. It indicates the Trace pod is unable to get an electrical signal from the mentioned pins: EMU6 through EMU16, which may mean any hardware-related issue with the Trace routing:

    - a bad cable / connector;

    - a cold solder joint on these BGA balls;

    - an unrouted board, if this is a custom board;

    - an unsuitable JTAG connector for core trace (TI 14 or 20-pin), if this is a custom board.  

    I checked the C6678 datasheet and the EMU pins are not muxed with any other functions, thus ruling out any pinmux configuration issues.

    You can try to see if at least some of the EMU pins are still working by selecting a STM Trace (menu Tools --> Hardware Trace Analysis --> Memory Throughput Analysis) and check if a Trace job can be configured with the settings below:

    Unfortunately I do not have such combination of tools installed anymore, but all the procedures above work on my Pro Trace connected to a C6678 EVM via the TI 60-pin connector.

    Despite the software components are old, I don't have any report of bugs with these particular releases.

    I will try to see if additional diagnostics can be obtained and will reply here if I find something relevant.

    Hope this helps,

    Rafael

  • Ok, so we tracked this down to a problem with the adapter.

    There are two flavors of the TI 60-pin to MIPI 60 pin adapter, one from Spectrum Digital, and one from BlackHawk DSP. The BlackHawk adapter does not work with the Spectrum Digital XDS560v2 Pro Trace. Only the Spectrum Digital adapter works with it.

    I don't have both adapters to see what the differences are between them.