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

Support Platforms that include an existing design and expose interface to that design as Resource #308

nmigen-issue-migration opened this issue Jan 19, 2020 · 1 comment


Copy link

Issue by smunaut
Sunday Jan 19, 2020 at 13:50 GMT
Originally opened as m-labs/nmigen#308

The typical use case I have for this are boards where the USB function is provided using soft core. But having the user deal with that is often annoying when all they want is data in/out.

So typically I would like to have a platform that exposes for instances "uart_tx" and "uart_rx" or "in_data / in_valid / in_ready" as Resources just like if they were physical pins, but in fact they're just internal connections to a module that's always included when using that Platform.

In this particular case this module is written in Verilog and includes the SoC and USB core that handles all the USB and DFU etc ... and just provide an easy data pipe in/out.

Copy link

rroohhh commented May 27, 2020

Something similar is also interesting for SoC's like the Zynq.

It would be nice to be able to add a PS7 instance to the platform, as well as maybe additional support modules, like a AXI interconnect, which when put in the platform could be more easily used all over the design hierarchy.

Additionally there are zynq board that only get their clock from this PS7 instance, so it would be nice, if this these resources then also could be used for things like default_clk.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

No branches or pull requests

3 participants