In the Si5395-91 & Si5345-40 devices, DCO mode is intended to be used within the range of +/-350ppm. It is possible to use DCO mode beyond this range, but it is important to be aware of the following caveats:

• DCO mode works according to the following equation

where Fvco is the VCO frequency, NDEN is the N-divider denominator, NNUM is the N-divider numerator, NNUM,DELTA is the value which the numerator is being incremented/decremented by per step, X is the net amount of steps applied, and R is the integer R-divider value. If DCO mode is operated within a narrow frequency range, Fout has an approximately linear relation to X. However, as the frequency range increases, Fout becomes increasingly nonlinear with respect to X. Consequently, the actual frequency step size will be significantly different from the desired step size as the N-divider is continually incremented/decremented.

• ClockBuilder Pro optimizes the value of the N-divider to avoid noisy values of N within the +/-350ppm range when DCO mode is enabled. Beyond the +/-350ppm range, the N-divider may land on noisy values of N, thus degrading the noise performance of the device.

The following are the recommended solutions to address the above issues:

• DCO mode may be configured to increment/decrement the NDEN instead of NNUM. This results in a perfectly 1st order polynomial relation between Fout and X. However, NDEN has less resolution than NNUM, so the minimum resolution of DCO mode will be higher in this case. Although incrementing NDEN results in a perfectly linear step, it does not solve the noise issues related to using DCO mode over a large frequency range. Please contact Silicon Labs customer support to implement this solution.
• Using Frequency-on-the-Fly (FOTF) not only results in perfectly linear steps, but also optimizes the frequency plan to avoid noisy N-divider values across the entire range of desired frequencies. For example, if the desired output is 50MHz to 100MHz in 1MHz steps, Frequency-on-the-Fly will give far superior noise performance to DCO mode and give perfectly linear steps.

For more details on DCO mode and FOTF, please refer to the following application notes:

• DCO Mode with Si5395/94/92/45/44/42: https://www.silabs.com/documents/public/application-notes/an858-dco-applications-jitter-attenuators.pdf
• DCO Mode with Si5391/41/40: https://www.silabs.com/documents/public/application-notes/AN959.pdf
• Frequency-on-the-Fly: https://www.silabs.com/documents/public/application-notes/an1178-frequency-otf-jitter-atten-clock-gen.pdf

In the Si5395-91 & Si5345-40 devices, DCO mode is intended to be used within the range of +/-350ppm. It is possible to use DCO mode beyond this range, but it is important to be aware of the following caveats:

• DCO mode works according to the following equation

where Fvco is the VCO frequency, NDEN is the N-divider denominator, NNUM is the N-divider numerator, NNUM,DELTA is the value which the numerator is being incremented/decremented by per step, X is the net amount of steps applied, and R is the integer R-divider value. If DCO mode is operated within a narrow frequency range, Fout has an approximately linear relation to X. However, as the frequency range increases, Fout becomes increasingly nonlinear with respect to X. Consequently, the actual frequency step size will be significantly different from the desired step size as the N-divider is continually incremented/decremented.

• ClockBuilder Pro optimizes the value of the N-divider to avoid noisy values of N within the +/-350ppm range when DCO mode is enabled. Beyond the +/-350ppm range, the N-divider may land on noisy values of N, thus degrading the noise performance of the device.

The following are the recommended solutions to address the above issues:

• DCO mode may be configured to increment/decrement the NDEN instead of NNUM. This results in a perfectly 1st order polynomial relation between Fout and X. However, NDEN has less resolution than NNUM, so the minimum resolution of DCO mode will be higher in this case. Although incrementing NDEN results in a perfectly linear step, it does not solve the noise issues related to using DCO mode over a large frequency range. Please contact Silicon Labs customer support to implement this solution.
• Using Frequency-on-the-Fly (FOTF) not only results in perfectly linear steps, but also optimizes the frequency plan to avoid noisy N-divider values across the entire range of desired frequencies. For example, if the desired output is 50MHz to 100MHz in 1MHz steps, Frequency-on-the-Fly will give far superior noise performance to DCO mode and give perfectly linear steps.

