TI中文支持网—–[Print the reset-command software log-file]—————————–
This utility has selected a 100- or 510-class product.
This utility will load the adapter 'jioserdesusbv3.dll'.
The library build date was 'Jun 3 2019'.
The library build time was '15:24:38'.
The library package version is '8.2.0.00004'.
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 '-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 XDS100v3 USB Debug Probe_0]
JTAG电路参考datasheet 14pin，不知道问题在哪，280049C的JTAG 14pin 2脚信号是否为悬空处理？
Susan Yang：
关于该错误，您可以看一下下面链接的说明
software-dl.ti.com/…/ccsv7_debugging_jtag_connectivity_issues.html
另外您在CCS内的target connection内的设置是怎样的？是否有使用Uniflash试一下？
user4295278：
回复 Susan Yang:
目前这个状态，Uniflash是怎么操作？
Susan Yang：
回复 user4295278:
uniflash的话，您可以点击右上角的Detect来检测是否可以连接，我这边是使用launchapad来测试的
若是还是不能连接的话，请给出您的相关原理图，谢谢
Susan Yang：
回复 user4295278:
另外在E2E上也有类似的帖子，您可以参考一下
e2e.ti.com/…/898467
user4295278：
回复 Susan Yang:
安装了UniFlash，可正常用的launchpad不能被检测出来，launchpad—F280049C。
另有问题，烧录之前晶振是否需要起振？还是DSP烧录成功过以后，晶振才会起振？目前晶振未起振。
JTAG相关引脚原理图即之前提供的完全参照datasheet配置，其他引脚会影响烧录么？
Susan Yang：
回复 user4295278:
user4295278安装了UniFlash，可正常用的launchpad不能被检测出来，launchpad—F280049C。
您现在使用的是launchpad？您之前不是说使用的是XDS100V3吗？launchpad上是XDS110
我对您的描述有些疑惑
另外launchpad的话，在CCS中需要设置为cjtag 2-pin
user4295278：
回复 Susan Yang:
我用launchpad调试过，是用的板载XDS110，里面的config配置是对的，可以正常调试；
现在自己画的板子用的14PinJTAG，XDS100V3，config配置就是选择280049C，XDS100V3，出现的上述问题。
Susan Yang：
回复 user4295278:
好的，谢谢您的反馈
software-dl.ti.com/…/ccsv7_debugging_jtag_connectivity_issues.html
这个链接内，您的回读数据是怎样的？自己画的板子使用uniflash能识别吗？
另外有一个相关的连接指南，您可以看一下
software-dl.ti.com/…/emu_xds_target_connection_guide.html
user4295278：
回复 Susan Yang:
以下是读回数据：
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.uniflash无法识别包括launchxl-f280049c在内的板子，只能手动添加，uniflash可以刷launchpad的程序
想要判断DSP供电是否正常，除了1.2V和3.3V供电，还有其他方法判断么？DSP未正常工作是否会有这个报错？
Susan Yang：
回复 user4295278:
类似下面的这种回读数据
-----[Perform the Integrity scan-test on the JTAG DR]------------------------This test will use blocks of 512 32-bit words.This test will be applied just once.Do a test using 0xFFFFFFFF.Scan tests: 1, skipped: 0, failed: 0Do a test using 0x00000000.Scan tests: 2, skipped: 0, failed: 0Do a test using 0xFE03E0E2.Test 3 Word 0: scanned out 0xFE03E0E2 and scanned in 0xFC07C1C5.Test 3 Word 1: scanned out 0xFE03E0E2 and scanned in 0xFC07C1C5.Test 3 Word 2: scanned out 0xFE03E0E2 and scanned in 0xFC07C1C5.Test 3 Word 3: scanned out 0xFE03E0E2 and scanned in 0xFC07C1C5.Test 3 Word 4: scanned out 0xFE03E0E2 and scanned in 0xFC07C1C5.Test 3 Word 5: scanned out 0xFE03E0E2 and scanned in 0xFC07C1C5.Test 3 Word 6: scanned out 0xFE03E0E2 and scanned in 0xFC07C1C5.Test 3 Word 7: scanned out 0xFE03E0E2 and scanned in 0xFC07C1C5.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: 1Do a test using 0x01FC1F1D.Scan tests: 4, skipped: 0, failed: 2Do a test using 0x5533CCAA.Scan tests: 5, skipped: 0, failed: 3Do a test using 0xAACC3355.Scan tests: 6, skipped: 0, failed: 4Some of the values were corrupted - 66.7 percent.The JTAG DR Integrity scan-test has failed.—–[Perform the Integrity scan-test on the JTAG DR]————————
This test will use blocks of 512 32-bit words.This test will be applied just once.
Do a test using 0xFFFFFFFF.Scan tests: 1, skipped: 0, failed: 0Do a test using 0x00000000.Scan tests: 2, skipped: 0, failed: 0Do a test using 0xFE03E0E2.Test 3 Word 0: scanned out 0xFE03E0E2 and scanned in 0xFC07C1C5.Test 3 Word 1: scanned out 0xFE03E0E2 and scanned in 0xFC07C1C5.Test 3 Word 2: scanned out 0xFE03E0E2 and scanned in 0xFC07C1C5.Test 3 Word 3: scanned out 0xFE03E0E2 and scanned in 0xFC07C1C5.Test 3 Word 4: scanned out 0xFE03E0E2 and scanned in 0xFC07C1C5.Test 3 Word 5: scanned out 0xFE03E0E2 and scanned in 0xFC07C1C5.Test 3 Word 6: scanned out 0xFE03E0E2 and scanned in 0xFC07C1C5.Test 3 Word 7: scanned out 0xFE03E0E2 and scanned in 0xFC07C1C5.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: 1Do a test using 0x01FC1F1D.Scan tests: 4, skipped: 0, failed: 2Do a test using 0x5533CCAA.Scan tests: 5, skipped: 0, failed: 3Do a test using 0xAACC3355.Scan tests: 6, skipped: 0, failed: 4Some of the values were corrupted – 66.7 percent.
The JTAG DR Integrity scan-test has failed.
