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.

CCS/TMS320F28027F: Connectiong the device to CCS

Part Number: TMS320F28027F
Other Parts Discussed in Thread: TMS320F28027, UNIFLASH

Tool/software: Code Composer Studio

Hi there,

I have issue connecting TMS320F28027F using xds100v2. (I myself designed the board, copying exactly LAUNCHXL-28027F).

I already followed these steps two times:

new target configuration >  Selecting XDS100v2 > Device: TMS320F28027 (my device is:TMS320F28027FPTT) >  Save.

Test connection is successful, and here is the message:

[Start: Texas Instruments XDS100v2 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\Mehdi\AppData\Local\TEXASI~1\CCS\
    ti\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 'Jan 24 2019'.
The library build time was '14:27:46'.
The library package version is '8.0.903.6'.
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 XDS100v2 USB Debug Probe_0]

 

and Then launching target configuration and selecting connect to target.

I did it two times and got these errors:

C28xx: GEL Output: 
Device Calibration not complete, check if device is unlocked and recalibrate.C28xx: Flash Programmer: Warning: The configured device (TMS320F280270), does not match the detected device (). Flash Programming operations could be affected. Please consider modifying your target configuration file.

Break at address "0x3ff7bf" with no debug information available, or outside of program code.

As I check  0x3F7FF8 – 0x3F7FFF memory addresses using UniFlash, they're all zeros. (Both times)... Note that I don't have power issues and XRSn pin is toggling.

1. Why am I facing this error and how to solve the issue?

3. Is there any step by step guide (document or videos) for me to connect 28027F through xds100v2?

2. Is there any chance by changing "Boot Mode". how can I change "Boot Mode"? I know the table which is presented in the datasheet, I don't know how to change the boot mode and what exactly is the meaning of each of the boot modes?

  • Mehdi,

    If the password locations are showing value 0x0 then it means some how these location got programmed. Can you check your map file and see if there is anything mapped on that location?

    Regards,

    Vivek Singh

  • Dear Vivek Singh,

    I haven't reached this level.

    As I told you above, I just wanted to connect to my device and I got those errors... I explained it step by step.

    :((

    Just some devices are left. I'm afraid, I try again and then I permanently lock it again!

    BTW I attach my design and PCB FYKI. Please check, if there are any mistakes.

    JTAG_CONNECTION.pdf

  • My problem was already solved. :)

    I designed a new board with TMS320F28027F and it worked well. Before getting started, I checked XRS pin and it was not toggling!

    The only difference between my new board and the old one is that XRS pin in the previous design was toggling at first and in this one wasn't (I mean it was 3.3V).

    I don't know where the problem was and how could that pin's status differs on each board!?!