-
Notifications
You must be signed in to change notification settings - Fork 32
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
[Request] A proposal for CSRs #2
Comments
Comment by HarryHo90sHK For reference, here are the meanings of the access type Enums:
Please also refer to: http://www.keil.com/pack/doc/CMSIS/SVD/html/elem_special.html#elem_access |
Comment by whitequark Thanks, I'll take a look soon. |
Comment by whitequark Thank you for the proposal. I have in mind some ways to simplify the code in your branch. I'm going to sketch out an implementation I have in mind, and then ask you for feedback to make sure I didn't miss anything important. |
Superseded by #68. |
Issue by HarryHo90sHK
Friday Sep 27, 2019 at 07:10 GMT
Originally opened as m-labs/nmigen-soc#2
#1 Following the general ideas discussed, I have made a new abstraction for CSR objects in my fork (HarryMakes/nmigen-soc@ba5f354 fixed). An example script is given below, which will print all the fields and their properties in a CSR named "test". You might also test the slicing functionality using the format
mycsr[beginbit:endbit]
, but please note that the upper boundary is exclusive.The text was updated successfully, but these errors were encountered: