SPRZ455D december   2020  – june 2023 DRA829J , DRA829J-Q1 , DRA829V , TDA4VM , TDA4VM-Q1

ADVANCE INFORMATION  

  1.   1
  2. 1Modules Affected
  3. 2Nomenclature, Package Symbolization, and Revision Identification
    1. 2.1 Device and Development-Support Tool Nomenclature
    2. 2.2 Devices Supported
    3. 2.3 Package Symbolization and Revision Identification
  4. 3Silicon Revision 1.1/1.0 Usage Notes and Advisories
    1. 3.1 Silicon Revision 1.1/1.0 Usage Notes
      1.      i2134
    2. 3.2 Silicon Revision 1.1/1.0 Advisories
    3.     i2024
    4.     i2038
    5.     i2048
    6.     i2049
    7.     i2050
    8.     i2052
    9.     i2053
    10.     i2054
    11.     i2055
    12.     i2062
    13.     i2063
    14.     i2064
    15.     i2065
    16.     i2067
    17.     i2079
    18.     i2081
    19.     i2083
    20.     i2085
    21.     i2086
    22.     i2087
    23.     i2090
    24.     i2091
    25.     i2092
    26.     i2093
    27.     i2094
    28.     i2095
    29.     i2096
    30.     i2097
    31.     i2098
    32.     i2099
    33.     i2100
    34.     i2101
    35.     i2102
    36.     i2103
    37.     i2103
    38.     i2115
    39.     i2116
    40.     i2117
    41.     i2118
    42.     i2119
    43.     i2120
    44.     i2121
    45.     i2122
    46.     i2123
    47. 3.3 i2124
    48. 3.4 i2126
    49. 3.5 i2127
    50.     i2128
    51.     i2129
    52.     i2131
    53.     i2132
    54.     i2133
    55.     i2134
    56.     i2137
    57.     i2138
    58.     i2139
    59.     i2141
    60.     i2143
    61.     i2144
    62.     i2145
    63.     i2146
    64.     i2147
    65.     i2148
    66.     i2149
    67. 3.6 i2150
    68. 3.7 i2151
    69. 3.8 i2152
    70.     i2153
    71.     i2154
    72.     i2155
    73.     i2157
    74.     i2159
    75.     i2160
    76.     i2161
    77.     i2162
    78.     i2163
    79.     i2164
    80.     i2166
    81.     i2168
    82.     i2171
    83.     i2173
    84.     i2174
    85.     i2177
    86.     i2178
    87.     i2179
    88.     i2180
    89.     i2182
    90.     i2183
    91.     i2184
    92.     i2185
    93.     i2187
    94.     i2188
    95.     i2189
    96.     i2190
    97.     i2191
    98.     i2196
    99.     i2197
    100.     i2198
    101.     i2199
    102.     i2200
    103.     i2205
    104.     i2207
    105.     i2208
    106.     i2210
    107.     i2211
    108.     i2213
    109.     i2214
    110.     i2215
    111.     i2216
    112.     i2217
    113.     i2219
    114.     i2221
    115.     i2227
    116.     i2228
    117.     i2229
    118.     i2230
    119.     i2232
    120.     i2234
    121.     i2235
    122.     i2238
    123.     i2239
    124.     i2244
    125.     i2245
    126.     i2246
    127.     i2249
    128.     i2253
    129.     i2257
    130.     i2271
    131.     i2274
    132.     i2275
    133.     i2277
    134.     i2278
    135.     i2279
    136.     i2283
    137.     i2305
    138.     i2306
    139.     i2307
    140.     i2310
    141.     i2311
    142.     i2312
    143.     i2320
    144.     i2329
    145.     i2351
    146.     i2362
    147.     i2366
    148.     i2371
    149.     i2383
  5.   Trademarks
  6.   Revision History

i2239

PCIe: The 2-L SerDes PCIe Reference Clock Output is temporarily disabled while changing Data Rates

Details

