--- Quote Start ---
1-What are you looking to test? The transceivers?
Yes, the main purpose is to to test transceivers, in particular with the Altera PHY IP cores. But besides these, I want to know how to create a design for two boards to communicate one another using some simpler protocol than the PHY IP cores. The data rate can be any not greater than 11.3Gbps
--- Quote End ---
Unfortunately, there are lots of protocols, and lots of reasons for selecting a specific one. What is your final application? Are you going to be having FPGAs communicating with FPGAs, or do you need to interface with a 10G switch, or a Serial RapidIO switch, or SATA drives, or ... etc etc?
--- Quote Start ---
2-What have you tried so far?
I have tried to test XCVR with On-chip debugging design examples provided by Altera. Then I created similar designs with Lowlatency and Custom PHY for various data rates using Qsys. However, I would like to have a 10Gbase-r PHY design and I could not create this in Qsys. I don't know if it is possible to create such design by using available components in Qsys.
--- Quote End ---
What have you managed to test? Have you only tried these in hardware, or have you simulated them in Modelsim?
--- Quote Start ---
3-Do you know how to configure the ALTGX and ALGX_RECONFIG components?
I have general idea about the ALTGX and ALTGX_RECONFIG but have not ever used these as I want to try designing with Qsys first.
--- Quote End ---
You're doing things in reverse. Qsys is a
convenience for connecting components. For a successful system design, you need to
understand how these components work. For that understanding, you should start by configuring an ALTGX, an ALTGX_RECONFIG, create a reset controller, and then get them working in simulation and hardware. Use SignalTap II to trace that the hardware does what the simulation does (it doesn't, but the handbook tells you the difference - the key is being able to see and understand the differences). Since all other components are based on these two components, this will give you a fundamental understanding of how the interfaces work.
--- Quote Start ---
4-What do you have in addition to the GT boards? Do you have break out cables? A synthesizer to provide a common clock between the boards?
I have SMA cables for physical connection between the two boards. For a synthesizer to provide the common clock, if you can make this clearer?
--- Quote End ---
If one board uses a 156.25MHz reference that is actually a few kHz high, and the other board uses a reference that is a few kHz low, then one board will send data to the other
faster than ideal. The clock-and-data recovery (CDR) in the receiver will track the higher frequency, however, if you use a FIFO to cross clock domains between the recovered clock and the local clock, you will eventually get a FIFO overrun (or underrun in the case of a slower transmitter). Protocols like 10G take care of this by having protocol codes that can be added or deleted. If you are implementing FPGA-to-FPGA communications, then the system becomes simpler if you use a
synchronous reference. You can implement this reference using an external synthesizer and send a copy of the signal to each board, or you can use one of your boards as the clock source and the other can receive a clock from the first, and use it for clocking its receiver logic.
To understand what I am talking about, configure an ALTGX transmitter with one reference frequency (156.25MHz + something), and an ALTGX receiver with another frequency (156.25MHz - something), and
simulate it using Modelsim.
If you don't know how to use Modelsim, its time to learn :)
Ask questions, and I'll try to help.
Cheers,
Dave