Changes between Version 8 and Version 9 of Writing Rules/Caba


Ignore:
Timestamp:
Mar 27, 2007, 8:07:39 PM (18 years ago)
Author:
alain
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • Writing Rules/Caba

    v8 v9  
    4040= Component indexation =
    4141
    42 In a VCI-based architecture, all initiators must be indexed. Targets are identified by their assigned address space segment. However, for simplification purposes, we'll also give an index to the targets. Index space for targets is different from index space for initiators.
     42In a VCI-based architecture, all initiators and targets must be indexed. Index space for targets is different from index space for initiators.
    4343 * The target index is used by interconnects, that decode the VCI address MSB bits to get the target index.
    4444 * The initiator index is used by the interconnect components to route the response packets.
    … …  
    4747
    4848Indexes can be
    49  * a simple scalar index, in case of a ''flat'' interconnect
     49 * a simple scalar index, in case of a ''flat'' interconnect.
    5050 * a composite index in case a hierarchical two level interconnect where each component is identified by two scalars: (cluster_index, local_index).
    5151
    … …  
    6161The advanced VCI signals are defined in [source:trunk/soclib/systemc/include/caba/interface/vci_signals.h caba/interface/vci_signals.h].
    6262
    63 As several VCI signals can have variable widths, all VCI components must be defined with templates. The [source:trunk/soclib/systemc/include/caba/interface/vci_param.h caba/interface/vci_param.h] file contains the definition of the VCI parameters object. This object must be passed as a template parameter to the component.
     63As VCI signals can have variable widths, all VCI components must be defined with templates. The [source:trunk/soclib/systemc/include/caba/interface/vci_param.h caba/interface/vci_param.h] file contains the definition of the VCI parameters object. This object must be passed as a template parameter to the component.
    6464
    6565A typical VCI component declaration is:
    … …  
    8787
    8888Most hardware components use this memory map:
    89  * VCI interconnect components contain a ''routing table'' used to decode the addresses and
     89 * VCI interconnect components contain a ''routing table'' used to decode the VCI address MSB bits and
    9090   route VCI commands to the proper targets.
    9191 * VCI target components must be able to check for segmentation violation when receiving a
    9292   command packet. Therefore, the base address and size of the segment allocated to a given
    9393   VCI target must be ''known'' by this target.
    94  * A cache controller supporting ''uncached segments'' must contain a ''cacheability table''
    95    addressed by the address MSB bits.
     94 * A cache controller supporting uncached segments must contain a ''cacheability table''
     95   addressed by the VCI address MSB bits.
    9696
    9797In order to simplify the memory map definition, and the hardware component configuration, a