Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Kintex7 xc7k325 support #1794

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Kintex7 xc7k325 support #1794

wants to merge 1 commit into from

Conversation

jrrk2
Copy link

@jrrk2 jrrk2 commented Dec 7, 2021

I followed the guide to add new parts, more or less, some experimental features had to be commented out. No validation on real hardware has been done, this is just to establish if the pull request changes can run

@mithro
Copy link
Contributor

mithro commented Dec 7, 2021

@kgugala Who should review this?

@jrrk2
Copy link
Author

jrrk2 commented Dec 7, 2021

The build failed, but a necessary step: 'make db-prepare-kintex7'
does not seem to be included in the regression flow. As far as
I can see this needs to run before 'make -C fuzzers part_only'

@mithro
Copy link
Contributor

mithro commented Dec 7, 2021

I believe that make db-prepare-kintex7 should be run and committed?

@mithro
Copy link
Contributor

mithro commented Dec 7, 2021

Actually maybe I'm wrong...

@mithro
Copy link
Contributor

mithro commented Dec 7, 2021

========================================
Preparing database
----------------------------------------

Preparing kintex7 files
============================
Part xc7k160tfbg484-1 has an unsupported device xc7k160t
Part xc7k160tfbg484-2 has an unsupported device xc7k160t
Part xc7k160tfbg484-2L has an unsupported device xc7k160t
Part xc7k160tfbg484-3 has an unsupported device xc7k160t
Part xc7k160tfbg676-1 has an unsupported device xc7k160t
Part xc7k160tfbg676-2 has an unsupported device xc7k160t
Part xc7k160tfbg676-2L has an unsupported device xc7k160t
Part xc7k160tfbg676-3 has an unsupported device xc7k160t
Part xc7k160tfbv484-1 has an unsupported device xc7k160t
Part xc7k160tfbv484-2 has an unsupported device xc7k160t
Part xc7k160tfbv484-2L has an unsupported device xc7k160t
Part xc7k160tfbv484-3 has an unsupported device xc7k160t
Part xc7k160tfbv676-1 has an unsupported device xc7k160t
Part xc7k160tfbv676-2 has an unsupported device xc7k160t
Part xc7k160tfbv676-2L has an unsupported device xc7k160t
Part xc7k160tfbv676-3 has an unsupported device xc7k160t
Part xc7k160tffg676-1 has an unsupported device xc7k160t
Part xc7k160tffg676-2 has an unsupported device xc7k160t
Part xc7k160tffg676-2L has an unsupported device xc7k160t
Part xc7k160tffg676-3 has an unsupported device xc7k160t
Part xc7k160tffv676-1 has an unsupported device xc7k160t
Part xc7k160tffv676-2 has an unsupported device xc7k160t
Part xc7k160tffv676-2L has an unsupported device xc7k160t
Part xc7k160tffv676-3 has an unsupported device xc7k160t
Part xc7k160tifbv676-2L has an unsupported device xc7k160ti
Part xc7k160tifbg484-2L has an unsupported device xc7k160ti
Part xc7k160tifbg676-2L has an unsupported device xc7k160ti
Part xc7k160tifbv484-2L has an unsupported device xc7k160ti
Part xc7k160tiffv676-2L has an unsupported device xc7k160ti
Part xc7k160tiffg676-2L has an unsupported device xc7k160ti
Find pins for xc7k70tfbg484-1
Find pins for xc7k70tfbg676-1
Find pins for xc7k70tfbv484-1
Find pins for xc7k70tfbv676-1
----------------------------------------

@mithro
Copy link
Contributor

mithro commented Dec 7, 2021

