Hi,
We have a Xilinx VC707 with FMC110, and we are using the 4DSP reference design CD243.
Using the original reference design files, we can generate the .XISE project using the 4FM GUI Control App, and we can synthesize, implement, and generate the programming .BIT file in Xilinx ISE 14.2. Then, we are able to run the provided Fmc110App.exe, and we see the correct CID 243.
We made some changes to some of the reference design files (no updates to the top-level constellation, star, nor wormhole files, though), and after generating the .XISE project and the programming .BIT file using the same tools, when we run the provided Fmc110App.exe, we get a CID of 63 now.
We modified the Fmc110App.exe test program to "accept" a CID of 63, but then we receive several errors when the Fmc110App.exe test program tries to read star offsets, temperatures, voltages, etc. and detect the FMC110 hardware (it cannot).
It looks like cid_package.vhd contains constant values for CID, SW/FW build versions, etc., which seems to explain the CID 63 that the Fmc110App.exe test program is reading back, but this is also the original, unedited cid_package.vhd file, so it is identical to the file in the original reference design.
When we look at vc707_fmc110.h (in output\vc707_fmc110), I do see the CID defined as 0xF3=243, and the SW build verison as non-zero. How is this file generated? By the 4FM GUI Control App?
Thus, it looks like the test program reads back CID 63 with the changed design .BIT file and CID 243 with the reference design .BIT file. Both cid_package.vhd and vc707_fmc110.h are the same in these constants, so it seems like there is something else causing the different behavior.
Please help. Do you have any ideas/suggestions on what/why this might be? How do the CID and FW/SW versions get set when the cid_package.vhd file contains fixed constants?
Thank you!