dk018_C6713配置文档_百度文库
两大类热门资源免费畅读
续费一年阅读会员，立省24元！
评价文档：
喜欢此文档的还喜欢
dk018_C6713配置文档
T​I​ ​C73​ ​D​S​P​ ​在​C​C​S.中​使​用​T​D​S6U​S​B​-​p​l​u​s​的​配​置​信​息
阅读已结束，如果下载本文需要使用
想免费下载本文？
把文档贴到Blog、BBS或个人站等：
普通尺寸(450*500pix)
较大尺寸(630*500pix)
你可能喜欢TDS560USB PLUS DAVINCI CCS 3.3 英文_百度文库
两大类热门资源免费畅读
续费一年阅读会员，立省24元！
评价文档：
喜欢此文档的还喜欢
TDS560USB PLUS DAVINCI CCS 3.3 英文
阅读已结束，如果下载本文需要使用
想免费下载本文？
把文档贴到Blog、BBS或个人站等：
普通尺寸(450*500pix)
较大尺寸(630*500pix)
你可能喜欢Davinci调试环境的搭建（三） - lintax的专栏
- 博客频道 - CSDN.NET
4024人阅读
调试环境的搭建（三）
五、安装程序的编译环境
公司提供了高效的编译器和集成开发环境 ，可以方便的编译调试程序，同时的帮助文档也是十分全面。
、安装CCS3.3
这部分安装比较简单，详细指导参见公司的安装指南，可分成两部分：
，解压并安装
一般使用默认的配置即可，但是要注意在选择仿真芯片类型时，必须同时选上、，以及TMS470系列，这是由于需要同时支持与的仿真运行。
，运行，采用默认的配置即可。
、安装TDS560USB驱动
安装驱动与设置都需要仔细操作，一步操作错误就会导致最后使用不起来。
驱动时注意事项
请注意正确连接针的电缆，该电缆接错可能会导致仿真器或目标系统永久损坏；仿真器孔插头的第六孔已经封闭，目标系统针插针的第六针应该拔掉。如果不能确定接插件的连接方向，请与您的经销商联系或查询我们的网站中的相关信息。
为发挥仿真器的性能，主机应具备接口。如果没有的接口，最好使用转接卡。
请不要带电拔插电缆。
在移动和搬运系统时，请注意上的线缆不能负重，否则内部电缆容易损坏。
）设备驱动程序安装
将TDS560USB仿真器与目标板连接、计算机相连。
然后将电源与TDS560USB仿真器相连，此时POWER灯亮，READY闪烁。
按照Windows
的“发现新硬件”提示指定 WintechDigital　TDS560USB设备驱动程序所在的目录。在产品安装光盘的drivers目录下 (Win98/SE
是在 drivers/win98_me, Win2000/XP是drivers/win2k_xp )。
设备驱动安装完成后，Windows将在设备列表中列出TDS560USB Emulator for Windows 98
或TDS560USB Emulator for Windows 2000/XP/2003。
如果找不到这个设备，请检查硬件的连接是否正确。
如果误把TDS560USB Emulator for Windows 98驱动程序安装到Windows 2000/XP/2003系统中，请在设备管理器中对该设备使用“更新驱动程序”功能。
）安装仿真器工具软件
在安装仿真器工具软件之前，请确认CCS已经安装，否则仿真器无法工作。运行产品安装光盘根目录下的。
根据您的需要选择类型，再选定相应的目录。我们是选上了C6000，OMAP，Others
软件安装完成后，可以在桌面上看到
WintechDigital
快捷方式图标，同时在CCS目录下建立“TDS560USB”目录。
如果需要更换CCS,请重新运行Setup.exe卸载仿真器工具软件，并再次运行Setup.exe，选定新的DSP及新的CCS路径。
在板卡上使用仿真器时进行设置的步骤如下：
首先要注意：
CCS的版本需要是3.2版本或更高版本；
设置前必须已经运行过仿真器光盘所附带的支持工具。
．启动后，选择，双击
设置连接名称：
不用作任何改动，直接完成。
．选择并在中栏双击或拖到左栏中
5．在弹出窗口中设置的个数为
．点击跳过。
7．设置和端口号，名字随便取，但是端口号必须为为。
．以上步骤完成后，选择左栏的
．在中间栏拖到左栏中，扫描链中的处理器。
．设置处理器的文件
此处需要选中随板提供的
DaVinciEVM_arm.gel 文件
11．开始设置在左栏中选中然后把中间栏的拖到左栏的中
．设置处理器的文件。
此处需要选中随板提供的
DaVinciEVM_dsp.gel 文件
13．到此，设置工作完成，存储并退出。
以上步骤完成后，先断开仿真器电源，将上的电缆与目标板接口相连，然后打开目标板电源，接通仿真器电源，运行。观察两个指示灯，如果灯和灯轮流闪烁，表示正常工作，否则请断开仿真器的电源，拔下线缆，重新检查前面的硬件连接和软件安装、设置是否正确。
CCS及驱动都安装完成之后，在运行前，最好先运行一下
，如果复位正常，则运行进行实时仿真，如果不能正常复位，请拔下仿真器电源和电缆，重新连接硬件，并检查硬件连接和软件安装是否正确。
Davinci的程序分程序及程序，程序我们在中编辑和编译，程序在中编辑，在中的工具链下编译。
下面以视频编解码版本的编译为例，来说明调试程序操作步骤。
版本中有部分，分别是：
解码算法&&&&&& ：VidDec_lib
编码算法&&&&&& ：VidEnc_lib
编译环境：video_copy
运行程序：videoloop
运行目录&&&&&& ：loop
与目录推荐放在安装路径下的目录下，我的存放路径为：。
、与目录都存放在服务器下，目录必须存放在所共享的、板卡可以访问的根文件系统内，而与目录没有存放路径的限制，推荐将这两个目录存放在同一路径下。
、在Windows上编译DSP端运行库
由于只是编译，并不需要仿真器的参与，以下编译时仿真器都不是必须的。在调试的过程中，才会需要用到仿真器。
启动，在中分别编译视频解码工程及视频编码工程，得到所生成的库文件及。
、在Linux中编译DSP可执行程序
将在中编译的改名复制为
将在中编译的复制为
也可以使用及同目录下的批处理文件来实现以上两次改名复制。
在环境下的目录下先执行
make clean
生成端的可执行文件；并且将拷贝至运行目录中。以上的生成并拷贝至运行目录可以使用同目录下的脚本执行文件来实现。（脚本是为了简化调试步骤而使用的，大家自己写出就是了）
、在Linux中编译ARM可执行程序
在环境下进入工程，运行，生成端可执行程序，将拷贝至运行目录中。
这一步的及拷贝也可以使用同目录下的脚本文件来执行。
、启动板卡，执行程序
启动板卡，使用登录，然后进入运行目录中。首先运行装载模块程序，然后运行端可执行程序。在运行过程中，会根据需要调用端的视频解码算法程序及视频编码算法程序。
以上的、、步使用脚本文件需要注意：
IP地址与路径必须与实际情况匹配，特别是在程序版本升级及服务器更换时。
编译时，注意要先。
* 以上用户言论只代表其个人观点，不代表CSDN网站的观点或立场
访问：51335次
排名：千里之外
原创：25篇
评论：29条
(2)(4)(4)(2)(1)(1)(1)(1)(1)(2)(5)(2)From Texas Instruments Wiki
The XDS560v2 System Trace Emulator is the second generation of the XDS560-class emulators. It provides cost effective real-time emulation, debugging, and high-performance System Trace (STM) for Texas Instruments devices over both USB and Ethernet PC interfaces.
The System Trace (STM) capability is a set of built-in capabilities on the device that monitors synchronization and timing between cores and on-chip peripherals either configured via the Trace features of Code Composer Studio or built into the application (by using the library ). This has multiple uses: the ability to track bus and peripheral activity, monitor and benchmark data throughput, transfer debug messages through the JTAG channel (via modified printf or putc routines) and more.
Note: this is different than Core Trace or Instruction Trace, which is the emulation technology that performs real-time gathering of all instructions being executed in a processor. For these types of traces please check the
This is available with selected
enabled devices.
The System Trace capability is compliant to Mobile Industry Processor Interface System Trace Protocol or MIPI STP for short. See www.mipi.org for more details.
Native 60 pin MIPI HSPT target cable, with adapters to: 20 pin compact TI, 14 pin TI, and 20 pin ARM connectors
Target debugging with JTAG (IEEE 1149.1) and IEEE 1149.7
Up to 50 MHz TCLK
Control for power-up/boot-mode on EMU0/1 pins
Auto sensing target voltage range from 1.2 volts to 4.1 volts
Approx 50% faster code download than XDS560 (v1)
JTAG debug isolation mode - ability to disconnect the emulator connection and have this result in the debug subsystem power down. This blocks driving any JTAG signals by the emulator/cable when
is not connected.
When the last CCS core/node disconnects, all the emulator/cable output signals will be tri-stated (Hi-Z). This blocks driving any JTAG signals by the emulator/cable.
JTAG TCLK loop-back option - ability to select TCLK loop-back with user-specified limit from Target Configuration in CCS
This enables CCS to connect to targets with no return clock (RTCK) pin.
Map boot-mode pins (EMU0 & EMU1) - ability to map boot-mode pins to any of the following pins
EMU1 = Pin TRD0.2 and EMU0 = Pin TRD0.1
EMU1 = Pin TRD0.1 and EMU0 = Pin TRD0.0
EMU1 = Pin EXTF and EMU0 = Pin EXTE
Support for 1-4 pin System Trace with up to 100 MHz export clock (System Trace is compliant to MIPI STP)
128 MBytes System Trace buffer storage
Auto compensating calibration for edge jitter, channel skews and duty cycle for robust trace data capture
Adaptive receiver technology supporting setup/hold times up to 1.5ns
Available on selected
enabled devices
The interfaces available vary by model.
Most offer a USB2.0 high speed interface and some additionally offer Ethernet.
The XDS560v2 System Trace Emulator utilizes the 60-pin MIPI HSPT connector. The connector and target board electrical requirements and recommandation for Trace and JTAG support can be found in .
Also see your Emulator manufacturer's documentation for emulator specific information. Users may also want to read the "Common Trace Transmission Problems and Solutions" at .
MIPI Connector recommendation can be found .
20 pin compact TI connector can be used for System Trace as it has 4 pins for data and 1 pin for clock (EMU0-5).
TI 14 pin can be used, but can only carry 1 pin data and 1 pin clock (EMU0/1)
ARM 20 pin connectors should NOT be used for CTools System Trace enabled devices as it does not carry signals for System Trace.
TI E-Store Product Folder (TBD)
(USB/Ethernet)
(USB/Ethernet)
Your emulator should have come with adapters. If not, please contact your manufacturer.
With more recent versions of XDS560v2 firmware user1 is unaffected and user2 will receive the "Error initializing emulator" message.
With older versions of XDS560v2 firmware user1 is disconnected.
LED Name     
Color       
Meaning                            
ON- Power ON
OFF - Power Off
ON - CCS debugger connected
OFF- CCS debugger disconnected
ON - XDS560v2 System Trace Emulator FPGA programmed
OFF- XDS560v2 System Trace Emulator FPGA not programmed
ON - XDS560v2 System Trace Emulator ready (see note 1)
OFF - XDS560v2 System Trace Emulator not ready
FLASH (momentary) - Ethernet connection refused (see note 2)
ACTIVITY-1
ON - XDS560v2 System Trace Emulator is booting
FLASH (momentary) - XDS560v2 System Trace Emulator configuration activity
ACTIVITY-2
ON - XDS560v2 System Trace Emulator to Host activity (trace upload)
OFF - No transfer
ACTIVITY-3
ON - Data capture by STM receiver
OFF - No capture
ACTIVITY-3,
ACTIVITY-2,
SAFE MODE.  When all three are simultaneously flashing this indicates safe mode.  The likely causes are a failed firmware upgrade, or multiple failed boot attempts. See
While booting into SAFE MODE the green ACTIVITY-1 LED and the red STATE-3 LED will both be ON.
Only one ethernet client may use the XDS560v2 System Trace Emulator at a time.  The ethernet connection will be refused if another client is already connected in CCS.  In this case the error message will be "Error initializing emulator".
A: The XDS560v2 System Trace emualtor supports Code Composer Studio v4.2 and newer.
A: No, the XDS560v2 System Trace emulator is supported by Code Composer Studio v4.2 and newer.
Spectrum Digital provides a utility which has much of the functionality as XDS560v2 System Trace Emulatorconf. This utility is called SD560v2Config.exe. This utility can be found in "...\ccsv4\common\uscif" directory. The manual is available via the HELP-&Documentation from within the utility.
Once the POWER, STATE-2 and the STATE-3 LEDs are ON (all of them), XDS560v2 System Trace emulator is ready to use.
You can also use the
configuration utility. For example, dtc_conf get sd560v2u 0 will display all the XDS560v2 System Trace Emulator configuration variables of the connected XDS560v2 System Trace Emulator. Since the command will display an error if the XDS560v2 System Trace Emulator is not connected or hasn't finished booting, this command may be used to determine that the link between your PC and the XDS560v2 System Trace emulator is good.
This means the XDS560v2 System Trace Emulator is in safe mode. This may occurr if ...
A XDS560v2 System Trace Emulator firmware update has failed.
The XDS560v2 System Trace Emulator fails to completely boot multiple times.
You can use the
utility to boot back into normal mode. Issue the following two commands to reboot into normal mode ...
$ dtc_conf set sd560v2u 0 safeMode=false
$ dtc_conf boot sd560v2u 0
booting...
If the XDS560v2 System Trace Emulator fails to boot into normal mode the firmware may be corrupt or safe mode has been activated if power has been cycled repeatedly.
The above example shows USB. For Ethernet, change the above instructions for "sd560v2u" to "sd560v2e" and "0" should change to the IP address.
USB connection
Make sure that USB cable is plugged in, drivers are installed correctly, and its functional.  Hint: in Windows use the device manager to see the USB device is recognized/removed when the USB cable is plugged/unplugged respectively.
Also, check if the USB port is correctly selected. There could be an issue if you are trying to use another USB emulator at the same time from the same PC.  Please disconnect the USB cable of any emulator that is not in use.
Ethernet Connection:
Check the IP address of the XDS560v2 System Trace Emulator entered in the CCS board configuration. You can read the IP address via a USB connection using the   Note: it is possible for the XDS560v2 System Trace Emulator's IP address to change if it is configured for DHCP.  This is more likely if the XDS560v2 System Trace Emulator has been powered off for an extended period of time or moved to another location.
Make sure another CCS user isn't already connected.  The XDS560v2 System Trace Emulator limits ethernet connections to one CCS client at a time.  You can use the
to determine if another user is connected and what IP address they are using.
Look at the LED on the emulator ethernet connection. These should be blinking indicating network connection.
General Troubleshooting
If you see a USB error such as:
C:\ccsv4\common\uscif\dtc_conf get sd560v2u 0 ipAddress
E_RPCENV_IO_ERROR(-6) No connection
ERROR: 1 : dtc_conf_utils_rpc.cpp(54) : operation failed : sd560v2u:0
It might be due to the USB connection on your PC. Try a different USB port (If in front, move to back. Try different USB cable).
If using Spectrum Digital XDS560v2 then try the SD560v2Config utility and under the USBStatus tab run USB TestLoopBack.
This runs a simply USB packet test to verify basic drivers and hardware connections.
You shold be able to look in Windows Devices to see if it is setup properly. It should look like below when USB is setup correctly.
This usually means that a device that was previously connected has been disconnected. Ensure that all the devices are connected by selecting the device in the tree list and pressing the Connect button.
The message indicates that no target transmitter clock was detected during the receiver calibration. This usually means that the external pin manager has not been enabled. To enable it run the appropriate GEL script commands for your device.
This is probably caused by not turning on option to view non-debuggable devices. This option can be turned on from CCS debug view options. Once the option is checked, you need to re-launch the debugger.
A: If someone is already using the emulator on ethernet, you may get an error message like SC_ERR_OCS_ALREADY_OPEN. This means someone already has a connection to the emulator.
A: When using DTC_CONF, the ACTIVITY-1 LED should blink briefly.
A: For example, using DTC_CONF get x.x.x.x will blink ACTIVITY-1 LED.
A: The problem is that .NET is not installed on your computer. Download and install
to fix the problem.
A: Versions prior to and including epkRev=5.0.329.0 have a bug that can cause certain values of the dtcName variable to prevent ethernet from starting (hint: dtc_conf get sd560v2u 0 epkRev). 
Change the dtcName to all alpha-numeric characters and reboot the DTC (hint: dtc_conf set sd560v2u 0 "dtcName=Abc_123"). See .
A: Certain settings of the dtcConfig variable will prevent ethernet from starting. If your network supports DHCP (or you aren't sure), change the dtcConfig to "dhcp" and reboot the DTC (hint:  dtc_conf set sd560v2u 0 "dtcConfig=dhcp").  If your network does not support dhcp you may set dtcConfig to a static IP address instead.See .
A: If a network connection is not present while the DTC is booting ethernet will not be started.
Connect the network first, then reboot the DTC.