完善资料让更多小伙伴认识你，还能领取20积分哦， 立即完善>
3天内不再提示
电子发烧友论坛|
我在ti的LM4F232开发板上，用XDS100V2进行JTAG调试，用了开发板10PIN端子。连接了 3.3V GND TMS TCK TDI TDO REST这几个信号。连接测试部成功。以下为测试报告
[Start] Execute the command: %ccs_base%/common/uscif/dbgjtag -f %boarddatafile% -rv -o -F inform,logfile=yes -S pathlength -S integrity [Result] -----[Print the reset-command software log-file]----------------------------- This utility has selected a 100- or 510-class product. This utility will load the adapter 'jioserdesu***.dll'. The library build date was 'Dec 19 2011'. The library build time was '21:32:12'. The library package version is '5.0.569.0'. The library component version is '35.34.39.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 now 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-ones. The test for the JTAG DR bypass path-length failed. The JTAG DR bypass scan-path is stuck-at-ones. -----[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 0xFFFFFFFF. Test 2 Word 1: scanned out 0x00000000 and scanned in 0xFFFFFFFF. Test 2 Word 2: scanned out 0x00000000 and scanned in 0xFFFFFFFF. Test 2 Word 3: scanned out 0x00000000 and scanned in 0xFFFFFFFF. Test 2 Word 4: scanned out 0x00000000 and scanned in 0xFFFFFFFF. Test 2 Word 5: scanned out 0x00000000 and scanned in 0xFFFFFFFF. Test 2 Word 6: scanned out 0x00000000 and scanned in 0xFFFFFFFF. Test 2 Word 7: scanned out 0x00000000 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: 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. Scan tests: 1, skipped: 0, failed: 0 Do a test using 0x00000000. Test 2 Word 0: scanned out 0x00000000 and scanned in 0xFFFFFFFF. Test 2 Word 1: scanned out 0x00000000 and scanned in 0xFFFFFFFF. Test 2 Word 2: scanned out 0x00000000 and scanned in 0xFFFFFFFF. Test 2 Word 3: scanned out 0x00000000 and scanned in 0xFFFFFFFF. Test 2 Word 4: scanned out 0x00000000 and scanned in 0xFFFFFFFF. Test 2 Word 5: scanned out 0x00000000 and scanned in 0xFFFFFFFF. Test 2 Word 6: scanned out 0x00000000 and scanned in 0xFFFFFFFF. Test 2 Word 7: scanned out 0x00000000 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: 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] 
0
|
|
相关推荐
3 个讨论
|
|
|
我试了一下，没有问题，楼主请用CCSV5再试。 需要一个转接头: processors.wiki.ti.com/.../JTAG_configuration_for_CCS_and_Stellaris |
|
|
|
|
|
|
|
Emily1225 发表于 2020-4-9 16:20 楼主也可以用XDS510工具调试，注意RTCK引脚的设置，9脚和11脚短接 |
|
|
|
|
|
|
|
只有小组成员才能发言，加入小组>>
NA555DR VCC最低电压需要在5V供电，为什么用3.3V供电搭了个单稳态触发器也使用正常?
666 浏览 3 评论
MSP430F249TPMR出现高温存储后失效了的情况，怎么解决？
597 浏览 1 评论
对于多级放大电路板，在PCB布局中，电源摆放的位置应该注意什么？
1047 浏览 1 评论
730 浏览 0 评论
普中科技F28335开发板每次上电复位后数码管都会显示，如何熄灭它？
519 浏览 1 评论
请问下tpa3220实际测试引脚功能和官方资料不符，哪位大佬可以帮忙解答下
157浏览 20评论
请教下关于TAS5825PEVM评估模块原理图中不太明白的地方，寻求答疑
119浏览 14评论
在使用3254进行录音的时候出现一个奇怪的现象，右声道有吱吱声，请教一下，是否是什么寄存器设置存在问题？
123浏览 13评论
TLV320芯片内部自带数字滤波功能，请问linein进来的模拟信号是否是先经过ADC的超采样？
121浏览 12评论
TPA6304-Q1: TPA6304 两片公用一组I2C的话，其中一片配置不成功怎么办
163浏览 10评论
/6 
关注我们的微信
下载发烧友APP
电子发烧友观察
版权所有 © 湖南华秋数字科技有限公司
电子发烧友 （电路图） 湘公网安备 43011202000918 号 电信与信息服务业务经营许可证：合字B2-20210191
工商网监
湘ICP备2023018690号
1746
评论
淘帖
1855
67
