Changes between Version 59 and Version 60 of Writing Rules/Tlmt

Timestamp:

Nov 15, 2008, 3:10:42 PM (17 years ago)

Author:

alain

Comment:

--

Writing Rules/Tlmt

@@ -172 +172 @@
 
 To receive a VCI response packet, a call-back function must be defined as a member function of the 
-class '''my_initiator'''. This call-back function (named '''my_nb_transport_bw()''' in the example), must be
+class '''my_initiator'''. This call-back function (named '''vci_rsp_received()''' in the example), must be
 declared in the '''my_initiator''' class and
 is executed each time a VCI response packet is received on the '''p_vci_init''' port. The function name is not 
 constrained, but the arguments must respect the following prototype:
 {{{
-  tlm::tlm_sync_enum my_nb_transport_bw                // for resp messages 
-    ( soclib_vci_types::vci_payload_type &payload,     // payload
-      soclib_vci_types::tlmt_phase_type   &phase,      // transaction phase
+  tlm::tlm_sync_enum vci_rsp_received                // for resp messages 
+    ( soclib_vci_types::tlm_payload_type &payload,     // payload
+      soclib_vci_types::tlm_phase_type   &phase,      // transaction phase
       sc_core::sc_time                   &time);       // resp time
 }}}
-
+The return value (type tlm::tlm_sync_enum)  must be sytematically set to tlm::TLM_COMPLETED in this implementation
 The function parameters are identical to those described in the forward transport function 
 
-The actions executed by the call-back function depend on the response transaction type ('''m_command''' field), as well as 
+In the general case, the actions executed by the call-back function depend on the response transaction type ('''m_command''' field), as well as 
 the '''pktid''' and '''trdid''' fields.
 
-In the proposed example :
- * In case of of a blocking read , the call-back function updates the local time, and reactivates the suspended thread.
- * In case of a non-blocking write, the call-back function does nothing.
- 
+For sake of simplicity, in the proposed example the call-back function does not make any distinction between VCI transaction types :
+
 == C.3) Initiator Constructor ==