For more details on DCO mode and FOTF, please refer to the following application notes:

• DCO Mode with Si5395/94/92/45/44/42: https://www.silabs.com/documents/public/application-notes/an858-dco-applications-jitter-attenuators.pdf
• DCO Mode with Si5391/41/40: https://www.silabs.com/documents/public/application-notes/AN959.pdf
• Frequency-on-the-Fly: https://www.silabs.com/documents/public/application-notes/an1178-frequency-otf-jitter-atten-clock-gen.pdf

In the Si5395-91 & Si5345-40 devices, DCO mode is intended to be used within the range of +/-350ppm. It is possible to use DCO mode beyond this range, but it is important to be aware of the following caveats:

• DCO mode works according to the following equation

where Fvco is the VCO frequency, NDEN is the N-divider denominator, NNUM is the N-divider numerator, NNUM,DELTA is the value which the numerator is being incremented/decremented by per step, X is the net amount of steps applied, and R is the integer R-divider value. If DCO mode is operated within a narrow frequency range, Fout has an approximately linear relation to X. However, as the frequency range increases, Fout becomes increasingly nonlinear with respect to X. Consequently, the actual frequency step size will be significantly different from the desired step size as the N-divider is continually incremented/decremented.

• ClockBuilder Pro optimizes the value of the N-divider to avoid noisy values of N within the +/-350ppm range when DCO mode is enabled. Beyond the +/-350ppm range, the N-divider may land on noisy values of N, thus degrading the noise performance of the device.

The following are the recommended solutions to address the above issues:

• DCO mode may be configured to increment/decrement the NDEN instead of NNUM. This results in a perfectly 1st order polynomial relation between Fout and X. However, NDEN has less resolution than NNUM, so the minimum resolution of DCO mode will be higher in this case. Although incrementing NDEN results in a perfectly linear step, it does not solve the noise issues related to using DCO mode over a large frequency range. Please contact Silicon Labs customer support to implement this solution.
• Using Frequency-on-the-Fly (FOTF) not only results in perfectly linear steps, but also optimizes the frequency plan to avoid noisy N-divider values across the entire range of desired frequencies. For example, if the desired output is 50MHz to 100MHz in 1MHz steps, Frequency-on-the-Fly will give far superior noise performance to DCO mode and give perfectly linear steps.

For more details on DCO mode and FOTF, please refer to the following application notes:

• DCO Mode with Si5395/94/92/45/44/42: https://www.silabs.com/documents/public/application-notes/an858-dco-applications-jitter-attenuators.pdf
• DCO Mode with Si5391/41/40: https://www.silabs.com/documents/public/application-notes/AN959.pdf
• Frequency-on-the-Fly: https://www.silabs.com/documents/public/application-notes/an1178-frequency-otf-jitter-atten-clock-gen.pdf

In the Si5395-91 & Si5345-40 devices, DCO mode is intended to be used within the range of +/-350ppm. It is possible to use DCO mode beyond this range, but it is important to be aware of the following caveats:

• DCO mode works according to the following equation

where Fvco is the VCO frequency, NDEN is the N-divider denominator, NNUM is the N-divider numerator, NNUM,DELTA is the value which the numerator is being incremented/decremented by per step, X is the net amount of steps applied, and R is the integer R-divider value. If DCO mode is operated within a narrow frequency range, Fout has an approximately linear relation to X. However, as the frequency range increases, Fout becomes increasingly nonlinear with respect to X. Consequently, the actual frequency step size will be significantly different from the desired step size as the N-divider is continually incremented/decremented.

• ClockBuilder Pro optimizes the value of the N-divider to avoid noisy values of N within the +/-350ppm range when DCO mode is enabled. Beyond the +/-350ppm range, the N-divider may land on noisy values of N, thus degrading the noise performance of the device.

The following are the recommended solutions to address the above issues:

