• State
  • Locked Locked
  • Replies 36 replies
  • Subscribers 83 subscribers
  • Views 1031 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.

CCSTUDIO-C2000: XDS100v1

ahugron hugron
Intellectual 330 points
Part Number: CCSTUDIO-C2000
Other Parts Discussed in Thread: LAUNCHXL-F280049C, TMS320F280049C

Hi,

I have installed CCS v12 and I am using a old demo board using an F28027 for a TMDSHVPFCKIT. The board is using the XDS100v1 and windows device manager find the device. xds100serial.exe also find the device.

  I cannot debug the board or when I click verify, the scan fails. See below. Do CCS v12 supports XDS100v1?

Regards,

Arnaud

[Start]

Execute the command:

%ccs_base%/common/uscif/dbgjtag -f %boarddatafile% -rv -o -F inform,logfile=yes -S pathlength -S integrity

[Result]


-----[Print the board config pathname(s)]------------------------------------

C:\Users\AHUGRO~1.XP~\AppData\Local\TEXASI~1\
CCS\ccs1200\0\0\BrdDat\testBoard.dat

-----[Print the reset-command software log-file]-----------------------------

This utility has selected a 100/110/510 class product.
This utility will load the adapter 'jioserdesusb.dll'.
The library build date was 'Jun 17 2022'.
The library build time was '22:30:41'.
The library package version is '9.8.0.00235'.
The library component version is '35.35.0.0'.
The controller does not use a programmable FPGA.
The controller has a version number of '4' (0x00000004).
The controller has an insertion length of '0' (0x00000000).
This utility will attempt to reset the controller.
This utility has successfully reset the controller.

-----[Print the reset-command hardware log-file]-----------------------------

The scan-path will be reset by toggling the JTAG TRST signal.
The controller is the FTDI FT2232 with USB interface.
The link from controller to target is direct (without cable).
The software is configured for FTDI FT2232 features.
The controller cannot monitor the value on the EMU[0] pin.
The controller cannot monitor the value on the EMU[1] pin.
The controller cannot control the timing on output pins.
The controller cannot control the timing on input pins.
The scan-path link-delay has been set to exactly '0' (0x0000).

-----[The log-file for the JTAG TCLK output generated from the PLL]----------

There is no hardware for programming the JTAG TCLK frequency.

-----[Measure the source and frequency of the final JTAG TCLKR input]--------

There is no hardware for measuring the JTAG TCLK frequency.

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

This path-length test uses blocks of 64 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.

-----[Perform the Integrity scan-test on the JTAG IR]------------------------

This test will use blocks of 64 32-bit words.
This test will be applied just once.

Do a test using 0xFFFFFFFF.
Scan tests: 1, skipped: 0, failed: 0
Do a test using 0x00000000.
Test 2 Word 0: scanned out 0x00000000 and scanned in 0xFFFFFFFF.
Test 2 Word 1: scanned out 0x00000000 and scanned in 0xFFFFFFFF.
Test 2 Word 2: scanned out 0x00000000 and scanned in 0xFFFFFFFF.
Test 2 Word 3: scanned out 0x00000000 and scanned in 0xFFFFFFFF.
Test 2 Word 4: scanned out 0x00000000 and scanned in 0xFFFFFFFF.
Test 2 Word 5: scanned out 0x00000000 and scanned in 0xFFFFFFFF.
Test 2 Word 6: scanned out 0x00000000 and scanned in 0xFFFFFFFF.
Test 2 Word 7: scanned out 0x00000000 and scanned in 0xFFFFFFFF.
The details of the first 8 errors have been provided.
The utility will now report only the count of failed tests.
Scan tests: 2, skipped: 0, failed: 1
Do a test using 0xFE03E0E2.
Scan tests: 3, skipped: 0, failed: 2
Do a test using 0x01FC1F1D.
Scan tests: 4, skipped: 0, failed: 3
Do a test using 0x5533CCAA.
Scan tests: 5, skipped: 0, failed: 4
Do a test using 0xAACC3355.
Scan tests: 6, skipped: 0, failed: 5
Some of the values were corrupted - 83.3 percent.

