TMS320F28027: Onboard XDS110 and TMS320F28027

Susan Yang

Part Number: TMS320F28027
Other Parts Discussed in Thread: MSP-EXP432E401Y, , MSP432E401Y

Dear team,

My customer is using Onboard XDS110(MSP-EXP432E401Y) to debug their custom TMS320F28027 board. But the Onboard XDS110 CAN NOT debug their custom TMS320F28027 board.

The F28027 board works well because the independent XDS100V2 and XDS110 emulators can debug it.

CCS Test Connection Log

[Start: Texas Instruments XDS110 USB Debug Probe]

Execute the command:

%ccs_base%/common/uscif/dbgjtag -f %boarddatafile% -rv -o -S integrity

[Result]


-----[Print the board config pathname(s)]------------------------------------

C:\Users\ADMINI~1\AppData\Local\TEXASI~1\
CCS\ccs1011\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 'jioxds110.dll'.
The library build date was 'May 7 2020'.
The library build time was '21:10:18'.
The library package version is '9.2.0.00002'.
The library component version is '35.35.0.0'.
The controller does not use a programmable FPGA.
The controller has a version number of '5' (0x00000005).
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 XDS110 with USB interface.
The link from controller to target is direct (without cable).
The software is configured for XDS110 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 has occurred and this utility has aborted]--------------------

This error is generated by TI's USCIF driver or utilities.

The value is '-233' (0xffffff17).
The title is 'SC_ERR_PATH_BROKEN'.

The explanation is:
The JTAG IR and DR scan-paths cannot circulate bits, they may be broken.
An attempt to scan the JTAG scan-path has failed.
The target's JTAG scan-path appears to be broken
with a stuck-at-ones or stuck-at-zero fault.

[End: Texas Instruments XDS110 USB Debug Probe]

Customers have tried to lower the TCLK frequency to 100kHz, 500kHz, 1MHz, 2MHz, 3MHz, and the error message remains unchanged.

They CAN use the same way to debug 28035 board.

Test waveform when use independent XDS110 emulators：

Test waveform when use onboard XDS110 emulators：

Please help to check this issue.

over 4 years ago

0 MatthewPate over 4 years ago

TI__Guru* 80640 points

Susan,

I'm going to give my answer, but I'm also going to loop in the MSP432 team since they designed this launchpad.

I am unsure that the XDS RESET OUT signal is equivalent to the TRSTn signal that is on the F2802x JTAG. On this LaunchPad I think this signal is a reset output signal to drive the reset on the target MSP432, vs controlling the Test Reset signal that our JTAG requires on the F28027.

The XDS110 implementation looks to be 4 pin cJTAG vs the full JTAG selection in CCS Target.

The external XDS110 has this signal correctly brought to the standard TI 14-pin header.

Now, on devices with TRSTn, this is a simple signal, holding it low will keep the test logic in reset, bringing it high will take the test logic out of reset.

If you configure the emulator on the MSP432 LP as a full JTAG in the XDS110 target config, and then manually (with a wire jumper) pull TRSTn on the F28027 from low to high, then connect, this may work.

Again, I'm going to push to the MSP432 forum in case they have more info.

Best,

Matthew

0 Susan Yang over 4 years ago in reply to MatthewPate

TI__Genius 9955 points

Thanks matt!

Now the customer can debug 28027 with the onboard XDS110.

But he CAN NOT connect 28035 with the same onboard XDS110.

Test waveform when use independent XDS110 emulators：

Test waveform when use onboard XDS110 emulators：

Please help to check this issue.

0 desouza over 4 years ago in reply to Susan Yang

TI__Guru**** 171224 points

Hi,

I was asked to provide some comments.

A few reference waveforms can be seen at the post below. They may be useful to compare levels, signaling, etc.

https://e2e.ti.com/support/tools/code-composer-studio-group/ccs/f/code-composer-studio-forum/661170/ccs-tm4c123gh6pm-xds100v2-debugging-issue/2442314#2442314

MatthewPate is correct about the TRST signal being needed to reset the JTAG state machine on the C2000 and the MSP432E401Y 10-pin JTAG connector does not feature this signal. The XDS Reset Out is instead the nRESET (also called System Reset). Details about the various pinouts can be found at:

https://dev.ti.com/tirex/explore/node?node=AEnDVmEAFjxrbZ8Vfn.lBg__FUz-xrs__LATEST

Most of the time the C2000 devices can be connected without the TRST signal, but it can be critical for certain operations such as Flash programming.

https://e2e.ti.com/support/microcontrollers/c2000-microcontrollers-group/c2000/f/c2000-microcontrollers-forum/544269/tms320f28069f-jtag-programming-via-launchpad/1987763#1987763

One additional aspect is that certain C2000 boards have a very low pull down resistor on the TRST signal that affects the XDS110 operation (although it works with XDS100 or other Debug Probes). A reference is mentioned in the thread below:

https://e2e.ti.com/support/tools/code-composer-studio-group/ccs/f/code-composer-studio-forum/628509/ccs-tmdsemu110-u-xds110-not-working-but-my-xds100v2-works-fine/2334404#2334404

It seems you already tried various TCLK speeds, which is usually a great method to try to overcome any issues with the connections. Additional tips, for both HW and SW, can be found at:

https://dev.ti.com/tirex/explore/node?node=AJ0stIncCUg6d9b-LOVu9w__FUz-xrs__LATEST

Hope this helps,

Rafael

0 Susan Yang over 4 years ago in reply to desouza

TI__Genius 9955 points

The customer still can NOT connect 28035.

Do a test using 0xFE03E0E2.
Test 3 Word 0: scanned out 0xFE03E0E2 and scanned in 0x5FE03E07.
Test 3 Word 1: scanned out 0xFE03E0E2 and scanned in 0x0FE03E0C.
Test 3 Word 2: scanned out 0xFE03E0E2 and scanned in 0x0FE03E0E.
Test 3 Word 3: scanned out 0xFE03E0E2 and scanned in 0x0FE03E0E.
Test 3 Word 4: scanned out 0xFE03E0E2 and scanned in 0x0FE03E0E.
Test 3 Word 5: scanned out 0xFE03E0E2 and scanned in 0x0FE03E0E.
Test 3 Word 6: scanned out 0xFE03E0E2 and scanned in 0x0FE03E0E.
Test 3 Word 7: scanned out 0xFE03E0E2 and scanned in 0x0FE03E0E.

The details of the first 8 errors have been provided.
The utility will now report only the count of failed tests.
Scan tests: 3, skipped: 0, failed: 1
Do a test using 0x01FC1F1D.
Scan tests: 4, skipped: 0, failed: 2
Do a test using 0x5533CCAA.
Scan tests: 5, skipped: 0, failed: 3
Do a test using 0xAACC3355.
Scan tests: 6, skipped: 0, failed: 4
Some of the values were corrupted - 65.6 percent.

The JTAG IR Integrity scan-test has failed.

0 desouza over 4 years ago in reply to Susan Yang

TI__Guru**** 171224 points

Susan,

Please apologize for the delay. Was your customer able to get around this issue?

The invalid data read back issue is mostly related to hardware. The Debugging JTAG page I sent in my previous post (last link) contains information about this issue - just search for invalid data read back.

As mentioned in the reference, this error can be caused by the pull down TRST resistor.

I don't have much more ideas to try, but hopefully these will be enough to overcome this issue.

Regards,

Rafael

C2000™︎ microcontrollers

C2000 microcontrollers forum

TMS320F28027: Onboard XDS110 and TMS320F28027