aboutsummaryrefslogtreecommitdiffstats
path: root/machxo2/examples/README.md
diff options
context:
space:
mode:
authorWilliam D. Jones <thor0505@comcast.net>2021-02-08 16:55:26 -0500
committergatecat <gatecat@ds0.me>2021-02-12 10:36:59 +0000
commit730e543ca65e97f1518fd0a9e692b233e15dcdbd (patch)
treed26c3f73b96669364b25293065be4b6453d24bee /machxo2/examples/README.md
parent0b0faa2f1c1e0cf148a6cee37041320def12678c (diff)
downloadnextpnr-730e543ca65e97f1518fd0a9e692b233e15dcdbd.tar.gz
nextpnr-730e543ca65e97f1518fd0a9e692b233e15dcdbd.tar.bz2
nextpnr-730e543ca65e97f1518fd0a9e692b233e15dcdbd.zip
machxo2: Add prefix parameter to simple.sh. Update README.md.
Diffstat (limited to 'machxo2/examples/README.md')
-rw-r--r--machxo2/examples/README.md8
1 files changed, 4 insertions, 4 deletions
diff --git a/machxo2/examples/README.md b/machxo2/examples/README.md
index 13964602..d4a89f7a 100644
--- a/machxo2/examples/README.md
+++ b/machxo2/examples/README.md
@@ -1,8 +1,8 @@
# MachXO2 Architecture Example
This directory contains a simple example of running `nextpnr-machxo2`:
-* `simple.sh` generates JSON output (`{pack,place,pnr}blinky.json`) of a
- classic blinky example from `blinky.v`.
+* `simple.sh` produces nextpnr output in the files `{pack,place,pnr}*.json`,
+ as well as pre-pnr and post-pnr diagrams in `{pack,place,pnr}*.{dot, png}`.
* `simtest.sh` will use `yosys` to generate a Verilog file from
`{pack,place,pnr}blinky.json`, called `{pack,place,pnr}blinky.v`. It will
then and compare `{pack,place,pnr}blinky.v`'s simulation behavior to the
@@ -10,8 +10,8 @@ This directory contains a simple example of running `nextpnr-machxo2`:
compiler and `vvp` runtime. This is known as post-place-and-route simulation.
* `mitertest.sh` is similar to `simtest.sh`, but more comprehensive. This
script creates a [miter circuit](https://www21.in.tum.de/~lammich/2015_SS_Seminar_SAT/resources/Equivalence_Checking_11_30_08.pdf)
- to compare the output port values of `{pack,place,pnr}blinky.v` against the
- original `blinky.v` _when both modules are fed the same values on their input
+ to compare the output port values of `{pack,place,pnr}*.v` against the
+ original Verilog code _when both modules are fed the same values on their input
ports._
All possible inputs and resulting outputs can be tested in reasonable time by