Changes between Version 34 and Version 35 of Writing Rules/Tlmt


Ignore:
Timestamp:
Feb 19, 2008, 6:38:10 PM (16 years ago)
Author:
fpecheux
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • Writing Rules/Tlmt

    v34 v35  
    1111
    1212This document describes the modeling rules for writing TLM-T SystemC simulation models for SoCLib.
    13 Those rules enforce the PDES (Parallel Discrete Event Simulation) principles. Each PDES process involved in the simulation has is own, local time, and processes synchronize through timed messages.
    14 Models complying with those rules can be used with the "standard" OSCI simulation engine (SystemC 2.x), but can be used also with others simulation engines, especially distributed, parallelized simulation engines.
    15 
    16 Besides you may also want to follow the [WritingRules/General general SoCLib rules].
     13These rules enforce the PDES (Parallel Discrete Event Simulation) principles. Each PDES process involved in the simulation has its own local time, and PDES processes synchronize through messages piggybacked with time information.
     14Models complying to these rules can be used with the "standard" OSCI simulation engine (SystemC 2.x), but can also be used also with others simulation engines, especially distributed, parallelized simulation engines.
     15
     16The interested user should also look at the [WritingRules/General general SoCLib rules].
    1717
    1818= B) Single VCI initiator and single VCI target =
    1919
    20 Figure 1 presents a minimal system containing one single initiator, and one single target. In the proposed example, the '''my_initiator''' module behavior is modeled by the SC_THREAD  '''execLoop()''', that contains an infinite loop.  The call-back function '''rspReceived()''' is executed when a VCI response packet is received by the initiator module.
     20Figure 1 presents a minimal system containing one single initiator, --VciSimpleInitiator--, and one single target, --VciSimpleTarget--. In the proposed example, the '''my_initiator''' module behavior is modeled by the SC_THREAD  '''execLoop()''', that contains an infinite loop.  The call-back function '''rspReceived()''' is executed when a VCI response packet is received by the initiator module.
    2121
    2222[[Image(tlmt_figure_1.png, nolink)]]