CCS/TMS320VC5505: Can connect with xds100 emulator

Hi Mark,

Thanks for your message.

As you suggested, In order to connect ccsv6 to circuit board of TMS320VC5505 eZDSP USB STICK (Revision B), I updated CCSv6 "TI Emulators" to 7.0.48.0 emupack by downloading standalone installer located at http://processors.wiki.ti.com/index.php/XDS_Emulation_Software_Package .

The emupack was installed in ccv6 folder of CCS installation directory i.e. in C:\ti\ccsv6.

However, it seems like still cannot connect ccsv6 to circuit board of TMS320VC5505 eZDSP USB STICK (Revision B) as when new target configuration is created in ccsv6,  "Texas Instruments XDS100 USB Emulator" does not appear in "connection" list of new target.                                       

Also, I tried to update CCSv6 "TI Emulators" component using Help->Check For Updates. But still  "Texas Instruments XDS100 USB Emulator" does not appear in "connection" list of new target when new target configuration was created using ccv6.  

Can you suggest me when creating new target configuration, which "Connection" you are using and what "Board or Device" type you are selecting.

Satyajit,

The "Connection" should be "Texas Instruments XDS100v1 USB Debug Probe".  For "Board or Device" I used "USBSTK5505_VC5505". Can you share both the working and non-working target configuration files (.ccxml)?  Also are you getting the same error as before?  What message do you get when you try to do "Test Connection" from the target configuration setup page?

Thanks,

Mark

Hi Mark,

The snapshot of working .ccxml created in ccsv4 is attached here.

Also, the snapshot of non-working  .ccxml created in ccsv6 is attached here.

The error is :

Error connecting to the target:
(Error -151 @ 0x0)
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.
(Emulation package 7.0.48.0)

Satyajit,

Can you attach the actual .ccxml file or copy and paste the file data from the "Source" tab for both configurations?

Since this is working for CCSv4, I get the impression that the actual issue is not FTDI drivers or faulty hardware.

Thanks,
Mark

Hi Mark,

In addition to last post, please see the snapshot of Advanced settings of working target and settings of non-working target. The difference is highlighted in red.

Working target:

Non-working Target:

The source data for working .ccxml file is:

<?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 XDS100 USB Emulator_0">
<instance XML_version="1.2" desc="Texas Instruments XDS100 USB Emulator_0" href="connections\TIXDS100usb_Connection.xml" id="Texas Instruments XDS100 USB Emulator_0" xml="TIXDS100usb_Connection.xml" xmlpath="connections"/>
<connection XML_version="1.2" id="Texas Instruments XDS100 USB Emulator_0">
<instance XML_version="1.2" href="drivers\tixds100c55x.xml" id="drivers" xml="tixds100c55x.xml" xmlpath="drivers"/>
<platform XML_version="1.2" id="platform_0">
<instance XML_version="1.2" desc="USBSTK5505_0" href="boards\usbstk5505.xml" id="USBSTK5505_0" xml="usbstk5505.xml" xmlpath="boards"/>
</platform>
</connection>
</configuration>
</configurations>


Also, the source data for non-working .ccxml file is:

<?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 XDS100v1 USB Debug Probe_0">
<instance XML_version="1.2" desc="Texas Instruments XDS100v1 USB Debug Probe_0" href="connections/TIXDS100usb_Connection.xml" id="Texas Instruments XDS100v1 USB Debug Probe_0" xml="TIXDS100usb_Connection.xml" xmlpath="connections"/>
<connection XML_version="1.2" id="Texas Instruments XDS100v1 USB Debug Probe_0">
<instance XML_version="1.2" href="drivers/tixds100c55x.xml" id="drivers" xml="tixds100c55x.xml" xmlpath="drivers"/>
<platform XML_version="1.2" id="platform_0">
<instance XML_version="1.2" desc="USBSTK5505_VC5505_0" href="boards/usbstk5505_VC5505.xml" id="USBSTK5505_VC5505_0" xml="usbstk5505_VC5505.xml" xmlpath="boards"/>
</platform>
</connection>
</configuration>
</configurations>

Satyajit,

I'm still looking into this.  In the meantime, can you confirm that you selected to install Spectrum Digital support when you installed CCSv6?

Also, does the device entry in the Device Manager look similar to the following?

Thanks,

Mark

Hi Mark,

Usually I do "Select All" while software installation.

Also, I am not quite sure how to check Device manager. Please suggest me if possible.

Thanks for your help.

Regards,

Satyajit

Satyajit,

The Device Manager is accessible from the Control Panel on Windows. You are using Windows correct?

Thanks,
Mark

Hi Mark,

The device manager screenshot is shown below..I don't find any device entry.

Satyajit,

Okay, so I don't see an XDS100 in your Device Manager. Is this the same computer with the working CCSv4 installation? Can you still successfully connect in CCSv4? Does unplugging and re-plugging the device change anything in the Device Manager?

Thanks,
Mark

Hi Mark,

yes, it is the same computer I am using for ccsv4. After plugging device, I can see part highlighted in red in below screenshot.

Satyajit,

The USBSTK5505 uses a FTDI device for JTAG, and it seems that CCSv4 is able to recognize a generic Serial Port driver for it. However, this was a characteristic of our software that, for CCS releases starting with v5.x, renders a connection unusable.

In a system with proper XDS100 installed device drivers you should be seeing instead the entries shown in section 2.6 of the following page:
processors.wiki.ti.com/.../XDS100

In order to update the device drivers, please right click on each highlighted serial port entry on the Device Manager and select "Update Driver Software" then select "Browse my computer for driver software" and then point to the following directory:
C:\ti\ccsv6\ccs_base\emulation\windows\xds100_drivers

Windows should be able to find updated drivers at this location. If not, repeat the procedure above and, instead of pointing to the directory, instead select "Let me pick from a list of device drivers on my computer". You should have either a "TI XDS Channel A" (or B) or "XDS100 Class Debug Port" (or "XDS100 Class Auxiliary Port").

Hope this helps,
Rafael

Dear Rafael,

Thanks for your message.

As you suggested, I inserted the circuit board of TMS320VC5505 eZDSP USB STICK (Revision B) into PC and then right clicked on below highlighted part in red.

Then, as you suggested, I tried to update Driver Software" and  selected "Browse my computer for driver software" and then pointed to the following directory:
C:\ti\ccsv6\ccs_base\emulation\windows\xds100_drivers
However, I get the message as shown below:

I am not sure why I am not able connect ccsv6 to revision b of ezdsp. I can connect ccsv6 to revision D of ezdsp.

 

Satyajit,

Thanks for following this procedure; since "Rev D" works for you, this seems to indicate to me that your "Rev B" board has a blank FTDI device on it.

Sections 6.4.8 and 6.4.9 of the page I sent before will help you with verifying this scenario and reprogramming the FTDI device.

Note: if you are using the newer FTDI program called FT_Prog (the section above still mentions MProg), please use the attached template that I got from my USBSTK5505 Rev A and follow the procedure shown in the links below.

Hope this helps,

Rafael

USBSTK5505_XDS100v1.zip

Dear Rafael,

Thanks for message.

Actually, "Rev B" board might not have a blank FTDI device on it as I can upload the bin file into the device using ccs v4.

The problem could be with software ccsv 6 as I am not able to connect "Rev B" board with css v6. However, I can connect the board using ccs v4.