6. Error Codes

6. 1. API

Error Num Error Message and description


API-001      Error executing <string>_AtLoad_Initialize(): <string>




API-002      Could not open dynamic library '<string>'
          reason: <string>




API-003      Cannot read file <string>




API-004      Internal error #<decimal>




API-005      <string>:<decimal>: '<string>' not defined




API-006      <string>:<decimal>: '<string>' already used, primary declaration line <decimal>, file <string>




API-007      <string>:<decimal>: Only int*, void*, double *, char* and FILE* are accepted




API-008      <string>:<decimal>: illegal format string '%%<character>'




API-009      <string>:<decimal>: not enough arguments for format




API-010      <string>:<decimal>: only const char* accepted




API-011      <string>:<decimal>: too many arguments for format




API-012      <string>:<decimal>: exclude can't be in a conditional block




API-013      <string>:<decimal>: '*' doesn't match with type




API-014      <string>:<decimal>: function type FILE* doesn't match




API-015      <string>:<decimal>: type of variable '<string>' doesn't match




API-016      <string>:<decimal>: '<string>' might be used uninitialized




API-017      <string>:<decimal>: digit '<decimal>' doesn't match




API-018      <string>:<decimal>: string '<string>' doesn't match




API-019      <string>:<decimal>: flow '<string>' doesn't match




API-020      <string>:<decimal>: undefined type '<string>'




API-021      <string>:<decimal>: sizeof(<string>) is unknown




API-022      <string>:<decimal>: assignment from <string><string> to <string><string> without a cast




API-023      <string>:<decimal>: incompatible type assignment <string><string> != <string><string>




API-024      <string>:<decimal>: variable '<string>' can not be indexed




API-025      <string>:<decimal>: forbiden operation on this variable type




API-026      <string>:<decimal>: '<string>' has an unexpected type




API-027      <string>:<decimal>: '<string>' should not be pointers




API-028      <string>:<decimal>: type of '<string>' and '<string>' mismatch




API-029      <string>:<decimal>: '<string>' and '<string>' should not be pointers




API-030      <string>:<decimal>: '<string>' has an unexpected type




API-031      <string>:<decimal>: unauthorized test on type '<string>'




API-032      <string>:<decimal>: interpreter can not cast <string> to <string>




API-033      <string>:<decimal>: too few arguments for function 'malloc'




API-034      <string>:<decimal>: too many arguments in function 'malloc'




API-035      <string>:<decimal>: too few arguments for function 'callfunc'




API-036      <string>:<decimal>: callfunc: only 'char *' pointer type can be used in function call




API-037      <string>:<decimal>: can not assign <string><string> to <string><string>




API-038      <string>:<decimal>: unknown variable '<string>'




API-039      <string>:<decimal>: unautorized operation on pointers




API-040      <string>:<decimal>: unautorized operation on type <string><string>




API-041      <string>:<decimal>: division by zero




API-042      <string>:<decimal>: unautorized operation on type '<string>'




API-043      <string>:<decimal>: can not make the requested dereference of '<string><string>'




API-044      <string>:<decimal>: can not make the dereference of '<string>'




API-045      <string>:<decimal>: Can not call functions with more then <decimal> arguments




API-046      <string>:<decimal>: function '<string>' can't be found in the dynamic libraries




API-047      <string>:<decimal>: <string>




API-048      error happens at <string>:<decimal>




API-049      <string>:<decimal>: variable '<string>' already declared in this scope




API-050      <string>:<decimal>: type '<string>' must be used as pointer




API-051      <string>:<decimal>: type of '<string>' must be 'FILE *'




API-052      <string>:<decimal>: Fatal error while executing program




API-053      <decimal> errors. Cannot execute




API-054      <string>:<decimal>: parameter '<string>' is uninitialised




API-055      <string>:<decimal>: conflicting type for parameter '<string>' : '<string><string>'!='<string><string>'




API-056      <string>:<decimal>: return value for void function




API-057      <string>:<decimal>: return value for void function




API-058      <string>:<decimal>: conflicting type for return value : '<string><string>'!='<string><string>'




API-059      Function '<string>' used in action was not found
     Location(s):




API-060      <string>:<decimal>: too many arguments in function '<string>'




API-061      <string>:<decimal>: too few arguments for function '<string>'




API-062      Somewhere: function '<string>' can't neither be found in interpreter nor in the dynamic libraries




API-063      Somewhere executing <string>




API-064      Error happens at somewhere when executing '<string>'




API-065      Error executing TCL function '<string>'




6. 2. AVT

Error Num Error Message and description


AVT-000      Usage: avtdeltoken toolname servername hostname hostid hosttoken pid

When using the AVT license server (avtld), avtdeltoken allows to delete a token. Be careful, deleting a token under use will crash the corresponding process.




AVT-001      Character out of [0-9A-Za-z] range in avertecbanner

An illegal value has been used within an internal function. Please, report internal errors to Avertec Support.




AVT-002      Resulting size bigger than <decimal> columns not allowed in avertecbanner

The formatting size of an object or a text does not fit the avertec banner dimensions. Please, report internal errors to Avertec Support.




AVT-003      '<string>' is not a valid variable

Invalid variable in avttools.conf file. Check variable name or suppress wrong variable definition.




AVT-004      File avttools.conf, syntax error line <decimal>

File avttools.conf cannot be printed. Correct synthax error (see documentation)




AVT-005      '<string> = <string>' with no effect. Value '<string>' already set with '<string>'

A variable has been set twice within avttools.conf, suppress one if possible.




AVT-006      File avttools.conf, multiple declaration of '<string>'

A variable has been set several times. Conflicts may occur. Check the declarations of the variable within avttools.conf file and keep only one.




AVT-007      Word <string> too long

The string provided to the license server is too long. Use avtinfo to ensure valid value or license file are provided.




AVT-008      String too long

The line or message provided to the license server is too long.




AVT-009      Impossible to delete this token

The token cannot be deleted. Check token name and user rights.




AVT-010      Usage: avtgenkey toolname vendor server hostid date license type

The license server avt (avtld) failed to handle the license key of avtlicense file.




AVT-011      Usage: avtinfo tool_name

avtinfo displays information for the avt license server (avt). Ensure a valid tool_name is used.




AVT-012      Bad Format For Date

The date in the license file is not valid. The license file may be invalid. Check the license file in use.




AVT-013      Bad Token: <string>

An invalid token has been requested by the license server. Check license file is valid and up to date.




AVT-014      Option -<character> requires an operand

The specified option is not properly used. Check tool's usage.




AVT-015      Unrecognised option: -<character>

The specified option is unknown. Check tool's usage.




AVT-016      Unrecognized Command line

Command line synthax invalid. Check tool's usage.




AVT-017      Error in opening file <string>

The specified file cannot be open. Check user's rights, and file path.




AVT-018      Usage: avtreserve tool_name minutes [nb_token]

Display the usage of binary avtreserve. avtreserve is used by the avt license server (avtld).




AVT-019      Unable to reserve token

Token reservation failed. Check token name and reservation command synthax.




AVT-020      Usage: avttool tools_name_list

Display usage for monitoring tokens information.




AVT-021      Run failed

The binary ends with an error. Other messages should bring more information.




AVT-022      Impossible to give token

The license server was unable to get a pid for the token process.




AVT-023      License server <string> not responding

The license server is unreachable. Check a valid license server is running.




AVT-024      Environment variable <string> is not defined

A variable needs to be set in the environment. Avertec documentation supplies the user with the variables legal values.




AVT-025      ...try with server <string>

Another license server has been found and will be tryed. This can occur if the original license server specified by the user was not found or returned an error.




AVT-026      Bad license server <string>

The license server is not valid or was not responding. Check a valid license server is running.




AVT-027      <string>

The running tool encountered an error. Specific information supplied by the tool is displayed.




AVT-028      Token never taken

No token information available for the license server. If a binary (avtinfo, avtdeltoken, or other avt license server utility) has been used, please check the relevant usage.




AVT-029      Bad token description

The command line synthax used is not valid. Check for relevant avt license server utility usage.




AVT-030      Bad file name, check autorisation for <string>

The utility failed to open the specified license key or log file.




AVT-031      Missing part of log file

The avt license server returns an error with the license log file. Usually not a critical error for the running process if avtld is used rather than flexnet.




AVT-033      AVT-_LICENSE_FILE not set and $AVT_TOOLS_DIR/etc/avtlicense.lic missing.
     If errors occur, please check your Flexlm license paths.

