Keil Logo

Technical Support

On-Line Manuals

C166 User's Guide

C166 Introduction Compiling Programs Language Extensions Preprocessor Advanced Programming Error Messages Fatal Errors Actions Messages Errors and Warnings Reference Error C1 Warning C2 Error C3 Error C4 Error C5 Error C6 Error C7 Error C8 Warning C9 Error C10 Error C11 Warning C12 Warning C13 Warning C14 Error C15 Error C16 Error C17 Error C18 Error C19 Error C20 Error C21 Error C22 Error C23 Error C24 Error C25 Error C26 Error C27 Error C28 Error C29 Warning C30 Error C31 Error C32 Error C33 Warning C34 Warning C35 Error C36 Warning C38 Error C39 Warning C40 Error C41 Error C42 Error C44 Error C45 Warning C46 Warning C47 Error C48 Error C49 Error C50 Error C51 Warning C52 Error C53 Error C54 Error C55 Error C56 Warning C57 Error C60 Error C61 Error C64 Error C65 Error C66 Error C67 Error C68 Error C69 Error C70 Error C71 Warning C72 Error C73 Error C74 Error C75 Error C76 Error C77 Error C79 Error C80 Error C81 Error C82 Error C83 Error C84 Error C85 Error C86 Error C87 Error C88 Warning C89 Error C90 Error C91 Error C92 Error C93 Error C94 Warning C95 Warning C96 Error C97 Error C98 Error C99 Error C100 Warning C101 Warning C102 Error C103 Error C104 Warning C105 Error C106 Warning C107 Error C109 Error C110 Warning C111 Warning C112 Warning C113 Warning C114 Error C115 Error C116 Error C117 Warning C118 Error C119 Error C120 Error C121 Error C122 Error C123 Error C124 Error C125 Error C126 Error C127 Error C128 Error C129 Error C130 Error C131 Error C132 Error C133 Error C134 Warning C135 Error C136 Warning C137 Warning C138 Error C139 Warning C140 Error C141 Error C142 Error C143 Error C144 Warning C145 Warning C146 Warning C147 Error C148 Warning C149 Warning C150 Warning C151 Error C152 Warning C153 Error C154 Error C155 Error C156 Warning C161 Warning C162 Error C163 Warning C164 Warning C165 Warning C166 Warning C167 Warning C169 Warning C170 Warning C171 Warning C172 Error C173 Error C174 Warning C175 Warning C176 Error C177 Warning C178 Error C179 Error C180 Warning C181 Error C182 Error C183 Error C184 Warning C185 Error C186 Error C187 Error C188 Error C189 Error C190 Error C191 Warning C192 Error C193 Error C194 Error C195 Error C196 Warning C197 Warning C198 Warning C199 Warning C200 Error C201 Warning C300 Warning C301 Warning C302 Warning C303 Warning C304 Warning C305 Warning C306 Warning C307 Warning C308 Warning C309 Warning C310 Warning C311 Warning C312 Error C313 Warning C314 Warning C315 Warning C316 Error C317 Warning C318 Warning C319 Warning C320 Warning C321 Error C322 Error C323 Error C324 Warning C325 Warning C326 Warning C327 Warning C328 Warning C500 Library Reference Appendix


  • '(' After Control Expected
    Some control parameters need an argument enclosed in parentheses. This message is displayed when the left parenthesis is missing.
  • ')' After Parameter Expected
    This message indicates that the right parenthesis of the enclosed argument is missing.
  • '=' Expected
    This message indicates a syntax error with the specified WARNING directive or pragma.
  • Bad Digit In Number
    The numerical argument of a control parameter contains invalid characters. Only decimal digits are acceptable.
  • Can't Create File
    The filename defined on the FILE line cannot be created.
  • Can't Have General Control In Invocation Line
    General controls like EJECT cannot be included on the command line. Place these controls in the source file using the #pragma statement.
  • File Does Not Exist
    The filename defined on the FILE line, cannot be found.
  • File Write-Error
    An error occurred while writing to the list, preprint, work, or object file because of insufficient disk space.
  • Identifier Expected
    This message is generated when the DEFINE directive has no arguments. The DEFINE directive requires an identifier as its argument. This is the same convention as in the C language.
  • Line Too Long
    The maximum length of the command line may not exceed 500 characters. The same limit also applies to the contents of a command file (@cmdfile).
  • Memory Space Exhausted
    The compiler could not allocate enough memory to compile the specified source file. If you receive this message consistently, you should split the source file into two or more smaller files and re-compile.
  • More Than 100 Errors in Source-File
    During the compilation more than 100 errors were detected. This causes the termination of the compiler.
  • Non-Null Argument Expected
    The selected control parameter needs an argument (for example, a filename or a number) enclosed in parentheses.
  • Numeric Value Out Of Range
    The numerical argument of a control parameter is out of range. For instance, the OPTIMIZE directive allows only certain numbers. A value of 25 would generate this error message.
  • Parse Stack Overflow/Statements Are Too Nested
    The parse stack has overflowed. This can occur if the source program contains extremely complex expressions or if blocks are nested more than 31 levels deep.
  • Preprocessor: Line Too Long (32K)
    An intermediate expansion exceeded 32K characters in length.
  • Preprocessor: Macros Too Nested
    During macro expansion, the stack consumption of the preprocessor grew too large to continue. This message usually indicates a recursive macro definition, but can also indicate a macro with too many levels of nesting.
  • Respecified Or Conflicting Control
    A command-line parameter was specified twice or conflicting command-line parameters were specified.
  • Source Must Come From A Disk-File
    The source and include files must exist on either a hard disk or diskette. The console CON:, :CI:, or similar devices are not allowed as input files.
  • Unknown Class Name
    The first parameter specified using the RENAMECLASS directive must be one of the following predefined classes: BIT, BDATA, FCODE, FCONST, FDATA, HCONST, HDATA, IDATA, NCODE, NCONST, NDATA, SDATA, XCONST, or XDATA.
  • Unknown Control
    The selected control parameter is not recognized by the compiler.
  Arm logo
Important information

This site uses cookies to store information on your computer. By continuing to use our site, you consent to our cookies.

Change Settings

Privacy Policy Update

Arm’s Privacy Policy has been updated. By continuing to use our site, you consent to Arm’s Privacy Policy. Please review our Privacy Policy to learn more about our collection, use and transfers
of your data.