TLM Component Timing Values

You can specify that timing values be stored in the TLM component and supplied to the SystemC environment when the TLM component is used. Those values can be used in a system simulation environment which carries out accounting of execution times in the system, as described in the OSCI TLM-2.0 Language Reference Manual. These values—which you supply—represent approximations of the actual time consumed by operations involving the target device in a real system. They also add temporal realism to your system simulations.

At runtime, you can dynamically control the TLM component via a backdoor interface to enable and disable the return of timing information. See the generated test bench code for details (locate mw_backdoorcfg_IF).

You can represent the following timing values:

• Time consumed by execution of the behavior in the generated TLM component (this delay is simulated by a wait() or a time annotation, depending on the temporal decoupling, in the TLM component thread executing the algorithm step function)

• Time consumed by a write transfer to the TLM component (this delay is returned to the initiator as a wait or time annotation in transaction), with these further qualifiers:

  • Time consumed by a single write transaction or the first write operation of a burst

  • Time consumed by a subsequent write operation in a burst

• Time consumed by a read transfer from the TLM component (this delay is returned to the initiator as a wait or time annotation in transaction), with these further qualifiers :

  • Time consumed by a single read transaction or the first read operation of a burst

  • Time consumed by a subsequent read operation in a burst

Temporal Decoupling

TLM Component Naming and Packaging

© 1984-2012- The MathWorks, Inc.    -   Site Help   -   Patents   -   Trademarks   -   Privacy Policy   -   Preventing Piracy   -   RSS