Ok, here's a small variation on a previous post. My design is giving the wrong results in post-PAR simulation (no SDF errors or warnings, no timing violations in PAR), and I want to verify whether my multi-cycle paths are to blame. I would prefer to check this using behavioural code rather than the post-PAR model, because the latter takes days to run my complete testbench. How would you go about this? Post-PAR suggestions are also welcome, as are any other ideas as to the possible causes of such a discrepancy. Thanks in advance...
- posted
20 years ago
-- Pierre-Olivier -- to email me directly, remove all _N0SP4M_ from my address --