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

Add Project XRay backend currently supporting Kintex7 #308

Draft
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

carlosedp
Copy link
Contributor

@carlosedp carlosedp commented Feb 14, 2022

This PR adds support to Project XRay supporting Xilinx series 7 FPGAs.
Currently I'm testing with Kintex 7 and a QMTech board.

The work is based on https://github.com/kintex-chatter/xc7k325t-blinky-nextpnr and is in draft (although working) state.

The backend has hard-coded paths for the databases. This is still required to be able to use Docker container flow. We need to improve this.
Managed to fix the environment variables. Works on Docker but needs testing for locally installed tools.

The supporting files to run this are at https://gist.github.com/carlosedp/a7b4386b41ffdf60873c05eeae7155ec. There is the edalize launcher script with some changes due to how quotes are handled which I plan to send a PR too.

There is also a Dockerfile to build the toolchain container image and the databases. @umarcor once it's in a more stable and/or upstream state, we can integrate to hdlc repo.

The idea is to open this for discussion.

@umarcor
Copy link
Contributor

umarcor commented Feb 15, 2022

@carlosedp note that the "backend" is nextpnr in this case (VTR is supported as well). Project XRay is the "architecture documentation/database", equivalent to IceStorm, Project Trellis or Project Nexus. See:

@carlosedp
Copy link
Contributor Author

Ah yes, my idea here is to create the Project Trellis equivalent for XRay where Yosys backend is used by default but since nextpnr-xilinx is kinda different from the standard nextpnr, I decided now to keep it in the xray file instead of "plugging" the nextpnr backend.

Also the build and databases is a bit different so I created the Dockerfile myself. I believe it's still early since I used forked versions from @hansfbaier that did the amazing work starting this.

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.

None yet

2 participants