The JTAG IR Integrity scan-test has failed.

-----[Perform the Integrity scan-test on the JTAG DR]------------------------

This test will use blocks of 64 32-bit words.
This test will be applied just once.

Do a test using 0xFFFFFFFF.
Scan tests: 1, skipped: 0, failed: 0
Do a test using 0x00000000.
Test 2 Word 0: scanned out 0x00000000 and scanned in 0xFFFFFFFF.
Test 2 Word 1: scanned out 0x00000000 and scanned in 0xFFFFFFFF.
Test 2 Word 2: scanned out 0x00000000 and scanned in 0xFFFFFFFF.
Test 2 Word 3: scanned out 0x00000000 and scanned in 0xFFFFFFFF.
Test 2 Word 4: scanned out 0x00000000 and scanned in 0xFFFFFFFF.
Test 2 Word 5: scanned out 0x00000000 and scanned in 0xFFFFFFFF.
Test 2 Word 6: scanned out 0x00000000 and scanned in 0xFFFFFFFF.
Test 2 Word 7: scanned out 0x00000000 and scanned in 0xFFFFFFFF.
The details of the first 8 errors have been provided.
The utility will now report only the count of failed tests.
Scan tests: 2, skipped: 0, failed: 1
Do a test using 0xFE03E0E2.
Scan tests: 3, skipped: 0, failed: 2
Do a test using 0x01FC1F1D.
Scan tests: 4, skipped: 0, failed: 3
Do a test using 0x5533CCAA.
Scan tests: 5, skipped: 0, failed: 4
Do a test using 0xAACC3355.
Scan tests: 6, skipped: 0, failed: 5
Some of the values were corrupted - 83.3 percent.

The JTAG DR Integrity scan-test has failed.

