Other Parts Discussed in Thread: TMDSEMU110-U
Tool/software: Code Composer Studio
Dear Code Composor Studio expert,
I found that XDS110 can't work for UCD3138 in CCS9.3. After switching to CCS7.4, there is no such issue. It looks to me that this issue is caused by the latest XDS110 firmware in CCS9.3. Please see below test results from my side.
Here are what I have gotten in v9.3:
C:\ti\ccs930\ccs\ccs_base\common\uscif>dbgjtag -f @xds110 -S integrity
Updating the XDS110 firmware ... complete.
-----[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.
Test 5 Word 2: scanned out 0x5533CCAA and scanned in 0x5D33CCAA.
Test 5 Word 5: scanned out 0x5533CCAA and scanned in 0x5D33CCAA.
Test 5 Word 6: scanned out 0x5533CCAA and scanned in 0x5D33CCAA.
Test 5 Word 9: scanned out 0x5533CCAA and scanned in 0x5D33CCAA.
Test 5 Word 13: scanned out 0x5533CCAA and scanned in 0x5D33CCAA.
Test 5 Word 17: scanned out 0x5533CCAA and scanned in 0x5D33CCAA.
Test 5 Word 20: scanned out 0x5533CCAA and scanned in 0x5D33CCAA.
Test 5 Word 21: scanned out 0x5533CCAA and scanned in 0x5D33CCAA.
The details of the first 8 errors have been provided.
The utility will now report only the count of failed tests.
Scan tests: 5, skipped: 0, failed: 1
Do a test using 0xAACC3355.
Scan tests: 6, skipped: 0, failed: 2
Some of the values were corrupted - 11.5 percent.
The JTAG IR Integrity scan-test has failed.
-----[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.
Test 5 Word 0: scanned out 0x5533CCAA and scanned in 0x1533CCAA.
Test 5 Word 1: scanned out 0x5533CCAA and scanned in 0x1533CCAA.
Test 5 Word 5: scanned out 0x5533CCAA and scanned in 0x1533CCAA.
Test 5 Word 9: scanned out 0x5533CCAA and scanned in 0x1533CCAA.
Test 5 Word 12: scanned out 0x5533CCAA and scanned in 0x1533CCAA.
Test 5 Word 17: scanned out 0x5533CCAA and scanned in 0x1533CCAA.
Test 5 Word 18: scanned out 0x5533CCAA and scanned in 0x1533CCAA.
Test 5 Word 21: scanned out 0x5533CCAA and scanned in 0x1533CCAA.
The details of the first 8 errors have been provided.
The utility will now report only the count of failed tests.
Scan tests: 5, skipped: 0, failed: 1
Do a test using 0xAACC3355.
Scan tests: 6, skipped: 0, failed: 2
Some of the values were corrupted - 11.2 percent.
The JTAG DR Integrity scan-test has failed.
After switching to CCS7.4, there is no such issue:
C:\ti\ccsv7\ccs_base\common\uscif>dbgjtag -f @xds110 -S integrity
Updating the XDS110 firmware ... complete.
-----[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.