The flex license file was not found. Use the flexnet license utilities to get information about flexnet license status.




AVT-034      Flexlm returned error '<decimal>' when <string>.

A generic message displaying error numbers returned by flexnet. Flexnet (or FlexLM) documentation provide some clue to handle surch error number.




AVT-035      Unable to find Flexlm job corresponding to feature <string>

The specified feature is not valid or no job use it. Flexnet license utilities can provide information about the feature, and the jobs running.




AVT-036      Please, resolve Flexlm errors before running Avertec programs.

Flexnet encounters an error. As long as Flexnet license will not runs properly no licensed Avertec tool can be run. Dealling with license errors is a priority. Check if license file path and license daemon are valid and reachable.




AVT-037      Log level of variable '<string>' is not a number. It is '<string>'.

Please refer to the configuration of log report.




AVT-038      Log level of variable '<string>' must be a positive number less or equal to 9. It is '<string>'.

Please refer to the configuration of log report.




AVT-039      Log variable '<string>' is unknown.

Please refer to the configuration of log report.




AVT-040      Invalid value '<string>' for configuration variable '<string>', should be 'yes' or 'no'

Please refer to the HiTas Reference Guide.




AVT-041      Invalid value '<string>' for configuration variable '<string>', please refer to the Reference Guide for correct values

Please refer to the HiTas Reference Guide.




AVT-042      Invalid file format '<string>' for '<string>', please refer to the Reference Guide for valid formats

Valid formats are 'spice', 'lib', 'tlf3', 'tlf4', 'ttv', 'vhdl', 'verilog', 'dspf', 'spef' and 'inf'.




AVT-043      Could not find a file matching '<string>'

The specified filename filter does not match any files in accessible directories.




AVT-044      Multiple settings for configuration variable '<string>': '<string>' is overwritten by '<string>'




AVT-045      could not open file '<string>'




AVT-046      could not create file '<string>'




AVT-047      'avtWarningFilter' has been set to '<string>'




AVT-048      Subsequent call to 'avt_LoadFile' will not retain previous definitions of global parameters

The scope of .SCALE, .GLOBAL or other global parameters is limited to the files loaded by a single call of 'avt_LoadFile'. The values of those global parameters are not retained for subsequent calls of 'avt_LoadFile'.




AVT-049      Incorrect unit specified in '<string>'




AVT-050      Incorrect number of jobs <string>




AVT-051      received answer from job <decimal>, but is not running !




AVT-052      job <decimal> is not in state STAT_EXEC_WAIT when received begin packet




AVT-053      job <decimal> is not in state STAT_EXEC_RUN when received data




AVT-054      job <decimal> is not in state STAT_EXEC_RUN when received end




AVT-055      Job <decimal> aborted [<string>]




AVT-056      A system error occured when runing a new job




AVT-057      Statistical result file '<string>' already exist. Using '<string>'.




AVT-058      Error in <string> table. Entry <decimal> correspond to index <decimal>.




AVT-059      Received unhandled command '<string>' from job <decimal>




AVT-061      Invalid binary transfer




AVT-062      Failed to create directory '<string>'




AVT-063      Invalid value '<string>' for configuration variable '<string>'

Valid value are '1mW', '100uW', '10uW', '1uW', '100nW', '10nW', '1nW', '100pW', '10pW' and '1pW'.




6. 3. BEF

Error Num Error Message and description


BEF-000      Behavior out format <string> is not a legal format!
     A Verilog file will be dumped.

To describe the format for the generated behavior, you must set 'avtOutputBehaviorFormat' either to 'vhd' for VHDL or to 'vlg' for Verilog.\n




BEF-001      Behavior in format <string> is not a legal format!

To describe the format of input behavior, you must set 'avtInputBehaviorFormat' either to 'vhd' for VHDL or to 'vlg' for Verilog.\n




6. 4. BEG

Error Num Error Message and description


BEG-001      <string> Attempt to merge bit vector and single bit <string>




BEG-002      <string> Internal error <string>




BEG-003      <string> Connector declared in, used as out <string>




BEG-004      <string> Null condition <string>




BEG-005      <string> Conflicting vector <string>




BEG-006      <string> Expression and variable has different size <string>




BEG-007      <string> Parser Failure <string>




BEG-008      <string> Conflicting declaration and use <string>




BEG-009      <string> Conflicting bus use <string>




BEG-010      <string> Direction of declaration conflicts with use <string>




BEG-011      <string> Selected signal, vector expression not allowed <string>




BEG-012      <string> Attempt to insert a signal into a defined signal <string>




BEG-013      <string> Vector incompletely defined, made external <string>




BEG-014      <string> Connector declared out, used as in <string>




BEG-015      <string> Bad value for 'BEG_USER_WAY', accepted 'to' or 'downto' <string>




BEG-016      Unknown




BEG-017      <string> Trace: <string>




BEG-018      <string> Convert an In to Out <string>




6. 5. BEH

Error Num Error Message and description


BEH-000      syntax error




BEH-001      combinatory loop: `<string>`




BEH-002      cannot make bdd of empty expression




BEH-003      cannot find terminal `<string>`




BEH-004      illegal use of STABLE attribute




BEH-005      cannot simplify internal signals




BEH-006      cannot make derivatives of expressions




BEH-040      signal `<string>` never assigned




BEH-041      `<string>` has not an empty architecture




BEH-068      port `<string>` has unknwon type




BEH-069      port `<string>` has unknwon mode




BEH-070      unknown time unit




BEH-100      cannot find `<string>`




BEH-107      cannot open result file




BEH-101      <string>: unknown operator




BEH-102      <string>: cannot create empty atom




BEH-103      <string>: cannot build NOT of empty expression




BEH-104      <string>: cannot combine empty expressions




BEH-105      <string>: cannot find terminal




BEH-110      <string>: decompiler called on empty figure




BEH-115      <string>: illegal bit string value : `<character>`




BEH-116      <string>: the same expression cannot be used twice




BEH-119      <string>: empty guard expression: `<string>`




BEH-120      <string>: empty waveform expression: `<string>`




BEH-200      <string>: illegal use of attribute STABLE




BEH-201      <string>: unknown terminal operand `<string>`




BEH-202      <string>: unknown operator `<decimal>`




BEH-203      <string>: empty expression




BEH-199      <string>: Please contact Avertec support




BEH-300      beaux `<string>` not empty




BEH-301      bebus `<string>` not empty




BEH-302      bebux `<string>` not empty




BEH-303      beder not empty




BEH-304      befig `<string>` not empty




BEH-305      begen `<string>` not empty




BEH-306      bemsg `<string>` not empty




BEH-307      beout `<string>` not empty




BEH-308      bequad not empty




BEH-309      bereg `<string>` not empty




BEH-310      biabl not empty




BEH-311      binode not empty




BEH-312      %20s -> <string>




BEH-313      %23s <string>




BEH-315      bevectaux `<string>` not empty




BEH-316      bevectout `<string>` not empty




BEH-317      bevectbux `<string>` not empty




BEH-318      bevectbus `<string>` not empty




BEH-319      bevectreg `<string>` not empty




BEH-320      vectbiabl not empty




6. 6. BHL

Error Num Error Message and description


BHL-000      Internal error <string>




6. 7. BGL

Error Num Error Message and description


BGL-000      Internal error <string>




BGL-001      `<string>` line <decimal> :`<string>` is incompatible with the entity name




BGL-002      `<string>` line <decimal> :bad entity declaration




BGL-003      `<string>` line <decimal> :bad port clause declaration




BGL-004      `<string>` line <decimal> :port `<string>` already declared




BGL-005      `<string>` line <decimal> :illegal port declaration `<string>` (mode, type, guard mark)




BGL-006      `<string>` line <decimal> :bad port declaration




BGL-007      `<string>` line <decimal> :`<string>` is incompatible with the architecture name




BGL-008      `<string>` line <decimal> :bad architecture declaration




BGL-009      `<string>` line <decimal> :illegal declaration




BGL-010      `<string>` line <decimal> :signal `<string>` already declared




BGL-011      `<string>` line <decimal> :illegal signal declaration `<string>` (type, guard mark)




BGL-012      `<string>` line <decimal> :component `<string>` already declared




BGL-013      `<string>` line <decimal> :instance `<string>` already declared




BGL-014      `<string>` line <decimal> :`<string>` unknown component




