CCS/TMS320F28335: CCS/TMS320F28335

Zen Yee Kuek said:

I have tried loading the example "Flashing LEDs" from the TI Resource Explorer to the TMDSCNCD28335 that is connected to the Docking station, USB-EMU [R3}. However, the code cannot be executed and I have encountered several errors. 

The errors are appearing at project build time, and until the build is successful the program cannot be loaded to the target device.

Looking at the build output, it appears that some paths are not resolved correctly. For example:

--include_path="C:/Users/device_support/f2833x/v132/DSP2833x_headers/include" --include_path="C:/Users/device_support/f2833x/v132/DSP2833x_common/include" --include_path="C:/Users/development_kits/~SupportFiles/F2833x_headers"

The /device_support directory is inside ControlSuite, so I would expect the above path to be C:/ti/controlSUITE/device_support/f2833x/v132..., not C:/Users/device_support/f2833x/v132.

How exactly are you importing the project? Try opening a new CCS workspace and importing the project again.

Although this should all work with the versions you are using, both CCSv6 and ControlSuite are now old software. C2000Ware is the newer package that replaces ControlSuite and CCSv8 is the most current version. I would suggest upgrading to these newer versions unless there is a compelling reason to stay with the older versions. CCSv8 has a new, easy-to-use Resource Explorer interface from where you can directly import example projects from C2000Ware to help you get started quickly.

CCSv8: http://processors.wiki.ti.com/index.php/Download_CCS

C2000Ware: Install from standalone package or directly from Resource Explorer within CCS.

okay, i will install the new softwares and keep you posted! Thank you so much for the help.

Hi there, I have installed the new software and followed the tutorial videos in trying out the examples, and one difference that happened was that I had to configure the .ccxml file (target configuration file) and configure it to Texas Instrument XDS100v1 USB Debug Probe, and set the device to TMS320F28335. However, this device is plugged onto a Texas Instrument Docking Station, the USB-EMU R3. Would this affect it in any way? When I test the connection for the target configuration file, this is what is shown.

[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\Zenyee\AppData\Local\TEXASI~1\CCS\
ti\2\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 'Nov 27 2018'.
The library build time was '13:02:43'.
The library package version is '8.0.903.4'.
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 succeeded.
The JTAG IR instruction path-length is 38 bits.

The test for the JTAG DR bypass path-length succeeded.
The JTAG DR bypass path-length is 1 bits.

-----[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.
Scan tests: 2, skipped: 0, failed: 0
Do a test using 0xFE03E0E2.
Scan tests: 3, skipped: 0, failed: 0
Do a test using 0x01FC1F1D.
Scan tests: 4, skipped: 0, failed: 0
Do a test using 0x5533CCAA.
Scan tests: 5, skipped: 0, failed: 0
Do a test using 0xAACC3355.
Scan tests: 6, skipped: 0, failed: 0
All of the values were scanned correctly.

The JTAG IR Integrity scan-test has succeeded.

-----[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.
Scan tests: 2, skipped: 0, failed: 0
Do a test using 0xFE03E0E2.
Scan tests: 3, skipped: 0, failed: 0
Do a test using 0x01FC1F1D.
Scan tests: 4, skipped: 0, failed: 0
Do a test using 0x5533CCAA.
Scan tests: 5, skipped: 0, failed: 0
Do a test using 0xAACC3355.
Scan tests: 6, skipped: 0, failed: 0
All of the values were scanned correctly.

The JTAG DR Integrity scan-test has succeeded.

[End: Texas Instruments XDS100v1 USB Debug Probe_0]


After this is done, I debugged the program and this is the result that is shown.

**** Build of configuration Debug for project Example_2833xLEDBlink ****

"C:\\ti\\ccsv8\\utils\\bin\\gmake" -k all

gmake: Nothing to be done for 'all'.

**** Build Finished ****

However, the LEDs on the board are not blinking. Any help would be very much appreciated!

The Test Connection seems to have passed ok. 

Are you using an F28335 experimenter's kit? Most of the example projects are set up to load and run from RAM, so after the project is built and loaded onto the device, you would need to put it to Run manually using the CCS menu Run->Resume.

Could you try out another example, like gpio_toggle? That should also toggle the LEDs on the control card.

Hi,

Thank you so much for your help. I have resolved it and it was due to the LED being connected to pin 31 but the code was programming pin 32 instead. However, another issue has occured, which has to do with flashing the code into memory. There is no flash option in the menu containing the debug option, and that erasing what is on the flash memory itself is possible, however, flashing the code into the flash memory churns out an issue with the memory map and makes the flashing procedure stop. I have tried the example for flashing, and it does not work either. Would there be any advice that can be given? Sorry for any inconvenience caused.

Best Regards,
Zen