caiyu/nextpnr
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

More documentation tweaks

Browse Source 
Signed-off-by: David Shah <davey1576@gmail.com>
This commit is contained in:
David Shah 2018-08-01 10:51:32 +02:00
parent cceda82d40
commit b273475e51
2 changed files with 8 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
README.md
View File

@ -89,7 +89,7 @@ make -j$(nproc)
sudo make install sudo make install
``` ```
- For an ECP5 blinky, first synthesise using `yosys blinky.ys` in `ecp5/synth`. - For an ECP5 blinky on the 45k ULX3S board, first synthesise using `yosys blinky.ys` in `ecp5/synth`.
- Then run ECP5 place-and route using `./nextpnr-ecp5 --json ecp5/synth/blinky.json --basecfg ecp5/synth/ulx3s_empty.config --bit ecp5/synth/ulx3s.bit` - Then run ECP5 place-and route using `./nextpnr-ecp5 --json ecp5/synth/blinky.json --basecfg ecp5/synth/ulx3s_empty.config --bit ecp5/synth/ulx3s.bit`
- Note that `ulx3s_empty.config` contains fixed/unknown bits to be copied to the output bitstream - Note that `ulx3s_empty.config` contains fixed/unknown bits to be copied to the output bitstream
- You can also use `--textcfg out.config` to write a text file describing the bitstream for debugging - You can also use `--textcfg out.config` to write a text file describing the bitstream for debugging
@ -101,7 +101,7 @@ sudo make install
### nextpnr-generic ### nextpnr-generic
The generic target allows to run place and route for an arbitrary custom architecture. The generic target allows running placement and routing for arbitrary custom architectures.
``` ```
cmake -DARCH=generic . cmake -DARCH=generic .

12
docs/faq.md
View File

@ -52,12 +52,12 @@ Nextpnr and other tools
need an open source toolchain, we suggest you use [Yosys](http://www.clifford.at/yosys/) and nextpnr. need an open source toolchain, we suggest you use [Yosys](http://www.clifford.at/yosys/) and nextpnr.
* If you are developing FPGA code in **Verilog** for a **Lattice iCE40** with * If you are developing FPGA code in **Verilog** for a **Lattice iCE40** with
Yosys and the **existing Arachne-PNR toolchain**, we suggest you start thinking about Yosys and the **existing arachne-pnr toolchain**, we suggest you start thinking about
migrating to nextpnr. migrating to nextpnr.
* If you are developing Verilog FPGA code targeted at the Lattice ECP5 and * If you are developing Verilog FPGA code targeted at the Lattice ECP5 and
need an open source toolchain, you may consider the **extremely need an open source toolchain, you may consider the **extremely
experimental** ECP5 support in Yosys and nextpnr experimental** ECP5 support in Yosys and nextpnr.
* If you are developing FPGA code in **VHDL** you will need to use either a * If you are developing FPGA code in **VHDL** you will need to use either a
version of [Yosys with Verific support](https://github.com/YosysHQ/yosys/tree/master/frontends/verific) or the vendor provided tools due version of [Yosys with Verific support](https://github.com/YosysHQ/yosys/tree/master/frontends/verific) or the vendor provided tools due
@ -72,8 +72,8 @@ part of [Project IceStorm](http://www.clifford.at/icestorm/) to demonstrate it
was possible to create an open source place and route tool for the iCE40 FPGAs was possible to create an open source place and route tool for the iCE40 FPGAs
that actually produced valid bitstreams. that actually produced valid bitstreams.
For it's original purpose it has served the community extremely well. However, For its original purpose, it has served the community extremely well. However,
it was never designed to support multiple different FPGA devices, nor more it was never designed to support multiple different FPGA families, nor more
complicated timing driven placement and routing used by most commercial place and route complicated timing driven placement and routing used by most commercial place and route
tools. tools.
@ -91,7 +91,7 @@ of arachne-pnr.
### Why are you not just contributing to [Verilog to Routing](https://verilogtorouting.org)? ### Why are you not just contributing to [Verilog to Routing](https://verilogtorouting.org)?
We believe that [Verilog to Routing](https://verilogtorouting.org) is a great We believe that [Verilog to Routing](https://verilogtorouting.org) is a great
tool and many of the nextpnr developers have made (and continue to make) toolchain and many of the nextpnr developers have made (and continue to make)
contributions to the project. contributions to the project.
VtR is an extremely flexible toolchain but focuses on research around FPGA VtR is an extremely flexible toolchain but focuses on research around FPGA
@ -139,7 +139,7 @@ will soon be using Project X-Ray in a similar manner to Project Trellis.
[Project IceStorm](http://www.clifford.at/icestorm/) is both a project to [Project IceStorm](http://www.clifford.at/icestorm/) is both a project to
document the bitstream for the Lattice iCE40 series of parts **and** a full document the bitstream for the Lattice iCE40 series of parts **and** a full
flow including Yosys and Arachne-PNR for converting Verilog into a bitstream for flow including Yosys and arachne-pnr for converting Verilog into a bitstream for
these parts. these parts.
As the open source community now has support for multiple different FPGA parts, As the open source community now has support for multiple different FPGA parts,