Unverified Commit 9a099958 authored by Yuxiang Zhang's avatar Yuxiang Zhang Committed by GitHub
Browse files

Update README.md

parent 8545eae8
......@@ -4,18 +4,15 @@ Vivado installed into a docker image for CI purposes.
## Build instructions
1. This docker file assumes the Vivado download is available on a webserver somewhere. This can easily be the build machine using the webserver in Python.
```shell
cd /path/to/Vivado/download
python -m http.server
```
2. Copy your Vivado `Xilinx.lic` file into the directory.
1. Copy the Vivado installation package `Xilinx_Vivado_SDK_2018.1_0405_1.tar.gz` to this folder.
3. Potentialy modify the `install_config.txt` to change the install options.
4. Build the image (will take about 10 minutes) passing in a build arg
4. Build the image (will take about 30 minutes) passing in a build arg
```shell
docker build --build-arg VIVADO_TAR_HOST=host_ip:8000 --build-arg VIVADO_TAR_FILE=Xilinx_Vivado_SDK_2016.3_1011_1 -t vivado:2016.3 .
docker build --build-arg VIVADO_VERSION=2018.1 --build-arg VIVADO_TAR_FILE=Xilinx_Vivado_SDK_2018.1_0405_1.tar.gz -t vivado:2018.1 .
```
## Running
The `Dockerfile` sets up a `vivado` user to avoid running as root. I have only considered running Vivado in `batch` mode for running CI simulations and building bit files. For development work with the GUI you may have to fiddle with X11 settings.
```shell
docker run -ti --rm -e DISPLAY=$DISPLAY -v /tmp/.X11-unix:/tmp/.X11-unix vivado:2018.1
```
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment