07-31-2018 08:12 AM
I would like to be able to classify .mcs files on hand with respect to their intended (designed for) devices. I have already checked the document UG470 (7-Series device configuration guide). There, I have located the sample XC7K325T bitstream (on page 105) and the value written to IDCODE register was suggested to be the device ID. However, when I have tested with various different speed grades and classes, I observed that the resulting device ID is again the same.
Example: I have tried with following devices:
And for all I obtained following device ID: 03651093.
Due to constraints I had, I couldn't try devices with different pin count.
Is there a better way to extract this information? Possibly a more precise one?
07-31-2018 11:34 AM
for my own interest
can I ask why ?
07-31-2018 10:54 PM
08-01-2018 03:05 AM
For evil purposes :)
Actually, now I am working on a programming utility, which will program a SPI flash with configuration file for the FPGA. Somehow, I can choose/try to upload wrong file to the flash. To prevent accidents like that, I would love to be able to see whether .mcs file on hand is compatible with the accompanied chip or not.
Also, it would be cool if I can see whether this config file (generated by Xilinx) is compatible with the flash I have or not as well.
Reason why I don't use tools from Xilinx and design my own is to be faster (transferring the bitstream through another interface rather than JTAG).
08-01-2018 03:08 AM
I should try to explain my question with different wording. I have some .mcs files (generated with Vivado 2017.2 let's say) and I would like to be able to see whether it is for the FPGA chip I have or not.
08-01-2018 05:29 AM - edited 08-01-2018 05:29 AM
try to program the board would seem the easy choice,
08-05-2018 11:38 PM