Example of tracing of 4 tasks statically scheduled on scheduler called
"sched1" where the model has been configured to use an scheduling
penaly of 0s.
Using KisTA:
The KisTA library enables the creation of a .vcd
trace of the utilizations of the tasks assigned to each scheduler. For
it, you only has to call the trace_utilizations() method
associated to an scheduler before the simulation start. Once it has
been called, if the scheduler object has the name "sched_name", a trace file called "sched_name_trace.vcd" will be created at
the end of the simulation. Similarly, the user can set the name of the trace file by using the overloaded method trace_utilizations(std::string file_name) .
You can plot the .vdf file with your favourite waveform viewer (e.g. gtkwave, as shown in the figure above).
Using KisTA-XML:
In order to enable the setting of a trace, the KisTA-XML user has to us
the trace_rtos tag within the
analysis section. Such tag has associated an attribute "name" which
should contain the name of the scheduler the traceing is to be done for.
This attribute is mandatory.
<kista_configuration>
...
<analysis>
<!-- Trace
RTOS activity. A trace file called sched1_trace.vcd will be
generated-->
<rtos_trace
name="sched1"/>
<!-- Trace
RTOS activity making explicit the trace file name: rtos2_trace.vcd-->
<rtos_trace
name="sched2 file="rtos2_trace""/>
...
</analysis>
...
</kista_configuration>
