The Verilog-to-Routing (VTR) project is a world-wide collaborative effort to provide a open-source framework for conducting FPGA architecture and CAD research and development. The VTR design flow takes as input a Verilog description of a digital circuit, and a description of the target FPGA architecture. It then perfoms:
- Elaboration & Synthesis (ODIN II)
- Logic Optimization & Technology Mapping (ABC)
- Packing, Placement, Routing & Timing Analysis (VPR)
to generate FPGA speed and area results. VTR also includes a set of benchmark designs known to work with the design flow.
For most users of VTR (rather than active developers) you should download the latest packaged (and regression tested) version of VTR from here.
VTR's full documentation is available here.
If you have questions, or want to keep up-to-date with VTR, consider joining our mailing lists:
VTR-Announce: VTR release announcements (low traffic)
VTR-Users: Discussions about using VTR
VTR-Devel: Discussions about VTR development
VTR-Commits: VTR revision control commits
The following paper may be used as a general citation for VTR:
J. Luu, J. Goeders, M. Wainberg, A. Somerville, T. Yu, K. Nasartschuk, M. Nasr, S. Wang, T. Liu, N. Ahmed, K. B. Kent, J. Anderson, J. Rose and V. Betz "VTR 7.0: Next Generation Architecture and CAD System for FPGAs," ACM TRETS, Vol. 7, No. 2, June 2014, pp. 6:1 - 6:30.
Bibtex:
@article{vtr2014,
title={{VTR 7.0: Next Generation Architecture and CAD System for FPGAs}},
author={Luu, Jason and Goeders, Jeff and Wainberg, Michael and Somerville, Andrew and Yu, Thien and Nasartschuk, Konstantin and Nasr, Miad and Wang, Sen and Liu, Tim and Ahmed, Norrudin and Kent, Kenneth B. and Anderson, Jason and Rose, Jonathan and Betz, Vaughn},
journal = {ACM Trans. Reconfigurable Technol. Syst.},
month={June},
volume={7},
number={2},
pages={6:1--6:30},
year={2014}
}
This is the development trunk for the Verilog-to-Routing project. Unlike the nicely packaged releases that we create, you are working with code in a constant state of flux. You should expect that the tools are not always stable and that more work is needed to get the flow to run.
For new developers, please do the tutorial in tutorial/NewDeveloperTutorial.txt. You will be directed back here once you ramp up.
VTR development follows a classic centralized repository (svn-like) workflow. The 'master' branch is supposed to be the most current stable version of the project. Developers checkout a local copy of the code at the start of development, then do regular updates (e.g. git pull) to keep in sync with the GitHub master. When a developer has a tested, working change to put back into the trunk, he/she performs a git push operation. Unstable code should remain in the developer's local copy.
We do automated testing of the trunk using BuildBot to verify functionality and Quality of Results (QoR). You can see the state of the trunk here. QoR tracking links can be found here.
IMPORTANT: A broken build must be fixed at top priority. You break the build if your commit breaks any of the automated regression tests.
Please keep this up-to-date
Professors: Kenneth Kent, Vaughn Betz, Jonathan Rose, Jason Anderson, Peter Jamieson
Graduate Students: Kevin Murray, Jason Luu, Oleg Petelin, Jeffrey Goeders, Chi Wai Yu, Andrew Somerville, Ian Kuon, Alexander Marquardt, Andy Ye, Wei Mark Fang, Tim Liu, Charles Chiasson, Panagiotis Patros
Summer Students: Opal Densmore, Ted Campbell, Cong Wang, Peter Milankov, Scott Whitty, Michael Wainberg, Suya Liu, Miad Nasr, Nooruddin Ahmed, Thien Yu, Long Yu Wang, Matthew J.P. Walker, Amer Hesson, Sheng Zhong, Hanqing Zeng
Companies: Altera Corporation, Texas Instruments
Generally most code is under MIT license, with the exception of ABC which is distributed under its own (permissive) terms. Full license details can be found here.