tree: f106ade56f1bddc225c92494ae2cada2e9e5864f [path history] [tgz]
  1. .gitignore
  2. arty.sh
  3. basys3.sh
  4. defines.v
  5. demo_sw_led.py
  6. demo_sw_led_fasm.py
  7. fasm2bit.sh
  8. Makefile
  9. README.md
  10. roi_base.v
  11. roi_demoscene.v
  12. roi_inv.v
  13. runme.sh
  14. runme.tcl
  15. test_demo_sw_led.py
  16. top.v
minitests/roi_harness/README.md

ROI_HARNESS Minitest

Purpose

Creates an ROI with clk, inputs, and outputs to use as a partial reconfiguration test harness

Basic idea:
-LOC LUTs in the ROI to terminate input and output routing
-Let Vivado LOC the rest of the logic
-Manually route signals in and out of the ROI enough to avoid routing loops into the ROI
-Let Vivado finish the rest of the routes

There is no logic outside of the ROI in order to keep IOB to ROI delays short
Its expected the end user will rip out everything inside the ROI

To target Arty A7 you should source the artix DB environment script then source arty.sh

To build the baseline harness:

./runme.sh

To build a sample Vivado design using the harness:

XRAY_ROIV=roi_inv.v XRAY_FIXED_XDC=out_xc7a35tcpg236-1_BASYS3-SWBUT_roi_basev/fixed_noclk.xdc ./runme.sh

Note: this was intended for verification only and not as an end user flow (they should use SymbiFlow)

To use the harness for the basys3 demo, do something like:

python3 demo_sw_led.py out_xc7a35tcpg236-1_BASYS3-SWBUT_roi_basev 3 2

This example connects switch 3 to LED 2

Result