This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

TLK1501: TLK1501

Part Number: TLK1501

My board has two tlk1501 and SFP Fiber channels , and I test internal loopback and Transmit / Receive through a single fiber for each of them separatley , both of them can work normally, including hot-plug function as well. But when I  excutive data communication between them, I will randomly have the data bit error each time after power on, for example, I send 16'h8000 at channel_A, but get 16'h0030 on the RXD on channel_B , or other value different from the source data, there is about 30% percent that you will encounter this problem.

I use a FPGA to control two fiber channels, and give the same 50Mhz TX_CLK signal from fpga internal PLL output.

And I find a strange issue when I take the communication between the two fiber channels,  from the TLK1501 datasheet,we know that the RX_CLK is derived from the input serial data stream, but if I pull out the fiber , I still can measure the RX_CLK  signal by oscilloscope, is this normal?

  • Dachao Zhang,

    Your situation is not normal. See below for some follow up questions to your issue. 

    • Could you provide a simple block diagram of the system and the test you are using?
    • Do you have both TLK1501 transmitting and receiving or is one a transmitter and one a receiver? 
    • Is the LCKREFN pin low or high when you see this issue?
    • Does the FPGA provide a clean clock with low jitter? 
    • What do you see on the RX_ER/ PRBS_PASS and RX_DV/ LOS pin when the data received does not match the source? When measuring RX_CLK with no fiber connection, what is the Vpp of the signal? Is this on the transmitting or receiving TLK1501? 

  • Dachao Zhang,

    Is there any more support needed for this issue? If so please reply with any relevant details so that I can further assist you. For now I will be marking this thread as "TI Thinks Resolved".