From f466ad0faf6d5757d1cb3259486bb7604b9064f2 Mon Sep 17 00:00:00 2001 From: David Shah Date: Sun, 29 Jul 2018 14:17:02 +0200 Subject: Update README.md wrt ECP5 Signed-off-by: David Shah --- README.md | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-) diff --git a/README.md b/README.md index 8154f69f..dfe2af37 100644 --- a/README.md +++ b/README.md @@ -71,11 +71,16 @@ make -j$(nproc) sudo make install ``` -- For an ECP5 blinky, first synthesise using `yosys blinky.ys` in `ecp5/synth`. + - For an ECP5 blinky, 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` - 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 + - More examples of the ECP5 flow for a range of boards can be found in the [Project Trellis Examples](https://github.com/SymbiFlow/prjtrellis/tree/master/examples). + + - Currently the ECP5 flow supports LUTs, flipflops and IO. IO must be instantiated using `TRELLIS_IO` primitives and constraints specified + using `LOC` and `IO_TYPE` attributes on those instances, as is used in the examples. + ### nextpnr-generic The generic target allows to run place and route for an arbitrary custom architecture. -- cgit v1.2.3