make[1]: Entering directory '/tmpfs/src/github/symbiflow-prjxray-presubmit-db-kintex7/fuzzers'
.//run_fuzzer.py 000-init-db
2021-12-07T14:56:38 - xc7k70tfbv676-3/000-init-db               -    0s: Running fuzzer attempt: 0
mkdir -p fuzzer_ok
touch fuzzer_ok/fuzzer_000-init-db_xc7k70tfbv676-3.ok
.//run_fuzzer.py 001-part-yaml
2021-12-07T14:56:38 - xc7k70tfbv676-3/001-part-yaml             -    0s: Running fuzzer attempt: 0
.//run_fuzzer.py 075-pins
2021-12-07T14:56:38 - xc7k70tfbv676-3/075-pins                  -    0s: Running fuzzer attempt: 0
make[1]: Leaving directory '/tmpfs/src/github/symbiflow-prjxray-presubmit-db-kintex7/fuzzers'
source settings/kintex7_325t.sh && make -C fuzzers part_only
Traceback (most recent call last):
  File "/tmpfs/src/github/symbiflow-prjxray-presubmit-db-kintex7/utils/create_environment.py", line 66, in <module>
    main()
  File "/tmpfs/src/github/symbiflow-prjxray-presubmit-db-kintex7/utils/create_environment.py", line 59, in main
    environment = get_environment_variables()
  File "/tmpfs/src/github/symbiflow-prjxray-presubmit-db-kintex7/utils/create_environment.py", line 37, in get_environment_variables
    part_info = get_part_information(db_root, part)
  File "/tmpfs/src/github/symbiflow-prjxray-presubmit-db-kintex7/prjxray/util.py", line 48, in get_part_information
    assert part, "Part {} not found in {}".format(part, part_mapping)
AssertionError: Part None not found in {'xc7k70tfbg484-1': {'device': 'xc7k70t', 'package': 'fbg484', 'speedgrade': '1'}, 'xc7k70tfbg484-2': {'device': 'xc7k70t', 'package': 'fbg484', 'speedgrade': '2'}, 'xc7k70tfbg484-2L': {'device': 'xc7k70t', 'package': 'fbg484', 'speedgrade': '2L'}, 'xc7k70tfbg484-3': {'device': 'xc7k70t', 'package': 'fbg484', 'speedgrade': '3'}, 'xc7k70tfbg676-1': {'device': 'xc7k70t', 'package': 'fbg676', 'speedgrade': '1'}, 'xc7k70tfbg676-2': {'device': 'xc7k70t', 'package': 'fbg676', 'speedgrade': '2'}, 'xc7k70tfbg676-2L': {'device': 'xc7k70t', 'package': 'fbg676', 'speedgrade': '2L'}, 'xc7k70tfbg676-3': {'device': 'xc7k70t', 'package': 'fbg676', 'speedgrade': '3'}, 'xc7k70tfbv484-1': {'device': 'xc7k70t', 'package': 'fbv484', 'speedgrade': '1'}, 'xc7k70tfbv484-2': {'device': 'xc7k70t', 'package': 'fbv484', 'speedgrade': '2'}, 'xc7k70tfbv484-2L': {'device': 'xc7k70t', 'package': 'fbv484', 'speedgrade': '2L'}, 'xc7k70tfbv484-3': {'device': 'xc7k70t', 'package': 'fbv484', 'speedgrade': '3'}, 'xc7k70tfbv676-1': {'device': 'xc7k70t', 'package': 'fbv676', 'speedgrade': '1'}, 'xc7k70tfbv676-2': {'device': 'xc7k70t', 'package': 'fbv676', 'speedgrade': '2'}, 'xc7k70tfbv676-2L': {'device': 'xc7k70t', 'package': 'fbv676', 'speedgrade': '2L'}, 'xc7k70tfbv676-3': {'device': 'xc7k70t', 'package': 'fbv676', 'speedgrade': '3'}}
Makefile:204: recipe for target 'db-part-only-kintex7_325t' failed
make: *** [db-part-only-kintex7_325t] Error 1


[ID: 1446474] Build finished after 197 secs, exit value: 1


Warning: Permanently added 'localhost' (ED25519) to the list of known hosts.
[06:56:39] Collecting build artifacts from build VM
Build script failed with exit code: 1

@jrrk2
Copy link
Author

jrrk2 commented Dec 7, 2021

This is what I get running locally:

jrrk@jonathan-NUC10i7FNK:~/prjxray$ make db-prepare-kintex7


