Port prjxray to the Virtex-7 family, modelled on Kintex-7, targeting
xc7vx485tffg1761-2 (vc707). Non-breaking for the existing families.
Family registration:
- settings/virtex7.sh, settings/virtex7/devices.yaml
- Makefile: virtex7 in DATABASES/XRAY_PARTS + db-extras-virtex7 targets
- utils/update_parts.py, update_resources.py: virtex7 choice
- CI matrix (Pipeline.yml), Vivado edition (xilinx.sh), README
Architecture adaptations for the HP-bank-only VX part (verified non-breaking):
- update_resources.tcl: fall back to HP banks when no HR banks exist
- XRAY_IOSTANDARD env (default LVCMOS33; LVCMOS18 for virtex7), parameterised
across the fuzzer generate.tcl files
- fuzzers: enable HP-bank (iob18/ioi18) + IOI/HCLK handling for virtex7;
GTX skipped (ffg1761 bonds only ~7 of 14 GTX quads)
- 005-tilegrid: HP/HR bank tile handling; iob18_int INT offset 3->2;
ioi18 AUTO_FRAME; cfg PDRC-2 DRC disable; add_tdb skips unsolved edge tiles;
per-specimen retry for transient FlexLM SIGSEGV under concurrency
- per-family Vivado version gate (virtex7 -> v2020.1.1)
- XRAY_ROI and XRAY_ROI_GRID tuned to a compact CLBLL+CLBLM region
General fixes:
- tools/bitread.cc: fix use-after-free of the mmap'd bitstream (exposed by the
larger Virtex-7 bitstream)
- utils/environment.python.sh: add repo root to PYTHONPATH (PEP 660 editable
install doesn't expose the repo-root utils/ package)
Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
The previous xc7s50t branch was messed up. This new branch is created to re-submit xc7s50t's changes for merging.
Signed-off-by: Steve <steve.bohan.liu@outlook.com>
The resources.yaml file does not exists at the beginning of the db-prepare calls
but the environment wants to read it which leads to the following error:
Preparing artix7 files
============================
Traceback (most recent call last):
File ".../prjxray/utils/create_environment.py", line 62, in <module>
main()
File ".../prjxray/utils/create_environment.py", line 55, in main
environment = get_environment_variables()
File ".../prjxray/utils/create_environment.py", line 37, in get_environment_variables
part_info = get_part_information(db_root, part)
File ".../prjxray/prjxray/util.py", line 44, in get_part_information
"Mapping file {} does not exists".format(filename)
AssertionError: Mapping file .../prjxray/database/artix7/mapping/parts.yaml does not exists
Do not dump the environment during this stage because the XRAY_PART is the only
neccessary information which is set in the <family>.sh script.
Signed-off-by: Daniel Schultz <d.schultz@phytec.de>
Adds a db-extra-X-roi command which will call a Python tool because the
part list is some kind of dynamic and Makefiles can't read from a YAML file
and iterates over all keys.
Also some minor clean-ups with the kintex and zynq extra commands.
Signed-off-by: Daniel Schultz <d.schultz@phytec.de>
These informations are now stores in device-specific mapping files and
run_fuzzers stores them as variable.
Signed-off-by: Daniel Schultz <d.schultz@phytec.de>
* Move Python environment values into `utils/environment.python.sh`
* Source the `utils/environment.python.sh` before running Python
scripts.
* Add `DeprecationWarning` suppression for `distutils`
Now the output of `make test-py` returns `30 passed in N.NNs` instead of
the previous `30 passed, 1 warnings in N.NNs`
Signed-off-by: Tim 'mithro' Ansell <me@mith.ro>
There is an issue with the roi_harness creation, for which the
multi-process make does not correctly works for roi_harness target
Signed-off-by: Alessandro Comodi <acomodi@antmicro.com>
Dr Jonathan Richard Robert Kimmitt
Hans Baier
Unai Martinez-Corral
Alessandro Comodi
Steve
Daniel Schultz
Tomasz Michalak
Keith Rothman
Robert Winkler
Tim Ansell
Tim 'mithro' Ansell
Andrew Butt
Tim Callahan