TI中文支持网请教一下大家，我使用XDS100V2对合众达的DEC5502板子调试，但是现在死活连接不上板子，请大家帮忙分析一下问题出在哪里。
首先是驱动已经安装好了，如图：
然后建立CCXML配置文件，选择XDS100V2和TMS320VC5502芯片后，点击test connection后，提示出现fail，如下：
[Start]
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\YuAnNing\AppData\Local\.TI\1212777678\
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 'May 30 2012'.
The library build time was '22:52:27'.
The library package version is '5.0.747.0'.
The library component version is '35.34.40.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 512 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 512 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.
Test 3 Word 6: scanned out 0xFE03E0E2 and scanned in 0xFFFFFFFF.
Test 3 Word 7: scanned out 0xFE03E0E2 and scanned in 0xFFFFFFFF.
Test 3 Word 8: scanned out 0xFE03E0E2 and scanned in 0xFFFFFFFF.
Test 3 Word 9: scanned out 0xFE03E0E2 and scanned in 0xFFFFFFFF.
Test 3 Word 10: scanned out 0xFE03E0E2 and scanned in 0xFFFFFFFF.
Test 3 Word 11: scanned out 0xFE03E0E2 and scanned in 0xFFFFFFFF.
Test 3 Word 12: scanned out 0xFE03E0E2 and scanned in 0xFFFFFFFF.
Test 3 Word 13: scanned out 0xFE03E0E2 and scanned in 0xFFFFFFFF.
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 – 66.3 percent.
The JTAG IR 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: 0
Do a test using 0x00000000.
Scan tests: 2, skipped: 0, failed: 0
Do a test using 0xFE03E0E2.
Test 3 Word 17: scanned out 0xFE03E0E2 and scanned in 0xFFFFE0E2.
Test 3 Word 18: scanned out 0xFE03E0E2 and scanned in 0xFFFFFFFF.
Test 3 Word 19: scanned out 0xFE03E0E2 and scanned in 0xFFFFFFFF.
Test 3 Word 20: scanned out 0xFE03E0E2 and scanned in 0xFFFFFFFF.
Test 3 Word 21: scanned out 0xFE03E0E2 and scanned in 0xFFFFFFFF.
Test 3 Word 22: scanned out 0xFE03E0E2 and scanned in 0xFFFFFFFF.
Test 3 Word 23: scanned out 0xFE03E0E2 and scanned in 0xFFFFFFFF.
Test 3 Word 24: scanned out 0xFE03E0E2 and scanned in 0xFFFFFFFF.
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.9 percent.
The JTAG DR Integrity scan-test has failed.
[End]
如果点击此时点击debug的话，会报错，如图：
我这个程序在CCS3.3下用XDS510调试器可以成功仿真的，然后把工程导入CCS5后，就是这种问题了。现在我就是不太清楚到底是驱动出现了问题，还是调试器的硬件出现问题，哪位有经验的可以指点一下，毕竟我也是新学，有好多东西不了解。谢谢大家。
noaming：
你好，你所描述的“CCS3.3下用XDS510调试器”
你用的是XDS510还是XDS100？
XDS100确认版本是V2吗？
Anning Yu：
回复 noaming:
你好！我有一个瑞泰创新的ICETEK-5100USB V2.0A仿真器（也不能算是xds510），用其在CCS3.3下成功调试了板子。
我上面问的是我另一个仿真器，上面标识的是XDS100V2，在CCS5.2下使用，但是出现上述问题。我刚才在CCXML文件中修改仿真器为XDS100V1时，测试连接的显示如下：
[Start]
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\YuAnNing\AppData\Local\.TI\1212777678\ 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 'May 30 2012'.The library build time was '22:52:27'.The library package version is '5.0.747.0'.The library component version is '35.34.40.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 512 32-bit words.
The test for the JTAG IR instruction path-length succeeded.The JTAG IR instruction path-length is 0 bits.
The test for the JTAG DR bypass path-length succeeded.The JTAG DR bypass path-length is 0 bits.
—–[Perform the Integrity scan-test on the JTAG IR]————————
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.Scan tests: 3, skipped: 0, failed: 0Do a test using 0x01FC1F1D.Scan tests: 4, skipped: 0, failed: 0Do a test using 0x5533CCAA.Scan tests: 5, skipped: 0, failed: 0Do a test using 0xAACC3355.Scan tests: 6, skipped: 0, failed: 0All 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 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.Scan tests: 3, skipped: 0, failed: 0Do a test using 0x01FC1F1D.Scan tests: 4, skipped: 0, failed: 0Do a test using 0x5533CCAA.Scan tests: 5, skipped: 0, failed: 0Do a test using 0xAACC3355.Scan tests: 6, skipped: 0, failed: 0All of the values were scanned correctly.
The JTAG DR Integrity scan-test has succeeded.
[End]
这似乎表明测试通过了！但是debug的话还是和原来是一样的错误。这个仿真器我拆开看过，里面是一个FT2232H和一个CPLD，应该是XDS100V2。
noaming：
回复 Anning Yu:
The JTAG DR Integrity scan-test has succeeded.测试通过了，说明仿真器驱动没有问题了。
Debug是什么错误打印信息？通过JTAG和板子链接的吗？
Anning Yu：
回复 noaming:
debug的返回信息就是和我一楼贴的一样啊！后面这个检测通过了，但是这是我在选为XDS100V1条件下才出现的，而实际上我拿的是一个V2版的仿真器。
ge sw：
回复 Anning Yu:
你们好这个问题是怎么解决的啊 我也遇到了同样的问题 很着急啊
ge sw：
回复 ge sw:
我发现了这个问题
就是如果外部看门狗在的话，连接仿真器，就会把这个CPU给干掉，然后就会出现这个连不上的错误，所以，一定一定不能带着看门狗的跳线帽连接仿真器
shine sun：
回复 noaming:
遇到同样的问题，希望解决
ZYN：
您好！
想问下您的问题怎么解决的？遇到了相同的问题。
多谢
noaming：
回复 ZYN:
你可以重新建一个帖子，然后描述一下问题。
现在常使用的CCS版本是6.0，链接比较稳定
ZYN：
回复 noaming:
好的，多谢
