No, the netlist will not be considered as the one which has 'gated clocks' because the enable pin controls the D input inside the FF, and not the clock.
kr,
Avi
No, the netlist will not be considered as the one which has 'gated clocks' because the enable pin controls the D input inside the FF, and not the clock.
kr,
Avi
Well, in that case you will need to see the library spec then. I will still say that the lib vendor will not play with the clock, but to be sure, you will have to look into the lib spec. You can also have a look into the .lib file and see what are the pin functions there. Or looking at timing arcs in the .lib file may give you a clue whats going on insed the cell.
kr,
Avi
I have finally found what the issue was but could not trace to its origin. The pin connections of the flops with enable in my design were interchaged as follows:
CP --> E
E -- > D
D --> CP
When I realigned them in the netlist manually I could get the lec pass on the pre and post scan netlists.
we cant conform with that our design has gated clock. every flop has clock enable pin . gated clock is use to enable particular logic ( group of flip flops)