TI中文支持网
TEst connection出现信息如下
[Start: Texas Instruments XDS100v3 USB Emulator_0]
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\qinan\AppData\Local\TEXASI~1\CCS\
TI\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 'jioserdesusbv3.dll'.
The library build date was 'Jul 27 2016'.
The library build time was '18:31:37'.
The library package version is '6.0.407.3'.
The library component version is '35.35.0.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).
An error occurred while hard opening the controller.
—–[An error has occurred and this utility has aborted]——————–
This error is generated by TI's USCIF driver or utilities.
The value is '-233' (0xffffff17).
The title is 'SC_ERR_PATH_BROKEN'.
The explanation is:
The JTAG IR and DR scan-paths cannot circulate bits, they may be broken.
An attempt to scan the JTAG scan-path has failed.
The target's JTAG scan-path appears to be broken
with a stuck-at-ones or stuck-at-zero fault.
[End: Texas Instruments XDS100v3 USB Emulator_0]
Kevin Qiu1：
固件有更新过吗？烧写的是哪个例程，看下connection是否选择XDS110V3
user4656821：
回复 Kevin Qiu1:
这些都是设置正确的，固件也没有问题，烧录launchpad没有问题，就是调试自己的demo板出现问题
Kevin Qiu1：
回复 user4656821:
自己制作的板子是参考ti的设计吗，修改过哪些地方？自己制作的板子是需要烧写驱动的
试试以下几种方法：
1.按照文档2.4节操作：https://www.ti.com.cn/cn/lit/ug/swru532a/swru532a.pdf?ts=1595394739010&ref_url=https%253A%252F%252Fwww.ti.com.cn%252Fproduct%252Fcn%252FCC3200
2.将工程文件中的CC3200.ccxml文件替换为C:\ti\CC3200SDK_1.5.0\cc3200-sdk\tools\ccs_patch中的CC3200_xds100v3.ccml
3.用C:\ti\uniflash_3.4\ccs_base\common\uscif\xds110中的xdsdfu烧录firmware和bootloader文件
user4656821：
回复 Kevin Qiu1:
是自己制作的板子，没有添加flash芯片的话是不能进行调试吗？
Kevin Qiu1：
回复 user4656821:
是的，CC3200程序是引导加载到外部flash中执行的
user4656821：
回复 Kevin Qiu1:
那launchpad上面没有设置SOP的时候也可以进行仿真调试呀。
Kevin Qiu1：
回复 user4656821:
刚才表述不太准确，一般情况下，调试时都是把程序下载到芯片的FLASH 运行测试的，
代码的CODE 及data 的内容被写入到FLASH 中存储。不接SOP的时候是将程序加载到SRAM中运行的，
不过对代码大小有限制，掉电后程序会丢失
user4656821：
回复 Kevin Qiu1:
我知道这样做的，就是现在我自己制作的电路板烧录的时候找不到目标芯片，我看了原理图和CC3200的官方原理图是大致一样的，但是现在不知道是什么原因了
user4656821：
回复 Kevin Qiu1:
user4656821：
回复 Kevin Qiu1:
因为暂时用不到flash的操作就没有挂flash
