In accordance with an embodiment of the present invention, a programmable logic device includes a memory adapted to store information in the programmable logic device, an input/output circuit adapted to transfer information into or out of the programmable logic device, and an interconnect architecture adapted to route information within the programmable logic device. An interface circuit is provided to couple the memory and the input/output circuit to the interconnect architecture.
|
1. A programmable logic device comprising:
a memory adapted to store information in the programmable logic device;
an input/output circuit adapted to transfer information into or out of the programmable logic device;
an interconnect architecture adapted to route information within the programmable logic device; and
an interface circuit adapted to couple the memory and the input/output circuit to the interconnect architecture, wherein the interface circuit comprises a routing switch matrix and an input/output switch matrix.
8. A programmable logic device comprising:
a memory block adapted to store information;
a plurality of input/output circuits adapted to transmit or receive information for the programmable logic device;
means for routing information within the programmable logic device, wherein the routing means comprises vertical and horizontal routing resources; and
means for interfacing a portion of the memory block and a number of the input/output circuits to the routing means, wherein the interfacing means couples the portion of the memory block to the vertical routing resource and the horizontal routing resource and couples the number of the input/output circuits to only the vertical routing resource or the horizontal routing resource.
14. A method of providing an interface within a programmable logic device, the method comprising:
providing a memory block within the programmable logic device;
providing a first number of input/output circuits within the programmable logic device;
providing an interconnect circuit within the programmable logic device, wherein the interconnect structure comprises vertical and horizontal routing resources; and
interfacing the first number of input/output circuits and a portion of the memory block in combination to the interconnect circuit, wherein the interfacing couples the portion of the memory block to the vertical routing resource and the horizontal routing resource and couples the first number of input/output circuits to only the vertical routing resource.
2. The programmable logic device of
3. The programmable logic device of
4. The programmable logic device of
5. The programmable logic device of
6. The programmable logic device of
7. The programmable logic device of
9. The programmable logic device of
10. The programmable logic device of
11. The programmable logic device of
12. The programmable logic device of
13. The programmable logic device of
15. The method of
16. The method of
17. The method of
18. The method of
19. The method of
20. The method of
|
The present invention relates generally to electrical circuits and, more particularly, to interface block architectures, such as for programmable logic devices.
Programmable logic devices are utilized in a wide variety of applications. A typical programmable logic device (PLD, such as a field programmable gate array (FPGA) or a complex programmable logic device (CPLD)) may include a number of logic blocks, memory blocks (e.g., embedded blocks of random access memory (RAM)), and input/output (I/O) blocks interconnected generally through a programmable routing architecture (also referred to as the interconnect architecture).
The logic blocks (also referred to in the art as programmable logic cells, logic array blocks, or configurable logic blocks) and memory blocks are conventionally coupled through the interconnect architecture to the I/O blocks through a corresponding common routing interface block (also referred to as a common interface block or CIB) and the CIB also couples the I/O blocks to the interconnect architecture. For example,
PLD 100 also includes I/O blocks 150 (which communicate through pins 160 to external devices (not shown)) and common interface blocks (CIBs) 170 through which horizontal and vertical routing resources 130 and 140 are coupled to I/O blocks 150. As an interface, CIB 170 can be implemented in any number of ways, such as a distinct switch matrix or other I/O element (IOE) or as an integral part of I/O block 150.
One CIB 170 may be located at the end of each row and column and serve as the interface between I/O blocks 150 and logic blocks 120 and the interconnect architecture. For example,. CIB 170a located at the end of the row R1 may couple to and serve as the interface to the corresponding horizontal routing resource 130a for row R1, to the corresponding vertical routing resource 140a for column C1, and to adjacent CIBs 170.
One drawback of the generic CIB approach for the blocks (e.g., logic, memory, and I/O blocks) is that the CIB must be designed to interface with logic blocks, memory blocks, and I/O blocks (e.g., designed for the lowest common denominator). This may be an advantage in terms of symmetry or ease of use, but typically results in silicon and resource inefficiencies. For example, the CIBs may represent significant overhead and a significant percentage of the silicon area relative to the corresponding blocks.
Another drawback of the conventional PLD architecture is that optional embedded memory blocks are typically arranged in dedicated rows of memory blocks, which cannot be mixed with the logic blocks and generally divides up the logic blocks into discrete sections. For example, logic blocks 120 of the row R2 may be replaced with a row of the memory blocks. As illustrated in
Thus, the memory blocks typically are coupled within the logic block array, which restricts the designer's mixing and matching of the number of memory blocks and logic blocks for particular design requirements or targeted applications (e.g., memory blocks to logic blocks ratio) and also limits the placement of the memory blocks and logic blocks within the PLD (e.g., relative to the interconnect architecture to avoid unacceptable routing congestion). As a result, there is a need for improved PLD architectures, such as for the interface block architectures. SUMMARY
In accordance with one embodiment of the present invention, a programmable logic device includes a memory adapted to store information in the programmable logic device; an input/output circuit adapted to transfer information into or out of the programmable logic device; an interconnect architecture adapted to route information within the programmable logic device; and an interface circuit adapted to couple the memory and the input/output circuit to the interconnect architecture.
In accordance with another embodiment of the present invention, a programmable logic device includes a memory block adapted to store information; a plurality of input/output circuits adapted to transmit or receive information for the programmable logic device; means for routing information within the programmable logic device; and means for interfacing a portion of the memory block and a number of the input/output circuits to the routing means.
In accordance with another embodiment of the present invention, a method of providing an interface within a programmable logic device includes providing a memory block within the programmable logic device; providing a first number of input/output circuits within the programmable logic device; providing an interconnect circuit within the programmable logic device; and interfacing the first number of input/output circuits and a portion of the memory block in combination to the interconnect circuit.
The scope of the invention is defined by the claims, which are incorporated into this section by reference. A more complete understanding of embodiments of the present invention will be afforded to those skilled in the art, as well as a realization of additional advantages thereof, by a consideration of the following detailed description of one or more embodiments. Reference will be made to the appended sheets of drawings that will first be described briefly.
Embodiments of the present invention and their advantages are best understood by referring to the detailed description that follows. It should be appreciated that like reference numerals are used to identify like elements illustrated in one or more of the figures.
PLD 400 includes I/O blocks 150, logic blocks 204, memory block 202, and an interface block 402. Logic blocks 204 represent conventional logic blocks arranged, for example, in rows and columns (e.g., as described similarly in reference to
Interface block 402 represents a common interface block (CIB) to support one or more I/O blocks 150 and one or more memory blocks 202. Thus, interface block 402 (labeled combo CIB) may be viewed as representing a CIB that supports the interface combination of one or more I/O blocks 150 and one or more memory blocks 202. For example, interface block 402 may provide CIB functionality for four I/O blocks 150 and one memory block 202, as illustrated in
Interface block 402, by providing interface functionality to the combination of one or more I/O blocks 150 and memory blocks 202, may provide certain advantages over conventional techniques. For example, interface block 402 may provide a more optimal connectivity for each memory block 202 and I/O block 150 supported by interface block 402. Furthermore, interface block 402 may reduce the overall number of CIBs (e.g., by 33%), relative to conventional CIB techniques, and may provide die size or circuit area savings. By supporting one or more I/O blocks 150 and memory blocks 202, interface block 402 may also provide an optimized CIB without compromising routability.
Interface block 402 also allows the decoupling of memory block 202 from logic blocks 204. For example as shown in
Interface block 402 provides the combined CIB for one or more I/O blocks 150 and memory blocks 202. Interface block 402 may include a routing section, similar to that for logic block 204, and a CIB logic section, which provides any necessary, buffering, inverting, testing logic, or other conventional CIB functionality necessary for the desired application. It should be noted that at least a portion of the CIB logic may be provided by or extracted from a neighboring logic block 204 of PLD 500.
As an example, in accordance with an embodiment of the present invention, interface block 402 may be implemented in a modular fashion so that one or more interface blocks 402 may be utilized to provide the combined CIB interface for one or more I/O blocks 150 and one or more memory blocks 202. For example, as illustrated in
Interface block 402 may also be implemented to provide certain vertical and/or horizontal connectivity, depending upon its location and number/type of I/O blocks 150 and memory blocks 202 being supported. For example, in accordance with an embodiment of the present invention, interface block 402 may provide vertical and horizontal connectivity for memory blocks 202 and I/O blocks 150. Alternatively for example, in accordance with an embodiment of the present invention, interface block 402 may only provide horizontal or vertical connectivity for I/O blocks 150, depending upon their location on the PLD.
As an example, interface blocks 402 may only provide horizontal connectivity for I/O blocks 150 located to the left and/or right of the array of logic blocks 204, and similarly interface blocks 402 may only provide vertical connectivity for I/O blocks 150 located above and/or below the array of logic blocks 204. Thus, interface blocks 402 may be optimized for the desired number of I/O blocks 150 and memory blocks 202 and for the desired horizontal and/or vertical connectivity to the interconnect architecture. Furthermore, the number of I/O ports may be optimized based upon the number of I/O blocks 150 and memory blocks 202 supported.
Interface blocks 602, 604, 606, and 608 provide the routing interface (e.g., CIB functionality) for PLD 600. Interface blocks 602 may represent the combination CIBs for memory blocks 202 and associated I/O blocks 150 (not shown), as discussed similarly for interface blocks 402. For example, there may be four interface blocks 602 that provide the combined CIB functionality for the associated memory block 202 and associated I/O blocks 150 (e.g., twenty four I/O blocks 150). As further described herein in accordance with an embodiment of the present invention, interface blocks 602 may provide horizontal and vertical connectivity for the associated memory blocks 202, while providing only horizontal connectivity for the associated I/O blocks 150.
Interface blocks 604, 606, and/or 608 may also represent combination CIBs as described similarly herein for interface blocks 402 and provide horizontal and/or vertical connectivity for associated blocks. Consequently, some functionality of interface blocks 604, 606, and 608 may not be utilized. Alternatively, interface blocks 604, 606, and 608 may represent conventional CIBs 170 to provide the required interface functionality for logic blocks 204. For example, interface blocks 606 and 608 may provide the horizontal and/or vertical routing interface for the associated logic blocks 204 (e.g., within respective columns). As another example, interface blocks 604 may provide the horizontal and/or vertical routing interface for the associated logic blocks 204 (e.g., within respective rows).
In accordance with one or more embodiments of the present invention, the CIB architecture disclosed herein may be implemented in a number of different ways as would be appreciated by one skilled in the art. For example, interface block 402 may be implemented as a switch matrix or other type of IOE, switch, or routing element.
As a specific implementation example for interface block 402,
More specifically,
A block diagram 804 illustrates certain exemplary implementation specifics for common interface block architecture 800 in accordance with an embodiment of the present invention. For example, each interface block 402 includes an input/output (I/O) switch matrix 806 and a routing switch matrix 808 to support signal routing for six I/O blocks 150 and also support a portion of the signal routing for memory block 202.
Routing switch matrix 808 routes signals between routing resource 810 (e.g., an interconnect architecture, such as horizontal routing resource 130 and/or vertical routing resource 140) within the PLD and I/O switch matrix 806. For example, routing switch matrix 808 may include a number of multiplexers (e.g., labeled X0, Xl, X2, and X6 plus additional multiplexers) to route the signals and provide routing connectivity.
Specifically for example, routing switch matrix 808 may employ an 18:1 multiplexer (representing X0), a 20:1 multiplexer (representing X1), a 20:1 multiplexer (representing X2), and a 16:1 multiplexer (representing X6) to route signals from routing resource 810 to I/O switch matrix 806. In a similar fashion, routing switch matrix 808 would employ additional multiplexers to route signals from I/O switch matrix 806 to routing resource 810 (e.g., to horizontal routing resource 130 and/or vertical routing resource 140). For example, routing switch matrix 808 may only route signals from I/O blocks 150 via I/O switch matrix 806 to horizontal routing resource 130 or vertical routing resource 140, as disclosed herein, while routing signals from memory block 202 via I/O switch matrix 806 to horizontal routing resource 130 and vertical routing resource 140.
I/O switch matrix 806 receives the signals from routing switch matrix 808 and routes the signals appropriately to memory block 202 and six I/O blocks 150, as illustrated in an exemplary fashion in
Systems and methods are disclosed herein to provide, for example, one or more interface architectures for a PLD. For example, in accordance with an embodiment of the present invention, an interface block is disclosed to support the interface requirements for I/O blocks and memory blocks (e.g., combination common interface block (CIB) architecture). The interface block implementation may reduce the number of independent CIBs for the I/O blocks or the memory blocks. The interface block may also provide an optimized CIB architecture for vertical and horizontal connectivity without compromising routability, which may result in reducing and optimizing the required CIB area.
The interface block architecture, for example, may be beneficial for low cost PLDs and/or for I/O intensive PLD applications. For example, in accordance with an embodiment of the present invention, an exemplary implementation of a CIB architecture disclosed herein may be found in Lattices Semiconductor Corporation's MachXO Family of PLDs.
Embodiments described above illustrate but do not limit the invention. It should also be understood that numerous modifications and variations are possible in accordance with the principles of the present invention. Accordingly, the scope of the invention is defined only by the following claims.
Rutledge, David L., Agrawal, Om P., Lall, Ravindar M., Gustafson, Tom
Patent | Priority | Assignee | Title |
8120382, | Mar 05 2010 | XILINX, Inc.; Xilinx, Inc | Programmable integrated circuit with mirrored interconnect structure |
Patent | Priority | Assignee | Title |
5652904, | Aug 03 1993 | XILINX, Inc. | Non-reconfigurable microprocessor-emulated FPGA |
5705938, | May 02 1995 | XILINX, Inc. | Programmable switch for FPGA input/output signals |
5801547, | Mar 01 1996 | XILINX, Inc. | Embedded memory for field programmable gate array |
6255848, | Apr 05 1999 | XILINX, Inc.; Xilinx, Inc | Method and structure for reading, modifying and writing selected configuration memory cells of an FPGA |
6337579, | Mar 05 1999 | ACHLYS TECHNOLOGIES INC | Multichip semiconductor device |
6526559, | Apr 13 2001 | SRA INTERNATIONAL, INC | Method for creating circuit redundancy in programmable logic devices |
6627985, | Dec 05 2001 | ARBOR GLOBAL STRATEGIES, LLC | Reconfigurable processor module comprising hybrid stacked integrated circuit die elements |
6781226, | Dec 05 2001 | ARBOR GLOBAL STRATEGIES, LLC | Reconfigurable processor module comprising hybrid stacked integrated circuit die elements |
6917219, | Mar 12 2003 | XILINX, Inc. | Multi-chip programmable logic device having configurable logic circuitry and configuration data storage on different dice |
7112994, | Jul 08 2002 | LIBERTY PATENTS LLC | Three dimensional integrated circuits |
Executed on | Assignor | Assignee | Conveyance | Frame | Reel | Doc |
Nov 04 2005 | AGRAWAL, OM P | Lattice Semiconductor Corporation | ASSIGNMENT OF ASSIGNORS INTEREST SEE DOCUMENT FOR DETAILS | 016864 | /0148 | |
Nov 07 2005 | GUSTAFSON, THOMAS R | Lattice Semiconductor Corporation | ASSIGNMENT OF ASSIGNORS INTEREST SEE DOCUMENT FOR DETAILS | 016864 | /0148 | |
Nov 07 2005 | LALL, RAVINDAR L | Lattice Semiconductor Corporation | ASSIGNMENT OF ASSIGNORS INTEREST SEE DOCUMENT FOR DETAILS | 016864 | /0148 | |
Nov 23 2005 | RUTLEDGE, DAVID L | Lattice Semiconductor Corporation | ASSIGNMENT OF ASSIGNORS INTEREST SEE DOCUMENT FOR DETAILS | 016864 | /0148 | |
Nov 28 2005 | Lattice Semiconductor Corporation | (assignment on the face of the patent) | / | |||
Mar 10 2015 | Lattice Semiconductor Corporation | JEFFERIES FINANCE LLC | SECURITY INTEREST SEE DOCUMENT FOR DETAILS | 035223 | /0001 | |
Mar 10 2015 | Silicon Image, Inc | JEFFERIES FINANCE LLC | SECURITY INTEREST SEE DOCUMENT FOR DETAILS | 035223 | /0001 | |
Mar 10 2015 | DVDO, INC | JEFFERIES FINANCE LLC | SECURITY INTEREST SEE DOCUMENT FOR DETAILS | 035223 | /0001 | |
Mar 10 2015 | SIBEAM, INC | JEFFERIES FINANCE LLC | SECURITY INTEREST SEE DOCUMENT FOR DETAILS | 035223 | /0001 | |
May 17 2019 | JEFFERIES FINANCE LLC | DVDO, INC | RELEASE BY SECURED PARTY SEE DOCUMENT FOR DETAILS | 049827 | /0326 | |
May 17 2019 | JEFFERIES FINANCE LLC | SIBEAM, INC | RELEASE BY SECURED PARTY SEE DOCUMENT FOR DETAILS | 049827 | /0326 | |
May 17 2019 | JEFFERIES FINANCE LLC | Silicon Image, Inc | RELEASE BY SECURED PARTY SEE DOCUMENT FOR DETAILS | 049827 | /0326 | |
May 17 2019 | JEFFERIES FINANCE LLC | Lattice Semiconductor Corporation | RELEASE BY SECURED PARTY SEE DOCUMENT FOR DETAILS | 049827 | /0326 | |
May 17 2019 | Lattice Semiconductor Corporation | WELLS FARGO BANK, NATIONAL ASSOCIATION, AS ADMINISTRATIVE AGENT | SECURITY INTEREST SEE DOCUMENT FOR DETAILS | 049980 | /0786 |
Date | Maintenance Fee Events |
Jan 25 2008 | ASPN: Payor Number Assigned. |
Jul 06 2011 | M1551: Payment of Maintenance Fee, 4th Year, Large Entity. |
Jul 22 2015 | M1552: Payment of Maintenance Fee, 8th Year, Large Entity. |
Aug 05 2019 | M1553: Payment of Maintenance Fee, 12th Year, Large Entity. |
Date | Maintenance Schedule |
Feb 05 2011 | 4 years fee payment window open |
Aug 05 2011 | 6 months grace period start (w surcharge) |
Feb 05 2012 | patent expiry (for year 4) |
Feb 05 2014 | 2 years to revive unintentionally abandoned end. (for year 4) |
Feb 05 2015 | 8 years fee payment window open |
Aug 05 2015 | 6 months grace period start (w surcharge) |
Feb 05 2016 | patent expiry (for year 8) |
Feb 05 2018 | 2 years to revive unintentionally abandoned end. (for year 8) |
Feb 05 2019 | 12 years fee payment window open |
Aug 05 2019 | 6 months grace period start (w surcharge) |
Feb 05 2020 | patent expiry (for year 12) |
Feb 05 2022 | 2 years to revive unintentionally abandoned end. (for year 12) |