• DCO mode may be configured to increment/decrement the NDEN instead of NNUM. This results in a perfectly 1st order polynomial relation between Fout and X. However, NDEN has less resolution than NNUM, so the minimum resolution of DCO mode will be higher in this case. Although incrementing NDEN results in a perfectly linear step, it does not solve the noise issues related to using DCO mode over a large frequency range. Please contact Silicon Labs customer support to implement this solution.
• Using Frequency-on-the-Fly (FOTF) not only results in perfectly linear steps, but also optimizes the frequency plan to avoid noisy N-divider values across the entire range of desired frequencies. For example, if the desired output is 50MHz to 100MHz in 1MHz steps, Frequency-on-the-Fly will give far superior noise performance to DCO mode and give perfectly linear steps.

For more details on DCO mode and FOTF, please refer to the following application notes:

• DCO Mode with Si5395/94/92/45/44/42: https://www.silabs.com/documents/public/application-notes/an858-dco-applications-jitter-attenuators.pdf
• DCO Mode with Si5391/41/40: https://www.silabs.com/documents/public/application-notes/AN959.pdf
• Frequency-on-the-Fly: https://www.silabs.com/documents/public/application-notes/an1178-frequency-otf-jitter-atten-clock-gen.pdf

The Si534x/7x/8x/9x clock generators and jitter attenuators can generate clocks compatible with HCSL receivers. However, the designer must be careful not to use conventional HCSL termination networks but rather follow the recommended HCSL termination in the reference manual.

Conventional HCSL relies on steering a 15mA current across two 50 ohm resistors to ground, which generates the high and low levels of roughly 750mV and 0mV respectively. In contrast, the Si534x/7x/8x/9x driver generates the proper HCSL voltage swing on the driver side and then AC couples that signal to a 50 ohm (Thevenin) resistor divider network to set the proper HCSL common-mode level of about 0.375V at the receiver side.

Figure 1 shows proper HCSL termination for Si534x/7x/8x/9x devices, copied from the reference manual. Figures 2-4 show examples of commonly used HCSL termination networks which should not be used for Si53x4/x7/x8/9x devices.

*Please note that other product families in the Silabs timing portfolio may have different methods of terminating HCSL clocks, and the documentation will provide the proper termination network.

Proper HCSL Termination Networks

Examples of Improper HCSL Termination Networks

The Si534x/7x/8x/9x clock generators and jitter attenuators can generate clocks compatible with HCSL receivers. However, the designer must be careful not to use conventional HCSL termination networks but rather follow the recommended HCSL termination in the reference manual.

Conventional HCSL relies on steering a 15mA current across two 50 ohm resistors to ground, which generates the high and low levels of roughly 750mV and 0mV respectively. In contrast, the Si534x/7x/8x/9x driver generates the proper HCSL voltage swing on the driver side and then AC couples that signal to a 50 ohm (Thevenin) resistor divider network to set the proper HCSL common-mode level of about 0.375V at the receiver side.

Figure 1 shows proper HCSL termination for Si534x/7x/8x/9x devices, copied from the reference manual. Figures 2-4 show examples of commonly used HCSL termination networks which should not be used for Si53x4/x7/x8/9x devices.

*Please note that other product families in the Silabs timing portfolio may have different methods of terminating HCSL clocks, and the documentation will provide the proper termination network.

Proper HCSL Termination Networks

Improper HCSL Termination Networks

The Si534x/7x/8x/9x clock generators and jitter attenuators can generate clocks compatible with HCSL receivers. However, the designer must be careful not to use conventional HCSL termination networks but rather follow the recommended HCSL termination in the reference manual.

Conventional HCSL relies on steering a 15mA current across two 50 ohm resistors to ground, which generates the high and low levels of roughly 750mV and 0mV respectively. In contrast, the Si534x/7x/8x/9x driver generates the proper HCSL voltage swing on the driver side and then AC couples that signal to a 50 ohm (Thevenin) resistor divider network to set the proper HCSL common-mode level of about 0.375V at the receiver side.

Figure 1 shows proper HCSL termination for Si534x/7x/8x/9x devices, copied from the reference manual. Figures 2-4 show examples of commonly used HCSL termination networks which should not be used for Si53x4/x7/x8/9x devices.

*Please note that other product families in the Silabs timing portfolio may have different methods of terminating HCSL clocks, and the documentation will provide the proper termination network.

Proper HCSL Termination Networks

Improper HCSL Termination Networks

