硬件平台:Beagle Bone Black
软件平台:CCS5.4
仿真器:XDS100V2
JTAG:采用飞线的方式,将20芯转为14芯,然后与仿真器连接
问题描述:
采用CCS5.4去调试,在test configuration的时候弹出以下错误信息:
[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\LKL\AppData\Local\.TI\693494126\
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 'Apr 1 2013'.
The library build time was '23:55:08'.
The library package version is '5.1.73.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 '-183' (0xffffff49).
The title is 'SC_ERR_CTL_CBL_BREAK_FAR'.
The explanation is:
The controller has detected a cable break far-from itself.
The user must connect the cable/pod to the target.
[End]
这个时候我们PC端仿真器的驱动是显示安装成功的。
另外之前网上看到说可能JTAG管脚的问题,我也已经把20芯JTAG的第15脚SRST接到14芯的2脚TRST上了。错误依旧如上。
另外还有尝试了上电的时候摁住S2开关,不让板子启动FLASH里面的操作系统,虽然系统没有启动,但是错误依旧如上。
请问大神,这是什么原因造成的?
Shine:
看一下飞线的话,JTAG口和JTAG头之间的距离有没有超过6inch,如果超过的话,要考虑用buffer增加驱动。你也可以测量一下JTAG信号看是否正确?
http://processors.wiki.ti.com/index.php/XDS_Target_Connection_Guide#Buffered_Case
Jian Zhou:
回复 Shine:
Jtag口信号比较多,不建议用飞线。
xiaolin wang:
回复 Shine:
JTAG口和JTAG头之间距离比较短,都没有超过10CM。这个会影响这么大吗?那一般的BBB开发板JTAG口调试的时候采用什么方案呢?有特殊的连接线和座子吗?
xiaolin wang:
回复 Jian Zhou:
请问对于BBB开发板,常用的JTAG口调试方案是什么呢?像我遇到的这个问题,会是其它软件层面造成的影响吗?
xiaolin wang:
回复 Jian Zhou:
请问有什么比较合适的JTAG口调试方案吗?会不会是我软件层面的问题导致连接不上?
yongqing wang:
回复 xiaolin wang:
飞线10CM这个应该没有啥问题,找找连接的问题
Jian Zhou:
回复 yongqing wang:
BBB板子的JTAG调试,一般都是焊上插针后找合适的插座,或者把插座裁剪下,一般不会飞线。
yongqing wang:
回复 Jian Zhou:
目前正在使用JTAG就是用飞线调试 哈哈哈
xiaolin wang:
回复 yongqing wang:
能否咨询一下你的接线方案呢?我的邮箱是975316458@qq.com。我这都准备做转接板了,没有找到根本问题所在,可否借鉴下你的接线方案!