Dear Dani,
We do not have FMC204 on FMC2 unfortunately. You would need to modify star_lib\sip_fmc204\sip_files\sip_fmc204_vc707_0.ucf and change the physical mapping. In a stellarIP point of view one would create a sip_fmc204_vc707_1.ucf based on sip_fmc204_vc707_0.ucf. The new UCF should have updated "LOC=" to reflect FMC2 and also all the _0 in the UCF should be replaced with _1. As an example, DAC0_DCLK_N_0 becomes DAC0_DCLK_N_1.
Then you can modify the sdf file in the implement folder. Typically for the VC707-FMC204 (firmware 352):
1) The star declaration area should have a change related to sip_fmc204 ( this will make StellarIP to use your new fragment, sip_fmc204_1.ucf )
--STAR sip_fmc204 , ID=0 , FILE=sip_fmc204\sip_files\sip_fmc204_v7.lst; (remove)
++STAR sip_fmc204 , ID=1 , FILE=sip_fmc204\sip_files\sip_fmc204_v7.lst; (add)
2) All sip_fmc204.0 occurences in the file should be replaced with sip_fmc204.1.
Example:
--sip_cmd12_mux.0(cmd4_in) <= sip_fmc204.0(cmd_out);
++ sip_cmd12_mux.0(cmd4_in) <= sip_fmc204.1(cmd_out);
It would be easy to simply add FMC116 star in there which will default to FMC1. Then you can simply redesign your data paths and you will have your firmware supporting FMC204 and FMC116
We don't have Vivado support yet, well we do have it but we are busy converting millions of UCF towards XDC...
I hope that helps!
Best Regards,
Arnaud