08-13-2019 09:32 AM
We have a board which uses the xc7k325. The .bit file we have is meant for a xq7k325. Previously, we programmed this FPGA with Impact 14.7 without problems. When programming with Impact 14.7, it notifies the user of the difference but still successfully programs the FPGA. However, Vivado gives us the "Unsupported part xq7k325tr900" message when trying to program. Why can Impact 14.7 program the FPGA but not Vivado? How can we get Vivado to successfully program the FPGA despite the apparent incompatibility?
08-13-2019 11:21 AM
08-14-2019 07:53 AM
It's not recommended to use same bitstream file for different grade (for example: commercial and Industrial grade) FPGA device even though it is working for you. As this can cause timing issues on hardware.
You should regenerate bitstream for your design according to your device.
This https://www.xilinx.com/support/answers/24245.html and https://www.xilinx.com/support/answers/54561.html answer records might provide you some idea about timing variation between different grade of FPGA.
08-14-2019 08:10 AM - edited 08-14-2019 08:11 AM
However, Vivado gives us the "Unsupported part xq7k325tr900" message when trying to program. Why can Impact 14.7 program the FPGA but not Vivado? How can we get Vivado to successfully program the FPGA despite the apparent incompatibility?
In which category does this part xq7k325tr900 fall into? I mean Xilinx 6 series, 7 series, etc?
To me it looks like a "less than 7 series FPGA" since it could be successfully programmed using ISE14.7/Impact.
Now Vivado is meant to be used for Xilinx 7 series FPGAs and higher-class FPGA families. This might be the reason why Vivado refuses to recognize the part xq7k325tr900.
08-15-2019 01:27 PM
08-15-2019 02:12 PM
I'm using Vivado 2018.3. Unfortunately, I didn't generate the bit file because the code was written years ago by a different company. The source code also is not available. I just have to work with what I have. The parameter change might work.
08-15-2019 02:20 PM