DSP28335用XDS100v2连接不上，求问题所在？

刚接触DSP28335，CCS5.3编程环境，XDS100v2下载器，同样的程序和配置连接下载一个老板没有问题，现在项目需要用了一个新板，但是连接测试错误，错误信息如下，求高手指教。
[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\ADMINI~1\AppData\Local\.TI\4084209646\
    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 'Oct  3 2012'.
The library build time was '21:58:41'.
The library package version is '5.0.872.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 failed.
The many-ones then many-zeros tested length was 6 bits.
The many-zeros then many-ones tested length was -16352 bits.
The test for the JTAG DR bypass path-length failed.
The many-ones then many-zeros tested length was 8 bits.
The many-zeros then many-ones tested length was -16352 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.
Test 2 Word 0: scanned out 0x00000000 and scanned in 0x000000FF.
Scan tests: 2, skipped: 0, failed: 1
Do a test using 0xFE03E0E2.
Test 3 Word 0: scanned out 0xFE03E0E2 and scanned in 0xFC1FE7FF.
Test 3 Word 1: scanned out 0xFE03E0E2 and scanned in 0xFC1FC7FF.
Test 3 Word 2: scanned out 0xFE03E0E2 and scanned in 0xFC1FE7FF.
Test 3 Word 3: scanned out 0xFE03E0E2 and scanned in 0xFC1FE7EF.
Test 3 Word 4: scanned out 0xFE03E0E2 and scanned in 0xFC1FC7FF.
Test 3 Word 5: scanned out 0xFE03E0E2 and scanned in 0xFC1FC3FF.
Test 3 Word 6: scanned out 0xFE03E0E2 and scanned in 0xFC0FE7FF.
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: 2
Do a test using 0x01FC1F1D.
Scan tests: 4, skipped: 0, failed: 3
Do a test using 0x5533CCAA.
Scan tests: 5, skipped: 0, failed: 4
Do a test using 0xAACC3355.
Scan tests: 6, skipped: 0, failed: 5
Some of the values were corrupted - 66.7 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.
Test 2 Word 0: scanned out 0x00000000 and scanned in 0x0000007F.
Scan tests: 2, skipped: 0, failed: 1
Do a test using 0xFE03E0E2.
Test 3 Word 0: scanned out 0xFE03E0E2 and scanned in 0xFC1FE7FF.
Test 3 Word 1: scanned out 0xFE03E0E2 and scanned in 0xFC3FE7FF.
Test 3 Word 2: scanned out 0xFE03E0E2 and scanned in 0xFC0FE7FF.
Test 3 Word 3: scanned out 0xFE03E0E2 and scanned in 0xFC3FE7FF.
Test 3 Word 4: scanned out 0xFE03E0E2 and scanned in 0xFC1FC7FF.
Test 3 Word 5: scanned out 0xFE03E0E2 and scanned in 0xFE1FE7FF.
Test 3 Word 6: scanned out 0xFE03E0E2 and scanned in 0xFC1FE7FF.
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: 2
Do a test using 0x01FC1F1D.
Scan tests: 4, skipped: 0, failed: 3
Do a test using 0x5533CCAA.
Scan tests: 5, skipped: 0, failed: 4
Do a test using 0xAACC3355.
Scan tests: 6, skipped: 0, failed: 5
Some of the values were corrupted - 66.7 percent.
The JTAG DR Integrity scan-test has failed.
[End]

在线等，求帮助！

看不懂测试文档里的内容，能连接上以前的旧板子，证明软件上没有问题，但是现在硬件上没有查出问题，搁浅在这了，求帮助?

检查JTAG有没有插反，检查选择的仿真器类型是不是和你的仿真器型号一样

连接线又检查了一遍，没有错误。仿真器类型和型号也不会错，因为设置相同的连接别的28335就行，连接我这块就连不上了，我想知道从测试文档里最后几个failed中能否看出错误所在?

想问一下各位朋友，怎么检测DSP的JTAG引脚，现在怀疑是硬件上的问题，但是不知道怎么去测试，求方法。

突然想知道现在DSP的行情怎么样，本人刚毕业研究生，入了这个行不知道以后的前景会怎么样?

连接时提示这个错误，是什么问题
Error connecting to the target:
(Error -1015 @ 0x0)
Device is not responding to the request.  Device may be locked, or the emulator connection may be unreliable. Unlock the device if possible, and power-cycle the board. If error persists, confirm configuration and/or try more reliable JTAG settings (e.g. lower TCLK).
(Emulation package 5.0.872.0)

那你检查一JTAG的各个引脚是否有不能用的

可能是DSP芯片的问题，检查一下jtag周边的电路，看看电阻电容有没有焊接错误。

应该是DSP板子的供电出了问题