You use one of the XDC files (top_timing.xdc), in both synthesis and implementation, while you use the other file (top_physical.xdc) only during implementation.
At this point in your Tcl script, you read the XDC file using
the read_xdc command, which is used in both
synthesis and implementation.
- Add the following to your Tcl
script:
read_xdc ../Lab_3_4_sources/Constraints/top_timing.xdcThe design is now ready for synthesis.
In Non-Project Mode, unlike Project Mode, there are no design runs to launch. Additionally, there is no runs infrastructure managing the strategies used and the state of the design. You manually launch the various stages of synthesis and implementation.
- For synthesis, you use the synth_design command. Add the following to your
Tcl
script:
synth_design -top sys_integration_topBecause you created an in-memory project and set the target part, defining the target part is not needed here. However, you must provide the top-level module name with the
synth_designcommand.The various Verilog files read into the in-memory design in Step 1: Reading Design Source Files do not reference other files via an
`includestatement. If they did, you need to define the`includesearch directories with the-include_dirsoption.After synthesis, you must generate a design checkpoint to save the results. This approach allows you to restore the synthesized design at any time without the need to rerun synthesis.
- Add the following
write_checkpointcommand to your Tcl script:write_checkpoint -force post_synth.dcpUse the
-forceoption to overwrite the checkpoint file if it already exists.You can also generate any needed reports at this point, such as a post-synthesis timing summary report.
- Add the following line to your Tcl
script:
report_timing_summary -file timing_syn.rptThis command creates a comprehensive timing report for the design and writes the report to a file.