Bad Timing Delays after insterting IP Core generated from Simulink
2 Ansichten (letzte 30 Tage)
Ältere Kommentare anzeigen
Hello, I've got a vivado project with added simulink-generated IP Core.
I'm always getting huge timing delays on the implimentation stage.
For test purposes, I've made a very simple simulink project with multipliers.
![](https://www.mathworks.com/matlabcentral/answers/uploaded_files/415188/image.png)
I'm exporting it with the following settings:
![](https://www.mathworks.com/matlabcentral/answers/uploaded_files/415193/image.png)
Adding it to the following block design:
![](https://www.mathworks.com/matlabcentral/answers/uploaded_files/415198/image.png)
Connecting clock enable to constant 1, reset to inverted reset, used in previous blocks (because the simulink generated IP Core uses inverted reset).
I'm getting the following result:
![](https://www.mathworks.com/matlabcentral/answers/uploaded_files/415203/image.png)
I've tried both generating HDL code and packaging it into IP Core by Vivado and generating IP Core directly from Simulink. The results are the same.
There are no timing errors If I don't use simulink generated IP core (or HDL code).
Is there some settings I've applied wrong?
0 Kommentare
Antworten (2)
Wang Chen
am 16 Nov. 2020
Bearbeitet: Wang Chen
am 16 Nov. 2020
Hi Alex,
It looks like your model does potentially has a long critical path, as I don't see any pipeline delays on the data path.
Did you try to add pipelining registers?
Also, It looks like your data path is running on a slower rate(I saw the data path is in green rate, instead of red rate). An alternative option when your critical path is in slower rate is to use the “Enable-based multi-cycle path constraint” feature. This feature is by-default off.
You can refer following video to use multi-cycle path constraint feature:
Or following document:
Please also remember to apply the constraint to the new project when you add the generated HDL coder into Vivado project by yourself.
Also, following document page also shows some features (like back annotation of critical path to model) to help you identify critical path to meet timing:
Thanks,
Wang
Vighnesh Kamath
am 16 Nov. 2020
Hi Alex,
Is it possible for you to send your Simulink model from the above image?
We can do some analysis on it and try to provide you a solution to fix your problem.
Regards,
Vighnesh
0 Kommentare
Siehe auch
Kategorien
Mehr zu Speed Optimization finden Sie in Help Center und File Exchange
Community Treasure Hunt
Find the treasures in MATLAB Central and discover how the community can help you!
Start Hunting!