CCS/TMS320F28027: Connectivity through XDS100V3 from EMBEST

Hi Sibaprasad,

For CCS v5.5 all drivers are installed when XDS100 is selected during the installing. However, for older versions you might need to install the latest TI Emulation update to support XDS100v3.

You can do this from the following site: http://processors.wiki.ti.com/index.php/XDS_Emulation_Software_Package

Please try this, and let me know if it resolves your issue.

Best Regards,

Marlyn

Marlyn,

I tried all of these, but still having problem:

1. Installed EMUPack for CCSV5.3.0/XDS100V3, had the same problem,

2. Installed CCSV5.5.0, had the same problem,

4. Went back to my computer whether I develop my code on CCS V8.0 using XDS510LC USB. Created Target Config on CCSV8.0 as attached, and had the following problem:

-----------------------------------------------------------------------

[Start: Texas Instruments XDS100v3 USB Debug Probe_0]

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\Dell\AppData\Local\TEXASI~1\CCS\
CCS_V8\0\0\BrdDat\testBoard.dat

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

This utility has selected a 100- or 510-class product.
This utility will load the adapter 'jioserdesusbv3.dll'.

An error occurred while soft 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 '-151' (0xffffff69).
The title is 'SC_ERR_FTDI_OPEN'.

The explanation is:
One of the FTDI driver functions used during the connect
returned bad status or an error. The cause may be one or
more of: no XDS100 is plugged in, invalid XDS100 serial number,
blank XDS100 EEPROM, missing FTDI drivers, faulty USB cable.
Use the xds100serial command-line utility in the 'common/uscif'
folder to verify the XDS100 can be located.

[End: Texas Instruments XDS100v3 USB Debug Probe_0]

--------------------------------------

please help

XDS100V3_CCSV8.0_2019_07_05.pdf

Hi Sibaprasad,

Can you please refer to the following link for debugging JTAG connectivity issues. The issue you are seeing is described there under the 'Host Connection Error' section. More specifically I would check if your windows device drivers are properly installed, as per the instructions outlined in the section.

Please go through the debug steps outlined. If you are still unable to resolve the issue then let me know and we can look into this further.

Best Regards,

Marlyn

Marlyn,

I did the following

1. My TMS320F28027 board works with XDS510LC USB with 5V on the supply PIN.

2. I have changed that to 3.3V.

3. I have tried with CCSV5.5.0/XDS100V3 to communicate with the TMS320F28027 board, still no luck, same problem.

Questions:

1. Is XDS100V3 a cost effective version, low performance of XDS100V2 ?

2. Is there any jumper needed to be selected on VDS100V3 to make it work ?

3. How do I know, if the XDS100V3 driver is installed properly or not ?

4. Do we need to install XDS100V3 driver even with CCS V5.5.0 ?

5. Is XDS100V2 a better device than XDS100V3 ? Do I need to move to XDS100V2 ????

6. Did you people test XDS100V2 from EMBEST with TMS320F28027 and are happy with the performance ?

7. Why EMBEST wesbsite is sloppy if they are manufacturing this product, why no details on this device ?

8. Is this design given by TI to EMBEST to manufacture ?

Please help,

Sibaprasad,

1. Is XDS100V3 a cost effective version, low performance of XDS100V2 ?

The XDS100v3 is an updated XDS100v2 with support for the 1149.7 protocol and ARM Ltd's Single Wire Output (SWO). However, for C2000 devices an XDS100v3 is typically not necessary especially for the F28027 device, but can be used if that is what you are wondering.

2. Is there any jumper needed to be selected on VDS100V3 to make it work ?

The XDS100V3 has the capability of being set to an adaptor mode for the XDS560v1 as well as a UART mode. If your application does not require either then I would make sure that these modes are not enabled.

3. How do I know, if the XDS100V3 driver is installed properly or not ?

To check if the XDS100v3 is properly installed or not then check the Device Manager on your PC after connecting the XDS100v3 to the PC. You should see the following,

If the XDS100 does not show up in the Windows device manager or shows with an error, then the XDS100 was not programmed correctly, there is a problem with another FTDI based USB device, or the drivers became corrupt.

You can run the utility <xds100serial.exe> to find out which VIP/PID are programmed in the device. This utility is typically located in the following directory, CCS_INSTALL DIR/ ccsvx/ccs_base/common/uscif   

To check if the VID/PID for the EEPROM are programmed correctly check here 

4. Do we need to install XDS100V3 driver even with CCS V5.5.0 ?

No, with CCS V5.5 all of the XDS100V3 drivers should already be installed during the CCS installation. Please make sure that when you installed CCS you did it before connecting the XDS100 USB hardware. Also, when you tested the XDS100v3 with CCSv8 did you select the XDS100 during its installation if not I would re-install the EMU Pack for the XDS100v3 on that PC and then try to connect to it again.

5. Is XDS100V2 a better device than XDS100V3 ? Do I need to move to XDS100V2 ????

You should not need to move to an XDS100v2 instead of the XDS100v3 since your application worked well with the 510LC device. The current recommended emulator from TI (sold on  TI.com) is the XDS110 (http://www.ti.com/tool/tmdsemu110-u).

6. Did you people test XDS100V2 from EMBEST with TMS320F28027 and are happy with the performance ?

Third party companies like EMBEST build to specs provided by TI. Therefore, as far as how many devices are tested/performance metrics you would need to contact EMBEST. However, EMBEST is a member of the TI third party network.

7. Why EMBEST wesbsite is sloppy if they are manufacturing this product, why no details on this device ?

Please refer to EMBEST for questions regarding their website/product. TI does not oversee their website.

8. Is this design given by TI to EMBEST to manufacture ?

As previously mentioned EMBEST is a third party member of TI so they take the specs for the emulators and manufacture their own parts.

Please refer to the answers for questions 2, 3, and 4 and see if that helps.

Best Regards,

Marlyn

1. I could get the following result with CCSV5.5.0 and XDS510USB LC and my Tms320F28027 board, and it appears to be successful,

----------------------------------------------------------------------------------

[Start]

Execute the command:

%ccs_base%/emulation/drivers/sdjtag.exe -f %boarddatafile% -v -X reset -X scantest

[Result]

** BoardFilePath: C:\Users\user\AppData\Local\.TI\3849912086\0\0\BrdDat\testBoard.dat
** Resetting Emulator
 -- Emulator is Reset
** Emulator Scan Test
 -- Found JTAG IR Length of 38
 -- Found 1 device(s) in the scan chain

[End]

---------------------------------------------------------------------------------------

2. When XDS100V3 is connected to the PC, I see the following when opened device driver, even without connecting the target TMS320F28027 board.

still I get the same problem ,when I press test connection in Target Configuration file,

Questions:

1. XDS100V3 has two 14 PIN connector, I used the one that is at the edge of the board. Am I using the correct one ?

Hi Sibaprasad,

I have not heard from you in a few days. Where you able to try the previous suggestion to resolve your issue?

Best Regards,

Marlyn