• Products
• Events
• What's New
• User Support
• Company
• Contact Us

CoverageMaster winAMS FAQ

CasePlayer2 Analysis

019_08: How do I fix a CasePlayer2 analysis, "CasePlayer2-E-SYN : name (xxx) is not declared." error? I am using the IAR compiler.

Question:

I am using the IAR Compiler and I get one of the following errors when I run the CasePlayer2 analysis: "CasePlayer2-E-SYN : name (xxx) is not declared." or "CasePlayer2-E-SYN : Invalid character code found". The declaration concerns an I/O port. How can I fix it?

Answer:

When using the IAR compiler (ICCRL78) included in IAR’s "Embedded WorkBench" IDE for the Renesas Electronics RL78 family, the following analysis errors may occur during CasePlayer2 analysis.

This is because the IAR compiler uses a header file format with non-standard characters (ex: "@") to define I/O Ports and registers. CasePlayer2 only supports ANSI-C, GNU-C, C99 compliant code, and cannot process compiler-specific keywords or characters. Specific characters like "@" cannot be handled even by modifying the CasePlayer2 "C Option Parameter" settings.

Header File example:
__saddr __no_init volatile union { unsigned char P0; __BITS8 P0_bit; } @ 0xFFF00;

Note: "__saddr" and "__no_init" analysis errors can be fixed by adding them to the "C Option Parameter" settings. But @0xXXXXX cannot be fixed in this way.

To solve this, GAIO User Support can generate an alternate header file with CasePlayer2 compatible definitions for you. Send an request to GAIO User Support with the header file attached (ioxxxxx.h) and we will generate the alternate header file and send it to you.

After receiving the alternate header file, modify the "System Include Path" and "User Include Path" settings in CasePlayer2  "Settings" - "Preprocessor" settings so that the alternate header file is included instead of the original. With this solution the original header file does not need to be modified.

Related Technical Tips Search

Information Links