You are on page 1of 30

Error

Numbe
r

5617

5619

5621

5625
5629

5669

5670

5693

5701

5705

Message

Not parsable missing


token.

Cause
PCB Configuration file has
an invalid token, such as a
misspelled keyword,
invalid delimiter, or
erroneous syntax.

Solution
Check for errors with
keywords, delimiters,
whitespace. See also
5621.

Copy the file [filename]


to the working directory
or to the location
File does not exist in the
Unable to open file
specified
current working directory or
[filename].
by your WDIR variable.
WDIR path.
Specify your WDIR
variable to the location of
[filename].
Check for misspelled
keywords. If you have
modified the original
configuration file that was
PCB Configuration file has
installed for this PCB
unrecognized token, such as
Unrecognized token [token].
interface, refer to a
an unsupported
configuration file for one
keyword.
of the other PCB
interfaces to verify
keyword
spelling.
Unable to open file
File does not have read
Check permissions,
[filename].
permission.
correct as needed.
Token value is other than
[value] not in yes-no table.
Use only "yes" or "no."
yes or no.
Exclude keyword has value
which is something other
Correct value for Exclude
[string] not status word.
than: Error, Note,
keyword.
Warning.
Some warnings, errors or
Check ExcludeNums
Error exclusions in effect.
notes are being excluded
keyword in the PCB
from being displayed.
configuration file.
A keyword in the PCB
Check for misspelled
Wrong number of tokens.
configuration file is missing
keywords.
some tokens.
Input to one of the internal
functions is incorrect. This Check for required
Invalid input for
may be caused by
attributes on symbols,
[function_name] operation.
symbols missing some of correct as needed.
the required PCB attributes.
Error adding object %s of
Check objects for
Mismatch of object types.
type %s to object %s of type
incorrect or missing

%s.
5708

Could not open file %s for


%s access.

The specified file could not


be opened for the specified
access.

5709

Netlister cannot access the


WIR file.

You do not have read/write


permissions to the WIR file.

5711

Bad or missing wire file,


which can be caused by one
of the following:
Could not load ViewBase for
A composite Symbol
%s %s.
without an underlying
Schematic.
An error in the wire file.

5714

Object type %s not valid for


%s operation on object type Mismatch of object types.
%s.

5716

Could not set %s for object


%d of type %s.

Mismatch of object types.

5727

Global net %s on subcircuit


%s is being ignored.

A global net is implicitly


aliased as a named net.

5728

A use of global nets that


Using signal name from level conflicts with local net
above.
names used elsewhere in
the design.
An object is no longer on
the schematic. This may be
because of edits made to the
schematic after the PCB
netlist file was exported to
the place & route tool.

attributes.
Ensure that the specified
file has proper write
privileges.
Check and fix the
permissions to the WIR
file.
Try one of the following:
If there is no underlying
schematic, change the
Symbol Block type to
Module in Designer
Schematic.
Open the wire file in a
text editor and search for
the string called "error."
Correct
the problem you
identified in the
schematic (not directly in
the wire file).
Check the object for
incorrect or missing
attributes.
Check the object for
incorrect or missing
attributes.
Use a bus ripper to alias a
global net to another
named net.
Verify that all
occurrences of a specific
net name are either local
or global,
but not mixed.
Correct the schematic or
the PCB database, or
both, and try backannotation again.

5736

Could not find object %s of


type %s on schematic %s.

5758

Error while loading object of


A problem with an object.
type %s.

Check the object for


missing or incorrect
attributes.

5773

You deleted a net in PCB


layout, and it does not
support this change
automatically when you

Correct this problem


manually in the
schematic.

Manually disconnect net.

5774

Manually connect to old net


%s.

5775

Manually connect to new net


%s.

5776

Manually delete component.

5784

Back-annotation out of sync.

5791

Bad %s dictionary file at line


%d.

5792

%s dictionary entry %s at
line %d was deleted.

5793

Attribute %s found in both


Aliasing and Translation
configuration.

5795

No shape specified.

5800

Gpi Initialization Failed.


Aborting run.

back-annotate to a
schematic.
You made a net connection
in PCB layout, and it does
not support this change
automatically when you
back-annotate to a
schematic.
You made a net connection
in PCB layout, and it does
not support this change
automatically when you
back-annotate to a
schematic.
You made a component
deletion in PCB layout, and
it does not support this
change automatically when
you back-annotate to a
schematic.
The back-annotation
from/to list does not match
the object identifiers on the
current version of the
schematic.
A discrepancy between the
dictionary files and the
current version of the
schematics.
You deleted an object from
the schematics and the
software uses this warning
to inform you that it
updated the dictionary file.
Attribute Aliasing and
Translation are mutually
exclusive, but the software
found an attribute in both of
these sections of the PCB
configuration file.
The PCB library does not
have a shape specified for
the components
PKG_TYPE attribute.
Could not initialize and
load schematic database.

Correct this problem


manually in the
schematic.

Correct this problem


manually in the
schematic.

Correct this problem


manually in the
schematic.

Back-annotate to the
version used to generate
the current PCB netlist
file.
Back-annotate to the
version used to generate
the current PCB netlist
file.

No action required.

Correct the PCB


configuration file. The
attribute should be in only
one of these sections.
Correct either the PCB
library or the PKG_TYPE
attribute value.
Delete the wire files and
run Check Project from
within Designer
Schematic to regenerate

new wire files.


5801
5802

5806

vbLsuInit() already
Re-initializing schematic
Initialized. Returning old
database.
handle.
Error allocating memory for
You are low on memory.
object of type object_type.
Designer Schematic does
Component %s not found on not support adding
sheet 1 of design prototype. capacitors within the layout
using ECO mode.

5810

No schematic sheet in
memory.

5816

Unable to initialize LSU for


null design name.

5817

Unable to open filename.baf


for writing.

5818

Could not load schematic


schematic_name, missing or
bad data.

5819

Use message ID (5819) to


help identify message.

5822

Could not find


component/net instance (id).

5823
5826

No action required.
Close some applications
and rerun the interface.
Not available (N/A).

Check to make sure a


schematic sheet exists. If
The current sheet was not
you deleted the
found in memory.
schematic, delete the
corresponding wire file.
Correct the backThe design name passed for
annotation filename so
back annotation is a null
that it agrees with the
string.
schematic name.
Check to see if you have
Write permission lacking. write permission in the
current working directory.
Regenerate the schematic
The schematic file does not files by checking your
exist for this project, or
project from within
read/write permissions are Designer Schematic, and
incorrect.
make sure you have
read/write permissions.
The baf file specified in the
Copy the specified baf
command line does not
file to the current working
exist in the current working
directory.
directory.
Check to see if the
component or net instance
(id) is in the specified
schematic. Make sure that
You are trying to back
the schematic is written to
annotate attributes to a net
the disk when any change
or component that is not in
is made to it. If you still
the schematic.
have this problem then it
is possible that the logical
database and physical
database are out of sync.

