is it possible to use AD-FMCDAQ2-EBZ with ml605 or other virtex6 carrier boards or there are some limitations (like voltage, number of serial lanes ecc...) that prevent this configuration?
The biggest limitation of this board is its age, in other words, it's too old. All the reference designs for the AD-FMCDAQ2 are made on Vivado, this tool is not supporting the ML605 or any other 6th series Xilinx FPGA.
Currently we are supporting these boards: zc706, kc705 and kcu105. Or you can port to any other, at least 7 series FPGA development board, which has an HPC connector which can support at least eight transceiver lanes.
The answer for your second question, is yes. But once again, to port this design to an older tool, which supports Virtex 6, will require too much effort and I doubt that will worth it.
other (related) question: if we have a fmc virtex 6 carrrier with 4 GT on FMC connector, is still possible in theory to use (verifiying to have right required lanes) the AD-FMCDAQ2-EBZ selecting only ONE adc and ONE dac (halfing the number of communication lanes)?
I moved this post to the FPGA reference design community, hopefully someone here can help with your questions.
do you know if
Xilinx Zynq®-7000 All Programmable SoC Mini-ITX Development Kit
is supported (it seems quite similar to kc706)?
It's not supported as it is in the moment, but as you said, it has the same FPGA as the ZC706. To port the design for the ZC706 to Mini-ITX it's quite strait forward (you need to redefine the physical constraints), and we can help with that.
Just a note on the ML605 & V6.
The V6 devices do support DAQ2.
You can very well use Virtex 6-- there is nothing wrong with it. The ML605 has all 8 lanes populated on HPC (though they can only run up to 5G), you can also switch to another V6 device and use GTH (10Gbps).
What Istvan meant by "support" is lack of our reference designs. We do NOT have a reference design on V6 devices. That is simply because we were unable to maintain two different tools (especially these tools). It doesn't mean one can not use V6 devices on DAQ2.
Retrieving data ...