Forum Discussion

Altera_Forum's avatar
Altera_Forum
Icon for Honored Contributor rankHonored Contributor
8 years ago

"limit due to minimum pulse width violation" how to find out what is causing this.

I've got the following message/warning in the .sta report: +------------+-----------------+------------+--------------------------------------------+ ; Fmax ; Restricted Fmax ; Clock Name ...
Altera_Forum's avatar
Altera_Forum
Icon for Honored Contributor rankHonored Contributor
8 years ago

Ok, thanks, understood.

For the record my example above was faulty: because no output from the module was specified ('input [25:0]' o should have been 'output [25:0] o') the multiplication inside the module was optimised away along and thus the (I guess) some 'random' logic was left and this generated the minimum pulse width violation which went away when I fixed my code.

But I understand that regardless the point about timing of multiple instances is still valid.