| 1 | | [wiki:Component SocLib Components General Index] |
| 2 | | |
| 3 | | = !MappingTable Functional Description = |
| 4 | | |
| 5 | | This object is NOT an hardware component. It can be used by the system designer to describe |
| 6 | | the memory mapping and address decoding scheme of any hardware architecture build with |
| 7 | | the SoCLib hardware components. |
| 8 | | |
| 9 | | All VCI initiatores and VCI targets share the same "flat" address space, but the address decoding |
| 10 | | scheme supports a multi-level structured interconnect. |
| 11 | | |
| 12 | | == One level interconnect == |
| 13 | | |
| 14 | | This is the simplest case: |
| 15 | | * each VCI component is identified by a simple index. |
| 16 | | * and all VCI targets must have different indexes. Most hardware interconnects (such as the make the assumption that the target indexes |
| 17 | | * each VCI is identified by a simple index, and all initiators must have different indexes. The initiator index |
| 18 | | must be equal to the VCI SRCID value. |
| 19 | | * The VCI address is structured in two fields |
| 20 | | |
| 21 | | == Two level interconnect == |
| 22 | | |
| 23 | | The hardware architecture is supposed to be split into several subsystems (or clusters), |
| 24 | | with a global interconnect for inter-cluster communications, and one local interconnect in |
| 25 | | each cluster for intra-cluster communications. |
| 26 | | |
| 27 | | * each VCI component is identified by a structured index containing two indexes: |
| 28 | | * a global index that is the subsystem (or cluster) index. |
| 29 | | * a local index, that identifies the VCI component in the cluster. |
| 30 | | * All , and all targets must have different indexes. Most hardware interconnects (such as the make the assumption that the target indexes |
| 31 | | * each VCI is identified by a simple index, and all initiators must have different indexes. The initiator index |
| 32 | | must be equal to the VCI SRCID value. |
| 33 | | |
| 34 | | |
| 35 | | eand each VCI component is identified |
| 36 | | by abut the address decoding |
| 37 | | scheme supports. |
| | 1 | see [wiki:Component/MappingTable] |
