Changes between Version 7 and Version 8 of Component/Vci Pi Initiator Wrapper

Timestamp:

Feb 10, 2008, 10:56:39 AM (17 years ago)

Author:

alain

Comment:

--

Component/Vci Pi Initiator Wrapper

@@ -8 +8 @@
 It behaves as an intitiator on the PIBUS interface, and behaves as a target on
 the VCI interface. It can be used by a VCI initiator to interface a PIBUS based system on chip.
- * The VCI address and DATA fields must have 32 bits.
- * The VCI fields PLEN, CONTIG, CONS, WRAP, CFIXED, CLEN are ignored.
- * The supported PIBU response codes are PI_ACK_RDY, PI_ACK_WAT, and PI_ACK_ERR.
- * The VCI initiator is supposed to be "fair" : when a command packet starts, the CMDVAL signal is true until the last word of the VCI packet (marqued by the EOP signal), and the RSPACK signal is supposed to be always true.
- * The VCI command packet can have any length.
- * Only the two VCI commands VCI_CMD_READ & VCI_CMD_WRITE are supported.
- * Most output ports, including PI.A, PI.LOCK, VCI.RDATA, and VCI.RERROR are Mealy signals.
 
-== 2) Component definition& usage ==
+== 2) Component definition & usage ==
 
 source:trunk/soclib/soclib/module/network_component/vci_pi_initiator_wrapper/caba/metadata/vci_pi_initiator_wrapper.sd
@@ -45 +38 @@
  * soclib::caba::!VciTarget<vci_param> '''p_vci''' : The VCI port
  * soclib::caba::!PibusInitiator '''p_pi''' : The PIBUS port
+
+== 4) TLM-T Implementation ==
+
+There is no TLM-T implementation for this component.
+