BGL-015      `<string>` line <decimal> :illegal usage of implicit port map description




BGL-016      `<string>` line <decimal> :`<string>` unknown local port




BGL-017      `<string>` line <decimal> :`<string>` unknown port or signal




BGL-018      `<string>` line <decimal> :illegal concurrent statement




BGL-019      `<string>` line <decimal> :bad signal association




BGL-020      `<string>` line <decimal> :null array not supported




BGL-021      `<string>` line <decimal> :illegal constraint in declaration of type




BGL-022      `<string>` line <decimal> :signal `<string>` used out of declared range




BGL-023      `<string>` line <decimal> :width or/and type mismatch




BGL-024      `<string>` line <decimal> :port `<string>` connected to more than one signal




BGL-025      `<string>` line <decimal> :can only assign to/from an external connector




BGL-026      `<string>` line <decimal> :instance <string> mismatch with the model




BGL-027      `<string>` line <decimal> :Unhandled feature




BGL-028      `<string>` line <decimal> :<string>




BGL-029      Cannot open result file




BGL-030      Cannot continue further more.




BGL-031      `<string>` line <decimal> :Syntax error




BGL-032      Too many errors. Cannot continue further more




BGL-033      File does not exist : <string>




BGL-034      Abnormal parsing for : <string>




BGL-035      Connection missing on port `<string>`




BGL-036      Consistency checks will be disabled




BGL-038      Internal error <string> while executing <string>




BGL-037      `<string>` line <decimal> :<string>




6. 8. BVL

Error Num Error Message and description


BVL-000      Internal error <string>




BVL-001      `<string>` line <decimal> `<string>` is incompatible with the entity name




BVL-002      `<string>` line <decimal> Bad entity declaration




BVL-003      `<string>` line <decimal> Bad port clause declaration




BVL-004      `<string>` line <decimal> Port `<string>` already declared




BVL-005      `<string>` line <decimal> Illegal port declaration (mode, type, kind)




BVL-006      `<string>` line <decimal> Bad port declaration




BVL-007      `<string>` line <decimal> `<string>` is incompatible with the architecture name




BVL-008      `<string>` line <decimal> Bad architecture declaration




BVL-009      `<string>` line <decimal> Illegal declaration




BVL-010      `<string>` line <decimal> Signal `<string>` already declared




BVL-011      `<string>` line <decimal> Illegal signal declaration (type, kind)




BVL-012      `<string>` line <decimal> `<string>` unknown port or signal




BVL-013      `<string>` line <decimal> Illegal concurrent statement




BVL-014      `<string>` line <decimal> Label `<string>` already declared




BVL-015      `<string>` line <decimal> `<string>` is incompatible with the block's label




BVL-016      `<string>` line <decimal> Input port `<string>` cannot be assigned




BVL-017      `<string>` line <decimal> Illegal unguarded signal assignment for `<string>`




BVL-018      `<string>` line <decimal> Illegal guarded signal assignment `<string>`




BVL-019      `<string>` line <decimal> Some choices missing in the selected signal assignment




BVL-020      `<string>` line <decimal> Output port `<string>` cannot be read




BVL-021      `<string>` line <decimal> Duplicate choice in selected signal assignment




BVL-022      `<string>` line <decimal> Illegal use of OTHERS in selected signal assignment




BVL-023      `<string>` line <decimal> Null array not supported




BVL-024      `<string>` line <decimal> Incompatible constraint and type




BVL-025      `<string>` line <decimal> Illegal assignment of `<string>` (widths mismatch)




BVL-026      `<string>` line <decimal> Signal `<string>` used out of declared range




BVL-027      `<string>` line <decimal> Width or/and type mismatch




BVL-028      `<string>` line <decimal> Signal `<string>` assigned more than once




BVL-029      `<string>` line <decimal> Signal `<string>` never assigned




BVL-030      `<string>` line <decimal> Illegal condition on signal `<string>`




BVL-031      `<string>` line <decimal> BEPOR type is unknown




BVL-032      `<string>` line <decimal> `<string>` is not a bit string litteral




BVL-033      `<string>` line <decimal> Bad generic declaration




BVL-034      `<string>` line <decimal> Bad generic element




BVL-035      `<string>` line <decimal> `<string>`: when expression must be a constant




BVL-036      `<string>` line <decimal> Illegal generic declaration (type, kind)




BVL-037      `<string>` line <decimal> Illegal constant declaration (type, kind)




BVL-038      `<string>` line <decimal> Illegal use of attribute STABLE on `<string>`




BVL-039      `<string>` line <decimal> Different delays not supported on waveforms




BVL-040      `<string>` line <decimal> Syntax error




BVL-041      Too many errors. Cannot continue further more




BVL-042      `<string>` Error line <decimal> : <string>




6. 9. CBH

Error Num Error Message and description


CBH-000      Internal Error <string>




CBH-001      <string>: Possible cause library not charged




CBH-002      <string> needs a file as argument




CBH-003      <string>




6. 10. CGV

Error Num Error Message and description


CGV-001      Internal error #<decimal>




CGV-002      Internal warning #<decimal>




CGV-003      <string>:%ld: unknown internal error <decimal>




CGV-004      could not open file '<string>'




CGV-005      could not parse file '<string>'




6. 11. CNS

Error messages description not available yet.

6. 12. GNS

Error Num Error Message and description


GNS-001      instance <string> already exist in figure <string>




GNS-002      instance model is the figure <string> itself




GNS-003      connector number discrepancy between figure <string> and instance <string> in figure <string>




GNS-004      Internal error <decimal>




GNS-005      Internal warning <decimal>




GNS-006      <string>: can't find transistor '<string>' in model




GNS-007      Invalid symmetry detected for instance '<string>' (<string>) on connector '<string>' and ? (<string> and <string>)




GNS-008      no FCL match for `<string>' (instance:'<string>' model:`<string>')




GNS-009      Vector ordering failed on instance '<string>' (<string>) who might be used as \"exclude\"
     . Try to add 'NoOrdering' in the 'GnsFlags' variable




GNS-010      Found an alim linked to a 'not' alim : <string> and <string> in <string>




GNS-011      can't retrieve blackbox instance `<string>' (`<string>')




GNS-012      can't retrieve blackbox connector `<string>.<string>' (`<string>')




GNS-013      can not find generic variable '<string>', assumed value 0




GNS-014      could not find black box '<string>' in circuit




GNS-015      single connector '<string>' (instance '<string>') is linked to a vector connector <string>




GNS-016      vector connector '<string>' (instance '<string>') is linked to a single connector <string>




GNS-017      could not find correspondance for transistor '<string>'




GNS-018      found a transistor with no name




GNS-019      could not find correspondance for signal '<string>'




GNS-020      can't drive '<string>' type in function call




GNS-021      can't drive pointer type in function call




GNS-022      can't find figure '<string>'




GNS-023      Could not write file <string>.gns




GNS-024      Cannot create file <string>.gen




GNS-025      Can't redirect GENIUS output to '/dev/null'




GNS-026      <string>:<decimal>: division by zero




GNS-027      forbidden operators 'mod', 'rem', '**'




GNS-028      variable <string> not found




GNS-029      <string>:<decimal>: IF forbidden for GNS




GNS-030      a variable name was expected for instance '<string>', found a number




GNS-031      generic variable '<string>' not define




GNS-032      Value of '<string>' for instance '<string>' must be <decimal>, actually %ld




GNS-033      There should be at least one instance of model '<string>' with <string>=<decimal>




GNS-034      More than 1 unknown generic variable




GNS-035      variable '<string>' is not defined yet




GNS-036      <string>: can't go thru '<string>'




GNS-037      <string>: can't find instance '<string>' in model




GNS-038      no corresponding transistor for <string>




GNS-039      *** <decimal> error(s) detected, I can't get farther!! ***




GNS-040      for model instance '<string>' can not evaluate left or right bound for connector '<string>' l=<decimal> r=<decimal>




GNS-041      no correspondance found for signal '<string>(<decimal>)




GNS-042      Error: <string>




GNS-043      No model file in library




GNS-044      Cannot open model file <string>




GNS-045      no model <string> found




GNS-046      unknown connector (<string>) declared in symmetric connector list




GNS-047      invalid mix of vector and bit




GNS-048      unknown connector (<string>) declared in coupled connector list




GNS-049      Could not find subfigure '<string>' in file '<string>'




GNS-050      Spice file <string> should be a flat transistor netlist




