新手请教CCS版本不同出现的编译错误问题

anning

本人DSP新手，刚刚接触，碰到了一个麻烦的问题。
手头有一个合众达的DEC5502的板子，附带光盘里的所有例程是用CCS2.2写成的。手头只有两个仿真器，一个是ICETEK 5100 USB2.0(实质就是XDS510)，只支持CCS3.3和CCS4.X；另一个是明伟XDS100V2，支持CCSV4以上版本。
我现在把例程不论是搬到CCS5.2还是CCS3.3上都不能编译通过，都是同一个问题“#55-D too few arguments in macro invocation”        ，是CSL_GPT里的一个结构体出的问题。

现在把两个程序都传上来吧，问题应该是同一个，解决一个就行。




最后想顺便问下，我用那个XDS510在3.3下可以连接上目标版，但是另一个XDS100V2在CCS5.2下JTAG始终连接不上是怎么回事呢？（驱动显示已经安装上了）
[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\YuAnNing\AppData\Local\.TI\1212777678\
    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 'May 30 2012'.
The library build time was '22:52:27'.
The library package version is '5.0.747.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 test for the JTAG IR instruction path-length succeeded.
The JTAG IR instruction path-length is 38 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: 0
Do a test using 0x00000000.
Scan tests: 2, skipped: 0, failed: 0
Do a test using 0xFE03E0E2.
Test 3 Word 0: scanned out 0xFE03E0E2 and scanned in 0x000000E2.
Test 3 Word 1: scanned out 0xFE03E0E2 and scanned in 0x00000000.
Test 3 Word 2: scanned out 0xFE03E0E2 and scanned in 0x00000000.
Test 3 Word 3: scanned out 0xFE03E0E2 and scanned in 0x00000000.
Test 3 Word 4: scanned out 0xFE03E0E2 and scanned in 0x00000000.
Test 3 Word 5: scanned out 0xFE03E0E2 and scanned in 0x00000000.
Test 3 Word 6: scanned out 0xFE03E0E2 and scanned in 0x00000000.
Test 3 Word 7: scanned out 0xFE03E0E2 and scanned in 0x00000000.
The details of the first 8 errors have been provided.
The utility will now report only the count of failed tests.
Scan tests: 3, skipped: 0, failed: 1
Do a test using 0x01FC1F1D.
Scan tests: 4, skipped: 0, failed: 2
Do a test using 0x5533CCAA.
Scan tests: 5, skipped: 0, failed: 3
Do a test using 0xAACC3355.
Scan tests: 6, skipped: 0, failed: 4
Some of the values were corrupted - 66.5 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.
Scan tests: 2, skipped: 0, failed: 0
Do a test using 0xFE03E0E2.
Test 3 Word 0: scanned out 0xFE03E0E2 and scanned in 0xFFFFE0E2.
Test 3 Word 1: scanned out 0xFE03E0E2 and scanned in 0xFFFFFFFF.
Test 3 Word 2: scanned out 0xFE03E0E2 and scanned in 0xFFFFFFFF.
Test 3 Word 3: scanned out 0xFE03E0E2 and scanned in 0xFFFFFFFF.
Test 3 Word 4: scanned out 0xFE03E0E2 and scanned in 0xFFFFFFFF.
Test 3 Word 5: scanned out 0xFE03E0E2 and scanned in 0xFFFFFFFF.
Test 3 Word 6: scanned out 0xFE03E0E2 and scanned in 0xFFFFFFFF.
Test 3 Word 7: scanned out 0xFE03E0E2 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: 3, skipped: 0, failed: 1
Do a test using 0x01FC1F1D.
Scan tests: 4, skipped: 0, failed: 2
Do a test using 0x5533CCAA.
Scan tests: 5, skipped: 0, failed: 3
Do a test using 0xAACC3355.
Scan tests: 6, skipped: 0, failed: 4
Some of the values were corrupted - 66.5 percent.

The JTAG DR Integrity scan-test has failed.

[End]

monkerman

宏的参数数量不正确. 检查一下 GPT_GPTGCTL1_RMK 宏的定义处参数写法, 是可变参数宏么?
另外要仔细看看第一个错误是怎么回事. 也许是第一个引起的.

anning

monkerman 发表于 2013-3-27 19:37
宏的参数数量不正确. 检查一下 GPT_GPTGCTL1_RMK 宏的定义处参数写法, 是可变参数宏么?
另外要仔细看看第 ...

这个问题我昨天解决了。其实就是主文件中少给宏附了一个参数导致的，真不知道合众达当初这板子程序是怎么调通。改过后已经在CCS3.3下跑通了。
其实比较麻烦的是我手头的XDS100V2好像有问题，JTAG测试通不过。
这个板块人气不高啊，发了悬赏也就您一位回答的。

monkerman

anning 发表于 2013-3-28 10:04
这个问题我昨天解决了。其实就是主文件中少给宏附了一个参数导致的，真不知道合众达当初这板子程序是怎么 ...

解决些问题就好.
你还有人回答, 我的几乎都是我自己回复灌水. 唉......
仿真器连不上是不是没配置好? 你检查下工程配置(project->)或者那个.ccxml文件???
另外, 你计算机是啥系统? 32还是64位的? 都会影响.

anning

monkerman 发表于 2013-3-28 10:39
解决些问题就好.
你还有人回答, 我的几乎都是我自己回复灌水. 唉......
仿真器连不上是不是没配置好? 你 ...

32位win7系统。在CCS5.2下编辑.ccxml文件后点击JTAG TEST就显示fail了。至于工程里还有需要配置的吗？我看网上的关于CCS5的教程没有写到啊。

monkerman

在 project->properties  里有设置CPU系列, 型号, 仿真器, 库, 大小端等等.....你看一下.

maum61

大神们知道为什么仿真器停不住CPU吗？我一调试就出现C55xx: Trouble Halting Target CPU: Error 0x00000022/-2130 Error during:

Memory, Execution,  Cannot access memory address at 0x00000400

C55xx: Trouble Halting Target CPU: Error 0x80000022/-1144 Fatal Error during:

Memory, Execution,  The memory at 0x00000400 continually indicated it was 'not

ready' The emulator was unable to regain control of the processor. The

processor must be reset.  
C55xx: Failed to remove the debug state from the target before disconnecting.  

There may still be breakpoint op-codes embedded in program memory.  It is

recommended that you reset the emulator before you connect and reload your

program before you continue debugging这样的提示，根本用不了。我用的CCS4.13