Changes between Version 2 and Version 3 of Component/Vci Anoc

Timestamp:

Mar 5, 2009, 5:59:56 PM (15 years ago)

Author:

ivan.miro-panades@…

Comment:

--

Component/Vci Anoc

@@ -52 +52 @@
 The VCI request/response commands are converted into ANOC packets of 38 bits per flit. This conversion is represented in the next table. The yellow areas are reserved areas. The first flit contains the ANOC routing path while the second flit contains the VCI address. The third flits encodes all the information of the request command. A VCI read request command requires only these three flits while a write request command requires additional data flits. The forth and following flits contains the data to write and its associated byte enable signals.
 
+'''VCI request command encoded into a ANOC packet:'''
 
 [[Image(Diapositive3.GIF, align=top,nolink)]]
 
 The VCI response packet is similar as the request packet. The first flit contains the ANOC routing path while the second contains the response information. The response packet to a VCI write request contains just two flits, while the response to a VCI read request contains the additional flits. The third and following flits are the read data of the read request command.
+
+'''VCI response command encoded into a ANOC packet:'''
 
 [[Image(Diapositive4.GIF, align=top,nolink)]]
@@ -73 +76 @@
 ''width_network+ height_network -1 <= 9''
 [[BR]]
+[[BR]]
 
 == 2) Demonstrator platform ==
 The basic multi_timer-mips32 platform has been implemented using the vci_anoc_network interconnect. This demonstrator platform can be fond:
 
-''soclib/platform/topcells/caba-anoc-multi_timer-mips32
-''
+''soclib/platform/topcells/caba-anoc-multi_timer-mips32''
+
 The vci_anoc_network module is located:
 
-''soclib/module/network_component/vci_anoc_network
-''
+''soclib/module/network_component/vci_anoc_network''