plderror.txt

Protel99-SE-软件.zip

@Error_0005sa
invalid library interface
Level:Fatal
Either the device library was not created using the CUPL library manager, CBLD, or CSIMA and the device library are not compatible.
@Error_0006sa
bad library file: "library"
Level:Fatal
Either the device library does not exist or the contents of the device library have been damaged.
@Error_0007sa
device not in library: "device"
Level:Fatal
Either the specified target device does not exist or an entry has not been made in the device library for the device.
@Error_0008sa
invalid output format: "format"
Level:Warning
The download format is not available for the target device; for example, the JEDEC download format is not available for PROMS.
@Error_0009sa
invalid syntax: "symbol"
Level:Error
Either the symbol is used improperly, or a previous syntax error has caused the symbol to be used improperly.
@Error_0010sa
expecting device: "device"
Level:Fatal
The target device is not the same as used when CUPL created the absolute file.
@Error_0011sa
unknown symbol: "symbol"
Level:Error
The symbol, used in the order statement, was not previously defined in the CSIM or CUPL source files.
@Error_0012sa
too many symbols:
Level:Fatal
The number of symbols in the order statement exceeds the number of symbols previously defined in the CSIM and CUPL source files.
@Error_0013sa
excessive test value "value"
Level:Error
The test vector value is greater than the maximum possible value defined in the order statement. This error will occur when there are too many test values.
@Error_0014sa
insufficient test values
Level:Fatal
The test vector value is less than the minimum possible value defined in the order statement. This error will occur when there are too few test values.
@Error_0015sa
field already defined: "field"
Level:Error
The field name was previously used in either the CSIM or CUPL source files.
@Error_0016sa
too many errors
Level:Fatal
CSIM has encountered too many errors to continue.
@Error_0017sa
missing symbol "symbol"
Level:Error
CSIM expected a keyword.
@Error_0018sa
out of memory: "condition"
Level:Fatal
CSIM has used all the available RAM memory allocated by the operating system.
@Error_0019sa
user expected (value) for: "variable"
Level:Error
The test value expected by the user in the .SI file did not match the actual value computed by CSIM.
@Error_0020sa
unstable output: "variable"
Level:Error
The output variable did not have the same test value for two continuous evaluation passes after the maximum twenty passes were attempted. Check the logic equation for an untestable design.
@Error_0021sa
invalid test value: "value"
Level:Error
Either the test value is an invalid test vector symbol or the test value is used improperly; that is, a test value of 0 is used for an output.
@Error_0022sa
bad fault id: "jedec number"
Level:Error
The JEDEC number, given as the fault ID, is not the address of the beginning of a product term.
@Error_0023sa
could not read file: "filename"
Level:Fatal
CSIM could not read from the specified file. This occurs when the contents of the file have been corrupted.
@Error_0024sa
could not write file: "filename"
Level:Fatal
CSIM could not write to the specified file. This occurs when the file is write protected or there is no room left on the disk.
@Error_0025sa
inconsistent header information
Level:Warning
The header information in the CSIM source file does not match the header information in the CUPL source file used to create the absolute file.
@Error_0026sa
missing header item(s)
Level:Warning
At least one of the header statements is missing.
@Error_0027sa
old absolute file format for "filename"
Level:Fatal
The absolute file was created by an incompatible version of CUPL.
@Error_0028sa
statement too long
Level:Fatal
The statement exceeds 256 characters.
@Error_0029sa
invalid trace level: "number"
Level:Error
The trace level must be a decimal number in the range of 0 through 4.
@Error_0030sa
invalid character: "hex value"
Level:Error
CSIMA has encountered an illegal ASCII value in the source file. Make sure the file was created in nondocument mode on the word processor. This error can also be caused by files which were created over a serial modem upload/download link.
@Error_0031sa
disk read error, unexpected end of file: "filename"
Level:Fatal
CSIMA encountered an I/O error trying to read the indicated file. This error usually occurs when the file is being read from damaged media.
@Error_0032sa
feedback usage of undefined output:  "variable name"
Level:Fatal
The variable name does not exist in the ORDER statement and it is being used as input/feedback for another variable. Simulation cannot occur until all relevant variables are defined.
@Error_0033sa
pin number is undefined for:  "variable name"
Level:Fatal
When simulating a design in a specified device, CSIM needs to have all the pin numbers defined. The variable name in the PLD file was not assigned a pin number. The PLD file has to be recompiled with all the pin numbers in place.
@Error_10xxsa
program error: "specifies"
Level:Fatal
An operating system interface problem is suspected. Contact Logical Devices customer support.
@Error_0001sw
could not open: "filename"
Level:Fatal
WCSIM cannot continue because of the failure to open the indicated file. Be sure the file exists if it is an input.
@Error_0002sw
out of memory: "condition"
Level:Fatal
WCSIM has used all the available RAM memory allocated by the operating system. Check for the existence of print spoolers, RAM disks, or other memory-resident programs which may decrease the amount of memory available to the CUPL application program.
@Error_0003sw
too many symbols
Level:Fatal
The number of symbols in the order statement exceeds the number of symbols previously defined in the CSIM source file.
@Error_0004sw
index variable not matched
Level:Fatal
A variable list was defined using incorrect list notation. Refer to List Notation in the documentation.
@Error_0005sw
too many test vectors
Level:Fatal
The number of test vectors exceeded 1024.
@Error_0006sw
invalid syntax: 憇ymbol"
Level:Error
Either the symbol is used improperly, or a previous syntax error has caused the symbol to be used improperly.
@Error_0007sw
unrecognized value in test vector: "value"
Level:Error
Either the test value is an invalid test vector symbol or a character string exists in the ORDER statement.
Even though a character string is allowed in the ORDER statement, it conflicts with the test vector values being read in by the waveform displayer. Remove the character string from the ORDER statement to eliminate the error.
@Error_0001ba
invalid syntax: "statement line number"
Level:Fatal
The specified statement contains a syntax error.
@Error_0002ba
could not open: "filename"
Level:Fatal
CBLD cannot continue because of the failure to open the indicated file. Be sure the file exists if it is an input.
@Error_0003ba
invalid flag: "flag"
Level:Warning
CBLD will warn that the invalid flag cannot be evaluated, and then continue operation. Invoke CBLD without arguments for a list of valid flags.
@Error_0004ba
invalid library access key
Level:Warning
The version number of CBLD does not match the version number of the device library. This occurs when either CBLD or the device library, but not both, has been updated.
To prevent incompatibility problems, it is important that the version numbers match.
@Error_0005ba
invalid library interface
Level:Fatal
Either the device library was not created using CBLD, or the library and CBLD have different version numbers causing incompatibility problems.
@Error_0006ba
bad library file: "library"
Level:Fatal
Either the device library does not exist or the contents have been damaged.
@Error_0007ba
device not in library: "device"
Level:Warning
Either the specified target device does not exist or an entry has not been made in the device library for the device.
@Error_0008ba
inconsistent library access key
Level:Warning
During a build operation, the target library and a source library have different access keys.
@Error_0009ba
inconsistent library rev
Level:Warning
During a build operation, the target library and a source library have different revision numbers.
@Error_0010ba
too many devices for target library: "library"
Level:Fatal
The device library directory is full.
@Error_0011ba
device not in library: "device"
Level:Error
Either the specified device does not exist or an entry has not been made in the device library.
@Error_0012ba
could not find LIBCUPL in ENVIRONMENT
Level:Fatal
The LIBCUPL assignment has not been made in the ENVIRONMENT.
@Error_0013ba
too many devices on command line
Level:Error
The user has specified too many devices on the command for CBLD to proceed. The maximum allowable is determined by the command line limit of the operating system.
@Error_0014ba
disk write error: "filename"
Level:Fatal
CBLD encountered an I/O error in trying to write the indicated file. This error usually occurs when there is insufficient disk space.
@Error_0015ba
out of memory condition
Level:Fatal
CBLD has used all the available RAM memory allocated by the operating system. Check for the existence of print spoolers, RAM disks, or other memory-resident programs which may decrease the amount of memory available to the CUPL application program.
@Error_0000cf
disk stream error
Level:Fatal
Advanced PLD encountered an I/O error trying to seek into the file stream.
@Error_0001cf
disk stream error
Level:Fatal
Advanced PLD encountered an I/O error trying to write into the file stream.
@Error_0002cf
disk stream error
Level:Fatal
Advanced PLD encountered an I/O error trying to read from the file stream.
@Error_0000cs
Server Error:  Unable to run process
Level:Fatal
Unable to run process, check that the Netlist server is installed
@Error_0001cs
Symbol Error:  Cannot find symbol
Level:Fatal
The symbol cannot be found in the Pldnet.sdf file.  The symbol name has either been incorrectly spelt or there is no symbol declaration for this part type. 
@Error_0002cs
File Error: File not found
Level: Fatal;
The specified file is needed to continue compilation.  
@Error_0003cs
PldNet Logic Error: Missing equations
Level: Warning;
The specified part has no logic assosciated in the Pldnet.sdf file and will be ignored by the compiler.
@Error_0004cs
PldNet Logic Error: Symbol declaration invalid
Level: Warning;
Symbol has been incorrectly constructed in the PldNet.sdf file
@Error_0005cs
Buried Node Error : cannot find output pin
Level: Warning;
A pin on this part is buried and needs to be connected to an output pin on this device.  However there are no available output pins on the device.  Select a different device,or assign an output part to the pin on the part indicated by the net.  
@Error_0006cs
Pin Assignment Error : too many pins
Level: Fatal
The part used to make the pin declarations has more pins then those specified as allowable in the pldnet.sdf
@Error_0007cs
No path to input pin on device
Level: Fatal
The pin on the part specified needs to be connected to an input pin on the device.  However there is no path of parts using only inverters and/or buffers to the input pin.  Ensure also that you have the correct Net Identifier Scope setting in PLD:Configure.
@Error_0008cs
No matching pin in pldnet.sdf
Level: Fatal
There is no match between the pinname for this schematic part and the pinname used to describe the part logic in the pldnet.sdf. Either modify the part in the Advpld.lib or the symbol in the pldnet.sdf.  
@Error_0009cs
Invalid Pin definition
Level: Fatal
The pin definition you have declared for this part is not in the correct format. Do not use alphabetic characters. For example when using an IPAD8 you can declare LOC=PIN[1] or LOC=PIN[6,2] or LOC=PIN[4..1,6] as valid pin definitions. If you have selected a device, try LOC=PIN[*], an automatic pin assigment will be made when you compile.  If you have not selected a device then try leaving the pin statement empty.
@Error_0010cs
Design cannot fit into device
Level: Fatal
The number of pins declared for this design exceeds those available to the device.  Select a different device or choose a different minimsation method.
@Error_0001cd
Could not open: "filename"
Level:Fatal
Cannot continue because of the failure to open the indicated file. Be sure the file exists if it is an input.
@Error_0002cd
invalid library access key
Level:Fatal
The version of AdvPLD is not compatible with the version of the device library file. This occurs when either AdvPLD or the device library, but not both, has been updated.
@Error_0003cd
invalid library interface
Level:Fatal
Either the device library was not created using the AdvPLD library manager, CBLD, or AdvPLD and the device library are not compatible.
@Error_0004cd
bad library file: "library"
Level:Fatal
Either the device library does not exist or the contents of the device library have been damaged.
@Error_0005cd
device not in library: "device"
Level:Fatal
Either the specified target device does not exist or an entry has not been made in the device library for the device.
@Error_0006cd
too many errors
Level:Fatal
AdvPLD has encountered more than 30 errors.
@Error_0007cd
disk write error: "filename"
Level:Fatal
AdvPLD encountered an I/O error trying to write the indicated file. This error usually occurs when there is insufficient disk space.
@Error_0008cd
device not yet fully supported: "device"
Level:Fatal
There is an entry for the device in the device library, but the device is not fully supported by the current version of AdvPLD.
@Error_0009cd
Cannot find device library for this device
Level:Fatal
Device library cannot be found.
@Error_0010cd
out of memory: "condition"
Level:Fatal
AdvPld has used all available RAM memory which has been allocated by the operating system.