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: several questions of TLK1501

Part Number: TLK1501


Hi dear supporting team,

my customer has several questions on TLK1501, as attached red font, could you help on that? tks a lot! TLK1501 questions.docx

  • Hi Vera,

    We are working on this. ASAP I will be back with the answers.

    Thanks,

    Luis Omar Moran

    High Speed Interface

    SWAT Team

  • Question 1:TLK1501 TX side IDLE1、IDLE2 code is controlled by the pin or not?
    As shown in Figure 7 of the TLK1501 datasheet, the device will transmit IDLE and ignore the TX_EN/TX_ER pins if the receive state machine is not in the SYNC state. Once the device sees a consistent byte boundary control is returned to the TX_EN/TX_ER pins. This lets a customer tie TX_EN high while still providing IDLE’s for the remote receiving device to perform byte alignment.

    Question 2.
    1)Then is it aligned with standard that at ACQ status getting 1 valid data or 1Error Propagation(K30.7)will get into SYNC status?
    Yes, the SYNC machine is waiting for 1 Valid data or Error Propagation (K30.7).

    2)in check status,how about the output of RX_DV、RX_ER、RXD?
    In the CHECK status, the state machine is looking for valid code, if this is got, the link is re-established if not, is waiting for 3 invalid code and the link is lost.

    b)at ACQ status, could we guarantee when the corresponding side receiving 3 continuous K28.5 negative code to get into SYNC status?
    Yes, the devices was designed to when is in the ACQ status, upon receiving 3 consecutive IDLEs or carrier extend, the state machine enters to SYNC status.

    d)is there a rule on that during initial status, SERDES need send K28.5 negative code?
    There typically aren’t any issues with only sending IDLE during initial link up. As long as the BER is acceptable the link should continuously send data as expected.

    For the other questions, please let me check with the team, ASAP I'm back with the feedback, we are working on this.

    Thanks,
    Luis