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.

TCI6638K2K: SerDes settings - description needed

Part Number: TCI6638K2K


Hi,

I am looking after detailed description of Keystone II SerDes settings. In spruho3a document there are only short descriptions with no values presented. For example, on page 91, setting of register 058, there is field named DFE_OFFSET_CAL_TAP_EN_OVR_O_7_3. Description: DFE offset calibration TAP enable override. In a log I found that there is written 0x10 value. What does it mean? Where I can found values for other fields?

Best regards,

Ryszard

  • Hi,

    I've notified the factory team. Their feedback will be posted here.

    Best Regards,
    Yordan
  • Hi,

    We only have this Serdes user guide public document. The setting for other fields of this lane 058 register can be find in CSL, e.g, pdk_k2hk_4_0_5\packages\ti\csl\src\ip\serdes_sb\V0\csl_serdes2.h, looking for lines:

     CSL_FINSR(*(volatile uint32_t *)(base_addr + 0x200*(lane_num+1) + 0x58), ...)

    Regards, Eric

     

  • Are you having a specific issue? Programming the SerDes requires expert-level knowledge of the device, and so we can only support TI-provided configurations that are known to work. DFE programming also falls into this catagory. The PDK provides configurations for commonly used WCDMA and LTE protocols.
  • Thanks for reply.

    Due to observed errors on this link in our application I tried to look on settings of SerDes. I have some experience with other manufacturer's solutions. So I looked after description of settings as there are only names of fields in available document. I have not found descriptions so I asked here for help.

  • If you are using K2K, then there is no DFE peripheral (DFE is in K2L only). So this field - even if present - would have no effect.  I assume by link errors, you are referring to an AIF2 link.  In this case, I would suggest comparing your AIF2 configuration to one of the examples found in the LLD.  And, you can examine the "EE" registers in the AIF2 block for errors that the hardware has flagged.  Note that stopping the AIF2 (or the cores that are controlling it or the input/output descriptors) to read the registers will generate errors, so you need to read them while the link is running.

     -dave