GNS-060      other errors follow...




GNS-061      in model '<string>', connector '<string>' of unexistant instance '<string>' must not be linked the model interface




GNS-062      in model '<string>', if connector '<string>' of unexistant instance '<string>' is not used, it must be linked to a supply




GNS-063      in model '<string>', connector '<string>' of unexistant instance '<string>' must not be linked to another unexistant instance connector




GNS-064      Inconsistancies found for instance '<string>' of model '<string>'




GNS-065      Connector '<string>' of instance mismatched with connector '<string>' of model




GNS-066      Inconsistancies found for connector '<string>' of instance '<string>' with model '<string>'




GNS-067      Connector number mismatched




GNS-068      While parsing correspondance tables, line <decimal>, transistor out of context




GNS-069      While parsing correspondance tables, line <decimal>, could not find transistor '<string>' in original netlist




GNS-070      While parsing correspondance tables, line <decimal>, signal out of context




GNS-071      While parsing correspondance tables, line <decimal>, could not find signal '<string>' in original netlist




GNS-072      While parsing correspondance tables, line <decimal>, instance out of context




GNS-073      While parsing correspondance tables, line <decimal>, could not find instance correspondance '<string>' table




GNS-074      While parsing correspondance tables, line <decimal>, could not find instance correspondance table




GNS-075      While parsing correspondance tables, line <decimal>, variables out of context




GNS-076      While parsing correspondance tables, line <decimal>, dictionary entry without dictionary mode




GNS-077      While parsing correspondance tables, line <decimal>, too many entries in dictionary




GNS-078      While parsing correspondance tables, line <decimal> ignored




GNS-079      Could not find instance in model to start search with
     There should be at least one real instance in the model




GNS-080      could not find instance '<string>' in GNS toplevel instance




GNS-081      out of bounds with <string> and <string> started from <string>




GNS-082      computing error for index=%ld end=<decimal>




GNS-083      parameter discrepancy between <string> and <string>




GNS-084      infinite loop on <string>




GNS-085      transistor in loop is forbidden




GNS-086      <string>:<decimal>: GNS ignored expansed 'FOR' driven by variable '<string>'




GNS-087      several signals connected to connector <string> of instance '<string>'




GNS-088      vector connector <string> connected to single signal <string>




GNS-089      connector '<string>' with several signals




GNS-090      can not compute destination connector index for '<string>', the high bound of signal '<string>' is not known yet




GNS-091      vector connector '<string>' connected to one bit signal




GNS-092      bit number <decimal> is out of bounds for signal <string>




GNS-093      bit number <decimal> is out of bounds for connector <string>




GNS-094      transistor type/parameter discrepancy (<string>)




GNS-095      <string>:<decimal>: too many parameters for transistor '<string>'




GNS-096      <string>:<decimal>: a number was expected for instance '<string>', found a variable name




GNS-097      <string>:<decimal>: A positive non nul number was expected for instance '<string>'




GNS-098      <string>:<decimal>: unknown transistor parameter '<string>'




GNS-099      instance type/parameter discrepancy (<string>)




GNS-100      too many connectors in instance '<string>'




GNS-101      connectors <string> and <string> mismatch for instances <string> and <string>




GNS-102      not enough connectors in instance '<string>'




GNS-103      parameter discrepancy between instances <string> and <string>




GNS-104      <string>:<decimal>: a variable name was expected for instance '<string>', found a number




GNS-105      could not find generic variable '<string>' in entity variable list




GNS-106      several signals connected to connector <string> of instance <string>




GNS-107      no search done on connector '<string>' signal '<string>', model must be a connexe graph




GNS-108      no search done on signal '<string>(%ld)', model must be a connexe graph




GNS-109      can't compute connector bound for connector '<string>'
     certainly while building a fake instance or transistor




GNS-110      width mismatch between connector '<string>(<decimal>..<decimal>)' and signal '<string>(<decimal>..<decimal>)'




GNS-111      Index <decimal> is out of range for signal <string> (<decimal>..<decimal>)




GNS-112      Index <decimal> is out of range for signal <string>




GNS-113      <string>:<decimal>: negative vector bound computed for expression, values are <decimal> and <decimal>




GNS-114      no search done on connector '<string>(%ld)', model '<string>' must be a connexe graph




GNS-115      connector <string>.<string> is in coupled list but has no symetric




GNS-116      no symmetry found for connector <string> in coupled connector list




GNS-117      coupling won't work with vectors ... yet...




GNS-118      can not find coupled connector for '<string>'




GNS-119      could not find connector '<string>(<decimal>)' for instance '<string>'




GNS-120      while swapping <string> and <string>, one of the connector did not have coupled connector list while the other has




GNS-121      Internal limitation. too much symmetric informations.
          Actual limit is <decimal>




GNS-122      same signal in different symmetry list




GNS-123      same signal in different coupled list




GNS-124      <string>:<decimal>: array of signal '<string>' out of bounds with model line <decimal>




GNS-125      <string>:<decimal>: array doesn't match for '<string>' (line model <decimal>)




GNS-126      <string>:<decimal>: connector '<string>' is missing in left side of instance




GNS-127      <string>:<decimal>: too many connections in Port Map. Component line <decimal>




GNS-128      <string>:<decimal>: not enough connections in Port Map. Component line <decimal>




GNS-129      <string>:<decimal>: <string> already excluded




GNS-130      <string>:<decimal>: instance <string> doesn't exist in architecture <string> of <string>




GNS-131      <string>:<decimal>: INPUT '<string>' cannot be connected with OUTPUT '<string>'




GNS-132      <string>:<decimal>: OUTPUT '<string>' cannot be connected with INPUT '<string>'




GNS-133      <string>:<decimal>: OUTPUT '<string>' cannot be connected with INPUT '<string>'




GNS-134      <string>:<decimal>: only one variable authorized in a 'for' expression. Use Hierarchy!




GNS-135      <string>:<decimal>: forbidden operator '<string>' on variable




GNS-136      <string>:<decimal>: division by zero could appear




GNS-137      <string>:<decimal>: a generic isn't needed by model line <decimal>




GNS-138      <string>:<decimal>: a generic is needed by model line <decimal>




GNS-139      <string>:<decimal>: not enough variables in component. model ends at line <decimal> with '<string>'




GNS-140      <string>:<decimal>: type '<string>' doesn't match with model line <decimal>




GNS-141      <string>:<decimal>: too many variables in component. model ends at line <decimal> with '<string>'




GNS-142      <string>:<decimal>: a port isn't needed by model line <decimal>




GNS-143      <string>:<decimal>: a port is needed by model line <decimal>




GNS-144      <string>:<decimal>: a bit is expected for '<string>' line <decimal> of model




GNS-145      <string>:<decimal>: size of '<string>' mismatches with model line <decimal>




GNS-146      <string>:<decimal>: a vector is expected for '<string>' line <decimal> of model




GNS-147      <string>:<decimal>: predefined rule '<string>': IN Grid, INOUT Source, INOUT Drain, IN Bulk




GNS-148      <string>:<decimal>: There is no vector in predefined rule '<string>'




GNS-149      <string>:<decimal>: The predefined entity '<string>' don't have a generic




GNS-150      <string>:<decimal>: '<string>' must be an external connector




GNS-151      <string>:<decimal>: predefined rule '<string>' impossible to use as a transistor name as an entity name




GNS-152      <string>:<decimal>: more than one action defined for entity '<string>'




GNS-153      <string>:<decimal>: no architecture defined for entity '<string>'




GNS-154      <string>:<decimal>: too many (><decimal>) transistors in architecture '<string>' to start FCL




GNS-155      <string>:<decimal>: Generate forbidden with transistor in model <string>




GNS-156      <string>:<decimal>: Blackbox with generic variables not implemented yet




GNS-157      <string>:<decimal>: GNS can't start on a pure transistor netlist '<string>'




GNS-158      you must explicitly specify the vector range for '<string>'




GNS-159      <string>:<decimal>: negative vector index




GNS-160      <string>:<decimal>: vector direction error




GNS-161      no figure model <string> found




GNS-162      <string>:<decimal>: <string> instance '<string>' can't be found




GNS-163      <string>:<decimal>: '<string>' used several times, primary use line <decimal> in file <string>




GNS-164      <string>:<decimal>: variable '<string>' not defined




GNS-165      <string>:<decimal>: <string>




GNS-166      Cannot read file <string>