Preparing kintex7 files
============================
Part xc7k160tfbg484-1 has an unsupported device xc7k160t
Part xc7k160tfbg484-2 has an unsupported device xc7k160t
Part xc7k160tfbg484-2L has an unsupported device xc7k160t
Part xc7k160tfbg484-3 has an unsupported device xc7k160t
Part xc7k160tfbg676-1 has an unsupported device xc7k160t
Part xc7k160tfbg676-2 has an unsupported device xc7k160t
Part xc7k160tfbg676-2L has an unsupported device xc7k160t
Part xc7k160tfbg676-3 has an unsupported device xc7k160t
Part xc7k160tfbv484-1 has an unsupported device xc7k160t
Part xc7k160tfbv484-2 has an unsupported device xc7k160t
Part xc7k160tfbv484-2L has an unsupported device xc7k160t
Part xc7k160tfbv484-3 has an unsupported device xc7k160t
Part xc7k160tfbv676-1 has an unsupported device xc7k160t
Part xc7k160tfbv676-2 has an unsupported device xc7k160t
Part xc7k160tfbv676-2L has an unsupported device xc7k160t
Part xc7k160tfbv676-3 has an unsupported device xc7k160t
Part xc7k160tffg676-1 has an unsupported device xc7k160t
Part xc7k160tffg676-2 has an unsupported device xc7k160t
Part xc7k160tffg676-2L has an unsupported device xc7k160t
Part xc7k160tffg676-3 has an unsupported device xc7k160t
Part xc7k160tffv676-1 has an unsupported device xc7k160t
Part xc7k160tffv676-2 has an unsupported device xc7k160t
Part xc7k160tffv676-2L has an unsupported device xc7k160t
Part xc7k160tffv676-3 has an unsupported device xc7k160t
Part xc7k160tifbv676-2L has an unsupported device xc7k160ti
Part xc7k160tifbg484-2L has an unsupported device xc7k160ti
Part xc7k160tifbg676-2L has an unsupported device xc7k160ti
Part xc7k160tifbv484-2L has an unsupported device xc7k160ti
Part xc7k160tiffv676-2L has an unsupported device xc7k160ti
Part xc7k160tiffg676-2L has an unsupported device xc7k160ti
Part xc7k325tiffv676-2L has an unsupported device xc7k325ti
Part xc7k325tiffv900-2L has an unsupported device xc7k325ti
Part xc7k325tifbg676-2L has an unsupported device xc7k325ti
Part xc7k325tifbg900-2L has an unsupported device xc7k325ti
Part xc7k325tifbv676-2L has an unsupported device xc7k325ti
Part xc7k325tifbv900-2L has an unsupported device xc7k325ti
Part xc7k325tiffg900-2L has an unsupported device xc7k325ti
Part xc7k325tiffg676-2L has an unsupported device xc7k325ti
Part xc7k355tiffg901-2L has an unsupported device xc7k355ti
Part xc7k355tiffv901-2L has an unsupported device xc7k355ti
Part xc7k355tffg901-1 has an unsupported device xc7k355t
Part xc7k355tffg901-2 has an unsupported device xc7k355t
Part xc7k355tffg901-2L has an unsupported device xc7k355t
Part xc7k355tffg901-3 has an unsupported device xc7k355t
Part xc7k355tffv901-1 has an unsupported device xc7k355t
Part xc7k355tffv901-2 has an unsupported device xc7k355t
Part xc7k355tffv901-2L has an unsupported device xc7k355t
Part xc7k355tffv901-3 has an unsupported device xc7k355t
Part xc7k410tfbg676-1 has an unsupported device xc7k410t
Part xc7k410tfbg676-2 has an unsupported device xc7k410t
Part xc7k410tfbg676-2L has an unsupported device xc7k410t
Part xc7k410tfbg676-3 has an unsupported device xc7k410t
Part xc7k410tfbg900-1 has an unsupported device xc7k410t
Part xc7k410tfbg900-2 has an unsupported device xc7k410t
Part xc7k410tfbg900-2L has an unsupported device xc7k410t
Part xc7k410tfbg900-3 has an unsupported device xc7k410t
Part xc7k410tfbv676-1 has an unsupported device xc7k410t
Part xc7k410tfbv676-2 has an unsupported device xc7k410t
Part xc7k410tfbv676-2L has an unsupported device xc7k410t
Part xc7k410tfbv676-3 has an unsupported device xc7k410t
Part xc7k410tfbv900-1 has an unsupported device xc7k410t
Part xc7k410tfbv900-2 has an unsupported device xc7k410t
Part xc7k410tfbv900-2L has an unsupported device xc7k410t
Part xc7k410tfbv900-3 has an unsupported device xc7k410t
Part xc7k410tffg676-1 has an unsupported device xc7k410t
Part xc7k410tffg676-2 has an unsupported device xc7k410t
Part xc7k410tffg676-2L has an unsupported device xc7k410t
Part xc7k410tffg676-3 has an unsupported device xc7k410t
Part xc7k410tffg900-1 has an unsupported device xc7k410t
Part xc7k410tffg900-2 has an unsupported device xc7k410t
Part xc7k410tffg900-2L has an unsupported device xc7k410t
Part xc7k410tffg900-3 has an unsupported device xc7k410t
Part xc7k410tffv676-1 has an unsupported device xc7k410t
Part xc7k410tffv676-2 has an unsupported device xc7k410t
Part xc7k410tffv676-2L has an unsupported device xc7k410t
Part xc7k410tffv676-3 has an unsupported device xc7k410t
Part xc7k410tffv900-1 has an unsupported device xc7k410t
Part xc7k410tffv900-2 has an unsupported device xc7k410t
Part xc7k410tffv900-2L has an unsupported device xc7k410t
Part xc7k410tffv900-3 has an unsupported device xc7k410t
Part xc7k410tiffv900-2L has an unsupported device xc7k410ti
Part xc7k410tiffv676-2L has an unsupported device xc7k410ti
Part xc7k410tiffg900-2L has an unsupported device xc7k410ti
Part xc7k410tiffg676-2L has an unsupported device xc7k410ti
Part xc7k410tifbv900-2L has an unsupported device xc7k410ti
Part xc7k410tifbv676-2L has an unsupported device xc7k410ti
Part xc7k410tifbg900-2L has an unsupported device xc7k410ti
Part xc7k410tifbg676-2L has an unsupported device xc7k410ti
Part xc7k420tffg1156-1 has an unsupported device xc7k420t
Part xc7k420tffg1156-2 has an unsupported device xc7k420t
Part xc7k420tffg1156-2L has an unsupported device xc7k420t
Part xc7k420tffg1156-3 has an unsupported device xc7k420t
Part xc7k420tffg901-1 has an unsupported device xc7k420t
Part xc7k420tffg901-2 has an unsupported device xc7k420t
Part xc7k420tffg901-2L has an unsupported device xc7k420t
Part xc7k420tffg901-3 has an unsupported device xc7k420t
Part xc7k420tffv1156-1 has an unsupported device xc7k420t
Part xc7k420tffv1156-2 has an unsupported device xc7k420t
Part xc7k420tffv1156-2L has an unsupported device xc7k420t
Part xc7k420tffv1156-3 has an unsupported device xc7k420t
Part xc7k420tffv901-1 has an unsupported device xc7k420t
Part xc7k420tffv901-2 has an unsupported device xc7k420t
Part xc7k420tffv901-2L has an unsupported device xc7k420t
Part xc7k420tffv901-3 has an unsupported device xc7k420t
Part xc7k420tiffv901-2L has an unsupported device xc7k420ti
Part xc7k420tiffv1156-2L has an unsupported device xc7k420ti
Part xc7k420tiffg901-2L has an unsupported device xc7k420ti
Part xc7k420tiffg1156-2L has an unsupported device xc7k420ti
Part xc7k480tiffv901-2L has an unsupported device xc7k480ti
Part xc7k480tiffv1156-2L has an unsupported device xc7k480ti
Part xc7k480tiffg901-2L has an unsupported device xc7k480ti
Part xc7k480tiffg1156-2L has an unsupported device xc7k480ti
Part xc7k480tffv901-1 has an unsupported device xc7k480t
Part xc7k480tffv901-2 has an unsupported device xc7k480t
Part xc7k480tffv901-2L has an unsupported device xc7k480t
Part xc7k480tffv901-3 has an unsupported device xc7k480t
Part xc7k480tffv1156-1 has an unsupported device xc7k480t
Part xc7k480tffv1156-2 has an unsupported device xc7k480t
Part xc7k480tffv1156-2L has an unsupported device xc7k480t
Part xc7k480tffv1156-3 has an unsupported device xc7k480t
Part xc7k480tffg901-1 has an unsupported device xc7k480t
Part xc7k480tffg901-2 has an unsupported device xc7k480t
Part xc7k480tffg901-2L has an unsupported device xc7k480t
Part xc7k480tffg901-3 has an unsupported device xc7k480t
Part xc7k480tffg1156-1 has an unsupported device xc7k480t
Part xc7k480tffg1156-2 has an unsupported device xc7k480t
Part xc7k480tffg1156-2L has an unsupported device xc7k480t
Part xc7k480tffg1156-3 has an unsupported device xc7k480t
Find pins for xc7k325tfbg676-1
Find pins for xc7k325tfbg900-1
Find pins for xc7k325tfbv676-1
Find pins for xc7k325tfbv900-1
Find pins for xc7k325tffg676-1
Find pins for xc7k325tffg900-1
Find pins for xc7k325tffv676-1
Find pins for xc7k325tffv900-1
Find pins for xc7k70tfbg484-1
Find pins for xc7k70tfbg676-1
Find pins for xc7k70tfbv484-1
Find pins for xc7k70tfbv676-1

