# Patent

## Title
Design tool selection and implementation of port adapters

## Abstract

Methods and apparatus are provided for allowing interconnection between ports associated with primary and secondary components in an embedded system. Ports may only support a particular bus type or set of attributes and a variety of ports may be incompatible. Bus types include Peripheral Components Interface (PCI) and Advanced Microcontroller Bus Architecture (AMBA) while attributes include bursting, non-bursting, word-wide, byte-wide, etc. Port adapters components are automatically selected from a library of port adapter components to allow connection of incompatible ports. Port adapters can be shared, chained, and intelligently selected for increased efficiency.

## Background
CROSS-REFERENCE TO RELATED APPLICATIONS
The present invention is related to concurrently filed U.S. patent application Ser. No. 11/216,688 titled DESIGN TOOL CLOCK DOMAIN CROSSING MANAGEMENT by Jeffrey Orion Pritchard, Paul Scheidt, Timothy Allen, the entirety of which is incorporated by reference for all purposes.
BACKGROUND OF THE INVENTION
1. Field of the Invention
The present invention relates to port adapters. In one example, the present invention relates to methods and apparatus for efficiently selecting and implementing port adapters on a programmable chip system.
2. Description of Related Art
Primary and secondary components in an embedded system are typically connected using compatible ports. In some examples, primary and secondary components have Peripheral Components Interface (PCI) or Advanced Microcontroller Bus Architecture (AMBA) ports that allow interconnection. Intellectual property (IP) blocks for implementing components are configured specifically with support for particular ports. Intellectual property blocks are compatible by construction.
Designers are forced to select only IP blocks that have support for particular standards or characteristics, preventing design flexibility. In other examples, standard crossing bridges are manually inserted into a design and components supporting particular standards are segregated onto different portions of a design.
Techniques and mechanisms for connecting ports associated with primary and secondary components have significant limitations. Consequently, it is desirable to provide improved methods and apparatus for allowing connections between ports associated with components in an embedded system.
SUMMARY OF THE INVENTION
Methods and apparatus are provided for allowing interconnection between ports associated with primary and secondary components in an embedded system. Ports may only support a particular bus type or set of attributes and a variety of ports may be incompatible. Bus types include Peripheral Components Interface (PCI) and Advanced Microcontroller Bus Architecture (AMBA) while attributes include bursting, non-bursting, word-wide, byte-wide, etc. Port adapters components are automatically selected from a library of port adapter components to allow connection of incompatible ports. Port adapters can be shared, chained, and intelligently selected for increased efficiency.
In one embodiment, a technique for implementing a programmable chip is provided. A first master component including a first master component port is received. A first slave component including a first slave component port is received. An indication to connect the first master component port to the first slave component port is received. The first master component port and the first slave component port are incompatible. A first port adapter component is selected from a library of port adapter components. The first master component port is connected to the first slave component port through the first port adapter component.
These and other features and advantages of the present invention will be presented in more detail in the following specification of the invention and the accompanying figures, which illustrate by way of example the principles of the invention.



BRIEF DESCRIPTION OF THE DRAWINGS
The invention may best be understood by reference to the following description taken in conjunction with the accompanying drawings, which illustrate specific embodiments of the present invention.
FIG. 1 is a diagrammatic representation of a programmable chip.
FIG. 2 is a diagrammatic representation showing master ports and slave ports associated programmable chip processor and peripherals.
FIG. 3 is a diagrammatic representation showing port adapter components
FIG. 4 is a diagrammatic representation showing a port adapter chain.
FIG. 5 is a diagrammatic representation showing an interconnection fabric.
FIG. 6 is a diagrammatic representation showing port adapter components associated with arbitration logic.
FIG. 7 is a flow process diagram showing one technique for selecting port adapter components.
FIG. 8 is a diagrammatic representation showing a technique for implementing the programmable chip.
FIG. 9 is a diagrammatic representation depicting a computer system.



