Changes between Version 15 and Version 16 of Writing Rules/Tlmt

Timestamp:

Dec 27, 2007, 10:43:53 AM (16 years ago)

Author:

alain

Comment:

--

Writing Rules/Tlmt

@@ -18 +18 @@
 = B) Single VCI initiator and single VCI target =
 
-Figure 1 presents a minimal system containing one single initiator, and one single target. In the proposed example, the initiator module doesn't contains any parallelism, and can be modeled by a single SC_THREAD, describing a single PDES process. The activity of the '''my_initiator ''' module is described by the SC_THREAD '''execLoop()''', that contain an infinite loop. The variable '''m_time''' represents the PDES process local time.
+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 member variable '''m_time''' ('''H''' on the figure) represents the PDES process local time. The call-back function '''rspReceived()''' is executed when a VCI response packet is received by the initiator module.
 
 [[Image(tlmt_figure_1.png, nolink)]]
 
-Contrary to the initiator, the target module has a purely reactive behaviour. There is no need to use a SC_THREAD to describe the target behaviour : A simple method is enough. 
+Contrary to the initiator, the target module has a purely reactive behaviour. There is no need to use a SC_THREAD : The target behaviour is entirely described by the call-back function '''cmdReceived()''', that is executed when a VCI command
+packet is received by the target module.
 
 The VCI communication channel is a point-to-point bi-directionnal channel, encapsulating two separated uni-directionnal channels : one to transmit the VCI command packet, one to transmit the VCI response packet.
@@ -274 +275 @@
 
 Interrupts are asynchronous events that are not transported by the VCI network.
-As illustrated in Figure 5, each interrupt line is modeled by a specific point to point, uni-directional channel. It use two ports of type ''!'IrqOutPort''' and '''!IrqinPort''' that must be declared as member variables of the source and destination modules respectively.
+As illustrated in Figure 5, each interrupt line is modeled by a specific point to point, uni-directional channel. It use two ports of type '''!IrqOutPort''' and '''!IrqinPort''' that must be declared as member variables of the source and destination modules respectively.
 
 [[Image(tlmt_figure_5.png, nolink)]]