You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
Currently porting third-party peripherals to
mtkCPU
may be problematic, because what is calledWishbone
in the CPU code (we haveWishboneBusRecord
,GenericInterfaceToWishboneMasterBridge
andWishboneSlave
classes) does not implement a real Wishbone interface - indeed, it's similar, but much simplified.Some examples of discrepancies:
strobe
signal is used at all - there is an assumption, thatstrobe == cyc
However, ideally we should implement and functionally verify Wishbone Bus, to make it easier for users to port their own peripherals.
The text was updated successfully, but these errors were encountered: