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.

TMS320C6727: Trouble Debugging TMS320c6727 DSP w/ XDS510 Plus Emulator

Part Number: TMS320C6727


We are having some issues while attempting to run a debug session in code composer version 5 using XDS510USB Plus Emulator.  Target CPU is c6727.   We recently switched to the ‘Plus’ version of this emulator, as we used to use the old XDS510USB. 

 

When debugging a test prototype DSP board, both emulators work fine.  The problem occurs when we try to run the debugger on a board that is set back in casing a couple of feet (only accessible to the emulator via a wire that connects to the DSP board that is in the case).  It seems as though the additional length of the JTAG connection is the problem (emulator to DSP connection).  However, the old XDS510USB emulator still works flawlessly in this case.

 

I am not 100% sure that the extra wire length is causing the ‘Plus’ emulator to fail, but it would seem to be the reason.  I am just unsure why the old emulator would work in this case, unless somehow it is outputting slightly more robust JTAG signals than the ‘Plus’ version.

 

Have you ever heard of a similar issue?  Perhaps there is a driver setting for this emulator that would help?  I tried to slow down the clock rate using code composer’s ‘targetconfigs’ options, with no success.

  • Hi,

    >>unless somehow it is outputting slightly more robust JTAG signals than the ‘Plus’ version.
    Precisely this. In certain systems that have some marginal specifications, sometimes either older or newer JTAG debuggers perform better by a small margin. While in general slowing down the speed can help overcome this, sometimes the specific JTAG debugger cannot overcome the load on one or more JTAG lines.

    >>Perhaps there is a driver setting for this emulator that would help?
    I can't spot anything on the Target Configuration editor settings, therefore I suspect there are no ways to workaround this in software.

    In hardware, though, there are some implementations where you can use buffers in the signal lines. Check section 7.2 of:
    processors.wiki.ti.com/.../XDS_Target_Connection_Guide

    Regards,
    Rafael