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

Timestamp:

Dec 27, 2007, 10:10:23 AM (17 years ago)

Author:

alain

Comment:

--

Writing Rules/Tlmt

@@ -249 +249 @@
 Therefore, the network is actually modeled as a cross-bar : In a physical network such as the multi-stage network described in Figure 2.a, conflicts can appear at any intermediate switch. In the '''VciVgmn''' network described in Figure 2.b, conflicts can only happen at the output ports. It is possible to model to specify a specific latency for each input/output couple. As in most physical interconnects, the general arbitration policy is round-robin.
 
-
-
-
-
-  
+[[Image(tlmt_figure_2.png, nolink)]]
 
 == E.1) Generic network modeling ==
 
- A in most physical network on chip, there is actually two fully independent networks for command packets and response packets. There is a routing function for each input port, and an arbitration function for each output port, but the two networks are not symmetrical :
+ As in most physical network on chip, there is actually two fully independent networks for command packets and response packets. There is a routing function for each input port, and an arbitration function for each output port, but the two networks are not symmetrical :
  * For the command network, the arbitration policy is distributed: there is one arbitration thread for each output port (i.e. one arbitration thread for each VCI target). Each arbitration thread is modeled by a SC_THREAD, and contain a local clock.
  * For the response network, there is no conflicts, and there is no need for arbitration. Therefore, there is no thread (and no local time) in the response network that is implemented by simple function calls.
 
 This is illustrated in Figure 3 for a network with 2 initiators and three targets :  
-As there is generally no thread attached to a in the physical interconnects, there
-
+
+[[Image(tlmt_figure_3.png, nolink)]]
 
 == E.2) VCI initiators and targets synchronisations ==
@@ -273 +269 @@
  * The '''cmdReceived()''' call-back function returns a date to the arbitration thread. This date is used to update the arbitration thread local time.  
 
+[[Image(tlmt_figure_4.png, nolink)]]
+
 = F) Interrupt modeling =
 
@@ -278 +276 @@
 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)]]
 
 == F.1) Source modeling ==