• State Resolved
  • Locked Locked
  • Replies 5 replies
  • Subscribers 54 subscribers
  • Views 2654 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.

XDS100v3 TMS320F28035 frequency connection problem CCS6.2

Michael Koval27
Intellectual 990 points
Other Parts Discussed in Thread: CODECOMPOSER, TMS320F28035

Hello! I tried all settings with my XDS100v3 and everytime receive this kind error:

C28xx: Error connecting to the target: (Error -516 @ 0x0) The user selected specific frequency failed the scan-path reliability test. The utility or debugger requested the JTAG controller and cable, that generate the JTAG clock, to provide a user selected fixed frequency.  The built-in scan-path reliability test has failed. This indicates that the JTAG controller and its cable cannot reliably communicate with the target system at that frequency. (Emulation package 6.0.407.3)

http://joxi.ru/gmvb1V8FLyVJlm

TMS320F28035 CodeComposer V6

Under XDS100v2 all debugging is  fine.

That is my configuration file:

<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<configurations XML_version="1.2" id="configurations_0">
<configuration XML_version="1.2" id="Texas Instruments XDS100v3 USB Debug Probe_0">
        <instance XML_version="1.2" desc="Texas Instruments XDS100v3 USB Debug Probe_0" href="connections/TIXDS100v3_Dot7_Connection.xml" id="Texas Instruments XDS100v3 USB Debug Probe_0" xml="TIXDS100v3_Dot7_Connection.xml" xmlpath="connections"/>
        <connection XML_version="1.2" id="Texas Instruments XDS100v3 USB Debug Probe_0">
            <instance XML_version="1.2" href="drivers/tixds100v2c28x.xml" id="drivers" xml="tixds100v2c28x.xml" xmlpath="drivers"/>
            <instance XML_version="1.2" href="drivers/tixds100v2cla.xml" id="drivers" xml="tixds100v2cla.xml" xmlpath="drivers"/>
            <property Type="choicelist" Value="0" id="The Converter Usage">
                <choice Name="Its bypassed, use 1149.1, mimic XDS100v2" value="nothing">
                    <property Type="choicelist" Value="3" id="The Emulator 1149.1 Frequency">
                        <choice Name="Fixed with user specified slower value" value="specific">
                            <property Type="stringfield" Value="488KHz" id="-- Enter a value from 488Hz to 1.0MHz"/>
                        </choice>
                    <choice Name="Adaptive with user specified limit" value="adaptive">
                            <property Type="stringfield" Value="1MHz" id="-- Enter a value from 488Hz to 30.0MHz"/>
                        </choice>
                    </property>
                </choice>
            <choice Name="Generate 1149.7 4-pin standard mode" value="enable">
                    <property Type="choicelist" Value="1" id="The Emulator 1149.1 Frequency">
                        <choice Name="Adaptive with user specified limit" value="adaptive">
                            <property Type="stringfield" Value="500Hz" id="-- Enter a value from 488Hz to 30.0MHz"/>
                        </choice>
                    </property>
                </choice>
            </property>
            <platform XML_version="1.2" id="platform_0">
                <instance XML_version="1.2" desc="TMS320F28035_0" href="devices/f28035.xml" id="TMS320F28035_0" xml="f28035.xml" xmlpath="devices"/>
            </platform>
        </connection>
    </configuration>
</configurations>

  • 0
    TI__Guru**** 171309 points

    Hi,

    Assuming the HW connections are correct, it seems your configuration went through several trial and error steps. Can you try to connect with the attached file?

    Hope this helps,

    Rafael

    F28035_XDS100v3.zip

  • 0 in reply to desouza
    Intellectual 990 points
    Thanks for replay. But it did not help. The same error. I substituted all ccxml files with your file ( in target configuration and debug configuration) and without happy end.
    But may be problem lies in my XDS, when I launch xds100serial.exe it gives error #18 while scanning XDS emulators. What this error means ? I could not find.
  • 0 in reply to Michael Koval27
    TI__Guru**** 171309 points
    Hi,

    I am sorry for the issues. Would you mind sending the output of the xds100serial utility? This way we can have a better idea on what may be happening.

    Also, if you are using Windows (the link to the screenshot does not show anything for me) can you see if the Control Panel shows two XDS100 devices as mentioned in the section below?
    processors.wiki.ti.com/.../XDS100

    If not, it is possible the VID/PID is not programmed. Check the information at the FAQ below:
    processors.wiki.ti.com/.../XDS100

    Hope this helps,
    Rafael
  • 0 in reply to desouza
    Intellectual 990 points

    Thank you desouza for your troubles. But it seems problem is  with my old PC ( WIndows XP). When I tried MProg.exe it too could not find any devices. ( Though they both are found in  device manager). I think something with FTDI drivers on my Windows XP , though Code Composer 6 by default has them ( but may be they was not installed correctly ( though XDS100v2 works properly with it).

    When I  plugged  XDS100v3 in  another PC with Windows 10 , it is found with xds100serial.exe and with  MProg too and I think all will  be OK with jtag , when I  have chance to check it out. 

    Thank again.

  • 0 in reply to Michael Koval27
    TI__Guru**** 171309 points

    Hi,

    Thank you for reporting back your findings. 

    Regards,

    Rafael