DETAILED DESCRIPTION OF SPECIFIC EMBODIMENTS
Reference will now be made in detail to some specific examples of the invention including the best modes contemplated by the inventors for carrying out the invention. Examples of these specific embodiments are illustrated in the accompanying drawings. While the invention is described in conjunction with these specific embodiments, it will be understood that it is not intended to limit the invention to the described embodiments. On the contrary, it is intended to cover alternatives, modifications, and equivalents as may be included within the spirit and scope of the invention as defined by the appended claims.
For example, the techniques of the present invention will be described in the context of programmable chips, bus access, and slave side arbitration buses. However, it should be noted that the techniques of the present invention can be applied to a variety of devices and buses. In the following description, numerous specific details are set forth in order to provide a thorough understanding of the present invention. The present invention may be practiced without some or all of these specific details. In other instances, well known process operations have not been described in detail in order not to unnecessarily obscure the present invention.
Furthermore, techniques and mechanisms of the present invention will sometimes be described in singular form for clarity. However, it should be noted that some embodiments include multiple iterations of a technique or multiple instantiations of a mechanism unless noted otherwise. For example, a processor is used in a variety of contexts. However, it will be appreciated that multiple processors can also be used while remaining within the scope of the present invention unless otherwise noted.
Master and slave components in an embedded system have master and slave ports that allow interconnection. For example, a master component processor may have a number of ports including master ports, slave ports, and test ports that allow the processor to interact with other components such as memory, network interfaces, etc. Other master components such as hardware accelerators can also have a number of ports include master ports, slave ports, and test ports that allow interconnection. The individual ports support particular bus standards such as PCI or AMBA and also have particular attributes such as width and bursting attributes.
A PCI master port that supports bursting is configured to operate with a PCI slave port that supports bursting. An AMBA master port that supports word-wide transactions is configured to interact with an AMBA slave ports that supports word-wide transactions.
In conventional systems, port compatibility in a system is ensured by using only IP blocks that implement components with ports that conform to particular standard or have particular characteristics. Any set of characteristics or parameters associated with a component connection to a bus or other interconnection fabric is referred to herein as port characteristics. IP blocks are compatible by construction, but a system designer faces limitations. For example, one limitation is that the number of IP blocks supporting a particular bus standard may be limited. Using a single bus standard, the designer will have a less than optimal design. If the designer decides to use an IP block with an incompatible port type, the designer will need to spend resources designing a “gasket” or “converter” that converts one port type to another.
The techniques and mechanisms of the present invention recognize that another limitation is decreased performance or increased resource usage. Some bus standards attempt to increase the number of port types supported by allowing flexibility in port attributes. For example, a bus standard may allow a variety of bus transaction types (bursting, non-bursting, word-wide, byte-wide, etc.). But these more complicated standards tend to complicate the port circuitry of IP blocks because ports on these buses must be aware of all transaction types, thereby decreasing system performance or increasing the cost of the IP. The techniques and mechanisms of the present invention recognize that the limitations are most pronounced when IP is targeted at programmable chips such as FPGAs. Rich bus standards supporting a variety of attributes require complex circuitry that is relatively expensive on programmable chips in order to differentiate among a variety of transaction types.
Bridges and custom circuitry can also be used to convert from one port type to another. However, adding bridges and custom circuitry is error prone, inefficient, and non-optimal. According to various embodiments, the techniques of the present invention analyze port types and connections required by system components. Port adapters available from a library of port adapters are automatically selected for connecting port types associated with different components. In some instances, multiple stages of port adapter components may be selected to allow connection of system components. Costs may be associated with different port adapters to allow efficient selection and optimization.
In one specific embodiment, a system-design tool collects an inventory of all of the port connections required in a design for implementation on a programmable chip. With this information, the tool then looks through a library of available port adapters to see how every required connection can be made. The tool then automatically inserts only the adapters that are required to allow the desired port connections of the design. For example, if a CPU has a word-wide data master port, and it needs to connect to a peripheral that has a byte-wide slave port, the system tool can look in its library, see that it has a “word-to-byte” adapter, and insert this adapter without intervention from the designer.
FIG. 1 is a diagrammatic representation showing one example of a system on a programmable chip that can use the techniques of the present invention for selecting port adapters. The system includes a processor core, a hardware accelerator, peripheral devices, and peripheral interfaces. Peripheral devices and peripheral interfaces are herein referred to as components. The system on a programmable chip includes processor core 101 and a hardware accelerator 103 as well as peripheral components UART 111, PIO 113, timer 115, and Ethernet 117. In some examples, the hardware accelerator 103 is a Digital Signal Processing (DSP) core, a cryptography accelerator, or a video processor. The components are interconnected using an interconnection fabric 107. Any mechanism or logic for connecting components in a system is referred to herein as an interconnection fabric or bus.
The programmable chip uses different types of resources that can be interchangeably used in different allocations to implement the system on a programmable chip. In one example, the programmable chip uses logic elements for implementing each of the various components on the programmable chip.
Logic elements typically can be implemented using components such as antifuses, static RAM, and EPROMS. Any mechanism on a programmable chip that performs an operation on a given number of input lines to provide one or more outputs based on information programmed is herein referred to as a logic element. Some logic elements are implemented as combinations of look up tables and switches for performing Boolean operations on input lines. In one example, a logic element includes a 16-bit SRAM lookup table (LUT) that can implement an arbitrary 4-input logic function, circuitry that forms a fast carry chain and a fast cascade chain, a register and preset/reset logic for the register.
The techniques and mechanisms of the present invention allow the implementation of a system on a programmable chip with automatic port adapter selection and configuration.
FIG. 2 is a diagrammatic representation showing one example of a system having components with varying ports. A processor 203 includes an Advanced Microprocessor Bus Architecture (AMBA) data master port 201 and an AMBA instruction master port 205. AMBA is an established on-chip bus standard that serves as an interconnect for a number of System-on-Chip (SoC) designs. AMBA provides structure for intellectual property (IP) component development. A variety of components include AMBA ports and compliance with the AMBA standard allows connection of a variety of components without understanding of the intricacies associated with other components.
The AMBA instruction master port 205 and the AMBA data master port 201 are connected to an AMBA slave port 223 associated with a memory component 221 over an interconnection fabric 241. The interconnection fabric can include one or more bus controllers or bus arbiters. A UART 211 has a Peripheral Component Interface (PCI) slave port 213. In some examples, a UART 211 may be configured with both AMBA slave ports and a PCI slave port 213. However, this may make the UART 211 more complicated and require more logic to implement the UART 211 on a programmable device. Consequently, the UART 211 may only be provided with a PCI slave port 213.
Designers typically custom configure logic to allow connection of the UART 211 and the associated PCI slave port 213 to the processor 203 and its associated AMBA port. Custom configured logic can be error prone and inefficient.
FIG. 3 is a diagrammatic representation showing use of a port adapter available from a port adapter library. Any mechanism holding logic such as IP blocks for implementing port adapters on a device is referred to herein as a port adapter library. In one embodiment, a port adapter library is a database that includes bus type adapters, bit width adapters, bursting adapters, clock domain crossing adapters, etc.
A processor 303 includes an Advanced Microprocessor Bus Architecture (AMBA) data master port 301 and an AMBA instruction master port 305. The AMBA instruction master port 305 and the AMBA data master port 301 are connected to an AMBA slave port 323 associated with a memory component 321 over an interconnection fabric 341. The interconnection fabric 341 can include one or more bus controllers or bus arbiters. A UART 311 has a Peripheral Component Interface (PCI) slave port 313. In some examples, a UART 311 may be configured with both AMBA slave ports and a PCI slave port 313. However, this may make the UART 311 more complicated and require more logic to implement the UART 311 on a device. Consequently, the UART 311 may only be provided with a PCI slave port 313.
According to various embodiments, the techniques of the present invention automatically select an AMBA/PCI port adapter 355 from a library of port adapters. The AMBA/PCI port adapter 355 includes an AMBA slave port 351 and a PCI master port 353. The port adapter PCI master port 353 is connected to PCI slave port 313 associated with UART 311. The port adapter AMBA slave port 351 is connected to the AMBA data master port 301 associated with processor 303. The preconfigured port adapter 355 reduces complexity in implementing a device. However, it is recognized that latency may increase. Port adapters available from a library may not be optimally configured for specific applications and may indeed slow transfers of data between the processor 303 and the UART 311. However, the techniques of the present invention recognize that the tradeoff is beneficial particularly when implemented using a system builder tool. A system builder or system design tool allowing a designer to select components for implementing a system on a chip or a system on a programmable chip emphasizes simplicity of design over latency. For more optimal latency, a component having a compatible port can be designed.
A variety of port adapters are available. In another example, a processor 303 has a word-wide data master port, and it needs to connect to a peripheral that has a byte-wide slave port. The system design tool can select a word-to-byte adapter from its library and insert the adapter without intervention from the designer.
The examples above describe point-to-point connections without “fan out” or “fan in.” Such connections can be resolved easily using adapters from a library and a backtracking search algorithm. According to various embodiments, an algorithm iteratively inserts candidate adapters from a library until the desired connection is possible. If necessary, when no adapter is available that directly connects the port types, the algorithm can search for a chain of adapters or stages of adapters. The algorithm can search for the adapter chain that resolves the connection with a minimum cost. According to various embodiments, costs are assigned to various adapters in the port adapter library. Costs may be associated with the amount of logic consumed on a device, latency introduced, etc. A solution with the lowest total cost may be selected.
FIG. 4 is a diagrammatic representation showing one example of port adapter chaining. A processor 403 includes an Advanced Microprocessor Bus Architecture (AMBA) word-wide data master port 401 and an AMBA word-wide instruction master port 405. The AMBA word-wide instruction master port 405 and the word-wide AMBA data master port 401 are connected to an AMBA word-wide slave port 461 associated with a word-wide/byte-wide port adapter 465 included in an interconnection fabric 441. According to various embodiments, the word-wide/byte-wide port adapter 465 has AMBA ports. The word-wide/byte-wide port adapter 465 also includes a byte-wide master port 463.
The byte-wide master port 463 associated with the word-wide/byte-wide port adapter 465 is connected to an AMBA byte-wide slave port 423 associated with memory 421. However, the byte-wide master port 463 can not be connected to the PCI byte-wide slave port 413 because of bus type incompatibility. Consequently, the word-wide/byte-wide port adapter 465 is chained to an AMBA/PCI port adapter 455 to allow connection to UART 411. The byte-wide master port 463 is connected to AMBA slave port 451 associated with AMBA/PCI port adapter 455. The AMBA/PCI port adapter 455 also includes a PCI master port 453. The PCI master port 453 is connected to the PCI byte-wide slave port 413. According to various embodiments, the AMBA/PCI port adapter 455 has byte-wide ports.
Sharing of adapters is encouraged by considering total cost. A system implemented using fewer adapters will generally have lower total cost. However, in some instances, sharing too extensively can adversely impact system performance. In some instances, the port adapter itself may become a system bottleneck. In one example, port adapters may be shared by a maximum of three or four components. In another example, a port adapter is not shared if it is used by a high bandwidth component.
A variety of interconnection fabrics can be used. FIG. 5 is a diagrammatic representation showing one example of an interconnection fabric. Although a slave side arbitration fabric is described, the techniques and mechanisms of the present invention can be implemented using other interconnection fabrics and buses. Any system level mechanism used to connected primary and secondary components is referred to herein as an interconnection fabric or bus. Any component or device that is operable to initiate read and write operations by providing control information is referred to herein as a primary component. Primary components are sometimes referred to as master components. Control information can include a particular address associated with a secondary component. Any component or device that responds to read or write operations with information sent back to the primary component regarding the read or write operation is referred to herein as a secondary component. Secondary components are sometimes referred to as slave components.
Some examples of primary components are processors, microcontrollers, and Ethernet devices. Some examples of secondary components are Universal Asynchronous Receiver Transmitters (UARTs), Parallel Input Output (PIO), program memory, and data memory. It should be noted that some components such as an Ethernet component can be both a primary component and a secondary component, as an Ethernet component has the capability of reading and writing to the secondary program memory while also responding to instructions from a primary system CPU.
The multiple primary and secondary components are connected using secondary side arbitration, sometimes referred to as slave side arbitration, simultaneous multiple primary components, or simultaneous multiple masters. A system using individual arbitrators that correspond to individual secondary components accessible by more than one primary component is referred to herein as a secondary side arbitration system. Any component or device that is configured to ensure that only one primary component can access any one of the secondary components at any given time is referred to herein as a system bus arbitrator or bus arbitration logic. Various schemes such as weighted fairness can be implemented to improve the efficiency of secondary component access, but such schemes can increase system complexity and latency. In conventional implementations, a computer system includes a single system bus arbitrator for each bus in the computer system.
A secondary side arbitration system no longer requires a bus or a system bus arbitrator that prevents a second primary component from accessing a second secondary component when a first primary component is accessing a first secondary component. According to various embodiments a secondary component such as peripheral interface 525 is associated with a secondary side arbitrator 551. Logic and mechanisms for selecting an input based on a bus control signal are referred to herein as an arbitrator or arbitration logic. It should be noted that although switching circuitry generally can be implemented using multiplexers, a variety of mechanisms including switches and transistors can be used.
However, secondary components UART 521 and PIO 523 are not associated with any arbitrator. In one example, secondary component UART 521 and secondary PIO 523 can only be accessed by primary CPU 513 and not by primary Ethernet device 515. A peripheral interface 525, however, can be accessed by both primary CPU 513 and primary Ethernet device 515.
According to various embodiments, a secondary side arbitrator 551 allows a first secondary component in a system to be accessed by a first primary component at the same time a second secondary component in the system is accessed by a second primary component. For example, peripheral interface 525 can be accessed by primary Ethernet 515 through secondary side arbitrator 551 at the same time, secondary UART 521 is accessed by primary CPU 513.
By allowing a CPU to access a secondary component at the same time another primary component such as a streaming output device or an Ethernet component is accessing memory, bus bottlenecks can be reduced. By using the simultaneous multiple primary component architecture, more direct connections between components can also be supported.
Although secondary side arbitrators provide many benefits to programmable chip designers, arbitration logic efficiency is still needed to prevent performance degradation. It is also beneficial to provide priority considerations and fairness with any arbitration logic, secondary side arbitration logic or otherwise. According to various embodiments, port adapters available from a port adapter library can be connected serially to secondary side or slave side arbitrators.
FIG. 6 is a diagrammatic representation showing ports adapters integrated with slave side arbitrators. According to various embodiments a secondary component such as peripheral interface 625 is associated with a secondary side arbitrator 651 and a bursting/non-bursting port adapter 653.
However, secondary components UART 621 and PIO 623 are not associated with any arbitrator. In one example, secondary component UART 521 and secondary PIO 623 can only be accessed by primary CPU 613 and not by primary Ethernet device 615. A peripheral interface 625, however, can be accessed by both primary CPU 613 and primary Ethernet device 615. Secondary components UART 621 and PIO 623 may also be connected to port adapters as needed.
FIG. 7 is a flow process diagram showing one technique for implementing a system using port adapters. At 701, desired connections between primary component ports and secondary components ports are identified. At 705, components having available compatible ports are connected. At 707, the largest number of remaining ports on the master side and/or slave side having shared standards and attributes are identified. A shared port adapter is provided if possible at 713. At 719, the next largest number of remaining unconnected ports on the master side and/or slave side having shared standards and attributes are identified and a shared port adapter is provided. At 723, additional shared and dedicated port adapters are provided. At 725, port adapters are associated with arbitration logic. It should be noted that a variety of techniques are contemplated for selecting ports adapters. Iterative, cot weighting, and graphing techniques can be used.
FIG. 8 is a diagrammatic representation showing implementation of an electronic device that can use arbitration logic according to various embodiments. An input stage 801 receives selection information typically from a user for logic such as a processor core as well as other components such as a streaming output device to be implemented on an electronic device. In one example, the input received is in the form of a high-level language program. A generator program 805 creates a logic description and provides the logic description along with other customized logic to any of a variety of synthesis tools, place and route programs, and logic configuration tools to allow a logic description to be implemented on an electronic device.
In one example, an input stage 801 often allows selection and parameterization of components to be used on an electronic device. The input stage 801 also allows configuration of variable or fixed latency support. In some examples, components provided to an input stage include intellectual property functions, megafunctions, and intellectual property cores. The input stage 801 may be a graphical user interface using wizards for allowing efficient or convenient entry of information. The input stage may also be a text interface or a program reading a data file such as a spreadsheet, database table, or schematic to acquire selection information. The input stage 801 produces an output containing information about the various modules selected.
In typical implementations, the generator program 805 can identify the selections and generate a logic description with information for implementing the various modules. The generator program 805 can be a Perl script creating HDL files such as Verilog, Abel, VHDL, and AHDL files from the module information entered by a user. In one example, the generator program identifies a portion of a high-level language program to accelerate. The other code is left for execution on a processor core. According to various embodiments, the generator program 805 identifies pointers and provides ports for each pointer. One tool with generator program capabilities is System on a Programmable Chip (SOPC) Builder available from Altera Corporation of San Jose, Calif. The generator program 805 also provides information to a synthesis tool 807 to allow HDL files to be automatically synthesized. In some examples, a logic description is provided directly by a designer. Hookups between various components selected by a user are also interconnected by a generator program. Some of the available synthesis tools are LEONARDO SPECTRUM, available from Mentor Graphics Corporation of Wilsonville, Oregon and SYNPLIFY available from Synplicity Corporation of Sunnyvale, Calif. The HDL files may contain technology specific code readable only by a synthesis tool. The HDL files at this point may also be passed to a simulation tool 809.
As will be appreciated by one of skill in the art, the input stage 801, generator program 805, and synthesis tool 807 can be separate programs. The interface between the separate programs can be a database file, a log, or simply messages transmitted between the programs. For example, instead of writing a file to storage, the input stage 801 can send messages directly to the generator program 805 to allow the generator program to create a logic description. Similarly, the generator program can provide information directly to the synthesis tool instead of writing HDL files. Similarly, input stage 801, generator program 805, and synthesis tool 807 can be integrated into a single program.
A user may select various modules and an integrated program can then take the user selections and output a logic description in the form of a synthesized netlist without intermediate files. Any mechanism for depicting the logic to be implemented on an electronic device is referred to herein as a logic description. According to various embodiments, a logic description is an HDL file such as a VHDL, Abel, AHDL, or Verilog file. A logic description may be in various stages of processing between the user selection of components and parameters to the final configuration of the device. According to other embodiments, a logic description is a synthesized netlist such as an Electronic Design Interchange Format Input File (EDF file). An EDF file is one example of a synthesized netlist file that can be output by the synthesis tool 807.
A synthesis tool 807 can take HDL files and output EDF files. Tools for synthesis allow the implementation of the logic design on an electronic device. Some of the available synthesis tools are Leonardo Spectrum, available from Mentor Graphics Corporation of Wilsonville, Oregon and Synplify available from Synplicity Corporation of Sunnyvale, Calif. Various synthesized netlist formats will be appreciated by one of skill in the art.
A verification stage 813 typically follows the synthesis stage 807. The verification stage checks the accuracy of the design to ensure that an intermediate or final design realizes the expected requirements. A verification stage typically includes simulation tools and timing analysis tools. Tools for simulation allow the application of inputs and the observation of outputs without having to implement a physical device. Simulation tools provide designers with cost effective and efficient mechanisms for both functional and timing verification of a design. Functional verification involves the circuit's logical operation independent of timing considerations. Parameters such as gate delays are disregarded.
Timing verification involves the analysis of the design's operation with timing delays. Setup, hold, and other timing requirements for sequential devices such as flip-flops are confirmed. Some available simulation tools include Synopsys VCS, VSS, and Scirocco, available from Synopsys Corporation of Sunnyvale, Calif. and Cadence NC-Verilog and NC-VHDL available from Cadence Design Systems of San Jose, Calif. After the verification stage 813, the synthesized netlist file can be provided to physical design tools 819 including place and route and configuration tools. A place and route tool typically locates logic cells on specific logic elements of a target hardware device and connects wires between the inputs and outputs of the various logic elements in accordance with logic required to implement an electronic design. The device can also be physically tested at 823.
For programmable logic devices, a programmable logic configuration stage can take the output of the place and route tool to program the logic device with the user selected and parameterized modules. According to various embodiments, the place and route tool and the logic configuration stage are provided in the Quartus Development Tool, available from Altera Corporation of San Jose, Calif. As will be appreciated by one of skill in the art, a variety of synthesis, place and route, and programmable logic configuration tools can be tested using various techniques of the present invention.
As noted above, different stages and programs can be integrated in a variety of manners. According to one embodiment, the input stage 801, the generator program 805, the synthesis tool 807, the verification tools 813, and physical design tools 819 are integrated into a single program. The various stages are automatically run and transparent to a user. The program can receive the user selected modules, generate a logic description depicting logic for implementing the various selected modules, and implement the electronic device. As will be appreciated by one of skill in the art, HDL files and EDF files are mere examples of a logic description. Other file formats as well as internal program representations are other examples of a logic description.
FIG. 9 is a diagrammatic representation showing a typical computer system that can be used to implement a programmable chip having bus arbitration with priority encoding and fairness. The computer system 900 includes any number of processors 902 (also referred to as central processing units, or CPUs) that are coupled to devices including memory 906 (typically a random access memory, or “RAM”), memory 904 (typically a read only memory, or “ROM”). The processors 902 can be configured to generate a test sequences for any designated processor. As is well known in the art, memory 904 acts to transfer data and instructions uni-directionally to the CPU and memory 906 is used typically to transfer data and instructions in a bi-directional manner.
Both of these memory devices may include any suitable type of the computer-readable media described above. A mass storage device 908 is also coupled bi-directionally to CPU 902 and provides additional data storage capacity and may include any of the computer-readable media described above. The mass storage device 908 may be used to store programs, data and the like and is typically a secondary storage medium such as a hard disk that is slower than memory. The mass storage device 908 can be used to hold a library or database of prepackaged logic or intellectual property functions, as well as information on generating particular configurations. It will be appreciated that the information retained within the mass storage device 908, may, in appropriate cases, be incorporated in standard fashion as part of memory 906 as virtual memory. A specific mass storage device such as a CD-ROM 914 may also pass data uni-directionally to the CPU.
CPU 902 is also coupled to an interface 910 that includes one or more input/output devices such as such as video monitors, track balls, mice, keyboards, microphones, touch-sensitive displays, transducer card readers, magnetic or paper tape readers, tablets, styluses, voice or handwriting recognizers, or other well-known input devices such as, of course, other computers. Finally, CPU 902 optionally may be coupled to a computer or telecommunications network using a network connection as shown generally at 912. With such a network connection, it is contemplated that the CPU might receive information from the network, or might output information to the network in the course of performing the above-described method steps. It should be noted that the system 900 may also be associated with devices for transferring completed designs onto a programmable chip. The above-described devices and materials will be familiar to those of skill in the computer hardware and software arts.
The hardware elements described above may be configured (usually temporarily) to act as multiple software modules for performing the operations of this invention. For example, instructions for running a generator program, input stage (e.g., a wizard), and/or compiler may be stored on mass storage device 908 or 914 and executed on CPU 908 in conjunction with primary memory 906.
Although many of the components and processes are described above in the singular for convenience, it will be appreciated by one of skill in the art that multiple components and repeated processes can also be used to practice the techniques of the present invention.
While the invention has been particularly shown and described with reference to specific embodiments thereof, it will be understood by those skilled in the art that changes in the form and details of the disclosed embodiments may be made without departing from the spirit or scope of the invention. For example, embodiments of the present invention may be employed with a variety of primary and secondary components and should not be restricted to the ones mentioned above. Although shared I/O lines have been described in the context of a memory controller and a simultaneous multiple primary component switch fabric, shared I/O lines can be used in a system without a memory controller and/or without a simultaneous multiple primary component switch fabric. It is therefore intended that the invention be interpreted to include all variations and equivalents that fall within the true spirit and scope of the present invention.