GNS-167      Error executing TCL funcion '<string>':
     <string>




GNS-168      internal: unknown transistor model '<string>'




6. 13. INF

Error Num Error Message and description


INF-001      <string>L and W not required

The parameters L and W won't be use because they have no meaning in this declaration.




INF-002      <string>unrecognized token '<string>', should be <string>

The expected token was not found.




INF-003      <string>unrecognized token '<string>'

The token is unknown and can't be handled.




INF-004      <string>invalid value '<string>', should be <string>

An invalid value has been encountred.




INF-005      <string>unknown section '<string>', ignoring section

The section is unknown and can't be handled.




INF-006      <string>unknown direction '<string>', ignoring section

The connector direction is unknown and can't be handled.




INF-007      <string>clock '<string>' is not delared yet

A clock signal is referenced but has not been declared yet.




INF-008      <string>no period specified for clock '<string>' or no default period

It's impossible to find a period to associate with the clock. Either the default period or the clock period should be defined.




INF-009      <string>:<decimal>: syntax error near '<string>'

A syntax error occured when parsing file. Either a signal name matchs a syntax token or the token is unknown. In the first case, consider enclosing the signal name with quote.




INF-010      <string>:<decimal>: syntax error in regular expression

An invalid regular expression have been detected.




INF-011      no figure name given, guessing it is '<string>'

The information file should begin with the figure name associated with the informations. If the name is not specified, a figure name will be guessed from the file name. This could lead to errors if the guessed name is wrong.




INF-012      can not open '<string>' information file

An error occured when trying to read the information file.




INF-013      <string>information on signal <string> already read -- ignored




INF-014      <string>information on signal '<string>' has already been set elsewhere -- overriding with inf values

A default value has been set by the netlist spice deck and will be shadowed by a new value who has more priority.




INF-015      <string>information '<string>' for '<string>' has already been set to '<string>' elsewhere -- overriding with inf value '<string>'

A default value has been set by the netlist spice deck and will be shadowed by a new value who has more priority.




INF-016      <string>information '<string>' for '<string>' has already been set elsewhere -- overriding with inf values

A default value has been set by the netlist spice deck and will be shadowed by a new value who has more priority.




INF-017      <string>information '<string>' for '<string>' has already been set to <decimal> elsewhere -- overriding with inf value <decimal>

A default value has been set by the netlist spice deck and will be shadowed by a new value who has more priority.




INF-018      could not create file '<string>'

An error occured when trying the open the information file in write mode.




INF-019      <string>slope defined for pin '<string>' <string> is too low, set to <string>




INF-020      <string>invalid check type ('<string>') for 'NoCheck' section




INF-021      unknown inf section '<string>'




INF-022      <string>unknown characteristic '<string>', ignoring this entry

The signal characteristic is unknown and can't be handled.




INF-023      name '<string>' doesn't match any <string> in circuit




INF-024      <string>incompatible tokens given for 'directives' section

Using "... with sig rising|falling" or "... before|after sig up|down" is forbidden.




INF-025      <string>invalid type '<string>', ignoring this entry

The given type does not apply to this section and can't be handled.




INF-026      <string>out of range probability value: <float>

The probability value must be a value ranging from 0 to 1.




INF-027      invalid marking <string>




6. 14. LOG

Error Num Error Message and description


LOG-000      Internal Error <string>




LOG-001      Maximum number of variables for BDDs reached




LOG-002      BDD's system not enough memory...




6. 15. MBK

Error Num Error Message and description


MBK-000      connector <string> not found in instance <string>




MBK-001      connector number mismatch beetwen instance <string> and figure <string>




MBK-002      can't evaluate '<string>', assuming 0




MBK-003      transistor length is null




MBK-004      transistor width is null




MBK-005      conflicting power supply on node '<string>' keeping <float>v (other is <float>v)




MBK-006      Can't flatten figure <string> because RC cache is active




MBK-007      lofigchain is missing on lofig <string>




MBK-008      Null CTC on signal %ld (1) in instance <string>




MBK-009      flattenlofig: connector <string> exists only in instance <string>




MBK-010      flattenlofig: connector <string> in instance <string>: number of physical nodes differ




MBK-011      Null CTC on signal %ld (2) in instance <string>




MBK-012      figure <string> not empty (type=%ld)




MBK-013      unflat error: no supply ground




MBK-014      unflattenlofig: connector number inconsistency between model '<string>' and instance '<string>'




MBK-015      duplosig impossible: signal %ld already exist




MBK-016      the radical <string> is already used in a vector




MBK-017      the radical <string> has a spurious vectorized value <string> (<string>)




MBK-018      figure '<string>': transistor '<string>' appears several times




MBK-019      can't open file <string>




MBK-020      addlofig impossible: figure <string> already exists




MBK-021      addlomodel impossible: model <string> already exists




MBK-022      illegal transistor type: %ld




MBK-023      addloins impossible: instance <string> already exist in figure <string>




MBK-024      addloins impossible: instance model is the figure <string> itself




MBK-025      addloins impossible: connector number discrepancy between figure <string> and instance <string> in figure <string>




MBK-026      addlocon impossible: connector <string> already exists in figure <string>




MBK-027      addlocon impossible: bad direction <character> in figure <string>




MBK-028      addlosig impossible: signal %ld already exist in figure <string>




MBK-029      getloins impossible: instance <string> doesn't exist in figure <string>




MBK-030      getlotrs impossible: transistor <string> doesn't exist in figure <string>




MBK-031      getlocon impossible: connector <string> doesn't exist in figure <string>




MBK-032      getlosig impossible: signal %ld doesn't exist in figure <string>




MBK-033      viewlo: empty list of figure




MBK-034      setsigsize() impossible: BKSIG not NULL




MBK-035      Conflict power supply on signal: <string>




MBK-036      u is not a square matrix




MBK-037      u and l matrix size mismatch




MBK-038      could not find a pivot




MBK-039      singular matrix given




MBK-040      matrix a and b size can not allow '*' operation




MBK-041      matrix a and b size can not allow '-' operation




MBK-042      matrix solve order has not been computed yet




MBK-043      matrix a and sol size can not allow solve operation




MBK-044      unreducable matrix given




MBK-045      fatal mbkalloc error: not enough memory when trying to allocate %lu bytes, top= %luKb




MBK-046      fatal mbkrealloc error: not enough memory




MBK-047      Can't open file <string> because too big




MBK-048      mbksysfopen: bad value for access




MBK-049      file <string> opened, file <string> ignored




MBK-050      file <string> opened for writting, file <string> is deleted




MBK-051      Cannot evaluate parameter <string>='<string>'<string>




MBK-052      Cannot evaluate expression '<string>=<string>' in figure '<string>': variable<string> <string> <string> unknown, assuming 0




MBK-053      Undefined <string> parameter '<string>' in subcircuit '<string>'




MBK-054      Error #<decimal> in avt communication protocol (<string>)




MBK-055      IP port <decimal> already in use. Waiting...




MBK-056      Can't activate master process in a slave process




MBK-057      not enought communication slot to handle new input connection !




MBK-058      Non slot to handle new input connection !




MBK-060      some communication slot are still active, but all process are finished !




MBK-061      a lofig is not allowed in the slave process !




MBK-062      a cnsfig is not allowed in the slave process !




MBK-063      a ttvfig is not allowed in the slave process !




MBK-064      a abnormal end-of-file was encountered !




MBK-065      error '<string>' while reading file '<string>'




MBK-066      error '<string>' while writing to file '<string>'




MBK-067      missing end of encryption marker in file '<string>'




MBK-068      Failed to transfer file '<string>'




MBK-069      Environment variable '<string>' is not set




MBK-070      Expression '<string>' returned negative value for <string>




MBK-071      Diode model evaluation returned <string> capacitance value




MBK-072      Resistive paths found between power supplies. If resistor names do not appear, consider using 'avt_config avtSpiKeepNames resistance'.




6. 16. MCC

Error Num Error Message and description


MCC-000      Unknown transition in mcc_generatesimgate




MCC-001      Default values assumed for vbs




MCC-002      Can't generate params for <string> ( L = %ldn, W = %ldn )




MCC-003      Can't find vds for a degraded transistor




MCC-004      Hspice bsim3v3 model used with invalid ACM value (<decimal>)




MCC-005      Level = 53, default ACM=10 used!!!




MCC-006      Level = 49, default ACM=0 used!!!




MCC-007      Invalid value of parameter MOBMOD, default value used!




