转载地址:http://www.chengkaiblog.com/technology/ccs-arget-configuration-setting-steps/
在本文中将详细介绍如何在Code Composer Studio (CCS)中设置target configuration。
环境:
开发板:TMDSEVM6670LE
模拟器:XDS560v2 Emulator
电源: 自带电源
步骤:
- Step1:在CCS 5.3中将界面切换到CCS Debug,这个按钮在软件界面的右上角。如果没有,请点击”CCS Edit”左边的添加按钮,将CCS Debug加上去。按钮如下图所示。
- Step2:点击当前界面左下角的按钮,如下图所示。弹出的界面如下图所示
- Step3:在该界面单击右键,并选择New Target Configuration,如下图所示。
- Step4:输入名字,还可以设置文件的存放位置(在本文中没有修改存放位置),最后单击Finish。如下图所示。
- Step5:在Connection中选择Blackhawk XDS5560v2-USB System Trace Emulator,在Board or Device后面输入过滤文字C6670(因为我的开发板上的DSP芯片是C6670),之后在下面TMS320C6670前面的复选框上打上√,单击Save和Test Connection。(注意:在单击Test Connection之前要把开发板用USB连接到电脑上并给开发板供电。)如果能够连接成功,会出现以下信息。
- Step 6:依次选择Advanced -> C66xx_0(此处是选择一个核,选其他的也可以) -> Browse -> Save -> Test Connection。注意:在单击Browse时会弹出一个选择文件的对话框,我们要选择的文件路径为:
这个路径根据自己安装CCS的路径而定。如果测试通过,会出现下面的信息。
123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162[ Start ]Execute the command :% ccs_base % / common / uscif / dbgjtag . exe - f % boarddatafile % - rv - o - F inform , logfile = yes - S pathlength - S integrity[ Result ]-- -- - [ Print the board config pathname ( s ) ] -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --C : \ Users \ chengkai \ AppData \ Local \ . TI \ 693494126 \0 \ 0 \ BrdDat \ testBoard . dat-- -- - [ Print the reset - command software log - file ] -- -- -- -- -- -- -- -- -- -- -- -- -- -- -This utility has selected a 560 / 2xx - class product .This utility will load the program 'bh560v2u.out' .Loaded FPGA Image : C : \ ti \ ccsv5 \ ccs_base \ common \ uscif \ dtc_top . jbcThe library build date was 'Oct 3 2012' .The library build time was '22:14:17' .The library package version is '5.0.872.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 '5' ( 0x00000005 ) .The controller has an insertion length of '0' ( 0x00000000 ) .The cable + pod has a version number of '8' ( 0x00000008 ) .The cable + pod has a capability number of '7423' ( 0x00001cff ) .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 Nano - TBC VHDL .The link is a 560 - class second - generation - 560 cable .The software is configured for Nano - TBC VHDL features .The controller will be software reset via its registers .The controller has a logic ONE on its EMU [ 0 ] input pin .The controller has a logic ONE on its EMU [ 1 ] input pin .The controller will use falling - edge timing on output pins .The controller cannot control the timing on input pins .The scan - path link - delay has been set to exactly '2' ( 0x0002 ) .The utility logic has not previously detected a power - loss .The utility logic is not currently detecting a power - loss .Loaded FPGA Image : C : \ ti \ ccsv5 \ ccs_base \ common \ uscif \ dtc_top . jbc-- -- - [ The log - file for the JTAG TCLK output generated from the PLL ] -- -- -- -- --Test Size Coord MHz Flag Result Description~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~1 none - 01 00 500.0kHz - similar isit internal clock2 none - 01 09 570.3kHz - similar isit internal clock3 512 - 01 00 500.0kHz O good value measure path length4 128 - 01 00 500.0kHz O good value auto step initial5 128 - 01 0D 601.6kHz O good value auto step delta6 128 - 01 1C 718.8kHz O good value auto step delta7 128 - 01 2E 859.4kHz O good value auto step delta8 128 + 00 02 1.031MHz O good value auto step delta9 128 + 00 0F 1.234MHz O good value auto step delta10 128 + 00 1F 1.484MHz O good value auto step delta11 128 + 00 32 1.781MHz O good value auto step delta12 128 + 01 04 2.125MHz O good value auto step delta13 128 + 01 11 2.531MHz O good value auto step delta14 128 + 01 21 3.031MHz O good value auto step delta15 128 + 01 34 3.625MHz O good value auto step delta16 128 + 02 05 4.313MHz O good value auto step delta17 128 + 02 13 5.188MHz O good value auto step delta18 128 + 02 23 6.188MHz O good value auto step delta19 128 + 02 37 7.438MHz O good value auto step delta20 128 + 03 07 8.875MHz O good value auto step delta21 128 + 03 15 10.63MHz O good value auto step delta22 128 + 03 1E 11.75MHz { O } good value auto step delta23 512 + 02 3E 7.875MHz O good value auto power initial24 512 + 03 0E 9.750MHz O good value auto power delta25 512 + 03 16 10.75MHz O good value auto power delta26 512 + 03 1A 11.25MHz O good value auto power delta27 512 + 03 1C 11.50MHz O good value auto power delta28 512 + 03 1D 11.63MHz O good value auto power delta29 512 + 03 1D 11.63MHz O good value auto power delta30 512 + 03 13 10.38MHz { O } good value auto margin initialThe first internal / external clock test resuts are :The expect frequency was 500000Hz.The actual frequency was 499110Hz.The delta frequency was 890Hz.The second internal / external clock test resuts are :The expect frequency was 570312Hz.The actual frequency was 569214Hz.The delta frequency was 1098Hz.In the scan - path tests :The test length was 16384 bits .The JTAG IR length was 6 bits .The JTAG DR length was 1 bits .The IR / DR scan - path tests used 30 frequencies .The IR / DR scan - path tests used 500.0kHz as the initial frequency .The IR / DR scan - path tests used 11.75MHz as the highest frequency .The IR / DR scan - path tests used 10.38MHz as the final frequency .-- -- - [ Measure the source and frequency of the final JTAG TCLKR input ] -- -- -- --The frequency of the JTAG TCLKR input is measured as 10.37MHz.The frequency of the JTAG TCLKR input and TCLKO output signals are similar .The target system likely uses the TCLKO output from the emulator PLL .-- -- - [ 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 succeeded .The JTAG IR instruction path - length is 6 bits .The test for the JTAG DR bypass path - length succeeded .The JTAG DR bypass path - length is 1 bits .-- -- - [ 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 : 0Do a test using 0x00000000.Scan tests : 2 , skipped : 0 , failed : 0Do a test using 0xFE03E0E2.Scan tests : 3 , skipped : 0 , failed : 0Do a test using 0x01FC1F1D.Scan tests : 4 , skipped : 0 , failed : 0Do a test using 0x5533CCAA.Scan tests : 5 , skipped : 0 , failed : 0Do a test using 0xAACC3355.Scan tests : 6 , skipped : 0 , failed : 0All of the values were scanned correctly .The JTAG IR Integrity scan - test has succeeded .-- -- - [ 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 : 0Do a test using 0x00000000.Scan tests : 2 , skipped : 0 , failed : 0Do a test using 0xFE03E0E2.Scan tests : 3 , skipped : 0 , failed : 0Do a test using 0x01FC1F1D.Scan tests : 4 , skipped : 0 , failed : 0Do a test using 0x5533CCAA.Scan tests : 5 , skipped : 0 , failed : 0Do a test using 0xAACC3355.Scan tests : 6 , skipped : 0 , failed : 0All of the values were scanned correctly .The JTAG DR Integrity scan - test has succeeded .[ End ]这样我们就创建好了Target Configuration。