Answers Database
ngdbuild M1.5i: WARNING:basnu:159 - Attribute "LOC" on "tx1a_dup0" is on the wrong type of object.
Record #5399
Problem Title:
ngdbuild M1.5i: WARNING:basnu:159 - Attribute "LOC" on "tx1a_dup0" is on the wrong type of
object.
Problem Description:
Urgency: standard
Running ngdbuild in M1.5i, The following warning messages may come up:
WARNING:basnu:159 - Attribute "LOC" on "tx1a_dup0" is on the wrong type of
object. Please see the "Attributes, Constraints, and Carry Logic" section of
the Libraries Guide for more information on this attribute.
WARNING:basnu:159 - Attribute "LOC" on "tx1b_dup0" is on the wrong type of
object. Please see the "Attributes, Constraints, and Carry Logic" section of
the Libraries Guide for more information on this attribute.
WARNING:basnu:159 - Attribute "LOC" on "tx2a_dup0" is on the wrong type of
object. Please see the "Attributes, Constraints, and Carry Logic" section of
the Libraries Guide for more information on this attribute.
........
........
However, those netnames in the warning messages are nowhere to
be found in the ucf file. Ngdbuild gives wrong signal names in
its warning messages.
Solution 1:
This problem will be fixed in the future release of the software.
What happened here is that the ucf file contains incorrect
netnames in the LOC constraints. They are supposed to be the
names between the IBUFs, IPADs, and OBUFs, and OPADs. But ucf
file uses the wrong netnames. They are the nets that are in the lower level.
To correct this problem, make sure the correct netnames are
used in the ucf file.
End of Record #5399 - Last Modified: 08/24/99 09:06 |
