Answers Database
Design Manager M1.5: New version is created instead of new revision eventhough the input design netlist has not changed
Record #4131
Product Family: Software
Product Line: M1 Graphical/General
Problem Title:
Design Manager M1.5: New version is created instead of new revision
eventhough the input design netlist has not changed
Problem Description:
Keywords: version, revision, netlist, abort, translate
Urgency: Standard
General Description:
When implementing a design where the input netlist (XNF, EDN, etc..)
has not changed, the 'Implement' dialog box (Design->Implement) shows that a
new version is to be created ('New version name' field) instead of a new revisio
n.
The following steps may have been taken to produce this issue:
1)Selecting Design->Implement->Run to begin processing a design.
2)Once Flow Engine was invoked, Translate was manually aborted by selecting the
'abort' button.
3)After answering YES to abort, the Flow Engine was closed.
4)Back in the DM, selecting Design->Implement brought up the 'Implement" dialog.
Here you notice that the 'New version name' field designates a new VERSION to be
created as opposed to a new revision. However, the input netlist has not change
d at all.
Solution 1:
This behavior comes about as a result of other features changes that have been
made to the M1.5 release.
A simple workaround exists:
Select "Overwrite last revision" from the 'Implement' status dialog so that a ne
w version is not created.
End of Record #4131
For the latest news, design tips, and patch information on the Xilinx design environment, check out the Xilinx Expert Journals! |