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.

xds200 test connection error

hi,

I have a xds200 usb emulator and a custom board with C6657 DSP.

Here is a issue that I could not pass the test connection. Error log is below.

-----[Perform the standard path-length test on the JTAG IR and DR]-----------

This path-length test uses blocks of 512 32-bit words.

The test for the JTAG IR instruction path-length failed.
The JTAG IR instruction scan-path is stuck-at-ones.

The test for the JTAG DR bypass path-length failed.
The JTAG DR bypass scan-path is stuck-at-ones.

I wonder if I mistook the diver of xds200, because below source is used in my xds200 configuration setting.

            <instance XML_version="1.2" href="drivers/tixds560icepick_d.xml" id="drivers" xml="tixds560icepick_d.xml" xmlpath="drivers"/>
            <instance XML_version="1.2" href="drivers/tixds560c66xx.xml" id="drivers" xml="tixds560c66xx.xml" xmlpath="drivers"/>
            <instance XML_version="1.2" href="drivers/tixds560cs_dap.xml" id="drivers" xml="tixds560cs_dap.xml" xmlpath="drivers"/>
            <instance XML_version="1.2" href="drivers/tixds560csstm.xml" id="drivers" xml="tixds560csstm.xml" xmlpath="drivers"/>
            <instance XML_version="1.2" href="drivers/tixds560etbcs.xml" id="drivers" xml="tixds560etbcs.xml" xmlpath="drivers"/>

Could you give me some points to solve this issue?

Thank you in advance.

bai

  • Hello,

    Jing Bai said:

    The test for the JTAG IR instruction path-length failed.
    The JTAG IR instruction scan-path is stuck-at-ones.

    The test for the JTAG DR bypass path-length failed.
    The JTAG DR bypass scan-path is stuck-at-ones.

    The "stuck-at-ones" error certainly points to a JTAG connectivity failure. Usually an issue with the scan path on the hardware target. Do you have another C6657 you can try? If the xds200 works with that one, then we can be fairly sure that it is an issue with your custom target and not the emulator.

    Thanks

    ki

  • hi Ki-Soo Lee,

    Thank you for your prompt reply.

    The "stuck-at-ones" error with our custom target has solved.

    The DSP power sequence had not completed, and DSP had been resetting continuously. So that jtag of C6657 was not ready for boundary scan.

    thanks

    bai

  • Good to hear. Thank you for the update!