CCS: What CCS´s version work with TMS320F28335 (Delfino)?

Geraldo,

The F28335 Experimenters kit should work with all of those versions of CCS.

There is an issue on Windows 10 where some users see a crash when they try to launch the debugger. However installing the latest TI Emulation update will resolve that issue.

Are you seeing a crash or just a failure to connect? What is the error message? Can you attach a screen capture?

I have a F28035 controlCARD plugged into my experimenters kit docking station. It connects fine for me with CCSv7.0. I have the usb cable connected and not the 5V power supply. I have the red switch set to USB.

Regards,
John

John,

Thank you by your answer. I´ve just installed ccs 7 again, but the configuration test didn´t run. See bellow:

1) I created a new "Target Configuration File" with TMS320F28335 and "Texas Instruments XDS100v1 USB Debug Probe". See the 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 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/tixds100c28x.xml" id="drivers" xml="tixds100c28x.xml" xmlpath="drivers"/>
<platform XML_version="1.2" id="platform_0">
<instance XML_version="1.2" desc="TMS320F28335_0" href="devices/f28335.xml" id="TMS320F28335_0" xml="f28335.xml" xmlpath="devices"/>
</platform>
</connection>
</configuration>
</configurations>

When I click in "Test Connection" I got following error:

[Start: Texas Instruments XDS100v1 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\geraldo\AppData\Local\TEXASI~1\
CCS\ccsv700\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 'jioserdesusb.dll'.
The library build date was 'Dec 9 2016'.
The library build time was '13:48:53'.
The library package version is '6.0.504.1'.
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).

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 '-150' (0xffffff6a).
The title is 'SC_ERR_FTDI_FAIL'.

The explanation is:
One of the FTDI driver functions used during
configuration returned a invalid status or an error.

[End: Texas Instruments XDS100v1 USB Debug Probe_0]

What do you think about this?

Thanks,

Geraldo.

Geraldo,

The SC_ERR_FTDI_FAIL error is an odd one but we have seen it before. It is an issue with CCS being able to communicate with the FTDI chip that is used on the XDS100 debug probe.

There is a set of instructions at the link below that has resolved the issue for some other users. Can you give these a try?
processors.wiki.ti.com/.../Debugging_JTAG_Connectivity_Problems

Regards,
John

John,

Last week I was attending a course then I could´t check this thread. 

Today I´ve just tested my project with another Delfinos´s Kit  and the the test run succesfully. Then I imported the example project named "Example_2833xLEDBlink" in my IDE and clicked in "Debug" button. Everything run well but the led in the TMS320´s board doesn´t blink.

What must I do? Must I use "debug" option? See bellow 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="configuration_0">
<instance XML_version="1.2" desc="Texas Instruments XDS100v1 USB Debug Probe" href="connections/TIXDS100usb_Connection.xml" id="Texas Instruments XDS100v1 USB Debug Probe" xml="TIXDS100usb_Connection.xml" xmlpath="connections"/>
<connection XML_version="1.2" id="Texas Instruments XDS100v1 USB Debug Probe">
<instance XML_version="1.2" href="drivers/tixds100c28x.xml" id="drivers" xml="tixds100c28x.xml" xmlpath="drivers"/>
<platform XML_version="1.2" id="platform_0">
<instance XML_version="1.2" desc="TMS320F28335" href="devices/f28335.xml" id="TMS320F28335" xml="f28335.xml" xmlpath="devices"/>
</platform>
</connection>
</configuration>
</configurations>

Thanks,

Geraldo.

Geraldo,

Your configuration file looks fine. I will pull in a C2000 expert to figure out why the LED is not blinking.

Regards,
John

Chris,

After change the lines of the source code the project has just run and the led blinked. Thank you.

I´m new in Texas´s technology but I´ll study the documentation to get knowlegment in DSP.

Thank you by your help and I´d like suggest to Texas´s team to update the online examples from the repository to work with CS2000´s devices.

By the way, how can I close this thread?

Thanks and best regards,

Geraldo.