Reset fails to respond when driven from vector containing clock enable
In the attached test, the active low reset output fails to go high when the active high input goes low.
There are several work-arounds. One is to define the FIXIT macro which modifies the test code. Another is to remove the clock_enable comment. Another is to delete slave_clk.
To reproduce, save the attached files in the current directory and run the commands: make ./obj_dir/Verror9
#2 Updated by Wilson Snyder over 3 years ago
- Status changed from New to Confirmed
Attributes such as the clock enables and clocks themselves are propagated signal-by-signal rather than bit-of-signal. So what's going on here is the clock enable attribute also gets associated with the reset. This is certainly a bug, but fairly fundamental so unfortunately is unlikely to be resolved any time soon, sorry.
#3 Updated by Todd Strader over 3 years ago
This looks very similar to a problem we had with vectors of clocks:
I've been slacking on cleaning this up for pushing back upstream, but the GitHub link has the code that we are currently using to address the issue. I haven't tried your code, however, my suspicion is that it will not work for you. But it should be trivial to apply the same technique for clock enable signals (as opposed to clocks).
Also available in: Atom