## Claims

1. A method for implementing an embedded system, the method comprising:
receiving a first master component including a first master component port;
receiving a first slave component including a first slave component port;
receiving an indication to connect the first master component port to the first slave component port, wherein the first master component port and the first slave component port are incompatible;
obtaining cost information assigned to a plurality of port adapter components from a library of port adapter components, the cost information including the amount of logic required and the latency introduced;
selecting a first port adapter component from the library of port adapter components; and
connecting the first master component port to the first slave component port through the first port adapter component.

2. The method of claim 1, further comprising receiving a second slave component including a second slave component port.

3. The method of claim 2, wherein the first port adapter component is shared by the first slave component and the second slave component.

4. The method of claim 3, wherein the first port adapter component includes slave side arbitration logic.

5. The method of claim 3, wherein the first port adapter component is coupled to slave side arbitration logic.

6. The method of claim 1, further comprising receiving a second master component including a second master component port.

7. The method of claim 1, further comprising selecting additional candidate port adapter components from the library of port adapter components until desired connections are made.

8. The method of claim 7, further comprising selecting port adapter components having the lowest associated costs first during selection of candidate port adapter components.

9. The method of claim 1, wherein the first port adapter component is a width adapter.

10. The method of claim 1, wherein the first port adapter component is a bursting adapter.