MCC-008      Computation of Vdsat failed! Default computation of Vdsat used!




MCC-009      Negative Leff for <string> (L = %ldn, W = %ldn)! default value assumed: Leff = %ldn




MCC-010      Negative Weff for <string> (L = %ldn, W = %ldn)! default value assumed : Weff = %ldn




MCC-011      Computation of Vdsat failed! Bad value for RDSMOD = 0 assumed




MCC-012      Technofile <string> to get doesn't exist!




MCC-013      Technofile <string> to delete doesn't exist




MCC-014      No model <string> in technofile <string>, can't get index!




MCC-015      No model <string> in technofile <string>, can't get model name!




MCC-016      No model <string> in technofile <string>, can't get XL!




MCC-017      No model <string> in technofile <string>, can't get XW!




MCC-018      Can't initialise diode model '<string>' parameters, unknown diode's level: <decimal>




MCC-019      Computation of VDDdeg for model <string> which is a PMOS transistor!




MCC-020      Issue occured while computing VDDdeg for model <string> (L=<float>,W=<float>), default value 'VDD (<float>) - VTH (<float>)' assumed (<float>)




MCC-021      Computation of VSSdeg for model <string> which is a PMOS transistor!




MCC-022      Issue occured while computing VSSdeg for model <string> (L=<float>,W=<float>), default value 'VTH' assumed (<float>)




MCC-023      mcc_dio_calcCDEP invalid value for TLEV! TLEV = 0 assumed




MCC-024      Issue occured while computing VTI_nmos




MCC-025      Issue occured while computing VTi_pmos




MCC-026      Technofile <string> doesn't exist, can't addmodel!




MCC-027      Model <string> doesn't exist!




MCC-028      No model <string> (<string> case L = %ldn, W = %ldn) for <string>

The technology file does not contain the model or the device size is out of the model ranges. It may also be necessary to load the techonology file before using CPE.




MCC-029      No model for diode model <string>!




MCC-030      Closest model assumed <string> (lmin = %ldn, lmax = %ldn, wmin = %ldn, wmax = %ldn)




MCC-031      Positive vbs (<float>) for transistor <string> (model <string> L=<float>u W=<float>u)




MCC-032      Negative vbs (<float>) for transistor <string> (model <string> L=<float>u W=<float>u)




MCC-033      <string> is used for best corner!




MCC-034      <string> is used for worst corner!
    




MCC-035      Could not characterize transistor model '<string>' with given PVT: vdd=<float>v temp=<float>

Check if the PVT suits your transistor model




MCC-036      Unknown transistor instance specific parameter '<string>'




MCC-037      Failed to evaluate <string>=<string>




MCC-038      Cannot evaluate model parameter <string>='<string>'<string>




MCC-039      Extra transistor instance specific parameter <string>=<float> found in subckt '<string>', found value used




MCC-040      Extra transistor instance specific parameter M=<decimal> : technology check won't work properly




MCC-041      <string> found on transistor <string> in technology file subckt '<string>'




MCC-042      Can't determine transistor model type for '<string>' using simToolModel setting '<string>'. Guessing '<string>'. Please set correct simToolModel ('<string>'?).




MCC-043      Can't open transistor model definition file <string>.




MCC-044      Parse error line <decimal> file <string>.




MCC-045      Can't parse transistor definition file. Search in <string> : <string>




6. 17. MGL

Error Num Error Message and description


MGL-001      syntax error line <decimal>




MGL-002      illegal vector range specification at line <decimal>

The bounds specified for a bussed signal are not numerical values.




MGL-003      port '<string>' already declared at line <decimal>

An external connector with the same name has already been declared in the module.




MGL-004      net '<string>' already declared at line <decimal>

A net with the same name has already been declared in the module.




MGL-005      net '<string>' used out of declared range at line <decimal>

A bit a range of bits is refered to for the given net despite being beyond the bounds specified in the net declaration.




MGL-006      width or/and type mismatch at line <decimal>

A port connection in an instantiation does not match the port specification of the module being instantiated.




MGL-007      escaped vector '<string>' not declared in strict bit ascending/descending order at line <decimal>

Only occurs if avtStructuralVerilogVector is set to yes. Escaped vectors declared as individual bits can be handled correctly only if the bits are declared in a strict ascending or descending order without any gaps.




MGL-008      escaped vector '<string>' not declared with all bits together at line <decimal>

Only occurs if avtStructuralVerilogVector is set to yes. Escaped vectors declared as individual bits can be handled correctly only if the bits are declared together.




MGL-009      Missing external connector for external signal '<string>' driving verilog netlist '<string>'

Occurs when driving an incoherent verilog netlist.




MGL-010      Cannot open file to drive verilog netlist '<string>'

File I/O error, check disk space and privileges.




6. 18. SLIB

Error messages description not available yet.

6. 19. SPF

Error Num Error Message and description


SPF-001      Invalid pin type '<string>' at line <decimal>

The pintype field does not contain a valid [IiOoSsBbJjXx] character.




SPF-002      Syntax error at line <decimal>, token '<string>'

The given line does not conform to legal SPF syntax. If token is 'CR', there are probably missing elements on the line.




SPF-003      Undeclared node '<string>' (line <decimal>)

The given node is not declared in the current net.




SPF-004      Net '<string>' with mismatching total capacitance (total=<float>pf, sum=<float>pf)

The total capacitance already associated with a net in a design does not match the value given for the total capacitance for the net in the SPF file.




SPF-005      Unsupported divider, using '/' (line <decimal>)

A missing or invalid character used to specify the hierarchy divider.




SPF-006      Unsupported delimiter, using ':' (line <decimal>)

A missing or invalid character used to specify the name delimiter.




SPF-007      Unknown syntax for BUSBIT section (line <decimal>)

Illegal syntax used to specify bus delimiters in the BUSBIT section.




SPF-008      Undefined design entity name

The name of the design to be annotated is not specified in the SPF file.




SPF-009      Entity '<string>' does not exist

The design entity specified for annotation does not exist. Either the netlist has not been loaded yet or the names do not match.




SPF-010      Unknown capacitance unit '<string>', assuming 'pf' (line <decimal>)

Illegal specification of capacitance unit. Legal values are ff, pf, nf, uf, mf, kf. The final 'f' is optional and case is irrelevant.




SPF-011      Unknown resistance unit '<string>', assuming none (line <decimal>)

Illegal specification of resistance unit. Legal values are f, p, n, u, m, k. The case is irrelevant.




SPF-012      Device or instance '<string>' cannot be found (line <decimal>)

The object specified for connection to the parasitic network does not exist.




SPF-013      Connector of transistor '<string>' named '<string>' cannot be found (line <decimal>)

The name used to specify the transistor connector is invalid. Legal names are g, d, s, b.




SPF-014      Connector of transistor '<string>' named '<string>' might be connected to the wrong signal (line <decimal>)

There may be an incoherance in the parasitic file.




SPF-015      Instance '<string>' cannot be found (line <decimal>)

The instance specified for connection to the parasitic network does not exist.




SPF-016      Connector of instance '<string>' named '<string>' cannot be found (line <decimal>)

The name used to specify the instance connector is invalid.




SPF-017      Connector '<string>' cannot be found (line <decimal>)

The external pin specified for connection to the parasitic network does not exist.




SPF-018      Connector named '<string>' is on the wrong equipotential (line <decimal>)

There may be an incoherance in the parasitic file.




SPF-019      Negative capacitance found (line <decimal>)

A negative value was used to specify a capacitance, this is ignored.




SPF-020      Negative resistance found (line <decimal>)

A negative value was used to specify a resistance, this is ignored.




SPF-021      <decimal> signal(s) missing in the netlist

Signals specified in the parasitic file do not exist in the netlist.




SPF-022      Don't know how to handle connector '<string>' for resistor annotation (line <decimal>)

The handled names for resistor connectors are 'pos', 'neg' , '1' and '2'.




SPF-023      Signal '<string>' missing in the netlist (line <decimal>)

Signal can not be found in netlist to annotate.




SPF-024      Failed to open file '<string>'

The dspf file was not found.




SPF-025      RC Network declaration for signal '<string>' continued at line <decimal>

Multiple consecutive declarations for the signal have been detected. They will be merged.




SPF-026      Don't know how to handle capacitance/diode connector '<string>' for capacitance/diode annotation (line <decimal>)

The handled names for capacitance and diode connectors are '1' and '2'.




