The Max oversampling ratio is the maximum ratio of the final design implementation sample rate to the original sample rate. This parameter enables you to limit clock frequency.
The following table shows the possible values for the maximum oversampling ratio and how they affect the design implementation.
| Max Oversampling value | Effect on design implementation |
|---|---|
Inf (default) | Sample rate is unconstrained. |
| 1 | Single-rate implementation; no overclocking. |
| > 1 | Oversampling is allowed, but limited to the specified maximum. |
In the Configuration Parameters dialog box, you can specify the maximum oversampling ratio:
In HDL Code Generation > Global Settings, click the Optimization tab.
For Max oversampling, enter your maximum oversampling ratio.
In the HDL Workflow Advisor, you can specify the maximum oversampling ratio:
In the HDL Code Generation > Set Code Generation Options > Set Advanced Options task, click the Optimization tab.
For Max oversampling, enter your maximum oversampling ratio.
On the command line, set the MaxOversampling property
using makehdl or hdlset_param.
For example, to set the maximum oversampling ratio to 4 for
a subsystem, dut, in your model, mymodel,
enter:
hdlset_param ('myModel/dut', 'MaxOversampling', 4)When the maximum oversampling ratio is 1, the following limitations apply:
DUT subsystem must be single-rate.
Delay balancing for the model must be enabled.
There can be at most one subsystem within a subsystem
hierarchy that has a nondefault SharingFactor or StreamingFactor setting.
You cannot instantiate multiple times a subsystem
with a nondefault SharingFactor or StreamingFactor setting
in its subsystem hierarchy.