-
Notifications
You must be signed in to change notification settings - Fork 69
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Interrupt enable definitions are not obeyed #67
Comments
And is that another typo in your output generator? Shouldn't the register name and the _next term be the same? Looks like you missed the 'e' from 'reg' in rg__status_global_irq. |
Not able to recreate this issue - directly copied your code (older version i think that didnt have the ->next assign) and see the following for _status assigns:
Assume you see no errors/warnings when running? If not, might try removing the comment prior to the ->enable assign (just a guess) Register name starting with "rg_" is no typo - just a way to allow easy identification of actual field registers by name. |
OK, I've attached a testcase with my full RDL. Untar it and run 'make'. The archive has the jar file and the preprocessor. Thanks. |
Thanks a lot. If you could fire off a build that would be useful as I can't currently build from source. See #63 |
Confirmed fixed. Thanks a lot. |
I've followed the example in the RDL spec on how to generate hierarchical interrupts. At the top level I have two registers with a single bit in each, one a global interrupt and one a global enable. I've tried using both the 'intr' and 'nonsticky intr' properties on the interrupt and it behaves the same way. How am I supposed to mask this top level interrupt?
That results in:
The text was updated successfully, but these errors were encountered: