SNAA421 November   2025 LMK05318B , LMK5B12204 , LMK5B33216 , LMK5B33414 , LMK5C33216A , LMK5C33414A

 

  1.   1
  2.   Abstract
  3.   Trademarks
  4. 1Start Here: Using TICS Pro for Configuration and Readback
    1. 1.1 TICS Pro Status Page
    2. 1.2 TICS Pro Default Setting
  5. 2Debug Procedure: From Device Start-Up to Locked Output State
    1. 2.1 Is the APLL Reference Valid?
      1. 2.1.1 Check Status of APLL Reference
      2. 2.1.2 Debug APLL Reference
    2. 2.2 Is the APLL Locked?
      1. 2.2.1 Check Status of APLL Lock
      2. 2.2.2 Debug APLL Lock
    3. 2.3 Is the DPLL Reference Valid?
      1. 2.3.1 Check Status of DPLL Reference Validation
      2. 2.3.2 Debug DPLL Reference Validation
    4. 2.4 Is the DPLL Selecting a Reference?
      1. 2.4.1 Check Status of DPLL Reference Selection
      2. 2.4.2 Debug DPLL Reference Selection
    5. 2.5 Is the DPLL Frequency Locked?
      1. 2.5.1 Check Status of DPLL Frequency Lock
      2. 2.5.2 Debug DPLL Frequency Lock
    6. 2.6 Is the DPLL Phase Locked?
      1. 2.6.1 Check Status of DPLL Phase Lock
      2. 2.6.2 Debug DPLL Phase Lock
  6. 3Summary
  7. 4References

Debug DPLL Frequency Lock

  1. Calculate the expected PFD, TDC, and VCO frequencies based on the DPLL and APLL registers.

    Confirm the numerator, denominator, N divider, pre-divider and post-divider settings are correct for the DPLL and APLL. Refer to the LMK data sheet for the PFD, TDC, and VCO equations.

  2. Check the LOFL lock and unlock thresholds.

    The LOFL status bit can falsely report an unlocked state due to improper threshold settings. Try widening the frequency lock threshold (see Table 2-24) by 10ppm to see if the LOFL status bit clears. Use TICS Pro to configure the threshold settings.

  3. Debug the TDC inputs by adding a frequency offset.

    Confirm the DPLL is actually locked to the DPLL reference and not misreporting LOFL=0 by applying a small frequency offset (such as 1ppm to 5ppm) to either the APLL reference or the DPLL reference. Observe the impact on the output frequency. When the DPLL is locked and properly configured, the outputs have the same frequency accuracy as the DPLL reference. When the DPLL is not locked, the outputs have the same frequency accuracy as the APLL reference. Therefore, a frequency offset applied to the DPLL reference results in a frequency offset applied to the output clocks by the same amount when the DPLL is locked.

    The following steps provide an example debug scenario with the results summarized in Table 2-19. In the example, the XO input is used as the APLL reference and the INx input is used as the DPLL reference. The "programmed frequency" refers to the configured register settings and the "expected output frequency" is the output frequency that is expected when measured.

    1. Use TICS Pro to configure the register settings for XO = 48MHz, INx = 156.25MHz, OUTx=156.25MHz.
    2. From readback, DPLL LOPL = 1.
    3. Route the output clock to a frequency counter or phase noise analyzer. Record the output frequency.
    4. Apply a 5ppm offset to the DPLL reference input by setting the frequency to 156.25MHz + 5ppm.
    5. Record the output frequency.
      1. Is there a 10ppm offset added to the output frequency? If yes, the DPLL is locked and the LOPL thresholds need to be adjusted. If no, contact TI for further support.
    Table 2-19 Applied Frequency Offset Debug Example
    PROGRAMMED FREQUENCY [MHz] APPLIED FREQUENCY [MHz] EXPECTED OUTPUT FREQUENCY [MHz]
    XO INx OUTx XO INx OUTx, WHEN DPLL IS LOCKED OUTx, WHEN DPLL IS UNLOCKED
    48 25 156.25 48 25 156.25 156.25
    48 25 156.25 48.00024 25 156.25 156.2507
    48 25 156.25 48 25.000125 156.2507 156.25
  4. Debug the TDC inputs by reading the APLL Numerator.

    The LMK device offers a status register, as seen in Table 2-23, to monitor the live APLL numerator value. When the DPLL is locked, the DPLL makes updates to the APLL numerator (at a rate defined by the TDC) until a 0ppm error between the DPLL reference and VCO output is attained. Since the DPLL reference has noise and jitter, the DPLL continuously makes corrections to the APLL numerator trying to achive a 0ppm error. Checking the live APLL numerator status for DPLL lock is similar to checking the tuning voltage (LFx pin) for APLL lock.

    Use the following pseudocode to get the frequency error (ppb) between the expected and measured VCO frequency, where APLL_NUM_STAT is the APLL numerator status register readback value and APLL_N_DIV is the APLL N divider register readback value. The APLL N divider register address is listed in Table 2-21. Graph the results over the time to get a time interval error (TIE) plot. In a stable DPLL locked state, the frequency error is near 0ppb and does not sporadically drift in an uncontrolled manner.

    
    get_APLL_NUM_STAT_as_ppb (phase_detect_freq, expected_vco_freq){
        numStatVal = Read_Reg("APLL_NUM_STAT")
        fract = numStatVal / (2^40)
        n_div = Read_Reg("APLL_N_DIV")
        meas_vco_freq = phase_detect_freq * (n_div + fract)
        ppb_error = 1e9 * ((meas_vco_freq – expected_vco_freq) / vco_freq)
        return ppb_error
    }
    
    Table 2-20 Live APLL Numerator - Status Register
    DEVICE FAMILY TICS PRO FIELD NAME LIVE APLL NUMERATOR
    REGISTER
    BAW APLL APLL2 APLL1
    LMK05318B, LMK05318 PLL1_NUM_STAT R127 to R123 N/A N/A
    LMK5B, LMK5CA, LMK5C APLLx_NUM_STAT R862 to R858 R799 to R795 R729 to R725(1)
    Column is not applicable for LMK5B12212 or LMK5C22212A.
    Table 2-21 APLL N Divider - Register
    DEVICE FAMILY TICS PRO FIELD NAME APLL N DIVIDER
    REGISTER
    BAW APLL APLL2 APLL1
    LMK05318B PLL1_NDIV R109 to R108 N/A N/A
    LMK5B or LMK5CA PLLx_NDIV R850 to R849[0] R787 to R786[0] R717 to R716[0](1)
    Column is not applicable for LMK5B12212 or LMK5C22212A.