Answers Database

Design Manager M1.5: Multi-pass place and route (MPPR) naming conventionhas changed (ex - p1_rev_2_3_4)


Record #4137

Product Family:  Software

Product Line:  M1 Graphical/General

Problem Title:
Design Manager M1.5: Multi-pass place and route (MPPR) naming
conventionhas changed (ex - p1_rev_2_3_4)



Problem Description:
Keywords: Design Manager, MPPR, M1.5, multi, revision, name

Urgency: Standard


After running MPPR in M1.4, revisions are created as follows:

p1_rev_2_2 (Routed, OK)
p1_rev_2_3 (Routed, OK)
...

Where p# refers to the number of times MPPR has been executed per version
Where the first digit is the overall effort level (-ol)
Where the second digit represents the placer cost table entry (-t)

In M1.5, this naming convention has changed slightly.


Solution 1:

After running MPPR in M1.5, revisions are created as follows:

p1_rev_2_2_2 (Routed, OK)
p1_rev_2_2_3 (Routed, OK)

Where p# refers to the number of times MPPR has been executed per version
Where the first digit is the placer effort level (-pl)
Where the second digit is the router effort level (-rl)
Where the third digit is the placer cost table entry (-t)

NOTE: By default, MPPR runs with the value specified by
the overall effort level (-ol), found under the Place and Route
tab of the Implementation Options.  However, if chosen, both placer and
router effort level can override this switch.

To specify the placer and router effort levels, an Implementation
Template must be created from within the Template Manager.

Ex: (p#_rev_4_5_#)

Program Name: par
Program Options: -pl 4 -rl 5

For information on how to use the Template Manager, please refer
to (Xilinx Solution 1227).  For further explanation of effort levels,
please refer to the online documentation (Development System Reference Guide, PA
R Options).



End of Record #4137