TI中文支持网[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)]————————————
/root/.TI/1524211065/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 'libjioserdesusb.so'.
The library build date was 'Aug 21 2013'.
The library build time was '00:19:23'.
The library package version is '5.1.232.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 JTAG IR instruction scan-path is stuck-at-zero.
The test for the JTAG DR bypass path-length failed.
The JTAG DR bypass scan-path is stuck-at-zero.
—–[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.
Test 1 Word 0: scanned out 0xFFFFFFFF and scanned in 0x00000000.
Test 1 Word 1: scanned out 0xFFFFFFFF and scanned in 0x00000000.
Test 1 Word 2: scanned out 0xFFFFFFFF and scanned in 0x00000000.
Test 1 Word 3: scanned out 0xFFFFFFFF and scanned in 0x00000000.
Test 1 Word 4: scanned out 0xFFFFFFFF and scanned in 0x00000000.
Test 1 Word 5: scanned out 0xFFFFFFFF and scanned in 0x00000000.
Test 1 Word 6: scanned out 0xFFFFFFFF and scanned in 0x00000000.
Test 1 Word 7: scanned out 0xFFFFFFFF and scanned in 0x00000000.
The details of the first 8 errors have been provided.
The utility will now report only the count of failed tests.
Scan tests: 1, skipped: 0, failed: 1
Do a test using 0x00000000.
Scan tests: 2, skipped: 0, failed: 1
Do a test using 0xFE03E0E2.
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 – 83.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.
Test 1 Word 0: scanned out 0xFFFFFFFF and scanned in 0x00000000.
Test 1 Word 1: scanned out 0xFFFFFFFF and scanned in 0x00000000.
Test 1 Word 2: scanned out 0xFFFFFFFF and scanned in 0x00000000.
Test 1 Word 3: scanned out 0xFFFFFFFF and scanned in 0x00000000.
Test 1 Word 4: scanned out 0xFFFFFFFF and scanned in 0x00000000.
Test 1 Word 5: scanned out 0xFFFFFFFF and scanned in 0x00000000.
Test 1 Word 6: scanned out 0xFFFFFFFF and scanned in 0x00000000.
Test 1 Word 7: scanned out 0xFFFFFFFF and scanned in 0x00000000.
The details of the first 8 errors have been provided.
The utility will now report only the count of failed tests.
Scan tests: 1, skipped: 0, failed: 1
Do a test using 0x00000000.
Scan tests: 2, skipped: 0, failed: 1
Do a test using 0xFE03E0E2.
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 – 83.3 percent.
The JTAG DR Integrity scan-test has failed.
[End]
Louis：
你好，
你说的仿真异常指的是无法使用仿真器连接DM368板子么？
pq wang：
回复 Louis:
是的连接APPRO dm368异常，均使用默认的配置，不知道是不是哪里设置的不对。
Eason Wang：
回复 pq wang:
XDS100接368，稳定性不是太好
建议你先降低TCK频率试试，并先做仿真器的自检
你的这个log贴出来，是自检的log还是connect target的log？
pq wang：
回复 Eason Wang:
是连接目标的测试log
手边，也有原厂的SEED-XDS560plus，有没有在CCS5.5下的驱动，麻烦一并共享一下包括linux和windos7的。
目前看到的驱动支持如下：
降低频率方式，测试中……
Eason Wang：
回复 pq wang:
仿真器驱动我不清楚，建议你可以直接问厂家。
一般来说你也可以选它表明兼容的spectrum或者blackhawk的型号。
我记得有些仿真器的驱动是基于特定CCS版本的，所以你有可能需要回退到5.1， 5.2的版本
pq wang：
回复 pq wang:
降低tck为最低的488hz时，输出连接测试结果如下：
[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)]————————————
/root/.TI/1524211065/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 'libjioserdesusb.so'.The library build date was 'Aug 21 2013'.The library build time was '00:19:23'.The library package version is '5.1.232.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 JTAG IR instruction path-length was not recorded.
—–[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
—–[An error has occurred and this utility has aborted]——————–
This error is generated by TI's USCIF driver or utilities.
The value is '-154' (0xffffff66).The title is 'SC_ERR_FTDI_WRITE'.
The explanation is:One of the FTDI driver functions used towrite data returned bad status or an error.
[End]
配置图示：
Eason Wang：
回复 pq wang:
我觉得还是回去看看JTAG有没有接好吧。。。（排线的两端。。。以及跳线设置）也得确保368机器是好的
然后看看560能不能连上。
Tony Chopper：
回复 Eason Wang:
请问怎么降低TCK频率，在哪里设置？
Tony Chopper：
回复 Eason Wang:
请问在CCS5里面怎么改变TCK频率
user1369122：
回复 Tony Chopper:
ccmxl文件去点一下，在CCS窗口里面会出现设置的。。。
或者你用help里面的搜索功能直接搜frequency啥的。。。
