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
Change the default IRQs. #34
Conversation
* Better error messages. * Search correct directories; - XXX/Vivado/<version> - XXX/<version>/ISE_DS/
@stffrdhrn - Can you give this change a test? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Seems fine, but be since uart is changed to uart0, don't you need to change some software elsewhere?
21ab5bf
to
bb4a031
Compare
Adding a bunch of fixes.
|
And a datapoint why something like this is important - I just discovered we are using the same IRQ value for LiteEth and HDMI0 in the HDMI2USB-litex-firmware (before we changing the value). That now provides the helpful error message; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
seems fine
* Reserve IRQ 0 to be used as a "non-maskable interrupt" (NMI) in the future. * Use IRQ 2 for the LiteX. This matches the standard mor1k config which connects the UART to IRQ 2. This change is needed for Linux running on LiteX as it gets grumpy with using IRQ 0 for anything other other than an NMI.
7a019e4
to
56ef229
Compare
Merging! |
Reserve IRQ 0 to be used as a "non-maskable interrupt" (NMI) in the future.
Make it harder to define duplicate IRQs and provide better error messages when it happens.
Use IRQ 2 for the LiteX. This matches the standard mor1k config which connects the UART to IRQ 2.
This change is needed for Linux running on LiteX as it gets grumpy with using IRQ 0 for anything other other than an NMI.