#Synplify pro batch mode update#

The operating frequency estimates are recorded for constrained and unconstrained cases after synthesis and after place and route. Run Xilinx ngdbuild, map, and par to create a routed netlist and post-route timing report.Īdditional scripting is added to the flow to evaluate the impact of Focus generated timing exceptions on maximum clock frequency. Default settings were used for logic synthesis, with the exception of the “auto-constrain frequency” option which was turned off.ģ.

Synthesize the RTL with Synplify_pro to create an EDIF file and an NCF constraint file containing the constraints translated to match the EDIF netlist and in Xilinx compatible format. Run Focus to generate timing exceptions.Ģ. Two cases were run for each design clock: the unconstrained case where there were no timing exceptions, and the constrained case where in addition to the clock, Focus generated timing exceptions were included. The Xilinx tool set of ngdbuild, map and par, read the EDIF netlist and constraint file from Synplify_pro, and create a routed design, final timing reports and a device programming file.įigure 1 shows the flow from RTL synthesis through place and route. Synplify_pro also prepares a translated constraint file to feed forward the same timing requirements to place and route. This set of constraints is used in initial logic synthesis and affects the resulting EDIF file generated for Xilinx place and route tools. Synplify_pro is a full-featured logic synthesis tool which reads constraints for false paths and multi-cycle paths as well as IO and clock constraints. Focus also provides the ability to verify the generated timing exceptions through assertions that can be checked as part of functional simulation. Focus generates false and multi-cycle paths in industry standard constraint formats. In about one quarter of these designs, the timing exceptions can make a one-speed grade improvement in FPGA performance after place and route.įishTail’s Focus is designed to identify the timing exceptions in the design, and requires data that is normally already available for your design synthesizable RTL, clock definitions and boundary constraints. We compare the design’s maximum clock frequency before and after place and route, with and without timing exceptions. In this paper we have studied the impact of timing exceptions on nine designs using Synplify_pro from Synplicity for logic synthesis, Xilinx tools for place and route, and Focus from FishTail to generate false and multi-cycle path timing exceptions. These timing exceptions have the ability to improve FPGA QoR by relaxing constraints on the timing paths of the design and potentially allow the FPGA to run faster. FishTail’s Focus tool can generate false path and multi-cycle path timing exceptions for the FPGA designer before the first synthesis run. Lattice recommends its customers obtain the latest version of the relevant information to establish that the information being relied upon is current and before ordering any products.FPGA designers are typically working with prototype designs without much synthesis history, so on the first pass of the design they will not have developed a set of false path and multi-cycle path constraints.

Lattice reserves the right to discontinue any product or service without notice and assumes no obligation to correct any errors contained herein or to advise any user of this document of any correction if such be made.

#Synplify pro batch mode update#

Lattice makes no commitment to update this documentation. Lattice may make changes to these materials, specifications, or information, or to the products described herein, at any time without notice. BECAUSE SOME JURISDICTIONS PROHIBIT THE EXCLUSION OR LIMITATION OF CERTAIN LIABILITY, SOME OF THE ABOVE LIMITATIONS MAY NOT APPLY TO YOU. IN NO EVENT WILL LATTICE OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER (WHETHER DIRECT, INDIRECT, SPECIAL, INCIDENTAL, OR CONSEQUENTIAL, INCLUDING, WITHOUT LIMITATION, DAMAGES FOR LOSS OF PROFITS, BUSINESS INTERRUPTION, OR LOSS OF INFORMATION) ARISING OUT OF THE USE OF OR INABILITY TO USE THE INFORMATION PROVIDED IN THIS DOCUMENT, EVEN IF LATTICE HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. WITHOUT ANY EXPRESS OR IMPLIED WARRANTY OF ANY KIND INCLUDING WARRANTIES OF ACCURACY, COMPLETENESS, MERCHANTABILITY, NONINFRINGEMENT OF INTELLECTUAL PROPERTY, OR FITNESS FOR ANY PARTICULAR PURPOSE.