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.

Incomplete SGMII documentation for 66AK2H, need to find location and offset of SGMII_SERDES_CGFTX0

I have looked through all the various posts here asking the same question in various ways because the TI documentation is badly incomplete. I have already read all the docs, and they just circularly refer to each other and never give an answer. and I have  looked through all the "example code' and they are bad hacks, incomplete and not at all commented (including the uBoot and linux drivers for EVM).

So I need a SIMPLE and non-referential answer to this question asap please:

What is the base address for the SGMII0 and SGMII1 registers and offsets for the following registers for this part (Keystone I):

SGMII_SERDES_STS 

SGMII_SERDES_CFGPLL 

SGMII_SERDES_CFGRX0 

SGMII_SERDES_CFGTX0 

SGMII_SERDES_CFGRX1 

SGMII_SERDES_CFGTX1 

Please please please DO NOT refer to other posts, or documents that do not exist, or example code. Please provide the values requested, as it should have been in the documentation for the part. We have spent hours now wasting out time instead of working on our board.

Thanks.

  • Hi Edmund,

    I've forwarded this to the designers of the Ethernet subsystem. Their feedback will be posted directly here.

    Best Regards,
    Yordan
  • Edmund,

    Sorry to know the bad experience of using TI documents. I am not sure if you are using C6678, if it is, all the info just in one place in the data sheet. www.ti.com/.../tms320c6678.pdf

    Table 3.3: Device State Control Registers

    0x02620158 0x0262015B 4B SMGII_SERDES_STS
    0x02620340 0x02620343 4B SGMII_SERDES_CFGPLL
    0x02620344 0x02620347 4B SGMII_SERDES_CFGRX0
    0x02620348 0x0262034B 4B SGMII_SERDES_CFGTX0
    0x0262034C 0x0262034F 4B SGMII_SERDES_CFGRX1
    0x02620350 0x02620353 4B SGMII_SERDES_CFGTX1

    Hope this is clear!

    Regards, Eric
  • Edmund,

    I thought you asked for Keystome I device as I saw "What is the base address for the SGMII0 and SGMII1 registers and offsets for the following registers for this part (Keystone I):", but the title of this thread is "Incomplete SGMII documentation for 66AK2H".

    My previous answer is for Keystone I device.

    If you are looking for those registers for Keystone II device, they don't exist, as Keystone I and Keystone II Serdes are totally different.

    Regards, Eric
  • Yes I realize that but all the documentations talking about the ethernet subsystem referring to Keystone II implementation DOES NOT include this part number. So by inference and because not all the submodules are updated at once we can only assume it is still using a KeyStone I implementation. I have seen documentation on the Keystone II version but it refers to other chips in the family. please note the tile of this document (SPRUHZ0).

    KeyStone II Architecture Network Coprocessor (NETCP) for K2E and K2L Devices 

    Also note that the documentation for the 66ak2H lists the following document for NETCP (SPRUGZ6) on page 19 of SPRS866E.

    KeyStone Architecture Network Coprocessor (NETCP)

    Do you even read your own documentation? By the SOC document it does not have a Keystone II NETCP implementation. Do you know how many threads on e2e have been about this exact same topic?

    So which is it really? Is is a KeyStone II NETCP on this part of KeyStone I? Which document are you telling me to read?

  • Edmund,

    Thanks for the explanation! I understood how the confusion came from. I draw a table for reference:

     

     

    NETCP

    GbE

    PA

    Serdes

    Keystone I:

    C6657, C6670, C6678

    SPRUGZ6

    SPRUGV9D

    SPRUGS4A

    N/A, look at datasheet

    Keystone II:

    K2H, K2K

    SPRUGZ6

    SPRUGV9D

    SPRUGS4A

    SPRUHO3A

    K2E, K2L

    SPRUHZ0

    SPRUHZ3A

    SPRUHZ2

    SPRUHO3A

     

    K2H and K2K are similar to Keystone I device, they share the same NETCP/GbE/PA documents.

    K2L and K2E are different from other Keystone II devices and use a different document sets.

    I will discuss with colleagues how to make this clear.

    Regards, Eric