[End]

  • 0
    TI__Mastermind 18211 points

    Hi Ahugron,

    Thanks for reaching out, let me transfer this question over to our CCS JTAG expert and they should follow up with a response shortly

    Regards,

    Peter

  • 0 in reply to Peter Luong1
    TI__Guru 50611 points

    Hi,

    XDS100v1 should work with CCS12. Was it working before you upgraded to CCS12?

    In the target configuration file, can you try slower clock speed?

    https://www.youtube.com/embed/mKxaztkCsYw

    Thanks & Regards,

    Santosh

  • 0 in reply to Santosh Jha
    Intellectual 330 points

    Hi

    I try a new demo board 280049C LAUNCHpad but still cannot foind the XD110. xdsdfu -e found 0 devices but device manager seems ok. See below.

    I am running WIndows 7 64 bits and I also have CCS v10.1 installed with CCS v12.

    Thanks Arnaud

    [Start: Texas Instruments XDS110 USB Debug Probe_0]

    Execute the command:

    %ccs_base%/common/uscif/dbgjtag -f %boarddatafile% -rv -o -S integrity

    [Result]


    -----[Print the board config pathname(s)]------------------------------------

    C:\Users\AHUGRO~1.XP~\AppData\Local\TEXASI~1\
    CCS\ccs1200\0\0\BrdDat\testBoard.dat

    -----[Print the reset-command software log-file]-----------------------------

    This utility has selected a 100/110/510 class product.
    This utility will load the adapter 'jioxds110.dll'.
    The library build date was 'Jun 17 2022'.
    The library build time was '22:30:41'.
    The library package version is '9.8.0.00235'.
    The library component version is '35.35.0.0'.
    The controller does not use a programmable FPGA.

    An error occurred while hard opening the controller.

    -----[An error has occurred and this utility has aborted]--------------------

    This error is generated by TI's USCIF driver or utilities.

    The value is '-260' (0xfffffefc).
    The title is 'SC_ERR_XDS110_OPEN'.

    The explanation is:
    An attempt to connect to the XDS110 failed.
    The cause may be one or more of: no XDS110 is connected, invalid
    firmware update, invalid XDS110 serial number, or faulty USB
    cable. The firmware and serial number may be updated using the
    xdsdfu utility found in the .../ccs_base/common/uscif/xds110
    directory of your installation. View the XDS110SupportReadMe.pdf
    file there for instructions.

    [End: Texas Instruments XDS110 USB Debug Probe_0]

  • 0 in reply to ahugron hugron
    Intellectual 330 points

    Forgot to say that I did not touch/change the demo board and all power LEDs are ON.

  • 0 in reply to ahugron hugron
    TI__Guru 50611 points

    Hi,

    If you are using LAUNCHXL-F280049C, open the target configuration file, and make sure you are XDS110, in 2-pin cJTAG mode.

    Here is users guide :

    C2000 Piccolo F28004x Series LaunchPad Development Kit (Rev. B)

  • 0 in reply to Santosh Jha
    Intellectual 330 points

    I still cannot find the launchpad. Board is working on a different computer with same cable. Displayed also same LEDs. I did fallow the user manual but still no luck. See image below.

    Thanks, Arnaud

  • 0 in reply to ahugron hugron
    TI__Guru 50611 points

    Are you using same version of CCS or it is different one?

    Can you run the 'Test Connection' and send the log from Console window?

  • 0 in reply to Santosh Jha
    Intellectual 330 points

    Same CCS version v12. Deivce on "Device manager" seems good, no warning and LED on board are good too. Here is the log when trying to debug:

    IcePick_C_0: Error initializing emulator: (Error -260 @ 0x0) An attempt to connect to the XDS110 failed. The cause may be one or more of: no XDS110 is connected, invalid firmware update, invalid XDS110 serial number, or faulty USB cable. The firmware and serial number may be updated using the xdsdfu utility found in the .../ccs_base/common/uscif/xds110 directory of your installation. View the XDS110SupportReadMe.pdf file there for instructions. (Emulation package 9.8.0.00235)

    Here is from Test connection:

    [Start: Texas Instruments XDS110 USB Debug Probe_0]

    Execute the command:

    %ccs_base%/common/uscif/dbgjtag -f %boarddatafile% -rv -o -S integrity

    [Result]


    -----[Print the board config pathname(s)]------------------------------------

    C:\Users\AHUGRO~1.XP~\AppData\Local\TEXASI~1\
    CCS\ccs1200\0\0\BrdDat\testBoard.dat

    -----[Print the reset-command software log-file]-----------------------------

    This utility has selected a 100/110/510 class product.
    This utility will load the adapter 'jioxds110.dll'.
    The library build date was 'Jun 17 2022'.
    The library build time was '22:30:41'.
    The library package version is '9.8.0.00235'.
    The library component version is '35.35.0.0'.
    The controller does not use a programmable FPGA.

    An error occurred while hard opening the controller.

    -----[An error has occurred and this utility has aborted]--------------------

    This error is generated by TI's USCIF driver or utilities.

    The value is '-260' (0xfffffefc).
    The title is 'SC_ERR_XDS110_OPEN'.

    The explanation is:
    An attempt to connect to the XDS110 failed.
    The cause may be one or more of: no XDS110 is connected, invalid
    firmware update, invalid XDS110 serial number, or faulty USB
    cable. The firmware and serial number may be updated using the
    xdsdfu utility found in the .../ccs_base/common/uscif/xds110
    directory of your installation. View the XDS110SupportReadMe.pdf
    file there for instructions.

    [End: Texas Instruments XDS110 USB Debug Probe_0]

  • 0 in reply to ahugron hugron
    TI__Guru 50611 points

    That is interesting.

    I just want to summarize it. If correct if anything is not correct below.

    • LAUNCHXL-F280049C EVM, connected to Laptop
    • Laptop has CCS 12 installed
    • Device manager is showing correctly, it has enumerated properly - XDS110 and Virtual COM port enumerated in device manager
    • You opened the target configuration manually, checked that it is using XDS110 with 2-pin cJATG advance mode
    • When you run 'Test Connection', it shows error code -260.

    As it reports USCIF error, we can update FTDI driver.

    Can you try other USB port on your laptop or different USB cable (smaller USB cable)?

    What is the bootmode? Can you put it in 'Waitboot' mode and then try.

  • 0 in reply to Santosh Jha
    Intellectual 330 points

    Yes, all is correct. I just also updated to latest FTDI driver from there web site. Try different cable and USB port. Try also boot "Wait boot" using switch but no success. See device manager:

  • 0 in reply to ahugron hugron
    TI__Guru 50611 points

    Do you have more than one board connected which has XDS110 emulator?

    Can you send the picture of your setup?

  • 0 in reply to Santosh Jha
    Intellectual 330 points

    Only 1 XDS110. See setup.

  • 0 in reply to ahugron hugron
    TI__Guru 50611 points

    Can you send the target configuration file (.ccxml file)?

  • 0 in reply to Santosh Jha
    TI__Guru 50611 points

    Is this new board or it was working before and stopped working? Can you check the bootmode? Please put the board in 'Waitboot' mode.

  • 0 in reply to Santosh Jha
    Intellectual 330 points

    Hi, See ccxml file. Rename extension.

    Board is working well on a different computer. No problem debugging. Using same demo example code from TI.

    I already tried waitboot by changing switch.

     

    Fullscreen TMS320F280049C_LaunchPad - Copy.txt Download 
    <?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 XDS110 USB Debug Probe_0">
                
        <instance XML_version="1.2" desc="Texas Instruments XDS110 USB Debug Probe_0" href="connections/TIXDS110_Connection.xml" id="Texas Instruments XDS110 USB Debug Probe_0" xml="TIXDS110_Connection.xml" xmlpath="connections"/>
                
        <connection XML_version="1.2" id="Texas Instruments XDS110 USB Debug Probe_0">
                        
            <instance XML_version="1.2" href="drivers/tixds510icepick_c.xml" id="drivers" xml="tixds510icepick_c.xml" xmlpath="drivers"/>
                        
            <instance XML_version="1.2" href="drivers/tixds510c28x.xml" id="drivers" xml="tixds510c28x.xml" xmlpath="drivers"/>
                        
            <instance XML_version="1.2" href="drivers/tixds510cla2.xml" id="drivers" xml="tixds510cla2.xml" xmlpath="drivers"/>
                        
            <instance XML_version="1.2" href="drivers/tixds510cs_child.xml" id="drivers" xml="tixds510cs_child.xml" xmlpath="drivers"/>
                        
            <property Type="choicelist" Value="4" id="SWD Mode Settings"/>
                        
            <property Type="choicelist" Value="1" id="The JTAG TCLK Frequency (MHz)">
                <choice Name="Fixed with user specified value" value="SPECIFIC">
                    <property Type="stringfield" Value="2MHz" id="-- Enter a value from 100.0kHz to 2.5MHz"/>
                </choice>
            </property>
            <platform XML_version="1.2" id="platform_0">
                                
                <instance XML_version="1.2" desc="TMS320F280049C_0" href="devices/f280049c.xml" id="TMS320F280049C_0" xml="f280049c.xml" xmlpath="devices"/>
                            
            </platform>
                    
        </connection>
            
    </configuration>
    