SPF-027      No declaration of crosstalk capacitance node '<string>' (line <decimal>), associated with net '<string>'




SPF-028      Node '<string>' (line <decimal>) could not be created, coupling capacitance to this node will be ignored

A coupling capacitance to a non existant signal in the netlist will be ignored.




6. 20. STM

Error Num Error Message and description


STM-000      Array bound write in model '<string>'




STM-001      Parse error file '<string>' line <decimal>




STM-002      solvepi (): non convergence




STM-003      Negative capacitance found on signal <string>




STM-004      Deleting more models than allocted




STM-005      stm_cell_delmodel: null cell




STM-006      stm_cell_delmodel: null model




STM-007      Can't open file '<string>'




STM-008      stm_addht impossible: hash table size is '0'




STM-009      stm_addhtitem impossible: value is STM_EMPTYHT or STM_DELETEHT




STM-010      Constraint calculation meaningless in SCM model




STM-011      Cannot resolve pi tree with tables: taking c1 + c2




STM-012      Cannot resolve pi tree with polynoms: taking c1 + c2




STM-013      Load parameter not yet implemented for polynoms




STM-014      Clock slew parameter meaningless in SCM models




STM-015      Clock slew parameter not yet implemented for polynoms




STM-016      Data slew parameter meaningless in SCM models




STM-017      Data slew parameter not yet implemented for polynoms




STM-018      imax not yet implemented for tables




STM-019      imax not yet implemented for polynoms




STM-020      Slew parameter not yet implemented for polynoms




STM-021      Merge of polynom models not yet implemented




STM-022      Reduction of polynoms not yet implemented




STM-023      Shift of polynoms not yet implemented




STM-024      Negation of polynoms not yet implemented




STM-025      No model type for signature




STM-026      STM cannot compute imax from constant model




STM-027      STM cannot compute vth from constant model




STM-028      STM cannot compute slope from constant model




STM-029      NULL model




STM-030      Lost memory consistency




STM-031      Shift of SCM models meaningless




STM-032      Negation of SCM models meaningless




STM-033      Table extrapolation




STM-034      Noise created twice




STM-035      Cannot get current file position




STM-036      Cannot set file position




STM-037      Bad unit for STM_CACHESIZE




STM-038      invth created twice




STM-039      Default capacitance range used for function model




STM-040      Could not find timing model file for figure '<string>'

The .stm file might not be accessible to the tool.




STM-041      Constant and table cannot be both valid




STM-042      CALL_SIMULATION called out of context




STM-043      CALL_SIMULATION can't find association for %p '<string>'




STM-044      CALL_SIMULATION_ENV called out of context




STM-045      CALL_SIMULATION_ENV can't find association for %p '<string>'




STM-046      CALL_CTK_ENV called out of context




STM-047      CALL_CTK_ENV can't find association for '<string>'




STM-048      GNS information not loaded, can't compute




STM-049      Could not retreive instance <string>




STM-050      Round overflow




STM-051      Parse error while reading TLF file line <decimal>




STM-052      Imprecision risk for delay '<string>(<character>)' to '<string>(<character>)', slope = <decimal>ps, load = <decimal>fF.




6. 21. TAS

Error Num Error Message and description


TAS-001      slope computing error : circuit not extracted or wrong extraction




TAS-002      netlist error: the connector <string> is not an input




TAS-003      netlist error: the connector <string> is not an output




TAS-004      the connector <string> is not used




TAS-005      the connector <string> can not reach the high level




TAS-006      the connector <string> can not reach the low level




TAS-007      can not force the level of connector <string>




TAS-008      can not open the file <string>




TAS-009      the signal <string> doesn't exist in the circuit or is not a transistor gate or is already declared




TAS-010      can not close the file <string>




TAS-011      no control signal in the latch %ld (<string>)




TAS-012      incomplete input list for the cone %ld (<string>)




TAS-013      the latch <string> is not a differential latch




TAS-014      error in technology file <string>




TAS-015      block without diffusion capacitance. can not measure the drain or source capacitance




TAS-016      block without diffusion capacitance drain and source capacitance will be measured with ACM=1 SPICE method




TAS-017      floating exception




TAS-018      no value or edge can be set for signal <string>. set to 0




TAS-019      can not find the slopes of the cone %ld (<string>)




TAS-020      no active branch found in the cone %ld (<string>)




TAS-021      error in the truth table %ld (<string>)




TAS-022      unknown state <string>




TAS-023      unknown column type <string>




TAS-024      non external branch containing connector cone %ld (<string>)




TAS-025      no slope on the node <string>




TAS-026      usage of the new delay switch model requiere to set the TAS_DELAY_SWITCH to NO.




TAS-027      tasalloc() error: not enough memory. only the critical path will be retained. freeing memory space




TAS-028      fatal error: not enough memory




TAS-029      unknown event %ld




TAS-030      no inout or output connector




TAS-031      loop detected: see the <string>.loop file for more informations




TAS-032      monolatch chain %ld (<string>)




TAS-033      the cone %ld (<string>) does not contain feedback pathes




TAS-034      non-external branch in the cone %ld (<string>)




TAS-035      latch on output connector <string>




TAS-036      precharge on output connector <string>




TAS-037      negative or zero delay between <string>




TAS-038      transistor link losed




TAS-039      too small resistance for signal <string>. set to 1




TAS-041      the precharge processing must be used with the 'ttv' file. the '-n' option will be set




TAS-042      there is no extractible path in the figure <string>




TAS-043      bad environment variable <string>




TAS-044      the cell characterization option is incompatible with the 'deb' file




TAS-045      errors detected in the netlist. see <string>.rep file for more details




TAS-046      latch on input connector <string> ignored




TAS-047      precharge on input connector <string> ignored




TAS-048      memory on input connector <string> ignored




TAS-050      transistors detected in figure <string> impossible in hierarchical mode or instances do not have timing files




TAS-051      impossible to find in figure <string>




TAS-052      bad connector direction on signal <string>




TAS-053      internal connector <string> not found in RCX view




TAS-054      only one connector on internal signal <string>




TAS-055      only input connectors or constante connectors on internal signal <string>




TAS-056      no input on internal signal <string>




TAS-057      conflict detected on internal signal <string>




TAS-058      no rc delay on signal <string>. may be the rc tree are not connected or there is no slope on the driver




TAS-059      more than one latch on signal <string>




TAS-060      more than one precharge on signal <string>




TAS-061      fatal error check your input files




TAS-062      figure <string> already exists




TAS-063      no rc delay on signal <string>. may be loop detected




TAS-064      no or bad rcx file for figure <string>




TAS-065      name <string> already exists




TAS-066      It is better to simulate the signal <string>




TAS-067      No timing model for instance <string>: flattened




TAS-068      No execution context (missing tas_setenv)




TAS-069      Conflicting temperature: <string>




TAS-070      PVT conditions prevent signal propagation on cone <string>, timing arc suppressed

Vin under static threshold (Increasing power supply may solves)




TAS-071      PVT conditions lead to out of bound parameters on cone <string>, timing arc suppressed

Delay and slope calculations failed on pass-gate (Increasing power supply may solves)




TAS-072      Signal '<string>' connected on power connector '<string>' of instance '<string>'




TAS-073      Could not find connector '<string>' in circuit '<string>'




TAS-074      can't extract path to simulate




TAS-075      can't get patterns to simulate the path




6. 22. TRC

Error Num Error Message and description


TRC-000      [AWE:<decimal>] Internal error :
     net <string>
     driver <string>
     receiver <string>

The internal data representation for parasitic element is not consistent. Please contact Avertec Support.




TRC-001      [AWE] Negative delay computed on net <string>

Parasitics on the net present some particularities, leading to an error when computing delays with AWE algorithm.




TRC-002      [AWE] All order fail when computing delay on net <string>

Parasitics on the net present some particularities, leading to an error when computing delays with AWE algorithm.




TRC-003      Can't open file <string> for direct access. Cache is not used.

The .rcx file is compressed, so it can't be opened for direct access. The cache is not used, the file is entirely loaded in memory, leading to more memory consumption.




TRC-004      avtElpCapaLevel mismatch #<decimal>.

The value of the avtElpCapaLevel variable is not consistent with previous setting.




TRC-005      Internal error #<decimal> on net <string>.

This is an internal error. Please contact Avertec Support




TRC-006      Internal error #<decimal>.

This is an internal error. Please contact Avertec Support




