Changes between Version 26 and Version 27 of Writing Rules/Tlmt

Timestamp:

Dec 28, 2007, 4:09:21 PM (17 years ago)

Author:

alain

Comment:

--

Writing Rules/Tlmt

@@ -182 +182 @@
 To receive a VCI command packet, a call-back function must be defined as a member function of the class '''my_target'''. This call-back function (named '''cmdReceived()''' in the example), will be executed each time a VCI command packet is received on the '''p_vci''' port. The function name is not constrained, but the arguments must respect the following prototype:
 {{{
-void  cmdReceived(vci_cmd_t  *cmd,
+uint32_t  cmdReceived(vci_cmd_t  *cmd,
                uint32_t  time)
 }}}  
@@ -230 +230 @@
 
     /////////////// call-back function 
-    sc_time  cmdReceived(vci_cmd_t *cmd, 
+    uint32_t  cmdReceived(vci_cmd_t *cmd, 
                 uint32_t cmd_time) 
     {
@@ -276 +276 @@
 As described in Figure 4, when a VCI command packet - sent by the corresponding arbitration thread - is received by a VCI target, two synchronization mechanisms are activated :
  * The '''cmdReceived()''' function sends a VCI response packet with a date to the source initiator, through the '''!VciVgmn''' response network. The corresponding date can be used to update the initiator local clock.
- * The '''cmdReceived()''' function returns a date to the arbitration thread. This date is used to update the arbitration thread local time.  
+ * The '''cmdReceived()''' function returns a date to the arbitration thread. This date is used to update the arbitration thread local clock.  
 
 [[Image(tlmt_figure_4.png, nolink)]]