Skip to content
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

interconnect to be unified #12

Open
bieganski opened this issue Feb 27, 2022 · 2 comments
Open

interconnect to be unified #12

bieganski opened this issue Feb 27, 2022 · 2 comments

Comments

@bieganski
Copy link
Owner

bieganski commented Feb 27, 2022

Currently porting third-party peripherals to mtkCPU may be problematic, because what is called Wishbone in the CPU code (we have WishboneBusRecord, GenericInterfaceToWishboneMasterBridge and WishboneSlave classes) does not implement a real Wishbone interface - indeed, it's similar, but much simplified.

Some examples of discrepancies:

  • no strobe signal is used at all - there is an assumption, that strobe == cyc
  • no tags are present
  • no select signal - chip select logic is moved to address decoder, that switches peripherals based on request address as shown here

However, ideally we should implement and functionally verify Wishbone Bus, to make it easier for users to port their own peripherals.

@robtaylor
Copy link

Do check out the new Interfaces RFC in Amaranth. We now discuss RFCs every Monday at 1700 UTC on the irc channel.

@bieganski
Copy link
Owner Author

oh, good to know, thank you! for sure will check it out.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants