- Invoke System Generator.
- On Windows systems select .
- On Linux systems, type
sysgenat the command prompt.
- Navigate to the Lab3 folder:
You can view the directory contents in the MATLAB® Current Folder browser, or type
lsat the command line prompt.
- Open the Lab3 design using one of the following:
- At the MATLAB
command prompt, type
- Double-click Lab3.slx in the Current Folder browser.
The Lab3 design opens, as shown in the following figure.
- At the MATLAB command prompt, type
- From your Simulink project worksheet, select or click the Run simulation button to simulate the design.
- Double-click the System Generator token to open the Properties Editor.
- Select the Clocking tab.
- From the Perform analysis menu, select Post
Synthesis and from Analyzer type menu select Timing as shown in the following figure.
- In the System Generator token dialog box,
When you generate, the following occurs:
- System Generator generates the required files for the selected compilation target. For timing analysis System Generator invokes the Vivado® Design Suite in the background for the design project, and passes design timing constraints to the Vivado Design Suite.
- Depending on your selection for Perform Analysis (Post Synthesis or Post Implementation), the design runs in the Vivado Design Suite through synthesis or through implementation.
- After the Vivado tools run is completed, timing paths information is collected and saved in a specific file format from the Vivado timing database.
- System Generator processes the timing information and displays a Timing Analyzer table with timing paths information as shown in the following figure.
- In the timing analyzer table:
- Paths with lowest slack values display, with the worst Slack at the top and increasing slack below
- Paths with timing violations have a negative slack and display in red.
- Cross probe from the Timing Analyzer table to the Simulink model by clicking any path in the Timing Analyzer table, which highlights the corresponding System Generator blocks in the model. This allows you to troubleshoot timing violations by analyzing the path on which they occur.
- When you cross probe, you see the corresponding path as shown in the following figure.
- Blocks with timing violations are highlighted in red.
- Double-click the second path in the Timing Analyzer table and cross-probe,
the corresponding highlighted path in green which indicates no timing