The representation of simulation time differs significantly between the HDL simulator and Simulink®. Each application has its own timing engine and the verification software must synchronize the simulation times between the two.
In the HDL simulator, the unit of simulation time is referred to as a tick. The duration of a tick is defined by the HDL simulator resolution limit. The default resolution limit is 1 ns, but may vary depending on the simulator.
To determine the current ModelSim resolution limit, enter
report simulator state at
the ModelSim prompt. You can override the default resolution
limit by specifying the -t option on the ModelSim command line,
or by selecting a different Simulator Resolution in the ModelSim Simulate
dialog box. Available resolutions in ModelSim are 1x, 10x, or
100x in units of fs, ps, ns, us, ms, or sec. See the ModelSim documentation
for further information.
To determine the current HDL simulator resolution limit, enter
$timescale at the HDL simulator prompt. See the HDL simulator
documentation for further information.
Simulink maintains simulation time as a double-precision value scaled to seconds. This representation accommodates modeling of both continuous and discrete systems.
The relationship between Simulink and the HDL simulator timing affects the following aspects of simulation:
Total simulation time
Input port sample times
Output port sample times
During a simulation run, Simulink communicates the current simulation time to the HDL simulator at each intermediate step. (An intermediate step corresponds to a Simulink sample time hit. Upon each intermediate step, new values are applied at input ports, or output ports are sampled.)
To bring the HDL simulator up-to-date with Simulink during cosimulation, you must convert sampled Simulink time to HDL simulator time (ticks) and allow the HDL simulator to run for the computed number of ticks.
The differences in the representation of simulation time can be reconciled in one of two ways using the HDL Verifier™ interface:
By defining the timing relationship manually (with Timescales pane)
When you define the relationship manually, you determine how many femtoseconds, picoseconds, nanoseconds, microseconds, milliseconds, seconds, or ticks in the HDL simulator represent 1 second in Simulink.
By allowing HDL Verifier to define the timescale (with Timescales pane)
When you allow the software to define the timing relationship, it attempts to set the timescale factor between the HDL simulator and Simulink to be as close as possible to 1 second in the HDL simulator = 1 second in Simulink. If this setting is not possible, HDL Verifier attempts to set the signal rate on the Simulink model port to the lowest possible number of HDL simulator ticks.
The Timescales pane of the HDL Cosimulation block parameters dialog box defines a correspondence between one second of Simulink time and some quantity of HDL simulator time. This quantity of HDL simulator time can be expressed in one of the following ways:
In relative terms (i.e., as some number of HDL simulator ticks). In this case, the cosimulation is said to operate in relative timing mode. The HDL Cosimulation block defaults to relative timing mode for cosimulation. For more on relative timing mode, see Relative Timing Mode.
In absolute units (such as milliseconds or nanoseconds). In this case, the cosimulation is said to operate in absolute timing mode. For more on absolute timing mode, see Absolute Timing Mode.
The Timescales pane lets you choose an optimal timing relationship between Simulink and the HDL simulator, either by entering the HDL simulator equivalent or by letting HDL Verifier calculate a timescale for you.
You can choose to have HDL Verifier calculate a timescale while you are setting the parameters on the block dialog by clicking the Timescale option then clicking Determine Timescale Now or you can have HDL Verifier calculate the timescale when simulation begins by selecting Automatically determine timescale at start of simulation.
The next figure shows the default settings of the Timescales pane (example shown is for use with ModelSim).
For instructions on setting the timing mode either manually or with the Timescales dialog box, see the Timescales pane in the HDL Cosimulation block reference.
Relative timing mode defines the following one-to-one correspondence between simulation time in Simulink and the HDL simulator:
|One second in Simulink corresponds
to N ticks in the HDL simulator, where |
This correspondence holds regardless of the HDL simulator timing resolution.
The following pseudocode shows how Simulink time units are converted to HDL simulator ticks:
InTicks = N * tInSecs
InTicks is the HDL simulator time
tInSecs is the Simulink time in
N is a scale factor.
The HDL Cosimulation block defaults to relative timing mode, with a scale factor of 1. Thus, 1 Simulink second corresponds to 1 tick in the HDL simulator. In the default case:
If the total simulation time in Simulink is specified
N seconds, then the HDL simulation will run
N ticks (i.e.,
at the default resolution limit).
Similarly, if Simulink computes the sample time of an HDL Cosimulation block input port as Tsi seconds, new values will be deposited on the HDL input port at exact multiples of Tsi ticks. If an output port has an explicitly specified sample time of Tso seconds, values will be read from the HDL simulator at multiples of Tso ticks.
To understand how relative timing mode operates, review cosimulation results from the following example model.
Absolute timing mode lets you define the timing relationship between Simulink and the HDL simulator in terms of absolute time units and a scale factor:
|One second in Simulink corresponds to (N * Tu) seconds in the HDL simulator, where Tu is an absolute time unit (for example, ms, ns, etc.) and N is a scale factor.|
In absolute timing mode, all sample times and clock periods in Simulink are quantized to HDL simulator ticks. The following pseudocode illustrates the conversion:
tInTicks = tInSecs * (tScale / tRL)
tInTicks is the HDL simulator time
tInSecs is the Simulink time
tScale is the timescale setting
(unit and scale factor) chosen in the Timescales pane
of the HDL Cosimulation block.
tRL is the HDL simulator resolution
For example, given a Timescales pane setting of 1 s and an HDL simulator resolution limit of 1 ns, an output port sample time of 12 ns would be converted to ticks as follows:
tInTicks = 12ns * (1s / 1ns) = 12
To configure the Timescales parameters for absolute timing mode,
you select a unit of absolute time that corresponds to a Simulink second,
rather than selecting
To understand the operation of absolute timing mode, you will again consider the example model discussed in Operation of Relative Timing Mode. Suppose that the model is reconfigured as follows:
Simulation parameters in Simulink:
s of Simulink time corresponds to
1 s of
HDL simulator time.
Total simulation time:
60e-9 s (60ns)
Input port (
24e-9 s (24 ns)
Output port (
12e-9 s (12 ns)
s (10 ns)
HDL simulator resolution limit:
Given these simulation parameters, the Simulink software will cosimulate with the HDL simulator for 60 ns, during which Simulink will sample inputs at a intervals of 24 ns, update outputs at intervals of 12 ns, and drive clocks at intervals of 10 ns.
The following figure shows a ModelSim wave window after a cosimulation run.
When setting a timescale mode, you may need to choose your setting based on the following considerations.
The following restrictions apply to the use of absolute and relative timing modes:
When multiple HDL Cosimulation blocks in a model are communicating with a single instance of the HDL simulator, all HDL Cosimulation blocks must have the same Timescales pane settings.
If you change the Timescales pane settings in an HDL Cosimulation block between consecutive cosimulation runs, you must restart the simulation in the HDL simulator.
If you specify a Simulink sample time that cannot be expressed as a whole number of HDL ticks, you will get an error.
When using noninteger time periods, the HDL simulator cannot represent such an infinitely repeating value. So the simulator truncates the time period, but it does so differently than how Simulink truncates the value, and the two time periods no longer match up.
The following example demonstrates how to set the timing relationship in the following scenario: you want to use a sample period of in Simulink, which corresponds to a noninteger time period.
The key idea here is that you must always be able to relate a Simulink time with an HDL tick. The HDL tick is the finest time slice the HDL simulator recognizes; for ModelSim, the default tick is 1 ns, but it can be made as precise as 1 fs.
However, a 3 Hz signal actually has a period of 333.33333333333... ms, which is not a valid tick period for the HDL simulator. The HDL simulator will truncate such numbers. But Simulink does not make the same decision; thus, for cosimulation where you are trying to keep two independent simulators in synchronization, you should not assume anything. Instead you have to decide whether it is convenient to truncate or round the number.
Therefore, the solution is to "snap" either the Simulink sample time or the HDL sample time (via the timescale) to valid numbers. There are infinite possibilities, but here are some possible ways to perform a snap:
Change Simulink sample times from 1/3 sec to 0.33333 sec and set the cosimulation block timescale to '1 second in Simulink = 1 second in the HDL simulator'. If you are specifying a clock in the HDL Cosimulation block Clocks pane, its period should be 0.33333 sec.
Keep Simulink sample times at 1/3 sec. and 1 second in Simulink = 6 ticks in the HDL simulator.
If you are specifying a clock in the HDL Cosimulation block Clocks pane, its period should be 1/3. Briefly, this specification tells Simulink to make each Simulink sample time correspond to every (1/3*6) = 2 ticks, regardless of the HDL time resolution.
If your default HDL simulator resolution is 1 ns, that means your HDL sample times are every 2 ns. This sample time will work in a way so that for every Simulink sample time there is a corresponding HDL sample time.
However, Simulink thinks in terms of 1/3 sec periods and the HDL in terms of 2 ns periods. Thus, you could get confused during debug. If you want this to match the real period (such as to 5 places, i.e. 333.33ms), you can follow the next option listed.
Keep Simulink sample times at 1/3 sec and 1 second in Simulink = 0.99999e9 ticks in the HDL simulator. If you are specifying a clock in the HDL Cosimulation block Clocks pane, its period should be 1/3.
In general, Simulink handles the sample time for the ports of an HDL Cosimulation block as follows:
If an input port is connected to a signal that has an explicit sample time, based on forward propagation, Simulink applies that rate to that input port.
If an input port is connected to a signal that does not have an explicit sample time, Simulink assigns a sample time that is equal to the least common multiple (LCM) of all identified input port sample times for the model.
After Simulink sets the input port sample periods, it applies user-specified output sample times to all output ports. Sample times must be explicitly defined for all output ports.
If you are developing a model for cosimulation in relative timing mode, consider the following sample time guideline:
|Specify the output sample time for an HDL Cosimulation block
as an integer multiple of the resolution limit defined in the HDL
simulator. Use the HDL simulator command |