![]() |
|
![]() |
|
Answers Database
EDIF2XNF 5.x: Error 3, port name not found on external library primitive for cell
Record #396
Product Family: Software edif2xnf -l $LCA/data/unified/edif4000 (XC4000 target, for example) or run Men2XNF8, which automatically infers the necessity for the -l option. Solution 2: A Mentor gen_lib part was inadvertently included in the schematic. EDIF2XNF is trying to match the ports on the gen_lib part with the ports from the Xilinx library, which are incompatible. The design must be modified so that all of its components come from the same library. You can check library usage with the "listref" command in Unix (a Mentor-supplied program) or with the Report -> Show References -> For Design selection in PLD_DMgr. Any references to the old library will show up, for example, as $LCA/lib4k (XC4000 design); while references to the Unified library will show up, for example, as $LCA/xc4000. Solution 3: You have mixed Unified and obsolete libraries. Men2XNF8, if it sees a single Unified Library component, assumes that the entire design was drawn with Unified Libraries. If there are any obsolete library parts in the design, EDIF2XNF (with the -l option) will try to crossmatch an obsolete library part with a Unified Library port description, the two of which will be incompatible. Even when running EDIF2XNF separately without the -l option, you will get a similar situation as in case #2, where the program tries to crossmatch a Unified library part with an obsolete library port description. The design must be modified so that all of its components come from the same library. You can check library usage with the "listref" command in Unix (a Mentor-supplied program) or with the Report -> Show References -> For Design selection in PLD_DMgr. Any references to the old library will show up, for example, as $LCA/lib4k (XC4000 design); while references to the Unified library will show up, for example, as $LCA/xc4000. End of Record #396 - Last Modified: 05/24/99 11:41 |
| For the latest news, design tips, and patch information on the Xilinx design environment, check out the Technical Tips! |