On Sep 3, 2010, at 8:20 , Jack Hickish wrote:
After a compile fails, it's worth checking the timing report in the compile directory ..../XPS_ROACH_BASE/implementation/system.twr Whilst a little bit cryptic, the report should at least give you some idea of which bits of the design are causing timing failure. It becomes reasonably clear if it's adders in the FIR, or casts in the FFT for example.
I concur! Blindly adding additional latency will certainly change things and maybe result in a deign that can meet timing, but it can (and often does) also result in unnecessary additional resource utilization. Having a better understanding of where timing is failing will lead to a more targeted solution.
I think it would be useful to track where timing problems occur across different designs. If this points to a particular library block as problematic across multiple designs, it would serve as justification for additional work on that block.
Dave