11. The method of claim 1, wherein the first port adapter component is a slave side arbitration bus to peripheral components interface (PCI) adapter.

12. A system for implementing a device, the system comprising:
means for receiving a first master component including a first master component port;
means for receiving a first slave component including a first slave component port;
means for receiving an indication to connect the first master component port to the first slave component port, wherein the first master component port and the first slave component port are incompatible;
means for obtaining cost information assigned to a plurality of port adapter components from a library of port adapter components, the cost information including the amount of logic required and the latency introduced;
means for selecting a first port adapter component from the library of port adapter components; and
means for connecting the first master component port to the first slave component port through the first port adapter component.

13. The system of claim 12, further comprising receiving a second slave component including a second slave component port.

14. The system of claim 13, wherein the first port adapter component is shared by the first slave component and the second slave component.

15. The system of claim 14, wherein the first port adapter component includes slave side arbitration logic.

16. A computer readable medium comprising computer code for implementing a programmable chip system, the computer readable medium comprising:
computer code for receiving a first master component including a first master component port;
computer code for receiving a first slave component including a first slave component port;
computer code for receiving an indication to connect the first master component port to the first slave component port, wherein the first master component port and the first slave component port are incompatible;
computer code for obtaining cost information assigned to a plurality of port adapter components from a library of port adapter components, the cost information including the amount of logic required and the latency introduced;
computer code for selecting a first port adapter component from the library of port adapter components, wherein the first port adapter is automatically selected from the library of port adapter components after analyzing cost information; and
computer code for connecting the first master component port to the first slave component port through the first port adapter component.

17. The computer readable medium of claim 16, wherein the first port adapter component is chained to a second port adapter component.

18. An embedded system for an integrated circuit (IC), comprising:
a first component having a first port with a first interface;
a second component having a second port with a second interface, wherein the second interface is incompatible with the first interface;
an interconnection fabric having a port adapter component for connecting the first port of the first component with the second port of the second component, wherein the port adapter component is automatically selected from a plurality of port adapter components, and wherein each of the plurality of port adapter components is associated with cost information, wherein the port adapter component is automatically selected using cost information including the amount of logic required and the latency introduced.

19. The embedded system of claim 18, wherein the first component is a master component and wherein the second component is a slave component.