• State
  • Locked Locked
  • Replies 8 replies
  • Subscribers 99 subscribers
  • Views 391 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

AM5K2E02: Issues using 1000 Base-SX optical SFP with AM5K2E02 SoC

Rob CARPENTER
Prodigy 10 points

Part Number: AM5K2E02

Hello,

We are trying to configure and use a 1000 Base-SX optical SFP with the AM5K2E02 SoC and are having trouble configuring the interface.

We are basing our config code for SerDes, SGMII, MACs and switch initialisation on the MCSDK CSL library which I believe covers PHYs only. We do also have copper PHYs on the same HW and are able to configure and use these with no issue.

Briefly, with the optical SFPs we are only able to achieve the SGMII link up status, and hence continue the initialisation steps for this connection, if the SFP is connected to a powered SFP at the other end at initialisation time.
If the remote SFP is not powered at initialisation time then we time out on the SGMII link up wait loop for that connection and continue with the other connections (copper PHYs and a copper SFP) since our application must start-up and cannot wait indefinitely.
We have tried periodically re-running the port-specific SGMII and MAC initialisation code during normal operation such that when the remote SFP is powered it can continue the initialisation steps for that port only but this does not work - we never see the SGMII link go up when the power is applied to the remote SFP.

We have updated our SGMII initialisation code from the TI example such that for the optical SFP connection we perform the Forced Link Configuration described in section 2.4.3.4 of manual SPRUHZ3A "KeyStone Architecture II Gigabit Ethernet (GbE) Switch Subsystem for K2E and K2L Devices".

We note that for the remote device on the optical connection (completely different HW) that it is able to initialise once at start-up with the AM5K2E02 device not powered (hence SFP not powered) and then sees the SGMII link go up once the AM5K2E02 device is powered. This is with no special code running during normal operation on the remote device and using identical SFPs on both devices.

Do you have any optical SFP specific example code or any other suggestions of what to try please?

Thank you

  • 0
    TI__Expert 7090 points

    Hi,

    I’ll look into this and get back to you within a day.
    Could you also confirm the SDK version you are currently using?

    Regards,

    Betsy Varughese

  • 0 in reply to Betsy Varughese
    Prodigy 65 points

    Hi Betsy,

    As my colleague is out for a couple of days, I'm replying on his behalf.
    I believe he is using the Processor SDK V04.02.00.09

    Thanks

  • 0 in reply to Daniel Moran
    TI__Expert 7090 points

    Hi Daniel,

    Thanks for sharing the details.

    Rob CARPENTER said:
    Do you have any optical SFP specific example code or any other suggestions of what to try please?

    I haven’t seen any specific examples for optical SFP in the SDK. I am looking into whether there’s any documentation available and will share it with you if I find something.

    Regards,

    Betsy Varughese

  • 0 in reply to Betsy Varughese
    TI__Expert 7090 points

    Hi Daniel,

    Could you please refer : SGMII Troubleshooting Guide & Gigabit Ethernet (GbE) Switch SS for K2E & K2L Devices User's Guide (Rev. A)  , it might help.

    Regards,

    Betsy Varughese

  • 0
    Prodigy 10 points

    Hi Betsy,

    Thank you for the referenced document which we will look at and hopefully will prove useful.

    In the meantime we have a few related queries.

    1 - We have found that we can establish the SGMII link up state when the remote device powers up after the AM5K2E by periodically running the full SerDes configuration (CSL_EthernetSerdesInit(), CSL_SerdesLaneEnable(common init) & CSL_SerdesLaneEnable(lane init)) followed by re-running the port-specific SGMII & MAC initialisation. Running the lane specific SerDes init (just CSL_SerdesLaneEnable(lane init)) with the lane specific SGMII and MAC init does not establish the link.
    The down side of performing the full SerDes configuration is that it disrupts other network connections that use other lanes in the same SerDes SGMII.
    Is there a way to perform a partial SerDes re-initialisation that only affects a single lane in that SerDes SGMII?

    2 - We note that in the AM5K2E0x datasheet (SPRS864D) that in table 8-9, bits 13-12 Ext Con, it refers to a possible 'MAC to fiber connection' as an option for the boot configuration.
    While we are not using the Ethernet boot this does imply that the device supports a fiber connection mode that is not described in the GbES for K2E manual (SPRUHZ3A). E.g. section 2.4.3 Modes of Operation does not refer to a Fiber mode, only the master/slave auto negotiation modes and forced link mode.
    There are also a few references elsewhere in the GbES manual to Fiber Mode but it is never fully explained.
    Also, In section 3.3.5 SGMII Advertised Ability Register (SGMII_MR_ADV_ABILITY), we note that there is a sub section for 'SGMII mode' but no other sub sections - possibly hinting that there should be another mode.
    Is there a Fiber Mode supported by the AM5K2E that is not described in the manuals?

  • 0 in reply to Rob CARPENTER
    TI__Expert 7090 points

    Hi Rob CARPENTER,

    Are you pointing to the table below "Ethernet (SGMII) Boot Device Configuration Field Descriptions "?

    Rob CARPENTER said:
    Is there a Fiber Mode supported by the AM5K2E that is not described in the manuals?

    I will take a look at the remaining questions and get back to you.
    Regards,
    Betsy Varughese
  • 0 in reply to Betsy Varughese
    Prodigy 10 points

    Hi Betsy,

    Thank you.

    Yes, that is the table we were referring to. It refers specifically to a 'fiber connection' which is what we are trying to use (fibre optical SFP). As I said, we are not trying boot from Ethernet but it does imply that the device has a fiber connection mode that isn't described in the GbES manual.

    Many thanks.

  • 0 in reply to Rob CARPENTER
    TI__Expert 7090 points

    Hi Rob CARPENTER,

    Rob CARPENTER said:
    As I said, we are not trying boot from Ethernet but it does imply that the device has a fiber connection mode that isn't described in the GbES manual.

    Yes, I checked the available documentation but couldn’t find much info on the fiber mode. But could you look into the files mentioned in the K2E PDK located at pdk_k2e_4_0_16/packages/ti/csl/src/ip/sgmii/V5/?

    Regards,

    Betsy Varughese