TRC-007      Negative ground capacitance found on signal <string>. code=<decimal>

The total capacitance on a net is negative. If it's a power supply net, it should be identified, and no operation on this signal would occur. Check configuration file.




TRC-008      Can't determine equivalent load on signal <string>.

The equivalent gate output load can't be computed. The gate output is probably not connected to anything.




TRC-009      The pi load for the equivalent gate load on signal <string> can't be determined.

The equivalent gate output load can't be computed. The gate output is probably not connected to anything, or parasitics on the net present some others particularities.




TRC-010      The equivalent gate output load gives a negative capacitance for signal <string>. 0 value is retained

This problem occurs when there is a very strong coupling between nets.




TRC-011      Can't open file <string>.<string> for writting.

Check usual Unix specification for file access: permission mode on file or on directory, disk space,...




TRC-012      An error occurs when writting in file <string>.

Check usual Unix specification for file access: permission mode on file or on directory, disk space,...




TRC-013      Try to load an RCX file version #<decimal>. Only 4th version is supported.

The RCX file is too old to be supported. It must be created with newer version of the tool.




TRC-014      File parse error : Line too long.

The length of a line in the RCX file is too long. This case occurs if there are very long signal or instance names, too many nodes on a connector, or if the file is corrupted. The last line of an RCX file is the word END.




TRC-015      File parse error line <decimal> in file <string>.<string>.

An element is not recognized in the RCX file. The file may be corrupted. The last line of an RCX file is the word END. If this is not the case, there has been a problem during the creation of the RCX file.




TRC-016      Error while getting environment variable : <string>. It is <string>

Check the Avertec Documentation to set proper values.




TRC-017      could not modify connector '<string>' origin group

This is an internal error in rc delay calculation with GNS.




TRC-018      rcx timing function does not exist

This is an internal error in rc delay calculation with GNS.




TRC-019      could not get connector '<string>' origin group

This is an internal error in rc delay calculation with GNS.




TRC-020      origin index of connector '<string>' is out of range

This is an internal error in rc delay calculation with GNS.




TRC-021      could not get connector '<string>' destination group

This is an internal error in rc delay calculation with GNS.




TRC-022      destination index of connector '<string>' is out of range

This is an internal error in rc delay calculation with GNS.




TRC-023      rcx timing function does not exist

This is an internal error in rc delay calculation with GNS.




TRC-024      rcx timing function already exist

This is an internal error in rc delay calculation with GNS.




TRC-025      missing rcx timing origin or destination group

This is an internal error in rc delay calculation with GNS.




TRC-026      could not find timings \"<character><character>\" between connectors '<string>' and '<string>' for signal '<string>'

This is an internal error in rc delay calculation with GNS.




TRC-027      could not find timings \"<character><character>\" for an input slope of <float>ps between connectors '<string>' and '<string>' for signal '<string>'

This is an internal error in rc delay calculation with GNS.




TRC-028      can't compute awe delay because a connector is missing : start='<string>' end='<string>'

This is an internal error in rc delay calculation.




TRC-029      can't compute awe delay because input slope is negative : start='<string>' end='<string>'

The input slope for rc delay calculation is negative. There is a problem with the gate model. Check technological parameters and power supply.




TRC-030      can't compute awe delay because power supply is less than vt : start='<string>' end='<string>'

Check power supply and technological parameter of the driver.




TRC-031      can't compute awe delay because threshold is greater than power supply : start='<string>' end='<string>'

The voltage on the rc net can't reach the threshold delay measure.




TRC-032      can't compute awe delay because because there is no rcx view or rcx view is typed RCXERROR : start='<string>' end='<string>'

This is an internal error in rc delay calculation.




TRC-033      can't compute effective load on signal <string> because there is not a valid rcx view.

This is an internal error in rc delay calculation.




TRC-034      can't get the file position : <string>

When using rc cache, can't get the file offset. Try to disable file compression if needed, or remove rc cache. Check unix file so.




TRC-035      can't set the file position : <string>

When using rc cache, can't change the position in file. Try to disable file compression if needed, or remove rc cache. Check unix file access so.




TRC-036      an error occured when reading file : <string>

This rcx file may be corrupted or truncated. The last line of the rcx file is EOF. Check disk space.




TRC-037      an inconsistant line has been read : <string>

The rcx file is corrupted or truncated. The last line of the rcx file is EOF. Check disk space.




TRC-038      No aggressor <string> found : <string>

The rcx file is corrupted or truncated. The last line of the rcx file is EOF. Check disk space.




TRC-039      Signal <string> is defined more than one time : <string>

The rcx file is corrupted.




TRC-040      Signal <string> is not defined : <string>

The rcx file is corrupted.




TRC-041      Problem in cache mechanism : the signal <string> can't be released




TRC-042      [AWE] can't compute the switching instant of the input for rc net <string>

There is a problem when computing the rc input slope on a net. In this case, the rc delay is equal to the switching instant of the rc output.




TRC-043      [AWE] can't compute the switching instant of the output for rc net <string>

There is a problem when computing the rc output slope on a net. In this case, the rc delay is equal to 0 and output rc slope is equal to input rc slope.




TRC-044      [AWE] can't determine the shape of the input for rc net <string>

The representation for the rc driver can't be determined. In this case, the rc delay is equal to 0 and output rc slope is equal to input rc slope.




TRC-045      internal problem in rcdelay cache : signal <string> is yet in cache

There is a proble in rcdelay cache mechanism. Desactivate rcdelay cache.




TRC-046      internal problem in rcdelay cache : no signal

There is a proble in rcdelay cache mechanism. Desactivate rcdelay cache.




TRC-047      internal problem in rcdelay cache : signal <string> is not in cache

There is a proble in rcdelay cache mechanism. Desactivate rcdelay cache.




TRC-048      internal problem in rcdelay cache : unknown data structure in cache for signal <string>

There is a proble in rcdelay cache mechanism. Desactivate rcdelay cache.




TRC-049      internal problem in rcdelay cache : no awe data for signal <string>

There is a problem in rcdelay cache mechanism. Desactivate rcdelay cache.




TRC-050      Net <string> is not connex

The rc description of a net doesn't connect all connectors\n




TRC-051      Disabling compression for <string>.rcx file as RC cache is active.

There is a request to write an .rcx file with the simultaneous uses of output filter and rc cache functionality activated. Since this last functionality requiers direct access on file, the output filter is not used for this file.




TRC-051      Net <string> is not connex

The rc description of a net doesn't connect all connectors\n




TRC-052      Can't solve the LU hybrid matrix on net <string> from locon <string>

There is a problem in awe computation with matrix.\n




TRC-053      Can't handle UTD for circuit '<string>' generated with avtEnableMultipleConnectorsOnNet=yes in hierarchical mode

avtEnableMultipleConnectorsOnNet=yes is supported only for transistor level netlists.\n




6. 23. VAL

Error messages description not available yet.

6. 24. YAG

Error Num Error Message and description


YAG-001      Circuit not found

Attempt to disassemble a circuit entity which does not exist.




YAG-002      RC cache must be deactivated in this mode

Disassembly modes which involve manipulation of hierarchy require that the RC be deactivated.




YAG-003      Connector '<string>' is power supply AND ground

The given external connector has been detected as both Vdd and Vss. This error is fatal.




YAG-004      No VDD signal in the circuit

No Vdd power supply has been identified in the circuit to disassemble. This error is not fatal, however, it is recommended to check the power supply configuration.




YAG-005      No VSS signal in the circuit

No Vss power supply has been identified in the circuit to disassemble. This error is not fatal, however, it is recommended to check the power supply configuration.




YAG-006      Can't open file '<string>'

The specified file cannot be opened. Check disk space and access privileges. This error may be fatal.




YAG-007      Can't close file '<string>'

The specified file cannot be closed. Check disk space and access privileges.




YAG-008      Unrecognized contraint '<string>' in the circuit

The specified mutual exclusion constraint has no correspondance in the circuit to disassemble.




YAG-009      Can't name toplevel <string> in Blackbox mode

Attempt to rename the top-level figure using a name which is already in use.




YAG-010      Figure '<string>' has no transistors and no instances

Circuit contains no elements to disassemble.




YAG-011      Transistors in non-leaf figure '<string>'

In hierarchical disassembly mode, if a no-leaf figure contains a mixture of transistors and instances then the result may not be as expected.




YAG-012      Signal '<string>' is not driven in behavioural figure