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.

TLK10031: TLK10031 Auto Negotiation When Only Capable of 1G-KX

Part Number: TLK10031

We designed a circuit with the TLK10031 PHY that will be used for a VPX Ultra-thin Pipe, thus we will use 1G-KX mode only.   Can the TLK10031 be configured to operate in 1G-KX mode only, but still support auto negotiation?   The idea is that, during auto negotiation, we would report to the mating UTP device that we support 1G mode only.

  • Hi,

    See below datasheet table with TLK10031 operating modes supported. The closest mode available is dual 10G-KR/1G-KX with auto-negotiation.

    Thanks,

    Rodrigo Natal

  • Thank you Rodrigo.  I'm assuming that, if we we're operating in "10G-KR/1G-KX with auto negotiation" mode, the TLK10031 would set its mode based on the mating device.  In other words, if the mating device was 10G then our PHY would set itself for 10G.  Likewise if the mating device was 1G.  Is this correct?

    Note that our TLK10031 circuit is configured for 1G Ethernet only.  We would like to enable auto negotiation as a 1G device only.  It seems that this would be a legitimate scenario.  When negotiating with the mating device we would report to it that we're 1G only, and that device would then set itself to 1G.   Please let us know if there's any way to set up our TLK10031 to do this.

  • I'm assuming that, if we we're operating in "10G-KR/1G-KX with auto negotiation" mode, the TLK10031 would set its mode based on the mating device.  In other words, if the mating device was 10G then our PHY would set itself for 10G.  Likewise if the mating device was 1G.  Is this correct?

    That is correct. 

    We would like to enable auto negotiation as a 1G device only

    Fixed 1G with auto-neg is not supported, only 10G/1G with auto-neg. To me, it seems like the 10G/1G with auto-neg mode should work for you.

    Thanks,

    Rodrigo