The 2-L SerDes PCIe Reference Clock Output will be temporarily disabled when either of the following occur:

  • Scenario A: Changing Data Rates to or from 8.0 GT/s, because the SerDes Common PLL is reprogrammed during the speed change
  • Scenario B: Changing Data Rates to or from any speed while the second lane of the SerDes is in a reset/powered-down state or used together with the first lane to form a two-lane link.
    • Examples of affected configurations include:
      • PCIe 1L with Second lane in reset/powered-down
      • PCIe 2L
    • Configurations not affected include:
      • PCIe + USB (with USB not in reset/powered-down)
      • PCIe + Ethernet (SGMII/QSGMII/XFI, not in reset/powered-down)

Some external PCIe components that are using the PCIe Reference Clock may not tolerate the disabling of the clock when changing data rates. However, the 2-L and 4-L SerDes in this Device family does not have an issue accepting this Reference Clock behavior. This means that a link that connects the 2-L or 4-L SerDes in one Device to the 2-L or 4-L SerDes in a second Device will not have an issue when one Device generates the Reference Clock and the other Device receives the Reference Clock.

Workaround

One workaround for both Scenario A and Scenario B is to use an external clock source to supply the PCIe Reference Clock to both the Root Complex and End Point Devices of the Link.

Scenario A can also be worked around by either of the following methods:

  1. Use a Single Link PCIe configuration in which CMNPLLLC is used for all PCIe data rates (2.5GT/s, 5.0GT/s, and 8.0GT/s). PHY_PLL_CFG[0] should also be set to 1'b0 to prevent reprogramming of CMNPLLLC when changing Data Rates to/from 8.0 GT/s.
  2. Do not operate the PCIe interface at the 8.0 GT/s Data Rate

Scenario B can also be worked around by either of the following methods:

1) Ensure that the second lane of the 2-L Serdes is out of reset, not part of a two-lane link, and not in a low-power state when the first lane is going through a speed change. One way to accomplish this is to setup dummy SerDes configurations on unused Lanes.

To setup a dummy Lane for the PCIe 1L configuration:

Setup second lane as USB or Q/SGMII. This can be done by configuring LANE_FUNC_SEL field in CTRLMMR_SERDES*_LN1_CTRL register in CTRL_MMR0 space.

Also SERDES configuration has to be performed for the second lane based on the protocol selected.

Please note that USB or Q/SGMII on second lane is a dummy configuration and is not expected to be functional.

Force enable the second lane by setting P1_FORCE_ENABLE to 1’b1 in LANECTL1 register. P1_ENABLE bit has to be retained at 1’b0.

Please note that if USB is selected for second lane, it is a dummy configuration and USB will not be functional. This is because forcing lane enable is not compatible with USB.

Q/SGMII can also be selected as dummy configuration if application is not using a given Q/SGMII instance. However, in case of Q/SGMII, this does not have to be a dummy configuration and it can be functional if required by application.

To setup dummy Lanes for the PCIe 2L configuration:

Setup a second SERDES to supply reference clock to refclk_p/refclk_n SERDES pins. For example if SERDES0 is being used for PCIe 2L then SERDES1/SERDES2/SERDES3 can be used as the second SERDES.

Select USB or Q/SGMII or PCIe (different instance than one being worked around) to be used on both lanes of the second SERDES using CTRLMMR_SERDES*_LN*_CTRL register. If USB is the selected protocol, second lane has to be marked as “Not used” in this register, but both lanes of SERDES have to be configured for USB.

Also program SERDES as per the selected protocol. Please note that this second SERDES is acting as a dummy configuration and is not expected to be functional. As a result, the SERDES and the Controller instance not used by the application has to be selected.

Force enable both lanes of the SERDES by setting P0_FORCE_ENABLE to 1’b1 in LANECTL0 register and P1_FORCE_ENABLE to 1’b1 in LANECTL1 register. P0_ENABLE and P1_ENABLE bits have to be retained at 1’b0.

Leave REFCLKP and REFCLKN pins of the first SERDES unconnected. Instead use REFCLKP and REFCLKN pins of the second SERDES to supply reference clock to link partner.

Provide same SOC internal reference clock to both first and second SERDES. This is important to ensure that the reference clock going to pins is phase aligned and within jitter limits with respect to the serial pins on the first SERDES.

2) Only operate the PCIe interface at the 2.5 GT/s Data Rate