Design Assessment Report¶
Early Analysis & Risk Prediction¶
The Design Assessment's primary goal is to make and report an assessment of the success/failure potential of Placement and Routing of an FPGA design, as well as the potential of meeting timing or not.
Its objectives are:
- Provide users with an early heads-up (post-synthesis and optimization) on the potential impediments to the placement or routing of the FPGA design. This will enable users to adjust the settings, the constraints, or even the RTL.
- Speed up debug and optimization time as well as save compute resources for FPGA designs, especially those that have low potential to successfully place or route.
- Give end-users actionable steps to mitigate the challenges. For instance,
- review stringent timing constraints,
- review the flow settings (synthesis, optimization, placement and routing), or
- adjust Floorplanning constraints to reduce congestion or unbalanced assignment of logic blocks to certain areas of the target device.
- Highlight the root causes of placement, routing or timing failures due to factors like
- high utilization of specific resources,
- high intrinsic congestion, artificial congestion due to user constraints, or
- other insights related to the FPGA design’s profile.
- In some cases, the proposed user actions recommend the use of particular recipes in the Plunify toolset.
How to use¶
- Synthesize, Place or Route the FPGA design. The Design Assessment Report provides insights at different stages of compilation.
- Firstly, analyse the design netlist by executing the following command in the InTime Tcl Console:
This may take a while.
plunify> results extract root
- Next, generate the assessment report by entering
A text report named "design_assessment_report.txt" will be generated in the project folder.
plunify> results assess_design
The report begins with an overview of the design / project, FPGA tool version and the compilation stage that is analysed;
1 2 3 4 5 6 7 8 9 10 11 12
13 14 15 16 17 18 19 20 21 22
The first table contains a quick synopsis of the potential of failure to give the reader an immediate "design score".
23 24 25 26 27 28 29
Subsequent sections present the details, and is usually in the format:
- Observations and summarized interpretation of the data; and finally,
- Suggested next steps
31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58
Using the Report¶
It is recommended that the reader checks each metric and its suggested action(s), to explore how to resolve the highlighted issues.