Author Topic: TE0803 + TEBF0808, WRONG Polarity on FMC  (Read 136 times)

htala

  • Active Member
  • *
  • Posts: 2
TE0803 + TEBF0808, WRONG Polarity on FMC
« on: August 20, 2019, 11:51:49 PM »
Hi, I noticed flipped polarity on some connections on FMC-FPGA connections like this:

TE0803 + TEBF0808

Conn Pin nameDesig.PinCarrier Net Namepin cpin mModule Net NameFPGA Pin
FMC-LA24_PJ5H28B65_L17_PJ4-19J4-19B65_L20_NH6
FMC-LA24_NJ5H29B65_L17_NJ4-17J4-17B65_L20_PJ6

And I want to use this signal for differential clock, How can I?

JH

  • Hero Member
  • *****
  • Posts: 942
Re: TE0803 + TEBF0808, WRONG Polarity on FMC
« Reply #1 on: August 21, 2019, 04:34:29 PM »
Hi,
polarity is swapped sometimes for better signal routing. Correct polarity is this one of the symbol pin name of the SoC. You can change polarity easy in your design.

For CLK polarity is in the most cases no matter.
But you need CLK input Pin to get CLK directly into the CLK routing resources of the SoC:
https://www.xilinx.com/support/documentation/user_guides/ug572-ultrascale-clocking.pdf
Xilinx U+ Zynq Pin definition, see:
https://www.xilinx.com/support/documentation/user_guides/ug575-ultrascale-pkg-pinout.pdf
or
https://www.xilinx.com/support/documentation/user_guides/ug1075-zynq-ultrascale-pkg-pinout.pdf


Route CLK over fabric into CLK routing resources of the SoC is also possible, but in this case tools has problems to calculate timings . It's not recommended and in case you still do it you must set some constrain attribute to allow vivado to do this otherwise you get an error. See Xilinx documentation.

br
John

htala

  • Active Member
  • *
  • Posts: 2
Re: TE0803 + TEBF0808, WRONG Polarity on FMC
« Reply #2 on: September 01, 2019, 09:49:03 AM »
What about GTH clock signals for  JESDI204B which is connected to IBUFDS_GTE4 ?
Isn’t clock polarity important here?

JH

  • Hero Member
  • *****
  • Posts: 942
Re: TE0803 + TEBF0808, WRONG Polarity on FMC
« Reply #3 on: September 02, 2019, 08:03:39 AM »
Hi,

why? It's a phase offset of 180°. In the most cases receiver and transceiver ref clk is not from the same crystal so you has still an offset  when you start and  and you always have a slight drift.
Receiver will make CLK recovery to align data. It is important that the accuracy of the reference CLK is within the required range.
In case data path of the lanes are swapped, you can easy invert (some protocols does it automatically). In case of JED IP core, enable debug pins and invert manually if necessary.


br
John