• State
  • Locked Locked
  • Replies 1 reply
  • Subscribers 33 subscribers
  • Views 283 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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: Support needed with TLK10031

Kristoffer Stenberg
Intellectual 1855 points
Part Number: TLK10031

Hi,

we are configuring the TLK10031 as 10GBASE-R rather than the default 10GBASE-KR like so: 

metnet60_cl45++ w c 0x1e 0x0000 0x8610 # 1.Reset Device
metnet60_cl45++ w c 0x07 0x0000 0x2000 # 3. Disable ANEG
metnet60_cl45++ w c 0x01 0x0096 0x0000 # 4. Disable Link Training
metnet60_cl45++ w c 0x1e 0x8020 0x03ff # 5. KR training settings
metnet60_cl45++ w c 0x1e 0x0004 0xd500 # 6. Fix FCS errors
metnet60_cl45++ w c 0x1e 0x000e 0x0008 # 7. Issue Data path reset

Although this works 99.9% of the time, we are occasionally seeing failures on the XFI -> XAUI path; which is usually fixed by re-issuing step 7 above - issue a data path reset.

I was wondering if you could first tell me if the above configuration for 10GBASE-R is correct - as the details of how to do this were gleaned from TI's support forum NOT the datasheet: https://e2e.ti.com/support/interface/f/138/p/718212/2677661?tisearch=e2e-sitesearch&keymatch=TLK10031#2677661

Could there be something else we are not quite doing correctly?

With Regards,
Kris

  • 0
    TI__Mastermind 19185 points

    As per the product datasheet: The TLK10031 device can be used to convert between XAUI (on the low speed port) and 10GBASE-R signaling (on the high speed port). The high speed side of the device meets the requirements of the 10GBASE-KR physical layer standard for 10 Gbps data transmission over a PCB backplane. The device can also be used for optical physical layers (like 10GBASE-SR or 10GBASE-LR) by interfacing to optical modules requiring SFI or XFI electrical signaling. For optical use cases, KR-specific features like Clause 73 auto-negotiation and link training should be disabled.

     

    Based on your procedure both KR and link training are being disabled, so I expect it should work. Based on evaluation feedback obtained via direct email, I would suggest trying the below slightly modified routine to see whether it eliminates the problem.

     

    metnet60_cl45++ w c 0x1e 0x0000 0x8610 # 1. Reset Device
            metnet60_cl45++ w c 0x07 0x0000 0x2000 # 3. Disable ANEG
            metnet60_cl45++ w c 0x01 0x0096 0x0000 # 4. Disable Link Training
            metnet60_cl45++ w c 0x1e 0x8020 0x03ff # 5. KR training settings
            metnet60_cl45++ w c 0x1e 0x0004 0xd500 # 6. Fix FCS errors
            metnet60_cl45++ w c 0x1e 0x000e 0x0008 # 7. Issue Data path reset
            metnet60_cl45++ w c 0x1e 0x000e 0x0008 # 8. Issue Data path reset again


    Regards,
    Rodrigo Natal
    HSSC Applications Engineer