projects
/
freedom-sifive.git
/ blobdiff
commit
grep
author
committer
pickaxe
?
search:
re
summary
|
shortlog
|
log
|
commit
|
commitdiff
|
tree
raw
|
inline
| side by side
README: note the vivado version requirements
[freedom-sifive.git]
/
README.md
diff --git
a/README.md
b/README.md
index 249875028ae271102f49d3540a76fa1cb19caaaf..3ba50116d80d40c21b9d808a67043492c2a8779f 100644
(file)
--- a/
README.md
+++ b/
README.md
@@
-44,7
+44,9
@@
$ make -f Makefile.e300artydevkit verilog
$ make -f Makefile.e300artydevkit mcs
```
$ make -f Makefile.e300artydevkit mcs
```
-These will place the files under `builds/e300artydevkit`.
+Note: This flow requires vivado 2017.1. Old versions are known to fail.
+
+These will place the files under `builds/e300artydevkit/obj`.
Note that in order to run the `mcs` target, you need to have the `vivado`
executable on your `PATH`.
Note that in order to run the `mcs` target, you need to have the `vivado`
executable on your `PATH`.
@@
-77,7
+79,9
@@
$ make -f Makefile.u500vc707devkit verilog
$ make -f Makefile.u500vc707devkit mcs
```
$ make -f Makefile.u500vc707devkit mcs
```
-These will place the files under `builds/u500vc707devkit`.
+Note: This flow requires vivado 2016.1. Newer versions are known to fail.
+
+These will place the files under `builds/u500vc707devkit/obj`.
Note that in order to run the `mcs` target, you need to have the `vivado`
executable on your `PATH`.
Note that in order to run the `mcs` target, you need to have the `vivado`
executable on your `PATH`.