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

OpenPiton Transducer in WARP-V #50

Open
wants to merge 24 commits into
base: master
Choose a base branch
from

Conversation

shivampotdar
Copy link
Collaborator

Integration of WARP-V with OpenPiton

Google Summer of Code 2020 Project with FOSSi Foundation

-- Shivam Potdar, India

This PR aims to add support for integrating WARP-V with Bring Your Own Core (BYOC) (A fork of OpenPiton from Princeton University)
(This one is pending for merge while other parts of the project are already upstream)

The following changes are made :

  • Other cores which are supported in BYOC have a separate transducer module which instantiated alongside the core. With WARP-V and the flexibility that is possible, we can generate one top-level module (warpv_openpiton) to directly contain all the interface signals with the BYOC Transaction-Response Interface (TRI).
  • Both decoding the encoding logic for the TRI signals is internal to the core
  • To support memory requests with variable latency, a generic external memory interface is in progress, which would eliminate the internal instruction and data memory conditionally.

@shivampotdar shivampotdar marked this pull request as draft August 30, 2020 20:23
@shivampotdar shivampotdar marked this pull request as ready for review August 30, 2020 20:24
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

Successfully merging this pull request may close these issues.

1 participant