Answers Database

M1.4: TIMESPEC paths originating from .NMC macros (physical macros) do not get written by Map to the .PCF file


Record #2892

Product Family:  Software

Product Line:  Merged Core

Problem Title:
M1.4:  TIMESPEC paths originating from .NMC macros (physical macros) do
not get written by Map to the .PCF file



Problem Description:
Keywords: 100684, nmc, macro, physical macro, hard macro, pcf

Urgency: standard

General Description:
In all versions of Map up to and including vM1.4, TIMESPEC paths originating fro
m .NMC macros (physical macros) do not get written by Map to the .PCF file.  As
a result,
TIMESPECs in a design that begin in a physical macro
do not get read by PAR.


Solution 1:

Edit a copy of the .pcf file generated by Map and manually add
the .NMC-originated TIMESPEC(s) to the .PCF file after the
"schematic end" line.  Then, when running PAR, specify the
name of the PCF file copy that you have edited as one of the
inputs to PAR:

   par inputdesign outputname pcfile

Use NCDREAD to determine the physical name of the block or net
referenced in the TIMESPEC (see the Chapter 1 of the
Development System Reference Guide for instructions on using
NCDREAD, and Chapter 8 of the same document for details on the
.PCF file format).

Reference #: 100684



End of Record #2892