Part Number: AFE7444EVM
We are working on the AFE7444EVM with the KCU105 and hence the corresponding refrence design. There are three user constraint files in our understanding (KCU105.xdc, KCU105_io_TI.xdc, KCU105_io.xdc).
There are lines connecting physical pins to the the rxp lines (rxp_in) however the pin connections for the txp lines are not present.
I have contacted our firmware support team regarding this. Please give me until Friday to get back.
We are glad that we were able to resolve this issue, and will now proceed to close this thread.
If you have further questions related to this thread, you may click "Ask a related question" below. The newly created question will be automatically linked to this question.
In reply to Vijayendra Varma Siddamsetty:
Here is the response I got from our firmware team:
"Generally we don’t have to specify the SERDES line pins. These are hard blocks in the FPGA and will have a dedicated pin. So when we use the JESD IP or the Transceiver IP, Vivado knows which transceiver pins are used. It need not be specified explicitly. To verify this you may open the IO Planning window of the Synthesized design. Note the lane swap between the JESD PHY IP (jesd204_phy_0) and the JESD204 Base IP (jesd204_tx & jesd204_rx). This accounts for the lane swap between the Transceiver EVM and the KCU platform."
With reference to the reference design, the DAC or the tx lines of the JESD interface are not connected (we checked the IO planning window of the synthesized design). This is making us weary about the reference design provided in terms of whether it will work or not. May I ask you to please have a look and provide us a fully working reference design.
Thanks for your support,
In reply to SM:
Which version of Vivado are you using to open this reference design? This is a Vivado 2016.1 project.
We have sometimes noticed that the inferred SERDES lane mapping shows up only after Implementation. Moreover, the reference design was validated to be working with the AFE74xx EVM GUI at 2x44210. You can proceed with the design without concerns. If you would prefer to have the SERDES lanes explicitly specified, you can add the attached constraints as a separate XDC or append to an existing file.”
Note:- Between the AFE74xx EVM and the KCU105, there is SERDES lane inversion on the first four TX and RX Lanes. The AFE74xx EVM GUI inverts the TX lanes and hence this inversion is not applied in the Reference design on the TX SERDES lanes, but this is required and hence implemented on the RX Lanes.
Thank you for your input. Will study further and revert.
All content and materials on this site are provided "as is". TI and its respective suppliers and providers of content make no representations about the suitability of these materials for any purpose and disclaim all warranties and conditions with regard to these materials, including but not limited to all implied warranties and conditions of merchantability, fitness for a particular purpose, title and non-infringement of any third party intellectual property right. No license, either express or implied, by estoppel or otherwise, is granted by TI. Use of the information on this site may require a license from a third party, or a license from TI.
TI is a global semiconductor design and manufacturing company. Innovate with 100,000+ analog ICs andembedded processors, along with software, tools and the industry’s largest sales/support staff.