Peripheral component interconnect (PCI) backplane connectivity system-on-chip (SoC)
By designing PCI backplane integrated circuits, the SoC host is modeled as a multifunction endpoint, low-latency and high-throughput communication between SoCs are realized, and access permissions are restricted through the output address translation unit and base address register, the existing solution is solved In the technology, the problem of increased delay and high cost of PCI address space interconnection between SoCs provides transparent memory access control.
Patent Information
- Application Number
- CN202411176857.9
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Priority Date
- 2018-12-14
- Filing Date
- 2019-12-13
- Publication Date
- 2024-12-03
Smart Images

Figure CN119066027A_ABST
Abstract
Description
[0001] Information about divisional applications
[0002] This case is a divisional application. The parent case of the divisional application is an invention patent application with application date of December 13, 2019, application number 201980070121.4, and invention name “Peripheral Component Interconnect (PCI) Backplane Connectivity System on Chip (SoC)”. Technical Field
[0003] This relates to the semiconductor field. Background Art
[0004] This involves the Peripheral Component Interconnect (PCI). Summary of the invention
[0005] In at least one example, an integrated circuit includes: an interconnect communication bus; and a peripheral component interconnect (PCI) multifunction endpoint (MFN-EP) coupled to the interconnect communication bus. Each MFN-EP includes an output address translation unit (ATU) configured to translate addresses internal to the integrated circuit into PCI addresses and at least one PCI functional circuit, wherein the at least one PCI functional circuit is configured to route communications to one of the other MFN-EPs of the IC via the interconnect communication bus, wherein the at least one PCI functional circuit includes an input ATU configured to translate PCI addresses into addresses internal to the integrated circuit.
[0006] In at least one example, a method of communicating between different peripheral component interconnect root complexes (PCI RCs) includes reading, by a processor of a backplane integrated circuit (IC), memory region configuration definitions, wherein each memory region configuration definition identifies a size of a memory region, identifies an IC communicatively coupled to the backplane IC at which the memory region is located, and identifies another IC communicatively coupled to the backplane IC that is permitted to access the memory region, wherein each IC is communicatively coupled to a different multi-function endpoint (MFN-EP) of the backplane IC, and for each IC permitted to access one of the memory regions, writing, by the processor, the size of the memory region in a base address register (BAR) of a peripheral component interconnect (PCI) functional circuit of the MFN-EP coupled to the IC. The method further includes: for each IC where the memory area is located, the processor configures a translation register of an output address translation unit (ATU) in the MFN-EP coupled to the IC with a local address local to the backplane IC and an address managed by the PCIRC of the IC; and for each IC that is allowed to access one of the memory areas, the processor configures a translation register of an input ATU in the PCI functional circuit of the MFN-EP coupled to the IC with a local address local to the backplane IC, wherein the translation register of the input ATU is associated with the BAR of the PCI functional circuit of the MFN-EP.
[0007] In at least one example, an integrated circuit includes: an interconnect communication bus; and a peripheral component interconnect (PCI) multifunction endpoint (MFN-EP) coupled to the interconnect communication bus, each PCI MFN-EP including a multiplexing device, a first address translation unit (ATU), and at least one PCI function circuit, each PCI function circuit including another ATU and a base address register (BAR). BRIEF DESCRIPTION OF THE DRAWINGS
[0008] Figure 1 Shown in various examples are systems having system-on-a-chip (SoC) interconnected by peripheral component interconnect (PCI) backplane integrated circuits (ICs).
[0009] Figure 2 A PCI backplane IC is shown in various examples.
[0010] Figure 3 The base address register (BAR) structure in each example is shown.
[0011] Figure 4 The input address translation unit (ATU) in each example is shown.
[0012] Figure 5 The output ATU in each instance is shown.
[0013] Fig. 6A Another system with SoCs interconnected through a PCI backplane IC is shown in various examples.
[0014] Figure 6B Another PCI backplane IC is shown in various examples.
[0015] Fig. 7A and Figure 7B A flow chart showing a method of configuring a PCI backplane IC in various examples. DETAILED DESCRIPTION
[0016] Peripheral Component Interconnect (PCI) is an increasingly important technology for facilitating communication between computing devices and peripheral devices. PCI Express (PCIe) systems are an evolution of earlier PCI systems that rely on a serial communication interface: one serial line output from a PCIe host and one serial line input to a PCIe host. A PCI Root Complex (RC) generates transaction requests on behalf of a PCIe host and manages the PCI address space, translating between internal addressing used by a PCIe host and the PCI address space. To accomplish the translation, the PCI RC may establish a memory map that defines the relationship between the internal addresses of the PCIe host and addresses in the PCI address space.
[0017] Emerging automotive applications are being designed to include multiple systems on chips (SoCs) with high communication bandwidth and relying on low latency. Peripheral component interconnect express (PCIe) provides low latency and high throughput communication to connect between these SoCs. However, challenges are encountered when translating between independent PCI address spaces of each in the SoC. Some methods of interconnecting SOCs with independent PCI address spaces involve switches, but these solutions have disadvantages. Simple switches resort to cascade connections that increase latency when two or more SoCs are interconnected via a PCI backplane. Complex switches avoid cascade connections but are too expensive. In addition, both simple switching solutions and complex switching solutions rely on non-transparent bridges (NTBs) to translate from the PCI address space of one SoC to the PCI address space of another SoC. The use of such NTB ports interferes with or prevents memory access constraints in the SoC—for example, allowing SoC2 to read from a predefined area of the memory of SoC1 while preventing SoC3 from reading the same defined area of the memory of SoC1.
[0018] The present description teaches a PCI backplane integrated circuit (IC) that provides a cost-effective inter-SoC PCI communication device that supports the ability of a SoC to restrict access to its memory. The PCI backplane IC models the SoC host as a separate function in a PCI Multifunction Endpoint (MFN-EP). For a first SoC to communicate with a second SoC via the PCI backplane IC, the first SoC communicates with a first PCI functional circuit of a first MFN-EP that models the second SoC. The first PCI functional circuit of the first MFN-EP communicates with a second MFN-EP via an interconnect communication bus of the PCI backplane IC, and the second MFN-EP passes the communication onto the second SoC. For the first SoC to communicate with a third SoC via the PCI backplane IC, the first SoC communicates with a second PCI functional circuit of the first MFN-EP that models the third SoC. The second PCI functional circuit of the first MFN-EP communicates with a third MFN-EP via an interconnect communication bus, and the third MFN-EP passes the communication onto the third SoC. For the first SoC to communicate with a fourth SoC via the PCI backplane IC, the first SoC communicates with a third PCI functional circuit of the first MFN-EP that models the fourth SoC. The third PCI functional circuit communicates with the fourth MFN-EP via the interconnect communication bus, and the fourth MFN-EP passes the communication to the fourth SoC. In order for the second SoC to communicate with the first SoC via the PCI backplane IC, the second SoC communicates with the first PCI functional circuit of the second MFN-EP that models the first SoC. The first PCI functional circuit of the second MFN-EP communicates with the first MFN-EP via the interconnect communication bus, and the first MFN-EP passes the communication to the first SoC.
[0019] Each MFN-EP includes PCI functional circuits. Each PCI functional circuit can be configured to indirectly map transactions from the PCI address space of its associated SoC to the PCI address space of the SoC modeled by that particular PCI functional circuit. The MFN-EP further includes an output address translation unit (ATU) for mapping transactions from other SoCs to the PCI address space of the SoC associated with that MFN-EP. These mappings provide the PCI backplane IC with the ability to restrict access to PCI memory regions of each of the SoCs, as configured by each of the SoCs.
[0020] This solution provides low latency, high throughput, and transparency, which allows the SoC to selectively restrict access to its memory regions.Because the PCI backplane IC is a single device manufactured by a single manufacturer, it can be more easily qualified for use in an automobile than a multi-device solution.
[0021] exist Figure 1, the system 100 includes a first system on chip (SoC) 102 having a first PCI root complex (RC) 104, a second SoC 106 having a second RC 108, a third SoC 110 having a third RC 112, a fourth SoC 114 having a fourth RC 116, and a peripheral component interconnect backplane integrated circuit (PCI backplane IC) 120. In an example, the PCI backplane IC 120 includes a first multi-function endpoint (MFN-EP) 122, a second MFN-EP 124, a third MFN-EP 126, a fourth MFN-EP 128, an interconnect communication bus 130, a processor 132, and a memory 134. Each of the MFN-EPs 122, 124, 126, 128 is coupled to the interconnect communication bus 130 through a communication path 136. The first RC 104 is communicatively coupled to the first MFN-EP 122 via an input line 140 and an output line 142, wherein the terms "input" and "output" are labeled relative to the PCI backplane IC 120. The second RC 108 is communicatively coupled to the second MFN-EP 124 via an input line 144 and an output line 146. The third RC 112 is communicatively coupled to the third MFN-EP 126 via an input line 148 and an output line 150. The fourth RC 116 is communicatively coupled to the fourth MFN-EP 128 via an input line 152 and an output line 154. In an example, each of the lines 140-154 is a serial communication line. In another example, each of the lines 140-154 includes parallel conductors.
[0022] In some contexts, SoCs 102, 106, 110, 114 may be referred to as remote SoCs or remote hosts. In an example, one or more SoCs of system 100 may be replaced by a processor that is not a system on a chip. In an example, PCI backplane IC 120 may have three MFN-EPs instead of the four MFN-EPs illustrated. In an example, PCI backplane IC 120 may have five or more MFN-EPs instead of the four MFN-EPs illustrated. In an example, system 100 may be a component of an automobile. For example, SoCs 102, 106, 110, 114 may be remote processors within the automobile that communicate with each other via PCI backplane IC 120. One of SoCs 102, 106, 110, 114 may include a camera sensor and support backup video functionality of the automobile. One of the SoCs 102 , 106 , 110 , 114 may include a radar processor and support radar sensing and ranging functionality for the automobile (eg, to support proximity alert and / or self-driving functionality).
[0023] As further described below, each of the MFN-EPs 122, 124, 126, 128 models a remote SoC and uses that model to provide a communication portal to the remote SoC it models. For example, the first MFN-EP 122 models each of the SoCs 106, 110, 114 as a PCI functional circuit and provides the first SoC 102 with a communication portal through which to access the other SoCs 106, 110, 114. The modeling of the SoCs 102, 106, 110, 114 provided by the MFN-EPs 122, 124, 126, 128 facilitates transparency of the SoCs' access to their memory based on the SoCs attempting to access that memory, as further described below. This transparency is desirable in some applications, such as where a SoC wishes to allow one or more specific other SoCs to access its memory but prohibit another specific SoC from accessing that memory.
[0024] The first SoC 102 may complete a transaction involving the second SoC 106 by sending a transaction to the first MFN-EP 122 via input line 140, wherein the transaction identifies a PCI functional circuit embedded in the first MFN-EP 122 corresponding to the second SoC 106. The transaction is multiplexed by the first MFN-EP 122 to the appropriate PCI functional circuit embedded in the first MFN-EP 122, and that PCI functional circuit transmits the transaction to the second MFN-EP 124 via the interconnect communication bus 130. The second MFN-EP 124 then completes the transaction with the second SoC 106 via output line 146. The interconnect communication bus 130 may be referred to as an interconnect. In some cases, a response is passed back from the SoC identified by the transaction to the SoC that initiated the transaction—for example, an acknowledgement token or requested data may be passed back.
[0025] Processor 132 executes computer-readable instructions stored in memory 134. Memory 134 includes a non-transitory computer-readable storage medium storing instructions. Instructions may be stored as software and / or data. Instructions may be stored as firmware. Processor 132 configures MFN-EPs 122, 124, 126, 128 during initialization of system 100—for example, thereby managing the configuration of the size of memory areas accessible by SoCs 102, 106, 110, 114 and the configuration of memory maps.
[0026] Figure 2 Additional details of MFN-EP 122, 124, 126, 128 are shown. Figure 21. The structure of the first MFN-EP 122 presented in FIG. 1 is representative of the structure of the MFN-EPs 124, 126, 128. In an example, each of the MFN-EPs 122, 124, 126, 128 is instantiated from the same intellectual property core (IP core). An IP core is a logic block and / or data block used to manufacture an application specific integrated circuit (ASIC) or a field programmable gate array (FPGA). The first MFN-EP 122 includes a multiplexing device 170, a first PCI functional circuit 172, a second PCI functional circuit 174, a third PCI functional circuit 176, and an output address translation unit (ATU) 178. In some contexts, the PCI functional circuits 172, 174, 176 may be referred to as functional blocks.
[0027] The PCI function circuits 172, 174, 176 correspond to PCI functions that can be called by the RC 104. Each of the PCI function circuits 172, 174, 176 includes a base address register (BAR) and an input ATU. The first PCI function circuit 172 includes a BAR 180 and an input ATU 182, the second PCI function circuit 174 includes a BAR 184 and an input ATU 186, and the third PCI function circuit 176 includes a BAR 188 and an input ATU 190. In another example, the MFN-EP 122 includes two PCI function circuits. In another example, the MFN-EP 122 includes four or more PCI function circuits. In an example, each MFN-EP of the PCI backplane IC 120 includes a number of PCI function circuits that is one less than the total number of MFN-EPs in the PCI backplane IC 120. The first PCI functional circuit 172 is communicatively coupled to the interconnect communication bus 130 via a communication path 136-1. The second PCI functional circuit 174 is communicatively coupled to the interconnect communication bus via a communication path 136-2. The third PCI functional circuit 176 is communicatively coupled to the interconnect communication bus via a communication path 136-3. The output ATU 178 is communicatively coupled to the interconnect communication bus via a communication path 136-4.
[0028] Each PCI functional circuit 172-176 is associated with a specific SoC (e.g., each PCI functional circuit 172-176 models a specific SoC to RC 104). For example, first PCI functional circuit 172 is associated to SoC B, such as second SoC 106; second PCI functional circuit 174 is associated to SoC C, such as third SoC 100; and third PCI functional circuit 176 is associated to SoC D, such as fourth SoC 114. Transactions received by MFN-EP from RC 104 via input line 140 are parsed by multiplexing device 170 to identify which PCI functional circuit 172-176 the transaction involves (and therefore which SoC the transaction involves), and then, direct the transaction to the identified one of the PCI functional circuits 172-176. The PCI functional circuits 172-176 use the BARs 180, 184, 188 and the input ATUs 182, 186, 190 to map the PCI address associated with the received transaction to an address offset and to a reference to an entry in the output ATU of the specified MFN-EP. Only transactions that match one of the mappings or transactions configured into the BARs 180, 184, 188 and the input ATUs 182, 186, 190 are routed by the PCI functional circuits via the interconnect communication bus. Thus, the SoCs 102, 106, 110, 114 can benefit from the transparency of restricting access to their memory provided by the PCI backplane IC 120 by not defining the mapping of a particular SoC to its memory or to a particular region of its memory.
[0029] For example, a transaction that identifies a PCI address in the PCI address space managed by the first RC 104 involves the first PCI functional circuit 172 (and therefore involves SoC B or the second SoC 106). The first PCI functional circuit 172 determines which BAR 180 is referenced by the PCI address associated with the received transaction and uses that in the BAR 180 to index into the input ATU 182 to locate the corresponding local address of the output ATU 178 associated with the second MFN-EP 124. The first PCI functional circuit 172 establishes a master-slave relationship with the second MFN-EP 124 via the interconnect communication bus 130 and sends the transaction along with the local address to the interconnect communication bus 130 via the communication path 136-1 and to the output ATU 178 of the second MFN-EP 124 through the interconnect communication bus 130 via the interconnect communication bus 130. In an example, the interconnect communication bus 130 may be an electronic crossbar switch or an electronic matrix switch, and the master-slave relationship may be established by configuring the switches in the interconnect communication bus 130. The second MFN-EP 124 uses the address offset and the index into the output ATU 178 to determine the PCI address in the PCI address space managed by the second RC 108 to which the transaction is routed to the second RC 108 of the second SoC 106 and sends the transaction via the multiplexing device 170 and via the output communication path 146 to the second RC 108 of the second SoC 106. In this way, the transaction from the RC 104 is transmitted by the initiating SoC to the designated SoC. Additional details on how the transaction is interconnected in the SoCs 102, 106, 110, 114 are provided below with an expanded example of the configuration of the BARs 180, 184, 188, the input ATUs 182, 186, 190, and the configuration of the output ATU 178.
[0030] Figure 3Additional details of one BAR 180 are shown. Although one of the BARs 180 is described herein, the others of BARs 180, BARs 184, and BARs 188 have similar structures. The instance of BAR 180 includes a memory region size parameter 202 and a PCI address parameter 204. In an example, the instance of BAR 180 includes a region size parameter 202 that can be configured by processor 132 during initialization of system 100 to contain the size of a memory region exported by or accessible by the SoC associated with BAR 180 (recall that BAR 180 is included within a specific one of PCI functional circuits 172-176 and the specific PCI functional circuit is associated to a specific one of SoCs 102, 106, 110, 114). In an embodiment, PCI backplane IC 120 supports SoCs 102, 106, 110, 114 that can each access up to 1 GB of memory. In an embodiment, the PCI backplane IC 120 supports SoCs 102, 106, 110, 114 that can each access up to a maximum of 2 GB of memory. In an embodiment, the PCI backplane IC 120 supports SoCs 102, 106, 110, 114 that can each access up to a maximum of 5 GB of memory. In an embodiment, the PCI backplane IC 120 supports SoCs 102, 106, 110, 114 that can each access up to a maximum of 10 GB of memory. In an embodiment, one of the SoCs 102, 106, 110, 114 contains one or more memory regions accessible to one or more of the other SoCs 102, 106, 110, 114. The amount of memory accessible to the SoCs 102, 106, 110, 114 is less than the maximum amount of memory. For example, if PCI backplane IC 120 supports SoCs 102, 106, 110, 114 that can each access a maximum of 2GB of memory, then any of those SoCs 102, 106, 110, 114 can access 10kB of memory, can access 100kB of memory, can access 1MB of memory, or can access no memory.
[0031] In an embodiment, each of the MFN-EPs 122, 124, 126, 128 is configured to communicate with an external PCI address space that is a large outbound memory area containing one or more regions. In an embodiment, each of the MFN-EPs 122, 124, 126, 128 is configured to communicate with an external PCI address space of up to 1 GB of memory. In an embodiment, each of the MFN-EPs 122, 124, 126, 128 is configured to communicate with an external PCI address space of up to 2 GB of memory. In an embodiment, each of the MFN-EPs 122, 124, 126, 128 is configured to communicate with an external PCI address space of up to 5 GB of memory. In an embodiment, each of the MFN-EPs 122, 124, 126, 128 is configured to communicate with an external PCI address space of up to 10 GB of memory.
[0032] The PCI address parameter 204 may be configured during initialization of the system 100 to be associated with a PCI address in a PCI address space managed by an RC 104, 108, 112, 116 of a SoC 102, 106, 110, 114 coupled to an MFN-EP 122, 124, 126, 128 containing a BAR 180 (recall that the BAR 180 is contained within a particular one of the PCI functional circuits 172-176 which is itself contained within a particular one of the MFN-EPs 122, 124, 126, 128, and that particular one of the MFN-EPs 122, 124, 126, 128 is coupled to the RC 104, 108, 112, 116 of the particular one of the SoCs 102, 106, 110, 114). The PCI address may be provided and programmed into the BAR of the BAR 180 by the RC 104, 108, 112, 116 of the SoC 102, 106, 110, 114 coupled to the MFN-EP 122, 124, 126, 128 of the BAR 180. If the memory region size parameter 202 of one of the BARs 180, 184, 188 has a null or zero value, then the processor 132 may not allow a value to be supplied to the PCI address parameter 204 of that BAR. In part, this is how the SoC 102, 106, 110, 114 restricts access to its memory space. If a first SoC does not provide a value to the memory region size parameter 202 of any BAR of a PCI functional circuit associated with a second SoC, then the second SoC is effectively prohibited from accessing any memory of the first SoC.
[0033] Figure 4Additional details of the input ATU 182 are shown. Although the input ATU 182 is described herein, the input ATUs 186, 190 have similar structures. The input ATU 182 includes translation registers 210. Each translation register 210 includes a local address parameter 214. In an example, the translation register 210 also includes a BAR identity. The local address parameter 214 identifies the local address of the PCI backplane IC 120. The local address is an address that is unique within a localized address domain, such as within the PCI backplane IC 120. The local address can be associated to a specific one of the MFN-EPs 122, 124, 126, 128 or to a PCI function block within the PCI backplane IC 120 via the interconnect communication bus 130 of the PCI backplane IC 120. The local address parameters 214 may be configured by the processor 132 during initialization of the system 100 to associate a particular BAR of the BARs 180 of the PCI functional circuits of the MFN-EPs 122, 124, 126, 128 to a corresponding local address of the PCI backplane IC 120. In an example, one of the BARs 180 is associated to the translation registers 210 by matching the BAR identity of that BAR to the BAR identity of the translation registers 210. The BARs in the BARs 180 may be statically associated to the translation registers 210 by hardware identities. For example, a first BAR of the BARs 180 may be predefined to be associated to a first translation register 210 in the input ATU 182, and a second BAR of the BARs 180 may be predefined to be associated to a second translation register 210 in the input ATU 182, and so on.
[0034] Figure 5 Additional details of the output ATU 178 are shown. The output ATU 178 includes translation registers 220. Each translation register 220 includes a local address parameter 222, a PCI address parameter 224, and a size parameter 226. The local address parameter 222 and the PCI address parameter 224 may be configured by the processor 132 during initialization of the system 100 to associate the local address value stored in the local address parameter 222 with the PCI address value stored in the PCI address parameter 224. The size parameter 226 may be configured by the processor 132 during initialization of the system 100 to identify the size of a memory region accessible by the SoC 102, 106, 110, 114 associated with the output ATU 178.
[0035] In an example, the number of BARs 180 in each PCI functional circuit 172 to 176 is 3. In an example, the number of translation registers 210 in each input ATU 182 is 3. In an example, the number of BARs 180 in each PCI functional circuit 172 to 176 is 6. In an example, the number of translation registers 210 in each input ATU 182 is 6. In an example, the number of BARs 180 in each PCI functional circuit 172 to 176 is equal to the number of translation registers 210 in each input ATU 182. In an example, the number of translation registers 220 in each output ATU 178 is greater than 12 and less than 96. In an example, the number of translation registers 220 in each output ATU 178 is 16. In an example, the number of translation registers 220 in each output ATU 178 is 32. In an example, the number of translation registers 220 in each output ATU 178 is at least 16. To further clarify the purpose of BAR 180, the purpose of input ATU 182, and the purpose of output ATU 178, an expanded example is provided below.
[0036] In an example, the memory 134 of the PCI backplane IC 120 is configured in advance with data defining the memory regions and the sizes of those memory regions accessible by the SoCs 102, 106, 110, 114. The data also defines which of the SoCs 102, 106, 110, 114 can access the memory regions. As an example, the memory 134 stores configuration data indicating that the first SoC 102 makes a first memory region of 25 Kbytes accessible by the second SoC 106 and the third SoC, and makes a second memory region of 80 Kbytes accessible by the fourth SoC 114. In this example, the configuration data stored in the memory 134 also instructs the fourth SoC 114 to make a third memory region of 100 Kbytes accessible to the first SoC 102, a fourth memory region of 150 Kbytes accessible to the first SoC 102, a fifth memory region of 75 Kbytes accessible to the second SoC 106, and a sixth memory region of 125 Kbytes accessible to the second SoC 106.
[0037] By defining the translations 210 and 220, access to a specific memory region in the first SoC may be granted by the second SoC. On the other hand, by not defining the translations 210 and 220, access to a specific memory region in the first SoC may be prohibited by the second SoC. The translations 210 of the input ATU 182, 186, 190 and the translations 220 of the output ATU 178 of the MFN-EP 122, 124, 126, 128 facilitate the advantage of transparency of the SoC 102, 106, 110, 114 controlling access to its memory region by other SoCs 102, 106, 110, 114.
[0038] In the example, when the PCI backplane IC 120 is powered on, before a communication link has been established between the PCI backplane IC 120 and the SoCs 102, 106, 110, 114, the processor 132 reads the memory access permissions from the memory 134 and configures the memory region size parameters 202 in the appropriate BARs 180, 184, 188 of the appropriate MFN-EPs 122, 124, 126, 128. In this example, the first PCI functional circuit 172 in each of the MFN-EPs 124, 126, 128 models or is associated with the first SoC 102, and the third PCI functional circuit 176 in each of the MFN-EPs 124, 126, 128 models or is associated with the fourth SoC 114. Given the example of configuration data described above, during power-on initialization of the PCI backplane IC 120, the memory region size parameter 202 of the BARs in the BARs 180 of the first PCI functional circuit 172 of the second MFN-EP 124 is assigned a value of 25 Kbytes, the memory region size parameter 202 of the BARs in the BARs 180 of the first PCI functional circuit 172 of the third MFN-EP 126 is assigned a value of 25 Kbytes, and the memory region size parameter 202 of the BARs in the BARs 180 of the first PCI functional circuit 172 of the fourth MFN-EP 128 is assigned a value of 80 Kbytes. Continuing with this example, a value of 100 Kbytes is assigned to the memory region size parameter 202 of a BAR in the BAR 188 of the third PCI function circuit 176 of the first MFN-EP 122, a value of 150 Kbytes is assigned to another BAR in the BAR 188 of the third PCI function circuit 176 of the first MFN-EP 122, a value of 75 Kbytes is assigned to the memory region size parameter 202 of a BAR in the BAR 188 of the third PCI function circuit 176 of the second MFN-EP 124, and a value of 125 Kbytes is assigned to the memory region size parameter 202 of another BAR in the third PCI function circuit 176 of the second MFN-EP 124.
[0039] After the PCI backplane IC 120 has completed its power-on initialization, the first SoC 102 and / or the first RC 104 establish a communication link with the first MFN-EP 122, the second SoC 106 and / or the second RC 108 establish a communication link with the second MFN-EP 124, the third SoC 110 and / or the third RC 112 establish a communication link with the third MFN-EP 126, and the fourth SoC 114 and / or the fourth RC 116 establish a communication link with the fourth MFN-EP 128. During this process of establishing communication links, the MFN-EPs 122, 124, 126, 128 inform the RCs 104, 108, 112, 116 of the values of the memory region size parameters 202 of the BARs 180, 184, 188. In this way, RCs 104, 108, 112, 116 learn the memory areas they can access and the sizes of those memory areas from the other SoCs 102, 106, 110, 114. In the above example, the first RC 104 learns that it can access a 100Kbyte memory area and a 150Kbyte memory area of the fourth SoC 114; the second RC 108 learns that it can access a 25Kbyte memory area of the first SoC 102, a 75Kbyte memory area of the fourth SoC 114, and a 125Kbyte memory area of the fourth SoC 114; the third RC 112 learns that it can access a 25Kbyte memory area of the fourth SoC 114; and the fourth RC 116 learns that it can access an 80Kbyte memory area of the first SoC 102.
[0040] Each of the RCs 104, 108, 112, 116, in response to learning the memory regions it can access and the sizes of those memory regions, allocates a PCI address in its respective PCI address space corresponding to those memory regions it can access, and notifies the appropriate ones of the PCI function circuits 172, 174, 176 of the MFN-EPs 122, 124, 126, 128 to which they are communicatively linked. This allocated PCI address is the first of a block of PCI addresses allocated by the RCs 104, 108, 112, 116 for communication to the accessible memory regions, wherein the number of PCI addresses in the block is equal to the corresponding memory region size parameter 202 of the corresponding BAR of the BAR 180.
[0041] In the above example, the first RC 104 assigns the starting point of the third region of the PCI address space (which the fourth RC 116 makes accessible to the first SoC 102) to the PCI address 1000000H (this example value is a hexadecimal number as indicated by the “H” suffix) in the PCI address space managed by the first RC 104 and stores 1000000H in the PCI address parameter 204 of the first BAR of the BAR 188 of the third PCI functional circuit 176 of the first MFN-EP 122. The first RC 104 maps the start point of the fourth region of the PCI address space (which the fourth RC 116 makes accessible to the first SoC 102) to the PCI address 1020000H in the PCI address space managed by the first RC 104 and stores 1020000H in the PCI address parameter 204 of the second BAR of the BAR 188 of the third PCI function circuit 176 of the first MFN-EP 122. In doing this mapping, the first RC 104 leaves enough PCI addresses between the 1000000H address and the 1020000H address to accommodate the size of the third region of the PCI address space (100 Kbytes).
[0042] The second RC 108 maps the start point of the fifth region of the PCI address space (which the fourth RC 116 makes accessible to the second SoC 106) to the PCI address 1000000H in the PCI address space managed by the second RC 108 and stores 1000000H in the PCI address parameter 204 of the first BAR of the BAR 188 of the third PCI functional circuit 176 of the second MFN-EP 124. The second RC 108 maps the start point of the sixth region of the PCI address space (which the fourth RC 116 makes accessible to the second SoC 106) to the PCI address 1020000H in the PCI address space managed by the second RC 108 and stores 1020000H in the PCI address parameter 204 of the second BAR of the BAR 188 of the third PCI functional circuit 176 of the second MFN-EP 124. When performing this mapping, the second RC 108 leaves enough PCI addresses between the addresses 1000000H and 1020000H to accommodate the size of the fifth region of the PCI address space (75 Kbytes). The second RC 108 maps the start of the first region of the PCI address space (which the first RC 104 makes accessible to the second SoC 106 and the third SoC 110) to the PCI address 1040000H in the PCI address space managed by the second RC 108 and stores 1040000H in the PCI address parameter 204 of the first BAR of the BAR 180 of the first PCI function circuit 172 of the second MFN-EP 124.
[0043] The third RC 112 maps the start point of the first region of the PCI address space (which the first RC 104 makes accessible to the third SoC 110 and the second SoC 106) to the PCI address 1000000H in the PCI address space managed by the third RC 112 and stores 1000000H in the PCI address parameter 204 of the first BAR of the BAR 180 of the first PCI functional circuit 172 of the third MFN-EP 126. The fourth RC 116 maps the start point of the second region of the PCI address space (which the first RC 104 makes accessible to the fourth SoC 114) to the PCI address 8000000H in the PCI address space managed by the fourth RC 116 and stores 8000000H in the PCI address parameter 204 of the first BAR of the BAR 180 of the first PCI functional circuit 172 of the fourth MFN-EP 128.
[0044] The example addresses above are arbitrary, and different addresses may be used in examples. Note that the PCI address parameter 204 value (1040000H) of the first BAR of the BAR 180 of the first PCI function circuit 172 of the second MFN-EP 124 is different from the PCI address parameter 204 value (1000000H) of the first BAR of the BAR 180 of the first PCI function circuit 172 of the third MFN-EP 126, even though both PCI address parameters 204 are associated with the same first region of the PCI address space controlled by the first RC 104. This illustrates the independence between the PCI address spaces managed by each of the individual RCs 104, 108, 112, 116.
[0045] The memory 134 of the PCI backplane IC 120 may also be configured with the addresses of the memory areas that the RCs 104, 108, 112, 116 associate to make accessible to other SoCs 102, 106, 110, 114. During power-on initialization of the PCI backplane IC 120, the processor 132 may read these addresses from the memory 134 and configure these addresses into the PCI address parameters 224 of the translation registers 220 in the output ATU 178 of the present MFN-EP 122, 124, 126, 128. The local address value of the PCI backplane IC 120 may be assigned by the processor 132 to the local address parameter 222 of this translation register 220 associated with the memory region, and the same local address value may be assigned by the processor 132 to the local address parameter 214 of the corresponding translation register 210 in the input ATU 182, 186, 190 of the corresponding one of the PCI functional circuits 172, 174, 176 of the appropriate MFN-EP 122, 124, 126, 128 (e.g., the MFN-EP associated to the SoC 102, 106, 110, 114 that has been authorized to access the memory region). In an alternative example, the RC 104, 108, 112, 116 may inform the PCI backplane IC 120 during communication link establishment of a PCI address associated to a memory region accessible by the SoC 102, 106, 110, 114, and the processor 132 may configure the translation registers 220, 210 at that time.
[0046] Continuing with the above example, the PCI backplane IC 120 is configured in advance with data indicating that the first RC 104 associates PCI address 3000000H with a first memory region accessible to the second SoC 106 and the third SoC 110, and associates PCI address 3080000H with a second memory region accessible to the fourth SoC 114. The PCI backplane IC 120 is configured in advance with data indicating that the fourth RC 116 associates PCI address 3000000H with a third memory region accessible to the first SoC 102, associates PCI address 3040000H with a fourth memory region accessible to the first SoC 102, associates PCI address 3080000H with a fifth memory region accessible to the second SoC 106, and associates PCI address 30B0000H with a sixth memory region accessible to the second SoC 106. Note that both the first RC 104 and the fourth RC 116 have accessible memory associated with duplicate PCI addresses (3000000H and 3080000H are used by both the first RC 104 and the fourth RC 116), but this is allowed because they are PCI addresses in the PCI address space independently controlled by each RC.
[0047] The PCI backplane IC 120 associates local address 183000000H to PCI address 3000000H and local address 183080000H to PCI address 3080000H of the first RC 104. The PCI backplane IC 120 associates local address 303000000H to PCI address 3000000H, local address 303040000H to PCI address 3040000H, local address 303080000H to PCI address 3080000H, and local address 3030B0000H to PCI address 30B0000H of the fourth RC 116. Note that PCI backplane IC 120 associates different local addresses to PCI address 3000000H of first RC 104 and PCI address 3000000H of fourth RC 116 , and associates different local addresses to PCI address 3080000H of first RC 104 and PCI address 3080000H of fourth RC 116 .
[0048] The PCI backplane IC 120 configures the first translation register 220 of the output ATU 178 of the first MFN-EP 122 to store 183000000H in its local address parameter 222 and 3000000H in its PCI address parameter 224. This first translation register 220 corresponds to the first memory area that the first SoC 102 makes accessible to the second SoC 106 and the third SoC 110. The PCI backplane IC 120 configures the second translation register 220 of the output ATU 178 of the first MFN-EP 122 to store 183080000H in its local address parameter 222 and 3080000H in its PCI address parameter 224. This second translation register 220 corresponds to the second memory area that the first SoC 102 makes accessible to the fourth SoC 114. The PCI backplane IC 120 configures the first translation register 210 of the input ATU 182 of the first PCI function circuit 172 of the second MFN-EP 124 to store 183000000H in its local address parameter 214 and configures the first translation register 210 of the input ATU 182 of the first PCI function circuit 172 of the third MFN-EP 126 to store 183000000H in its local address parameter 214. The first translation register 210 of the input ATU 182 of the first PCI function circuit 172 of the second MFN-EP 124 is associated with the first BAR of the BAR 180 of the first PCI function circuit 172 of the second MFN-EP 124. The first translation register 210 of the input ATU 182 of the first PCI function circuit 172 of the third MFN-EP 126 is associated with the first BAR of the BAR 180 of the first PCI function circuit 172 of the third MFN-EP 126. The PCI backplane IC 120 configures the first translation register 210 of the input ATU 182 of the first PCI function circuit 172 of the fourth MFN-EP 128 to store 183080000H in its local address parameter 214. The first translation register 210 of the input ATU 182 of the first PCI function circuit 172 of the fourth MFN-EP 128 is associated with the first BAR of the BAR 180 of the first PCI function circuit 172 of the fourth MFN-EP 128.
[0049] The PCI backplane IC 120 may configure the interconnect communication bus 130 to route communications involving local addresses extending from 180000000H to 1FFFFFFFFH to the first MFN-EP 124. The PCI backplane IC 120 may configure the interconnect communication bus 130 to route communications involving local addresses extending from 200000000H to 27FFFFFFFH to the second MFN-EP 124. The PCI backplane IC 120 may configure the interconnect communication bus 130 to route communications involving local addresses extending from 280000000H to 2FFFFFFFFH to the third MFN-EP 126. The PCI backplane IC 120 may configure the interconnect communication bus 130 to route communications involving local addresses extending from 300000000H to 37FFFFFFFH to the fourth MFN-EP 128. In another example, PCI backplane IC 120 may configure the interconnect communication bus 130 to route communications according to a different local address routing scheme than the example provided above.
[0050] The PCI backplane IC 120 configures the first translation register 220 of the output ATU 178 of the fourth MFN-EP 128 to store 303000000H in its local address parameter 222 and 3000000H in its PCI address parameter 224. The PCI backplane IC 120 configures the second translation register 220 of the output ATU 178 of the fourth MFN-EP 128 to store 303040000H in its local address parameter 222 and 3040000H in its PCI address parameter 224. The PCI backplane IC 120 configures the third translation register 220 of the output ATU 178 of the fourth MFN-EP 128 to store 303080000H in its local address parameter 222 and 3080000H in its PCI address parameter 224. The PCI backplane IC 120 configures the fourth translation register 220 of the output ATU 178 of the fourth MFN-EP 128 to store 3030B0000H in its local address parameter 222 and 30B0000H in its PCI address parameter 224 .
[0051] The PCI backplane IC 120 configures the first translation register 210 of the input ATU 190 of the third PCI function circuit 176 of the first MFN-EP 122 to store 303000000H in its local address parameter 214 and configures the second translation register 210 of the input ATU 190 of the third PCI function circuit 176 of the first MFN-EP 122 to store 303040000H in its local address parameter 214. The first translation register 210 of the input ATU 190 of the third PCI function circuit 176 of the first MFN-EP 122 is associated with a first BAR of the BAR 188 of the third PCI function circuit 176 of the first MFN-EP 122, and the second translation register 210 of the input ATU 190 of the third PCI function circuit 176 of the first MFN-EP 122 is associated with a second BAR of the BAR 188 of the third PCI function circuit 176 of the first MFN-EP 122.
[0052] The PCI backplane IC 120 configures the first translation register 210 of the input ATU 190 of the third PCI function circuit 176 of the second MFN-EP 124 to store 303080000H in its local address parameter 214 and configures the second translation register 210 of the input ATU 190 of the third PCI function circuit 176 of the second MFN-EP 124 to store 3030B0000H in its local address parameter 214. The first translation register 210 of the input ATU 190 of the third PCI function circuit 176 of the second MFN-EP 124 is associated with the first BAR of the BAR 188 of the third PCI function circuit 176 of the second MFN-EP 124, and the second translation register 210 of the input ATU 190 of the third PCI function circuit 176 of the second MFN-EP 124 is associated with the second BAR of the BAR 188 of the third PCI function circuit 176 of the second MFN-EP 124.
[0053] After the BARs 180, 184, 188, the translation registers 210 of the input ATUs 182, 186, 190, and the translation registers 220 of the output ATUs 178 of the MFN-EPs 122, 124, 126, 128 have been initialized and configured as described above, the PCI backplane IC 120 is ready to route transactions among the SoCs 102, 106, 110, 114. An example of transaction routing using the exemplary configuration described above is now described.
[0054] During operation of the system 100, the SoC 102 sends a transaction to the PCI address 1000000H to the first MFN-EP 122 via the first RC 104 over the input communication path 140. This PCI address 1000000H is associated with the first BAR of the BAR 188 of the third functional circuit 176 of the first MFN-EP 122 and is the first address in the associated block of PCI addresses. This PCI address is mapped to the local address 303000000H by the input ATU 190 of the third functional circuit 176 of the first MFN-EP 122. The third functional circuit 176 of the first MFN-EP 122 sends the transaction involving the local address 303000000H onto the interconnect communication bus 130. The interconnect communication bus 130 routes this to the fourth MFN-EP 128. The fourth MFN-EP 128 finds the translation register 220 in its output ATU 178 that maps the local address 303000000H to the PCI address 3000000H. Then, the fourth MFN-EP 128 sends the transaction involving the PCI address 30000000H to the fourth RC 116.
[0055] The above example illustrates how a SoC 102, 106, 110, 114 may make a region of its memory accessible to a specific other of the SoCs 102, 106, 110, 114—granting access to some of the SoCs 102, 106, 110, 114 and restricting access to other of the SoCs 102, 106, 110, 114. This example also illustrates how the PCI address space of one RC 104, 108, 112, 116 may be translated by the PCI backplane IC 120 into the PCI address space of a different RC of the RCs 104, 108, 112, 116. This approach provides many advantages over alternative interconnect technologies that may not support the ability to restrict access to SoCs 102, 106, 110, 114 individually (e.g., allowing a first SoC to access a first region of PCI address space and restricting a second SoC and other SoCs from accessing the first region, and allowing a second SoC to access a second region of PCI address space and restricting the first SoC and other SoCs from accessing the second region).
[0056] Fig. 6A and Figure 6BAnother example of a PCI backplane IC 121 is shown in the context of system 400. In the example, the PCI backplane IC 121 includes a first multi-function endpoint (MFN-EP) 123, a second MFN-EP 125, a third MFN-EP 127, an interconnect communication bus 130, a processor 132, a memory 134, and a local function circuit 135. The PCI backplane IC 121 shares several of the same structures as the PCI backplane IC 120, and these similar structures operate similarly to the corresponding structures of the PCI backplane IC 120. The local function circuit 135 provides some processing directly, rather than offloading transactions to the SoC 102, 106, 110 for processing. The local function circuit 135 can be an accelerator processing function. The local function circuit 135 can be an on-chip peripheral. The local function circuit 135 can be an IP block.
[0057] Reference now Figure 6B , each MFN-EP 123, 125, 127 has a fourth PCI function circuit 177 that receives transactions addressed to a local function circuit 135 by the RC 104 and transmits the transactions to the interconnect communication bus 130 via the communication path 136-5, and to the local function circuit 135 via the interconnect communication bus 130 for processing. In an example, the PCI backplane IC 121 includes two or more local function circuits 135 and two or more MFN-EPs, where each of the MFN-EPs includes a number of PCI function circuits 177 that matches the number of local function circuits 135. Note that because PCI transactions inherently identify functions, there is no need to translate the address of the PCI backplane IC 121 to route transactions to the local function circuits 135.
[0058] Fig. 7A and Figure 7B A method 300 for communicating between different peripheral component interconnect root complexes (PCI RCs) is shown. The sequence of steps of the method 300 spans Fig. 7A and Figure 7B . refer to Fig. 7AAt block 302, the method 300 includes reading, by a processor of a backplane integrated circuit (IC) (e.g., a processor 132 of a PCI backplane IC 120, 121), memory region configuration definitions, wherein each memory region configuration definition identifies a size of a memory region, identifies an IC where a memory region is located that is communicatively coupled to the backplane IC, and identifies another IC communicatively coupled to the backplane IC that is allowed to access the memory region, wherein each IC (e.g., SoC 104, 106, 110, 114) is communicatively coupled to a different multi-function endpoint (MFN-EP) of the backplane IC (e.g., MFN-EP 122, 124, 126, 128, 123, 125, 127). In an example, the backplane IC is a PCI backplane IC 120, 121. In an example, the processor 132 reads the memory configuration definitions from a memory 134. In an example, the processor 132 reads the memory configuration definitions from a memory external to the backplane IC.
[0059] At block 304, the method 300 includes, for each IC (e.g., SoC 104, 106, 110, 114) that is allowed to access one of the memory regions, writing, by the processor, the size of the memory region in a base address register (BAR) of a peripheral component interconnect (PCI) functional circuit coupled to the MFN-EP of the IC. For each memory region derived by the IC, the size of the memory region is programmed by the processor 132 into one or more of the BARs 180, 184, 188 of the corresponding one of the PCI functional circuits 172, 174, 176 that models the IC that is making the memory region accessible by one of the PCI functional circuits 172, 174, 176 via the IC associated thereto.
[0060] At box 306, method 300 includes configuring, by a processor (e.g., processor 132), for each IC where a memory region (e.g., a memory region that SoC 102, 106, 110, 114 is making accessible to another of the SoCs), a translation register (e.g., translation register 120) in an output address translation unit (ATU) (e.g., ATU 178) coupled to the IC with a local address that is local to the backplane IC (e.g., PCI backplane IC 120, 121) and an address managed by a PCI RC (e.g., one of RC 104, 108, 112, 116) of the IC. The processing of block 306 can be broken down into two parts: (A) assigning a local address local to the backplane IC to this memory area accessible by the IC and (B) configuring the translation registers of the ATU in the MFN-EP coupled to the IC.
[0061] At box 308, method 300 includes, for each IC that is allowed to access one of the memory regions (e.g., one of the memory regions that SoC 102, 106, 110, 114 is making accessible to another one of the SoCs), configuring, by the processor, a translation register (e.g., translation register 210) of an input ATU (e.g., one of input ATUs 182, 186, 190) in a PCI functional circuit (e.g., one of PCI functional circuits 172, 174, 176, 177) of an MFN-EP coupled to the IC with a local address that is local to the backplane IC, wherein the translation register of the input ATU is associated to a BAR of the PCI functional circuit of the MFN-EP.
[0062] At box 310, the method 300 includes, for each IC that is allowed to access a memory area (e.g., a memory area that is accessible to another one of the SoCs 102, 106, 110, 114), receiving, by an MFN-EP coupled to the IC, a PCI address managed by a PCI RC of the IC (e.g., one of PCI RCs 104, 108, 112, 116) and configuring the PCI address into a BAR of a PCI functional circuit of the MFN-EP coupled to the IC.
[0063] Reference now Figure 7B At block 312, the method 300 includes receiving, by the MFN-EP, a PCI transaction identifying a PCI functional circuit of the MFN-EP, wherein the PCI transaction includes a PCI address in a PCI address space managed by a PCI RC of an IC coupled to the MFN-EP, wherein the PCI functional circuit is associated to the IC where a memory region is located, and the IC coupled to the MFN-EP is allowed to access the memory region.
[0064] At block 314, the method 300 includes looking up, by the PCI functional circuit, a BAR of the PCI functional circuit based on the PCI address in the PCI transaction. At block 316, the method 300 includes reading, by the PCI functional circuit, a translation register associated with the looked-up BAR of the PCI functional circuit. At block 318, the method 300 includes determining, by the PCI functional circuit, a local address based on the translation register and the PCI address in the PCI transaction.
[0065] At block 320, the method 300 includes transmitting, by the PCI functional circuit, a PCI transaction to a local address via an interconnect communication bus of the backplane IC. At block 322, the method 300 includes routing the PCI transaction to a MFN-EP coupled to the IC where the memory region is located through the interconnect communication bus (e.g., the interconnect communication bus 130). At block 324, the method 300 includes transmitting, by the MFN-EP coupled to the IC where the memory region is located, the PCI transaction to a PCI RC of the IC where the memory region is located.
[0066] Modifications are possible in the arrangements described, and other alternative arrangements are possible within the scope of the claims.
Claims
1. A circuit comprising: A first functional circuit comprising: a first plurality of registers, each of the first plurality of registers configured to store an address associated with a memory region of a second circuit; and a first input address translation unit comprising a plurality of translation registers, each of the plurality of translation registers configured to associate one of the first plurality of registers to a local address associated with the second circuit, The first functional circuit is configured to: receiving a first transaction involving the second circuit, wherein the first transaction is associated with a first address; determining a first register from the first plurality of registers based on the first address; determining a first translation register from the plurality of translation registers based on the first register; determining a first local address associated with the second circuit based on the first translation register of the first input address translation unit; and The first transaction is transmitted to the second circuit based on the first local address.
2. The circuit of claim 1 , wherein the first functional circuit is configured to: The first input address translation unit is indexed based on the first register to determine the first native address.
3. The circuit according to claim 1, further comprising: an interconnect communication bus coupling said circuit with said second circuit; as well as a second functional circuit comprising a second plurality of registers and a second input address translation unit, wherein the second functional circuit is configured to: receiving a second transaction involving a third circuit, wherein the second transaction is associated with a second address; determining a second local address associated with the third circuit based on the second address, the second plurality of registers, and the second input address translation unit; as well as The second transaction is transmitted to the third circuit based on the second local address.
4. The circuit according to claim 3, further comprising: an output address translation unit configured to receive an output transaction involving the circuit, Wherein the output address translation unit comprises a plurality of output translation registers, each of the plurality of output translation registers being configured to store an output local address parameter, an address parameter associated with the interconnect communication bus, and a size parameter.
5. The circuit of claim 4, wherein: The size parameter identifies a memory size accessible to a device coupled to the circuit.
6. The circuit of claim 5, wherein: The memory size is associated with a memory region of the second circuit.
7. The circuit according to claim 3, wherein the first functional circuit establishes a master-slave relationship with the second functional circuit via the interconnection communication bus.
8. The circuit of claim 1, wherein: Each of the plurality of translation registers is configured to store an input native address parameter and a register identity.
9. The circuit of claim 8, wherein: The number of the first plurality of registers is equal to the number of the plurality of translation registers.
10. A method comprising: reading, by a processor, memory region configuration definitions for a memory region, wherein each memory region configuration definition identifies a size of a memory region, identifies a device in which the memory region is located, and identifies another device that is permitted to access the memory region; writing, by the processor, for each device that is allowed to access one of the memory regions, the size of the memory region into a base address register BAR of a functional circuit coupled to an interface circuit of the device, wherein each device is coupled to a different interface circuit; for each device having one of the memory regions, configuring, by the processor, a translation register of an output address translation unit (ATU) in the interface circuit coupled to the device with a local address; and For each device that is allowed to access one of the memory regions, configuring, by the processor, a translation register of an input ATU in the functional circuit of the interface circuit coupled to the device with the local address, wherein the translation register of the input ATU is associated with the BAR of the functional circuit of the interface circuit.
11. A method comprising: receiving, by the first functional circuit, from the first circuit a first transaction involving the second circuit, wherein the first transaction is associated with a first address; determining, by the first functional circuit, a first register from a plurality of registers based on the first address, wherein each of the plurality of registers stores an address associated with a memory region of the second circuit accessible to the first circuit; determining, by the first functional circuit, a first translation register from a plurality of translation registers of a first input address translation unit based on the first register, wherein each of the plurality of translation registers associates one of the plurality of registers to a local address associated with the second circuit; determining, by the first functional circuit, a first local address based on the first translation register of the first input address translation unit; as well as The first transaction is transmitted by the first functional circuit to the second circuit based on the first local address.
12. The method according to claim 11, further comprising: The first input address translation unit is indexed by the first functional circuit based on the first register to determine the local address.
13. The method according to claim 11, wherein: The first circuit is coupled to the second circuit via an interconnect communication bus.
14. The method according to claim 13, further comprising: receiving, by a second functional circuit from the second circuit, a second transaction involving a third circuit, wherein the second transaction is associated with a second address; determining, by the second functional circuit, a second local address based on the second address, a second plurality of registers, and a second input address translation unit of the second functional circuit; as well as The second transaction is transmitted by the second functional circuit to the third circuit based on the second local address.
15. The method according to claim 14, further comprising: A master-slave relationship is established by the first functional circuit and the second functional circuit via the interconnection communication bus.
16. The method of claim 13, further comprising: receiving the first transaction by an output address translation unit of the second circuit, Wherein the output address translation unit comprises a plurality of output translation registers, wherein each of the plurality of output translation registers stores an output local address parameter, an address parameter associated with the interconnect communication bus, and a size parameter.
17. The method of claim 16, wherein: The size parameter identifies a memory size accessible by the first circuit.
18. The method of claim 17, wherein: The memory size is associated with a memory region of the second circuit.
19. The method of claim 11, wherein: Each of the plurality of translation registers stores an input native address parameter and a register identity.