</configurations>

  • 0 in reply to ahugron hugron
    TI__Guru 50611 points

    Which demo application you are running?

    Please go to demo project, and to the folder 'target configurations', and check if TMS320F280049C_LaunchPad.ccxml is active?

  • 0 in reply to Santosh Jha
    Intellectual 330 points

    See image below. correct target active.

  • 0 in reply to ahugron hugron
    TI__Guru 50611 points

    It is so weird. Everything looks correct and I am clueless.

    Can you try one more thing?

    - Close CCS, restart it

    - Create a new workspace (different location)

    - Import blinky_led driverlib example

    - change build configuration to "CPU1_LAUNCHXL_RAM"

    - press 'bug' icon (make sure launchpad taget configuration is active)

  • 0 in reply to Santosh Jha
    Intellectual 330 points

    I did but still cannot debug. But when I did Project Wizard, it seems that it was able to detect my eval board automatically. 

  • 0 in reply to ahugron hugron
    TI__Guru 50611 points

    Can you follow the steps I mentioned above with Blinky_LED and,  CPU1_LAUNCHXL_RAM build configuration and making sure TMS320F280049C_Launchpad.ccxml  file as active and send the screen-shot.

  • 0 in reply to Santosh Jha
    Intellectual 330 points

    Here is the screen, still cannot debug.

  • 0 in reply to ahugron hugron
    Intellectual 330 points

    sorry, also with launchpadXL_RAM.

  • 0 in reply to ahugron hugron
    TI__Guru 50611 points

    Can you update the firmware of xds110?

    Go to C:/ti/ccs1200/ccs/ccs_base/common/uscif/xds110

    Open the readme file : XDS110SupportReadMe.pdf

    Follow the instruction to update the firmware.

    Let me know how it goes.

  • 0 in reply to Santosh Jha
    Intellectual 330 points

    cannot find device.

  • 0 in reply to ahugron hugron
    TI__Guru 50611 points

    Can you check if jumper J101 is connected on your board?

  • 0 in reply to Santosh Jha
    Intellectual 330 points

    Yes, all jumpers are there in J101.

  • 0 in reply to ahugron hugron
    TI__Guru 50611 points

    Do you have any other xds110 board? Does that get detected?

     

    Please refer to the XDS110 page for the troubleshooting tips:

    https://dev.ti.com/tirex/explore/node?node=A__ALFqIj4dX6S.TZRERoSphA__xdsdebugprobes__FUz-xrs__LATEST

     

    However based on the screenshot posted earlier, it looks like it is not an issue with the Windows drivers since it all looks fine.

    /cfs-file/__key/communityserver-discussions-components-files/171/pastedimage1664929938178v1.png

    Is this new Launchpad or it was working before and stopped working?

  • 0 in reply to Santosh Jha
    Intellectual 330 points

    I did uninstall and deleted driver with device manager. Reinstalled with driver from CCS12 directory. Driver was updated to a newer date (2020) but still cannot debug. Device manager seems good.

    Launchpad is good on a different computer but not mine.

  • 0 in reply to ahugron hugron
    TI__Guru 50611 points

    unfortunately I have no idea what else can go wrong.

  • 0 in reply to Santosh Jha
    TI__Guru 50611 points

    Do you have any other device with XDS110?

  • 0 in reply to Santosh Jha
    Intellectual 330 points

    I tried a new same demo board but same issue.

  • 0 in reply to ahugron hugron
    TI__Guru 50611 points

    Okay. So looks like board is not the issue. Something on your setup.

    Did you test with other setup/laptop, different USB port, or maybe Firewall setting?

  • 0 in reply to Santosh Jha
    Intellectual 330 points

    Yes, I try on a different laptop and it is ok. Only on my laptop where I get this issue. It is Windows 7 64 bits.

  • 0 in reply to ahugron hugron
    TI__Guru 50611 points

    What is CCS Version?

  • 0 in reply to ahugron hugron
    TI__Guru 50611 points

    I am not sure how well it is supported on Windows 7. I have never tested on Win7. Release notes says it should work.

    I do not have Win7 laptop to try and debug. I can check if anyone has tested on Win7, but I am not very hopeful.