From 889941bce12e18cf046aa57425b2b5e72fb0cc9b Mon Sep 17 00:00:00 2001 From: Dr Jonathan Richard Robert Kimmitt Date: Fri, 29 May 2026 11:06:47 +0100 Subject: [PATCH] README: pin Virtex-7 port to Vivado 2020.1 (2017.2 is too old) Add a callout block under the four-repo branch table noting that the Virtex-7 work was developed and validated against Vivado 2020.1, that other 2018+ releases may work, and that the upstream-recommended 2017.2 is too old for this device (predates xc7vx485tffg1761-2 HP-bank IOB18 support, several HCLK_IOI/CMT properties the fuzzers query, and the write_pip_txtdata bulk paths the utils.tcl patch exercises). Co-Authored-By: Claude Opus 4.7 --- README.md | 11 +++++++++++ 1 file changed, 11 insertions(+) diff --git a/README.md b/README.md index 7ac15171..2ec930aa 100644 --- a/README.md +++ b/README.md @@ -260,6 +260,17 @@ The work spans four sibling branches on the openXC7 GitHub: | openXC7/nextpnr-xilinx | `virtex7-support` | RAM128/256X1S packing + INT-tile constant-net bridge | | openXC7/demo-projects | `virtex7-branch` | VC707 reference `.bit` files + sources | +> **Vivado version.** This port was developed and validated against +> **Vivado 2020.1**. Other 2018+ releases may well work — the fuzzers and +> Tcl helpers are not knowingly using any 2020.1-specific feature — but the +> upstream-recommended **2017.2 is too old** for Virtex-7 here: it predates +> the device support files we need (`xc7vx485tffg1761-2` HP-bank IOB18 +> behaviour, several `HCLK_IOI`/`CMT` properties the fuzzers query, the +> `write_pip_txtdata` bulk-fetch paths the `utils.tcl` patch exercises). +> Set `XRAY_VIVADO_SETTINGS` accordingly: +> +> export XRAY_VIVADO_SETTINGS=/opt/Xilinx/Vivado/2020.1/settings64.sh + ### Achievements - **End-to-end open flow on real hardware (VC707):**