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

add kintex7 GTX site_type json #4

Merged
merged 1 commit into from
Jan 17, 2025
Merged

add kintex7 GTX site_type json #4

merged 1 commit into from
Jan 17, 2025

Conversation

lgl1227
Copy link

@lgl1227 lgl1227 commented Jan 17, 2025

I refer to vivado Device to export the GTX part of the xlsx file and convert it to site_type.json through the py script to complete the lack of GTX in the kintex7 series.
image

In addition, I also found a problem. The wire_intents.json in the kintex7 and artix7 folders seems to be the same. However, i think kintex7's wire_intents.json should be incorrect, at least there is no description of RIOI, RIOB18, etc.

@hansfbaier hansfbaier merged commit b6e9f26 into openXC7:master Jan 17, 2025
@hansfbaier
Copy link

OK, many thanks for the contribution!
I am also currently working on Kintex support, but focusing at prjxray at the moment.
I also have mostly complete fuzzers for GTXE2_COMMON and GTXE2_CHANNEL.
Please coordinate with me to avoid duplicate effort.

@lgl1227
Copy link
Author

lgl1227 commented Jan 17, 2025

I see.
I also followed the prjxray project and found this repository
https://github.com/openXC7/db-workspace-for-kintex7, I discovered your support work for kintex.
I am now more concerned about the source of the files in nextpnr-xilinx-meta. The project says it is derived from the vivado GUI through a tcl script.
However, I didn't find this script.I want to fix the nextpnr-xilinx-meta/kintex7/wire_intents.json file

@lgl1227
Copy link
Author

lgl1227 commented Feb 6, 2025

OK, many thanks for the contribution! I am also currently working on Kintex support, but focusing at prjxray at the moment. I also have mostly complete fuzzers for GTXE2_COMMON and GTXE2_CHANNEL. Please coordinate with me to avoid duplicate effort.

hi, Would you mind sharing the complete versions of these fuzzers (GTXE2_COMMON、GTXE2_CHANNEL ) so that I can test some GTX cases? I’d be happy to coordinate efforts to avoid any duplicate work.

@hansfbaier
Copy link

Hello, the fuzzers are in this branch:
https://github.com/openXC7/prjxray/tree/gtx-support
And the ongoing nextpnr-xilinx implementation (work in progress!) is here:
https://github.com/openXC7/nextpnr-xilinx/tree/gtx-support

@hansfbaier
Copy link

Please consider this merge request:
f4pga/prjxray#2494

@lgl1227
Copy link
Author

lgl1227 commented Feb 7, 2025

Hello, the fuzzers are in this branch: https://github.com/openXC7/prjxray/tree/gtx-support And the ongoing nextpnr-xilinx implementation (work in progress!) is here: https://github.com/openXC7/nextpnr-xilinx/tree/gtx-support

Thank you very much for providing the fuzzers for GTXE2_COMMON and GTXE2_CHANNEL! I really appreciate your help. I will proceed with testing and coordination based on the versions you shared.

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

Successfully merging this pull request may close these issues.

2 participants