The Si534x/7x/8x/9x clock generators and jitter attenuators can generate clocks compatible with HCSL receivers. However, the designer must be careful not to use conventional HCSL termination networks but rather follow the recommended HCSL termination in the reference manual.

Conventional HCSL relies on steering a 15mA current across two 50 ohm resistors to ground, which generates the high and low levels of roughly 750mV and 0mV respectively. In contrast, the Si534x/7x/8x/9x driver generates the proper HCSL voltage swing on the driver side and then AC couples that signal to a 50 ohm (Thevenin) resistor divider network to set the proper HCSL common-mode level of about 0.375V at the receiver side.

Figure 1 shows proper HCSL termination for Si534x/7x/8x/9x devices, copied from the reference manual. Figures 2-4 show examples of commonly used HCSL termination networks which should not be used for Si53x4/x7/x8/9x devices.

*Please note that other product families in the Silabs timing portfolio may have different methods of terminating HCSL clocks, and the documentation will provide the proper termination network.

Proper HCSL Termination Networks

Improper HCSL Termination Networks

In this article, an input is considered unused when that input is declared as “Unused (Powered-down)” in ClockBuilder Pro.

An active clock signal on an unused input must not violate the maximum and minimum voltage level at the input pins, which are +3.8V and -1.0V respectively. Permanent device damage may occur if the absolute maximum ratings are exceeded. If the unused input is AC coupled, then input pin will be biased at 0V. Therefore, the maximum peak-to-peak swing of the AC coupled input must not be greater than 2Vpp [0V – 2Vpp/2 = -1V] so that the signal does not fall below -1.0V. See below figure for example scenarios.

It is okay to provide an active clock signal to an unused input if:

• The clock is an AC coupled differential input format such as LVDS, LVPECL, or HCSL
• The clock is a DC coupled CMOS clock whose voltage levels are constrained to be within -1.0V and +3.8V.
• The clock is an AC coupled CMOS clock with a peak-to-peak swing <2.0V. Note that this peak-peak swing must take into account any overshoot or undershoot of the CMOS signal

It is not­ okay to provide an active clock signal to an unused input if:

• The clock is an AC coupled CMOS clock with a peak-to-peak swing >2.0V. Note that this peak-to-peak swing must take into account any overshoot or undershoot of the CMOS signal.

Whether an input is unused or enabled, the absolute maximum/minimum ratings cannot be violated. The designer must take into account any overshoot/undershoot in the signal, any temperature related effects that could cause increased overshoot/undershoot, or any uncertainty in the signal amplitude. It is always advised to leave some margin to minimize potential risks.

In this article, an input is considered unused when that input is declared as “Unused (Powered-down)” in ClockBuilder Pro.

An active clock signal on an unused input must not violate the maximum and minimum voltage level at the input pins, which are +3.8V and -1.0V respectively. Permanent device damage may occur if the absolute maximum ratings are exceeded. If the unused input is AC coupled, then input pin will be biased at 0V. Therefore, the maximum peak-to-peak swing of the AC coupled input must not be greater than 2Vpp [0V – 2Vpp/2 = -1V] so that the signal does not fall below -1.0V. See below figure for example scenarios.

It is okay to provide an active clock signal to an unused input if:

• The clock is an AC coupled differential input format such as LVDS, LVPECL, or HCSL
• The clock is a DC coupled CMOS clock whose voltage levels are constrained to be within -1.0V and +3.8V.
• The clock is an AC coupled CMOS clock with a peak-to-peak swing <2.0V. Note that this peak-peak swing must take into account any overshoot or undershoot of the CMOS signal

It is not­ okay to provide an active clock signal to an unused input if:

• The clock is an AC coupled CMOS clock with a peak-to-peak swing >2.0V. Note that this peak-to-peak swing must take into account any overshoot or undershoot of the CMOS signal.

Whether an input is unused or enabled, the absolute maximum/minimum ratings cannot be violated. The designer must take into account any overshoot/undershoot in the signal, any temperature related effects that could cause increased overshoot/undershoot, or any uncertainty in the signal amplitude. It is always advised to leave some margin to minimize potential risks.