Pin (pin_name) of instance


(instance_name) on
A pin is missing its label.
schematic (schematic_name)
was not found.
Segment number (#) of net You are trying to back

Check to see if all pins on


a symbol are labeled
properly.
Check to see if logical

(net_name) on schematic
(schematic_name) was not
found.

5834

5840

5841

5842

5848

5855

5856

annotate attributes to a
segment which does not
exist.

and physical databases


are in sync.

Check to see if the


component (id) is in the
specified schematic.
Make sure
Instance id on Schematic
you write the schematic to
You tried to back-annotate
schematic_name does not
the disk when you make
to a component that is not
exist. Check uid string uid any changes. Make sure
on the schematic.
sheet_name.
you back-annotate to the
version of the schematic
you used to make the
current PCB layout netlist
file.
The schematic being
Check to make sure the
updated no longer exists or
Use message ID (5840) to
schematic exists, and that
do not have write
help identify message.
you have write privileges
permissions to this
to the file.
schematic.
The attribute you are
updating no longer exists on
Use message ID (5841) to
this instance, possibly due
N/A.
help identify message.
to a change in the schematic
from running PCB interface
tools.
Change the permissions
Use message ID (5842) to
You do not have write
on sheet # so you can
help identify message.
permission to sheet #.
back annotate.
You are trying to create a Re-create the .baf file
Use message ID (5848) to
new sheet # when sheet # before attempting back
help identify message.
already exists.
annotation again.
If you are using the user
interface, then a dialog
box appears in which you
can change the OATs
OATs settings in the
The viewdraw.ini and PCB settings in the
viewdraw.ini and PCB
configuration files have
viewdraw.ini file.
configuration files are
different settings for
Otherwise, a failure
inconsistent.
OATs.
will occur and you will
need to change the OATs
settings in either the
viewdraw.ini file or the
PCB configuration file.
This schematic is currently
locked by another process Ensure there is nothing
Unable to save schematic %s.
and is being modified. The highlighted in the
Check if it is locked.
lock file in the lock
schematic.
directory under the sch sub-

dir contains the necessary


information.

5958

Bad Detach for F2038.

Can be a difference in the


pin labels between Designer
Schematic and the layout
system.

6000

Could not open file


[filename].

The indicated file is not


readable or writeable.

vpbGet [variables] failed.

A line in the PCB


configuration file (PKG
class="LAB") has been
commented out, i.e. has a
vertical bar ( | ) at the
beginning of the line.

6002

SEC: Required license not


found.

A valid license for the


indicated product was not
found.

6004

Could not write file


[filename].

6005

Illegal regular expression:


Code: [n].

6006

Component signal pin # not


on symbol.

6001

Correct any differences


between the pin labels on
the schematic symbols
and
the pins on the
geometries.
Depending on the severity
of the message, either
ignore the message or
verify that the directory
exists, the file exists
and/or the correct access
modes
are set.
Remove the comment
character to enable the
line.

Verify that the license file


or license server has valid
licenses for the
products you are using.
Check the privileges on
Unable to open the .baf file the current directory to
for writing.
ensure you have write
privileges.
A regular expression check
Correct the syntax.
at the indicated line in the
PCB Configuration File:
PCB configuration file
CHKVAL _REG_EXP
has improper syntax.
A SIGNAL or NC attribute
Add the attribute to the
was added to a component,
symbol or enable the
but no
automatic fix-up. PCB
corresponding SIGNAL or
Configuration File:
NC attribute appears on the
CHKBRD
symbol.
_BAD_SIG_NUM.
The pin will not be added.
You added or removed an
NC attribute after you
packaged the design. The Remove the NC attribute
PCB interface cannot
and run pcbfwd again to
change the component level repackage the design.
attribute once the design
has been packaged.

6007

A SIGNAL or NC attribute
was added to a component,
but no
corresponding SIGNAL or
Component signal pin added.
NC attribute appears on the
symbol.
The pin will be added
anyway.

6009

vbChkAttGen: Multiple
generators for attribute
[name].

6013

6016

6017

6018

6019

6020

6021

Add the attribute to the


symbol or ignore or
disable the message. PCB
Configuration File:
CHKBRD
_BAD_SIG_NUM.

Remove one of the


offending GENVAL
lines. PCB Configuration
File:
GENVAL.
Refer to the standard
configuration file and use
A CHKVAL, GENVAL, or
only the documented
Unknown procedure:
CHKBRD keyword is
procedure names. PCB
[procedure].
followed by an unknown
Configuration File:
procedure name.
CHKVAL, GENVAL,
CHKBRD.
There are too many
arguments on the PCB
configuration file line
Reduce the number of
Too many arguments on line.
indicated.
arguments on the line.
Some arguments will be
ignored.
The indicated keyword in
Refer to the standard PCB
the BeginChkRules section
Ambiguous keyword:
configuration file and use
of the PCB
[keyword].
only the documented
configuration file is
keywords.
ambiguous.
The indicated object type in
Refer to the standard PCB
the BeginChkRules section
Ambiguous object type:
configuration file and use
of the PCB
[type].
only the documented
configuration file is
object type keywords.
ambiguous.
The indicated attribute in
Refer to the standard PCB
the BeginChkRules section
Ambiguous attribute name:
configuration file and use
of the PCB
[name].
only the documented
configuration file is
attributes.
ambiguous.
The indicated error severity
Refer to the standard PCB
in the BeginChkRules
Ambiguous severity:
configuration file and use
section of the PCB
[severity].
only the documented
configuration file is
error severity keywords.
ambiguous.
Unrecognized keyword:
The indicated keyword in Refer to the standard PCB
[keyword].
the BeginChkRules section configuration file and use
The GENVAL keyword
appears more than once in
the PCB configuration
file for the same attribute.

6022

6023

6024

6025

6026

6027

6028

6029

6030

6031

of the PCB
configuration file is
unrecognized.
The indicated object type in
the BeginChkRules section
Unrecognized object type:
of the PCB
[type].
configuration file is
unrecognized.
The indicated attribute in
the BeginChkRules section
Unrecognized attribute name:
of the PCB
[name].
configuration file is
ambiguous.
The indicated error severity
in the BeginChkRules
Unrecognized severity:
section of the PCB
[severity].
configuration file is
unrecognized.
The indicated line in the
BeginChkRules section of
Missing attribute name.
the PCB configuration
file is missing an attribute
name.
The indicated line in the
BeginChkRules section of
Missing routine name.
the PCB configuration
file is missing a routine
name.
The indicated line in the
BeginChkRules section of
Missing object type.
the PCB configuration
file is missing an object
type.
The indicated line in the
BeginChkRules section of
Missing severity.
the PCB configuration
file is missing an error
severity.
The indicated line in the
BeginChkRules section of
Missing fixcode.
the PCB configuration
file is missing a fixcode.
The indicated line in the
BeginChkRules section of
Missing number.
the PCB configuration
file is missing an integer
argument.
Bad fixcode: [fixcode].
The indicated line in the

only the documented


keywords.
Refer to the standard PCB
configuration file and use
only the documented
object type keywords.
Refer to the standard PCB
configuration file and use
only the documented
attributes.
Refer to the standard PCB
configuration file and use
only the documented
error severity keywords.

Provide the appropriate


attribute name.

Refer to the standard PCB


configuration file and
provide the appropriate
procedure name.
Refer to the standard PCB
configuration file and
provide the appropriate
object type keyword.
Refer to the standard PCB
configuration file and
provide the appropriate
error severity keyword.
Refer to the standard PCB
configuration file and
provide the appropriate
fixcode.
Refer to the standard PCB
configuration file and
provide the appropriate
number.
Refer to the standard PCB

6032

Bad number: [number].

6033

Incorrect number of
arguments.

6034

BeginChkRules section of
the PCB configuration
file has an illegal fixcode.
The indicated line in the
BeginChkRules section of
the PCB configuration
file has an illegal number.
The indicated line in the
BeginChkRules section of
the PCB configuration
file has an incorrect number
of arguments.

The attribute value


indicated in the following
Illegal character [character].
message contains the illegal
character shown.

Illegal length [length].

The attribute value


indicated in the following
message has illegal length.

Replacement character
conflict.

The replacement character


specified in a CHKVAL
PCB configuration file
line is itself an illegal
character.

6037

Min length, max length


conflict.

The minimum and


maximum lengths specified
in a CHKVAL PCB
configuration file line are in
conflict.

6038

Expansion error n for string


value.

The attribute value


indicated in the following

6035

6036

configuration file and use


only the documented
fixcodes.
Refer to the standard PCB
configuration file and use
an appropriate value.
Refer to the standard PCB
configuration file and
provide the appropriate
arguments.
Fix the attribute value,
enable automatic fixups,
add a GENVAL fixup, or
change the PCB
configuration file to allow
this character. PCB
Configuration File:
CHKVAL
_NAME_CHK,
CHKVAL _LIST_CHK,
GENVAL.
Fix the attribute value,
enable automatic fixups,
add a GENVAL fixup, or
change the PCB
configuration file to allow
this length. PCB
Configuration
File: CHKVAL
_NAME_CHK,
CHKVAL _LIST_CHK,
GENVAL.
Specify a different
replacement character.
PCB Configuration File:
CHKVAL
_NAME_CHK,
CHKVAL _LIST_CHK.
Specify lengths which do
not conflict. PCB
Configuration File:
CHKVAL
_NAME_CHK,
CHKVAL _LIST_CHK,
CHKVAL _REG_EXP.
Fix the attribute value or
change the PCB

message cannot be
expanded
properly as a list.

6039

Illegal value [value].

The attribute value


indicated in the following
message is illegal.

6040

Missing character
[character].

The attribute value


indicated in the following
message is missing the
specified character.

6041

6043

6044

6045

configuration file. PCB


Configuration File:
CHKVAL _LIST_CHK.
Fix the attribute value,
add a GENVAL fixup, or
change the PCB
configuration file to allow
this value. PCB
Configuration File:
CHKVAL
_ENUM_CHK,
GENVAL.
Fix the attribute value,
enable automatic fixups,
add a GENVAL fixup, or
change the PCB
configuration file. PCB
Configuration File:
CHKVAL
_FND_CHAR,
GENVAL.

The SIGNAL attribute


Fix the attribute value.
value indicated in the
Bad signal value [value].
PCB Configuration File:
message which follows has
CHKVAL _SIG_CHK.
improper syntax.
Fix the attribute(s), enable
[second attribute]
automatic fixups, or
Always used following 6066,
change the PCB
Designer Schematic
where 6066 specifies the first
configuration file. PCB
attributes for the same
attribute in a conflict and
Configuration File:
package or package pin are
6043 specifies the second
CHKBRD_COMM_PIN3
in conflict.
attribute in the
,
conflict.
CHKBRD_REF_CONFL,
CHKBRD_VDVP_ATT.
[no attribute]
Fix the attribute(s), enable
Always used following 6066,
automatic fixups, or
where 6066 specifies the first
change the PCB
attribute in a conflict and
Designer Schematic
configuration file. PCB
6044 specifies the second
attributes for the same
Configuration File:
attribute in the
package or package pin are
CHKBRD_COMM_PIN3
conflict. In this case, the
in conflict.
,
conflict arises because the
CHKBRD_REF_CONFL,
second attribute is
CHKBRD_VDVP_ATT.
missing.
Automatic fixup is
Ignore the message or
repackaging the
change the PCB
Repacking (attribute
indicated Designer
configuration file. PCB
conflict).
Schematic component
Configuration
because of attribute
File: CHKBRD

6046

6047

6048

6049

6050

6051

conflicts with another


component or common pin
in the same package.
Automatic fixup is
repackaging the
indicated Designer
Schematic component
Repacking (device conflict).
because the DEVICE
specified conflicts with that
of another component in
the same package.
Automatic fixup is
repackaging the
indicated Designer
Repacking (pin # not on
Schematic component
symbol).
because the pin numbers do
not correspond to any valid
slot.
Automatic fixup is
repackaging the
indicated Designer
Repacking (pins from
Schematic component
different slots).
because pin numbers from
more than one slot have
been mixed together on
the same gate.
Automatic fixup is
repackaging the
indicated Designer
Repacking (duplicate slot). Schematic component
because another gate is
already packaged in the
same slot.
Automatic fixup is
repackaging the
indicated Designer
Schematic component
because the net connection
Repacking (net conflict).
on a common pin is
different from the
connection
for the same pin on a
different gate in the same
package.
Duplicate pin numbers exist
for different pins of the
Duplicate pin number.
same gate, based on #,
SIGNAL, and NC
attributes.

_REF_CONFL,
CHKBRD
_COMM_PIN3.

Ignore the message. PCB


Configuration File:
CHKBRD
_DEV_CONFL.

Ignore the message. PCB


Configuration File:
CHKBRD
_BAD_PIN_NUM.

Ignore the message. PCB


Configuration File:
CHKBRD
_MIXED_SLOT.

Ignore the message or


change the PCB
configuration. PCB
Configuration
File: CHKBRD
_DUPL_SLOT.
Ignore the message or
change the PCB
configuration file. PCB
Configuration
File: CHKBRD
_COMM_PIN1,
CHKBRD
_COMM_PIN2,
CHKBRD
_COMM_PIN4.
Fix the pin number(s), or
ignore the message if it is
an intentional default
SIGNAL override. PCB
Configuration File:

6052

Duplicate name: [name].

6053

Duplicate attribute.

6054

Duplicate slot - n.

6055

Bad name: [name].

6056

Bad attribute name.

CHKBRD _DUPL_PIN.
Remove the duplicate or
change the PCB
configuration file. PCB
Configuration File:
CHKBRD
A duplicate net name, gate
_DUPL_FNAME1,
name, or reference
CHKBRD
designator exists.
_DUPL_FNAME2,
CHKBRD
_DUPL_NNAME,
CHKBRD
_DUPL_RNAME.
Try one of the following:
Remove the duplicate or
change the PCB
configuration file. PCB
Configuration
File: CHKBRD
Duplicate attributes exist.
_DUPL_ATTR,
ALLOW_DUPL.
Check Project from
within DxDesigner, then
try running ViewPCB
again.
Repackage the gate(s),
enable automatic fixups,
More than one Designer
or ignore the message if
Schematic component has duplicate slots are
been packaged in the same allowed. PCB
slot of the same package.
Configuration File:
CHKBRD
_DUPL_SLOT.
Fix the name, enable
automatic fixups, add a
The indicated name is
GENVAL fixup, or
illegal for the reason
change the
specified in the preceding PCB configuration file to
message.
allow this name. PCB
Configuration File:
CHKVAL, GENVAL.
Fix the attribute name,
enable automatic fixups,
The indicated attribute
add a GENVAL fixup, or
name is illegal for the
change the PCB
reason specified in the
configuration file to allow
preceding message.
this attribute name. PCB
Configuration File:
CHKVAL, GENVAL.

The indicated attribute


value is illegal for the
reason specified in the
preceding message.

6057

Bad attribute value.

6058

Automatic fixup is updating


Designer Schematic attribute a ViewPlace attribute to be
overriding.
consistent with
Designer Schematic.

6059

[ViewPlace attribute]
Always used following 6066,
where 6066 specifies the
DxDesigner attributes for
Designer Schematic attribute the same package or
in a conflict and 6059
package pin are in conflict.
specifies the ViewPlace
attribute in the conflict.

6060

Automatic fixup is updating


Changing name old name to
an illegal name to a new
new name.
legal name.

6061

Changing attribute name to


new name.

Automatic fixup is updating


an illegal attribute name to
a new legal name.

6062

Changing attribute value to


new value.

Automatic fixup is updating


an illegal attribute value to
a new legal value.

6063

Changing shape to shape.

6064

Changing device to device.

Automatic fixup is updating


a ViewPlace package shape
to be consistent
with the Designer
Schematic PKG_TYPE for
the same package.
Automatic fixup is updating
a ViewPlace package

Fix the attribute value,


enable automatic fixups,
add a GENVAL fixup, or
change the PCB
configuration file to allow
this attribute value. PCB
Configuration File:
CHKVAL, GENVAL.
Ignore the message or
change the PCB
configuration file. PCB
Configuration
File: CHKBRD
_VDVP_ATT.
Fix the attribute(s), enable
automatic fixups, or
change the PCB
configuration file. PCB
Configuration File:
CHKBRD_COMM_PIN3
,
CHKBRD_REF_CONFL,
CHKBRD_VDVP_ATT.
Ignore the message or
change the PCB
configuration file. PCB
Configuration
File: CHKVAL,
GENVAL.
Ignore the message or
change the PCB
configuration file. PCB
Configuration
File: CHKVAL,
GENVAL.
Ignore the message or
change the PCB
configuration file. PCB
Configuration
File: CHKVAL,
GENVAL.
Ignore the message or
change the PCB
configuration file. PCB
Configuration
File: CHKBRD
_VDVP_SHP.
Ignore the message or
change the PCB

device name to be
consistent with the
DxDesigner device name
for the same package.

6065

Changing ViewPlace net to


net.

Automatic fixup is updating


a ViewPlace net connection
to be consistent
with the same connection in
Designer Schematic.

6066

Attribute conflicts with


[attribute].

Designer
Schematic attributes for the
same package or package
pin are in conflict.

6067

The indicated Designer


Schematic components
Refdes [refdes], device
have conflicting DEVICE
[device] conflicts with device
attributes
[device].
specified for the same
reference designator.

6069

6070

Net [net] conflicts with Net


[net].

The indicated Designer


Schematic pin-net
connection conflicts with
the pin-net
connection indicated in the
following message for the
same pin of the same
package.

test pin $1I4.GND27: Net


DGND-RED.

When you have a part with


a high pin count (typically,
a component of a
hetero device), you can get
two or more pins with the
same pin number.

configuration file. PCB


Configuration
File: CHKBRD
_VDVP_ATT.
Ignore the message or
change the PCB
configuration file. PCB
Configuration
File: CHKBRD
_VDVP_NET.
Fix the attribute(s), enable
automatic fixups, or
change the PCB
configuration file.
PCB Configuration File:
CHKBRD
_COMM_PIN3,
CHKBRD
_REF_CONFL,
CHKBRD _VDVP_ATT.
Fix the DEVICE
attribute(s), repackage the
gate(s), or enable
automatic
fixups. PCB
Configuration File:
CHKBRD
_DEV_CONFL.
Fix the connection(s),
repackage the gate(s),
enable automatic fixups,
or
change the PCB
configuration file. PCB
Configuration File:
CHKBRD
_COMM_PIN1,
CHKBRD
_COMM_PIN2,
CHKBRD
_COMM_PIN4,
CHKBRD _VDVP_NET.
Check the pin numbers on
each component of the
hetero device. Note that
the pcbnetlister doesn't
check for duplicate pin
numbers on different
components, even if the

hetero attribute exists. It


only checks pin numbers
on
a component.

6071

ViewPlace shape conflict.

The indicated ViewPlace


package has a shape which
conflicts with the Designer
Schematic PKG_TYPE for
the same package.
The indicated ViewPlace
package has a device which
conflicts with the Designer
Schematic device name for
the same package.
The indicated ViewPlace
pin-net connection does not
exist on the schematic.

6072

ViewPlace device conflict.

6073

ViewPlace net [net] not


connected in Designer
Schematic.

6074

Attribute added.

Automatic fixup is adding a


required attribute.

6075

ViewPlace package added.

Automatic fixup is adding a


new ViewPlace package to
correspond to a
package or reference
designator addition in
Designer Schematic.

6076

Missing [name] attribute.

The indicated required


attribute is missing.

6077

Missing shape pin.

The indicated package pin


is defined on the Designer
Schematic symbol for this
package, but
another Designer Schematic
symbol with the same
PKG_TYPE is
missing the same pin.

6078

There is no package in
Missing ViewPlace package
ViewPlace which
[REFDES].
corresponds to the indicated

Enable automatic fixups.


PCB Configuration File:
CHKBRD _VDVP_SHP.
Enable automatic fixups.
PCB Configuration File:
CHKB85RD
_VDVP_ATT.
Enable automatic fixups.
PCB Configuration File:
CHKBRD _VDVP_NET.
Ignore the message or
change the PCB
configuration file. PCB
Configuration
File: REQUIRE,
CHKBRD
_ILL_PINSWAP.
Ignore the message or
change the PCB
configuration file. PCB
Configuration
File: CHKBRD
_VDVP_PKG.
Add the attribute, enable
automatic fixups, or
change the PCB
configuration
file. PCB Configuration
File: REQUIRE.
Examine the symbols
with the same
PKG_TYPE, add the
missing pin to the
symbol(s), or ignore or
disable the message. PCB
Configuration File:
CHKBRD
_MISSING_PIN.
Enable automatic fixups.
PCB Configuration File:
CHKBRD _VDVP_PKG.

assigned Designer
Schematic reference
designator.

6079

Hetero device attribute


conflict.

6080

ViewPlace net deleted.

6081

Extra ViewPlace package.

6082

Extra shape pin [pin].

6083

Single pin net: [net].

6084

Bus pin on symbol.

Check the attributes on all


sections of the hetero
Hetero device attribute
device and correct them
conflict.
as
necessary.
Ignore the message or
Automatic fixup is deleting
change the PCB
the indicated net in
configuration file. PCB
ViewPlace because it no
Configuration
longer exists in Designer
File: CHKBRD
Schematic.
_VDVP_NET.
The indicated ViewPlace
package does not
Enable automatic fixups.
correspond to any assigned PCB Configuration File:
Designer Schematic
CHKBRD _VDVP_PKG.
reference designator.
The indicated package pin
is not defined on
Add the missing pin to
the Designer Schematic
the symbol, or ignore or
symbol for this
disable the
package, but
message. PCB
another Designer Schematic Configuration File:
symbol with the same
CHKBRD
PKG_TYPE defines
_EXTRA_PIN.
this pin.
Connect the net properly,
enable automatic fixups,
or ignore or disable the
message. PCB
Configuration File:
CHKBRD
The net on the indicated pin _SGL_PIN_NET.
is not connected to any
Also, if this message is
other pins and so cannot
the result of using the NC
be routed by a layout
attribute to identify nosystem without additional connect
connection information.
pins, this message may be
averted by specifying
NET NC in the General
portion
of the AttPassList section
of the PCB configuration
file.
A bus pin on a Designer
Put BusExpansion Yes in
Schematic symbol is not
the PCB configuration
being expanded into
file. This is the default

separate pins
before netlisting.

6085

n empty slot(s), device


[device].

6086

Not packaged.

6087

Pins have conflicting


numbers of slots.

6088

Component pin # not on


symbol.

6089

Pins from different slots on


one component.

6090

Illegal pinswap.

The indicated package of


the specified device type
has the number of unused
slots shown.

and
should not ordinarily be
changed. PCB
Configuration File:
CHKBRD
_BUS_PIN.
Ignore the message, fill
the empty slots, or use the
PCB configuration file
CreateSpareGates option
to create the spare gates
on a new top-level
schematic sheet and to
make default input
connections. PCB
Configuration
File: CHKBRD
_UNUSED_SLOT.

The indicated Designer


Schematic component could
Resolve the reported
not be packaged because of
errors.
errors reported in previous
messages.
Some of the pins on the
Fix the pin number
indicated Designer
attributes. PCB
Schematic symbol have
Configuration File:
missing or extra
CHKBRD
pin numbers defined for
_BAD_SLOTCNT.
some slots.
The pin number on the
Fix the pin number or
indicated Designer
enable the automatic
Schematic component pin
fixup. PCB Configuration
does not match
File:
any pin number defined on
CHKBRD
the Designer Schematic
_BAD_PIN_NUM.
symbol.
The pin numbers on the
Fix the pin numbers or
indicated Designer
enable the automatic
Schematic component have fixup. PCB Configuration
been mixed
File:
together from more than
CHKBRD
one gate.
_MIXED_SLOT.
Pins on the
Ignore or disable the
indicated Designer
message, verify or fix the
Schematic component have pin numbers, or enable
been swapped and there is the
no PINSWAP attribute that automatic fixup. PCB
indicates that this swap was Configuration File:
legal.
CHKBRD

6091

6092

6093

6094

_ILL_PINSWAP.
Verify that the HETERO
attribute on the
component is correct, and
The indicated Designer
if
Schematic component is
necessary instantiate a
part of a heterogeneous
spare gate for
Symbol [symbol] missing for device
any Designer Schematic
hetero device [device].
which includes
symbol listed which
another Designer Schematic
does not appear elsewhere
symbol which cannot be
in the schematic. PCB
found.
Configuration File:
CHKBRD
_BAD_HETERO.
Fix any incorrect
DEVICE attributes or
remove the library alias.
The indicated Designer
If this is
Schematic component(s)
really a heterogeneous
have different symbols but device, add or correct the
the
HETERO attribute on the
Bad hetero device [device],
same DEVICE attribute,
symbol(s) or
symbol [symbol].
and the HETERO attribute component(s) and include
has not been properly
the names of all the
specified; or the device
symbols which make up
library is aliased.
the device. PCB
Configuration File:
CHKBRD
_BAD_HETERO.
You added or removed a
HETERO attribute after you
Remove the HETERO
packaged the design.
attribute and run pcbfwd
The PCB interface cannot
again to repackage the
change the component level
design.
attribute once the
design has been packaged.
Ignore or disable the
The indicated Designer
message, or fix any
Schematic component pin is schematic problem
Pin shorted.
directly tied to another pin indicated. PCB
on
Configuration File:
the same gate.
CHKBRD
_PIN_SHORTED.
Ignore or disable the
message, connect the pin
The indicated Designer
properly, or use an NC
Pin not connected.
Schematic component pin is
attribute to indicate a pin
not connected to anything.
which is intentionally left
unconnected. PCB

6097

6098

6099

6100

Line too long.

The indicated line in the


PowerPCB ASC or ECO
file is too long.

The expected keyword


shown is missing at the
Missing keyword [keyword]. indicated line of the
PowerPCB ASC or ECO
file.
The keyword at the
indicated line of the
Ambiguous keyword
PowerPCB DS ASC or
[keyword].
ECO file is
ambiguous.
The unexpected keyword
shown is present at the
Unexpected keyword
indicated line of the
[keyword].
PowerPCB ASC or ECO
file.

6101

[refdes.pin] is already
connected to net [net].

6102

[refdes.pin] was not


connected to net [net].

Configuration File:
CHKBRD
_UNCON_PIN.
Verify that the file has the
correct format and was
properly generated from
PowerPCB.
Verify that the file has the
correct format and was
properly generated from
PowerPCB.
Verify that the file has the
correct format and was
properly generated from
PowerPCB.
Verify that the file has the
correct format and was
properly generated from
PowerPCB.

Fix the ECO file or


remove this ECO record,
update the schematic with
the
An ECO record at the
remaining ECOs, and
indicated line of the
generate a new ECO file
PowerPCB ECO file
by comparing a new
attempts to
forward
connect a pin to a net, but interface ASC output file
the pin already has a
with the existing
different net attached. The PowerPCB ASC database
ECO file may be old,
file
incorrect, or incomplete.
using the PowerPCB
ECOGEN program or the
POWERPCB Check
ASCII
function.
Fix the ECO file, or
An ECO record at the
update the schematic with
indicated line of the
the ECO file, then
PowerPCB ECO file
generate a
attempts to
new ECO file by
disconnect a pin from a net,
comparing a new forward
but the pin already is
interface ASC output file
disconnected. The ECO
with
file may be old, incorrect,
the existing PowerPCB
or incomplete.
ASC database file using

6103

Net [net] already exists.

6104

Package refdes already


exists.

6105

Incomplete data.

6106

Net [net] not found.

the PowerPCB ECOGEN


program or the
PowerPCB Check ASCII
function.
Fix the ECO file or
remove this ECO record,
update the schematic with
the
An ECO record at the
remaining ECOs, and
indicated line of the
generate a new ECO file
PowerPCB ECO file
by comparing a new
attempts to
forward
rename a net, but another
interface ASC output file
net already has the same
with the existing
name. The ECO file may
PowerPCB ASC database
be old, incorrect, or
file
incomplete.
using the PowerPCB
ECOGEN program or the
PowerPCB Check ASCII
function.
Fix the ECO file or
remove this ECO record,
update the schematic with
An ECO record at the
the
indicated line of the
remaining ECOs, and
PowerPCB ECO file
generate a new ECO file
attempts to
by comparing a new
rename a package, but
forward
another package already has interface ASC output file
the same reference
with the existing
designator. The ECO file
PowerPCB ASC database
may be old, incorrect, or
file
incomplete.
using the PowerPCB
ECOGEN program or the
PowerPCB Check ASCII
function.
The indicated line in the
Verify that the file has the
PowerPCB ASC or ECO
correct format and was
file does not have the
properly generated from
expected number of
PowerPCB.
arguments.
Verify that the file has the
The net referred to on the correct format and was
indicated line of the ECO properly generated from
file does not exist in the
layout. Fix the file or
schematic. The file may be remove the ECO record,
old, incorrect, or
update the schematic with
incomplete.
the
remaining ECOs, and

6107

6108

6109

Package [refdes] not found.

The package referred to on


the indicated line of the
database or ECO file
does not exist in the
schematic. The file may be
old, incorrect, or
incomplete.

Pin [refdes, pin] not found.

The package pin referred to


on the indicated line of the
PowerPCB ECO file
does not exist in the
schematic. The file may be
old, incorrect, or
incomplete.

Slot [refdes.slot] not found.

The package and/or slot


referred to on the indicated
line of the PowerPCB
ECO file does not exist in
the PowerPCB ASC file or
does not correspond to

generate a new ECO file


by comparing a new
forward
interface output file with
the existing database file
(such as with the
PowerPCB ECOGEN
command or the
PowerPCB Check ASCII
function).
Verify that the file has the
correct format and was
properly generated from
layout. Fix the file or
remove the ECO record,
update the schematic with
the
remaining ECOs, and
generate a new ECO file
by comparing a new
forward
interface output file with
the existing database file
(such as with the
PowerPCB ECOGEN
command or the
PowerPCB Check ASCII
function).
Fix the file or remove the
ECO record, update the
schematic with the
remaining ECOs, and
generate a new ECO file
by comparing a new
forward
interface ASC output file
with the existing
PowerPCB ASC database
file
using the PowerPCB
ECOGEN program or the
PowerPCB Check ASCII
function.
Verify that the files have
the correct formats and
were properly generated
from POWERPCB. Fix
the files or remove the
ECO record, update the

a slot defined on the


corresponding symbol.

6110

6112

6113

6116

schematic with the


remaining ECOs, and
generate a new ECO file
by
comparing a new forward
interface ASC output file
with the existing
PowerPCB ASC database
file using the PowerPCB
ECOGEN program or the
PowerPCB Check ASCII
function.
Verify that the directory
Could not write file
The indicated file could not
exists and that the correct
[filename].
be written.
access modes are set.
Verify that the
appropriate symbol is in
An ECO record at the
an accessible Designer
indicated line of the
Schematic library
PowerPCB ECO file
directory and/or provide a
Could not create new
attempts to
mapping for this device or
[device] package [refdes].
create a new package, but reference designator to
the appropriate symbol
the appropriate symbol in
cannot be
the
determined or loaded.
BeginNewSymRules
section of the PCB
configuration file.
An attempt was made to
generate device descriptions
for PowerPCB in the
form of a PowerPCB ASCII Reduce the number of
PARTTYPE library file, but PKG_TYPEs for this
the indicated
device, do not generate
device has too many
PARTTYPEs, or use the
Device [device] has [n]
associated PKG_TYPE
REQUIRE PCB
shapes.
attributes in DxDesigner for configuration file
the
keyword to
PowerPCB software to
locate any missing
handle it, or there is no
PKG_TYPE attributes.
associated PKG_TYPE for
this device in Designer
Schematic.
Automatic fixup is treating
Connect the net properly
the indicated pin as
or ignore or disable the
unconnected, because its
message. PCB
Ignoring single pin net:[net]. net
Configuration File:
did not connect to any other
CHKBRD
pins. The net will not
_SGL_PIN_NET.
appear in the netlist file.

6117

6118

6119

6120

6130

6138

6265

6284

6521

6523

6525

Fix the attribute syntax.


PCB Configuration File:
Bad pinswap definition.
CHKBRD_BAD_PINSW
AP.
Fix the attribute syntax.
The indicated PINSWAP
PCB Configuration File:
Unmatched parenthesis.
attribute has an unmatched
CHKBRD
parenthesis.
_BAD_PINSWAP.
Fix the attribute syntax.
The indicated PINSWAP
PCB Configuration File:
Mismatched parentheses.
attribute has mismatched
CHKBRD_BAD_PINSW
parentheses.
AP.
The indicated pin name in Fix the PINSWAP
the PINSWAP attribute is attribute. PCB
Bad pin name:[pin].
invalid because no
Configuration File:
symbol pin exists with that CHKBRD_BAD_PINSW
name.
AP.
A pin number is duplicated
Duplicate pin number [#] in between two or more
Remove duplicate pins
hetero 3 device.
symbols of a hetero type 3 from symbol(s).
device.
This error occurs whenever Make sure that
Multiple Symbols
there are multiple
inconsistent symbols with
<symname>device<devicena instantiations of
the same device name
me> are inconsistent.
inconsistent symbols with have
the same device name.
matching pins.
File <design>.baf, line 6037:
Skipping record for F176
during change
N/A.
N/A.
processing bad Iwr
processing.
Design attribute PKG_TYPE
being changed from <type1>
N/A.
N/A.
to <type2>
double check.
A parsing error occurred
Check these files for
Parse error.
while reading either the
possible errors.
comps, inst or net files.
Check the back
annotation file to ensure
Could not rename refdes of A component rename could
that it has the correct
gate %s to %s, IwrStat = %d. not be done.
rename
information.
This is a HETERO Type 2 Using the error message,
Could not update internal
problem. In the function
identify the function in
data for a pin DGND, net
dictionary, sometimes
question and determine if
GND1.
there are multiple instances multiple instances exist
of the same function
for the function. If so, try
The indicated PINSWAP
attribute has improper
syntax.

representing the different


components of the hetero
device and the order in
which the instances appear
may be different, which
could affect the back
annotation. The PCB
netlister
may not be able to correctly
define which instance it
should be looking at.

6530

6531

6532

6577

6631
6632

Case sensitivity in pin


numbersthe gates file
from pcbfwd has the
alphanumeric pin numbers
in upper case, but the gates
file from Board
Station has the
alphanumeric pin numbers
Could not update component in lower case. The Board
<#>.
Station
library geometry file needs
to have the pin
numbers/names in upper
case
because the Board Station
output gates file is derived
from that Board Station
library geometry file.
Could not find refdes
A specified package could
[refdes#] in schematic
not be found in the
database.
schematic.
A specified component
Could not find component
could not be found in the
%s in schematic database.
schematic.
Assuming the signal is
specified as a SIGNAL on a
Signal pin on device not
component. It is not
specified in POWERS or
specified as a Power or
GROUNDS.
Ground in the pcb
configuration file.
Writing partslist file
The partslist output file is
[filename].
being written.
Attribute [attribute_name]
More than one value is

rearranging the instance


numbers of the instances
in the function dictionary
so the netlister looks at
the correct one when back
annotating information
from the PCB layout. As
an example, a function
dictionary contains these
two entries:
$8I133 F81
$8I120 F81
Rearrange the entries to
look like the following:
$8I120 F81
$8I133 F81

Change the Board Station


geometry or gates file to
include upper case
alphanumeric pin
numbers.

Check schematic to
ensure specified package
exists.
Check schematic to
ensure specified
component exists.
Specify the signal as a
power or ground in the
pcb configuration file.
None, for informational
purposes only.
This may or may not

has conflicting values on


same PKG [pkg_name].

6633

6634

assigned to a single
attribute within one
package.

There is more than one


value assigned to
MULTIPLE_KEY for a
single
package.
The date, design name, or
Pagination ignored, exceeds
page number stamp exceeds
allowable line width.
allowable line width.
More than one
MULTIPLE_KEY [value]
chosen for same pkg
[pkg_name].

6635

No REV# Attributes found


on BOARD.

6636

No BAN# Attributes found


on BOARD.

6637

Internal Error: List - Table


out of sync.

6638

Header line count exceeded


3-lines. Ignored field label :
[field_label].

6639

Internal Warning:

require attention. If the


MULTIPLE or
ITEMIZER
keyword lists several
possible values for an
attribute, such as package
manufacturer, ignore this
message. If more than one
value for the attribute is
to be disregarded, remove
all values but the one you
want from the package.
Remove or comment out
all but one
MULTIPLE_KEY value.
Increase the width for the
last field.

Two methods exist to fix


this problem:
The REVISION_ON
Attach one or more
keyword is set to yes, and
REV# attributes to the
there are no REV#
board.
attributes
Change the
found on the board.
REVISION_ON keyword
setting to no.
Two methods exist to fix
this problem:
The BANNER_ON
Attach one or more
keyword is set to yes, and
BAN# attributes to the
there are no BAN#
board.
attributes
Change the
found on the board.
BANNER_ON keyword
setting to no.
This internal error should
not occur with the end
user. However, if it does,
An internal malfunction has record your actions prior
occurred.
to the error and contact
Mentor Graphics
Technical
Support.
The maximum line count
For more than three lines
for a standard header is
in a header, use
three, and this has been
ALT_HEADER.
exceeded.
An internal malfunction has This internal error should

UNKNOWN special data


field.

6640

6641

6642

6643

6644

6645

6646

6647

6802

6803

occurred.

The number of characters in


Value [string] truncated to fit the value string exceeds the
the data field defined.
allowable field
width.
The number of digits in the
SUM [number] truncated to
summed value exceeds the
fit the data field defined.
allowable field width.
Unbalanced double quotes in A specified field label is
.ini file for field:
missing a double quote
[field_label].
character.

not occur with the end


user. If it does, however,
record your actions prior
to the error and contact
Mentor Graphics
Technical
Support.
Increase the field width
for the specified value.
Increase the field width
for SUM.

Add a double quote


character where one is
missing.
Check for correct syntax
The .ini file specifies a field
in the field definitions,
definition mode other than
Bad FIELD_DEF type
and make sure the
SINGULAR,
[value] Changed to
keywords
ITEMIZER, or
SINGULAR.
are nothing other than
MULTIPLE, or the syntax
SINGULAR, ITEMIZER,
is incorrect.
or MULTIPLE.
The last column label
Label exceeds allowable line extends beyond the
Use ALT_HEADER, or
width. Ignored field label :
allowable line width in a
modify label string or
[field_label].
standard
field width.
header.
Adjusted ITEM/QTY value ITEM/QTY value exceeds
Increase the field width.
[value] to allowable width. the allowable field width.
The partlist.ini file is
The Standard and Field
No Standard or Field
missing the Standard
definitions are required to
definition found in the .ini
definition or Field
properly generate a parts
file.
definition
list. Add these definitions
sections.
sections appropriately.
Verify that the specified
file exists in the
The specified file cannot be
Unable to open file_name for
appropriate location under
found or does not have
writing.
the
appropriate permissions.
correct name and with
appropriate permissions.
Ensure this file is present
The pkgid.xrf file is missing
File %s not found.
in the project area and
from the project area.
rerun ViewPCB.
The specified line read from
Line %d in file %s has wrong
Review the specified line
the pkgid.xrf file has an
number of arguments.
for formatting errors.
incorrect format.

6805

6822

7100

7108

7127

7128

7129

7131

An illegal value has been


specified for the
PCAD_SECTNUM
attribute.
Two nets slated for
Could not swap net %s with
renaming could not be
%s. Manually fix!
located on the schematic.
You have drawn the entire
package on the schematic,
Unable to graphically
rather than drawing
represent the gate swap
each of the individual gates.
between package [package1]
The pcbfwd command
and package [package2].
cannot gate swap unless
individual gates are drawn.
Illegal value for attribute
PCAD_SECTNUM on
symbol %s.

You have assigned a


Pinswap attribute requires at pinswap attribute in the
least two pins.
following form:
PINSWAP=[Pin#m].

Change the value of this


attribute to a legal value.
Manually locate and
change these net names.

Instantiate the smallest


possible representation of
the gates that make up the
package.
Correct the value of the
attribute to include at
least two pins. For
example:
PINSWAP=[Pin#m,Pin#n
].

This message appears


during back-annotation.The
units were changed in
The Schematic units are
The layout house must
layout. Therefore, the units
inconsistent with the ASCII
export an ASCII file with
contained in the backfile units.
matching units.
annotation file do not
match the units in the
schematic.
You can continue to use
the PCB configuration
file from any of these
You are attempting to run a
versions, if you update
pcbfwd or pcbbck
the netlist file header line.
command using a PCB
This is the first line in the
Unsupported Version.
configuration file for either
PCB configuration file. It
POWERPCB Perform,
should read either:
PADS2000 or PowerPCB
NetFileHeader !PADS1.
POWERV2.0
NetFileHeader !PADSPOWERV3.0
Add the attribute to the
You have placed an
AttPassList in the PCB
attribute that is not in the
Warning: Attribute on
configuration file, set
standard AttPassList into
[Object] is not in AttPassList.
ExcludeName 7129 in the
the
PowerPCB.CFG file, or
PCB configuration file.
ignore the warning.
An attempt was made to
Replace the space with an
Space not allowed in value
back-annotate an attribute underscore or other
field for attribute [attribute].
value that contains a
appropriate character or

space.

7139

7202

7206

7300

7307

7463

Error: device attribute has


conflicting values.

The attribute on a device


has different value in
Designer Schematic than in
the layout
systemthe symbol
attribute value does not
match the component value.

Warning: rpack_tst net VDD:


NC attribute attached to
N/A.
multi-pin net.
Placing a device attribute
on only one part, and not on
another part or all
parts of the device.
For example, if
HETERO=(TYPE3),(TYPE
3A) is used, and only
Hetero symbol missing from symbol
hetero package on device
TYPE3 is placed on a part,
<devicename>.
the following warning
message is displayed when
a
check is performed:
PCB: Error 7206: New pkg
U1: Hetero symbol missing
from hetero package on
device TYPE3.
A component is referenced
in back-annotation that does
Component [component] not
not exist on the
found in schematic
schematic. Likely cause is
<schematic>.
modification to the
schematic during layout.
This occurs when
performing a back
annotation from Expedition
when a
MATCH_GROUP attribute
is attached to a group of
Net Props Write Error.
nets that does not have
the
MATCH_TOLERANCE
attribute applied to them.
This is an
unsupported attribute.
CES database update failed. N/A.

remove the attribute from


the POWERPCB ECO
file.
Change the attribute value
to be the same
in Designer Schematic
and in the layout
system.

N/A.

Make sure to specify the


same attributes for all
symbols in the hetero
package.

Resolve the inconsistency


between Designer
Schematic and layout.

Do not use the


MATCH_GROUP
attributes.

N/A.

7456

Error loading %s interface.

7600

Symbol'%s' Attribute
'%s=%s' was ignored.

7601

Could not add attribute %s


on object %s.

7602

Pin '%s' is not defined in


PDB Part '%s'."

7603

7604
7605
7606

7607

7608

7609

7610

Conflicting versions of
ePD installations and
System level error. A dll for
WDIR directory location
the interface cannot be
can
loaded.
cause DLL file to be
misplaced.
A symbol attribute has been
Remove the attribute on
overridden by a PDB
the symbol.
attribute.
Problem occurred trying to
add an attribute; this
attribute will not be added Internal Error.
to
the object.
Match all the pin labels
A Designer Schematic
from a Designer
symbol pin label was not
Schematic symbol with
found in a PDB part
the pin labels
definition.
defined for a PDB part.

Inconsistencies found
No Connect pins differ
between Dx and PDB No
on Designer Schematic and
Connect definitions for Parts
PDB parts.
Number %s.
Invalid central library or no
Initializing PDB Partition.
partitions were found on a
PDB.
Initializing PDB Partition
No parts defined in PDB
Part Numbers.
Partition.
Symbol '%s' did not match
The Designer Schematic
the PDB part definition of
symbol did not match the
Part Number '%s'."
matching PDB part symbol.
No Pin Mapping definitions Error obtaining pin maps
found for Symbol '%s' in Part from the PDB. The PDB
Number '%s'."
may be defective.
The pinswap defined for
a Designer Schematic
Pin swap definition for
component did not match
device '%s' does not match
the
PDB.
pinswap definition for a
matching PDB part.
Using central library '%s' for Specifies the central library
packaging.
being used when packaging.
A Designer Schematic
Inconsistent Pin Definitions symbol pin label was not
between Designer Schematic found or did not match a
and PDB Symbol '%s'.
pin label in
a PDB part definition.

Resolve differences
between Designer
Schematic and PDB parts.
Information only. No
action required.
Information only. No
action required.
Resolve differences
between Designer
Schematic and PDB parts.
Fix the problem in the
PDB.

Resolve differences
between Designer
Schematic and PDB parts.
Information only. No
action required.
Resolve differences
between Designer
Schematic and PDB.

7611

7613

7614

7615

7616

Inconsistent pin type


Pin Type did not match on
definitions between
pin '%s' for Designer
the Designer Schematic
Schematic and PDB Symbol
symbol and the
'%s'.
equivalent PDB symbol.
Designer
Designer Schematic Pin
Schematic package pin
Number '%s' did not match
number did not match the
the PDB definition of Part
matching PDB part
'%s'.
definition.
Designer
Designer Schematic Pin
Schematic package pin
Name '%s' did not match the name did not match the
PDB definition of Part '%s'. matching PDB part
definition.
NC Pin '%s' PDB mapping is Designer Schematic NC
not defined for Part Number package pin is not defined
'%s'.
in the matching PDB part.
Signal Pin '%s' PDB mapping Designer Schematic Signal
is not defined for Part
package pin is not defined
Number '%s'.
in the matching PDB part

7617

Designer Schematic Package


Shape '%s' was not found in
the PDB definition of Part
Number '%s'.

7618

Inconsistencies found
between Designer Schematic
and PDB parts.

7619

Inconsistencies found
between Dx and PDB parts.

7620

Invalid Generic Symbol %s.

7621

Part %s was not found in


PDB.

7622

PDB Part %s contains invalid


symbol swap groups defined.

Resolve differences
between Designer
Schematic and PDB.

Resolve differences
between Designer
Schematic and PDB.

Resolve differences
between Designer
Schematic and PDB.

Resolve differences
between Designer
Schematic and PDB parts.
Resolve differences
between Designer
Schematic and PDB parts.
Change the Designer
Schematic PKG_TYPE
attribute value to match
Invalid Designer Schematic one of the cells
Package Shape. Package
defined in the PDB part,
type was not defined in the or Add a cell that matches
matching PDB part.
the definition of the
Designer Schematic
PKG_TYPE attribute
value.
Mismatching of Symbols, Resolve differences
pins, pinswaps, slot or
between Designer
package types.
Schematic and PDB parts.
Parts definitions
Resolve differences
in Designer Schematic and between Designer
PDB do not match.
Schematic and PDB parts.
Generic symbol defined
Add generic symbol
in Designer Schematic is
definition to PDB.
not defined in PDB.
Designer Schematic part not Add Designer Schematic
defined in PDB.
part to PDB.
A part in the PDB has
multiple symbol swap
Use only Designer
groups (multiple subgates). Schematic compatible
This is not supported in
parts.
Designer Schematic.