Perhaps there is a problem getting the license for non-webpack parts ?

@mithro
Copy link
Contributor

mithro commented Dec 7, 2021

The CI system only currently has access to WebPack parts.

@mithro
Copy link
Contributor

mithro commented Dec 7, 2021

Is the xc7k325 part a non-webpack part?

@mithro
Copy link
Contributor

mithro commented Dec 7, 2021

Looks like only Kintex®-7 FPGA: • XC7K70T, XC7K160T are supported by the WebPack version.

@jrrk2
Copy link
Author

jrrk2 commented Dec 8, 2021

Perhaps we need two X-Ray databases, one that can be generated from WebPack, another (for larger parts) that has to be generated by owners of suitable boards (that come with an unlimited number of node-locked and device-locked threads). Another way would be to affiliate with an academic institution that has access to bulk licenses. Meanwhile, I will try and get a bitstream running on a real board to see if we have something usable.

@jrrk2
Copy link
Author

jrrk2 commented Dec 8, 2021

I committed my new database here (https://github.com/jrrk2/prjxray-db/tree/k325). I suppose that means that eventually anybody can use this part license-free.

GitHub
Project X-Ray Database: XC7 Series. Contribute to jrrk2/prjxray-db development by creating an account on GitHub.

@jeremyherbert
Copy link

jrrk2 makes a good point here; for example, the 7k325t and 7k420t dev kits are actually cheaper on aliexpress than the 7k160t. I suspect this because the larger parts are more popular in the supply chain, and 160t can fetch a higher price as the latest webpack can be used.

Using these parts without a vivado license is actually a major reason I am interested in the open source FPGA tooling.

@jrrk2
Copy link
Author

jrrk2 commented Dec 9, 2021

Furthermore the 7k325t part is used in the frequently encountered KC705 board from Xilinx and the Genesys2 board from Diligent. The latter comes with a Vivado node/device-locked license which may be used to generate the open-source database.

@mithro
Copy link
Contributor

mithro commented Dec 15, 2021

I'm very close to being able to access our license server on our Kokoro system.

@jrrk2
Copy link
Author

jrrk2 commented Dec 15, 2021

Thanks for the heads-up but this will not take us much further forward unless support is added for kintex7 in the symbiflow-arch-defs repo. I'm not familiar with CMake config files nor can I find any documentation on how to do this. In addition the Python support seems to be Ubuntu/Debian specific. I tried it on Fedora-35 and it didn't work.

@mithro
Copy link
Contributor

mithro commented Dec 15, 2021

@jrrk2 Did you log a bug about it not working on Fedora-35 somewhere?

@mithro
Copy link
Contributor

mithro commented Dec 15, 2021

@jrrk2 - @acomodi was providing some guidance for the Spartan 7 part @ #1789 (comment)

@MidsummerNight
Copy link
Contributor

Kintex 7 failed really fast. First make --dry-run and source settings/kintex7.sh && make -C fuzzers ran without actually running any fuzzers, then source settings/kintex7_325t.sh && make -C fuzzers part_only failed, which seems to be caused by make failing to find xc7k325t amongst a list consisted only of xc7k70t parts. My initial guess is some Makefiles aren't written correctly, haven't looked into it yet though.

@mithro
Copy link
Contributor

mithro commented Dec 24, 2021

Could the change to https://github.com/SymbiFlow/prjxray/pull/1794/files#diff-2aea961e96499d96f980a17a1110978f3bf66bcc1e4ec1e772aaec71f6932614 be breaking the xc7k70t part? All the other changes should only affect the xc7k325 if I understand them correctly?

GitHub
I followed the guide to add new parts, more or less, some experimental features had to be commented out. No validation on real hardware has been done, this is just to establish if the pull request ...

@mithro
Copy link
Contributor

mithro commented Dec 24, 2021

I'm a little unclear here, but it seems like the xc7k70 needs the orphan_int_column fuzzer but is not compatible with the dsp_int fuzzer, while the xc7k325 does work with the dsp_int fuzzer?

@mithro
Copy link
Contributor

mithro commented Dec 24, 2021

(FYI - I sent #1811 to be a bit clearer about this section of the Makefile.)

@jrrk2
Copy link
Author

jrrk2 commented Dec 24, 2021

Perhaps this anomaly would be explained by the DSP location limits being wrong in the environment configuration file ?

@mithro
Copy link
Contributor

mithro commented Dec 28, 2021

In order to test if the DSP fuzzer really is broken on Kintex7 (apart from the new part addition), I created #1816

@mithro
Copy link
Contributor

mithro commented Jan 6, 2022

As #1811 was passing, it has been merged. I rebased this pull request onto the merge and are now rerunning the CI to see if we still get the xc7k70tfbg676-2/051-pip-imuxlout-bypalts failure....

@mithro
Copy link
Contributor

mithro commented Jan 6, 2022

With the current limited set of changes, I don't see any reason that this change should affect the runs for the xc7k70tfbg676-2 parts which currently should pass.

@mithro
Copy link
Contributor

mithro commented Jan 12, 2022

2022-01-07T04:12:35 - xc7k325tffg900-2/005-tilegrid              - 1h15m: + /tmpfs/src/github/symbiflow-prjxray-presubmit-db-kintex7/build/tools/bitread --part_file /tmpfs/src/github/symbiflow-prjxray-presubmit-db-kintex7/database/kintex7/xc7k325tffg900-2/part.yaml -F 0x00000000:0xffffffff -o design.bits -z -y design.bit

2022-01-07T04:12:35 - xc7k325tffg900-2/005-tilegrid              - 1h15m: + python3 /tmpfs/src/github/symbiflow-prjxray-presubmit-db-kintex7/fuzzers/005-tilegrid/clb/../fuzzaddr/generate.py --oneval 1 --design params.csv --dword 0 --dframe 0

2022-01-07T04:12:35 - xc7k325tffg900-2/005-tilegrid              - 1h15m: make[2]: *** [run] Error 2

2022-01-07T04:12:35 - xc7k325tffg900-2/005-tilegrid              - 1h15m: 

2022-01-07T04:12:35 - xc7k325tffg900-2/005-tilegrid              - 1h15m: --------------------------------------------------------------------------

2022-01-07T04:12:35 - xc7k325tffg900-2/005-tilegrid              - 1h15m: !Failed! @ 2022-01-07T04:12:35.091602 with exit code: 2

2022-01-07T04:12:35 - xc7k325tffg900-2/005-tilegrid              - 1h15m: --------------------------------------------------------------------------

2022-01-07T04:12:35 - xc7k325tffg900-2/005-tilegrid              - 1h15m: WARNING: Fuzzer failed!

Makefile:91: recipe for target '005-tilegrid/run.xc7k325tffg900-2.ok' failed

make[1]: *** [005-tilegrid/run.xc7k325tffg900-2.ok] Error 2

make[1]: *** Waiting for unfinished jobs....

Signed-off-by: Jonathan Kimmitt <jonathan@kimmitt.uk>
Signed-off-by: Tim 'mithro' Ansell <tansell@google.com>
@hansfbaier
Copy link
Collaborator

The Kintex 325T support isn't really experimental anymore and has proven to work quite reliably.
So the title should be changed.
Unfortunately it looks like @jrrk2 currently does not actively develop this.
So we are waiting for the merge.

@jrrk2
Copy link
Author

jrrk2 commented Mar 29, 2023

I don’t have that hardware any more but if there is anything I can do ?

@hansfbaier
Copy link
Collaborator

@jrrk2 Could you change the title (remove 'experimental')

@jrrk2 jrrk2 changed the title Experimental Kintex7 xc7k325 support Kintex7 xc7k325 support Mar 29, 2023
@hansfbaier
Copy link
Collaborator

@jrrk2 Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

6 participants