The present disclosure relates generally to programmable devices, and more particularly to a programmable interconnect matrix.
Field-programmable gate arrays (FPGAs) and Programmable Logic Devices (PLDs) have been used in data communication and telecommunication systems. Conventional PLDs and FPGAs consist of an array of programmable elements, with the elements programmed to implement a fixed function or equation. Some currently-available Complex PLD (CPLD) products comprise arrays of logic cells. Conventional PLD devices have several drawbacks, such as limited speed and limited data processing capabilities.
In developing complex integrated circuits, there is often a need for additional peripheral units, such as operational and instrument amplifiers, filters, timers, digital logic circuits, analog to digital and digital to analog converters, etc. As a general rule, implementation of these extra peripherals create additional difficulties: extra space for new components, additional attention during production of a printed circuit board, and increased power consumption. All of these factors can significantly affect the price and development cycle of the project.
The introduction of the Programmable System on Chip (PSoC) features digital and analog programmable blocks, which allow the implementation of a large number of peripherals. A programmable interconnect allows analog and digital blocks to be combined to form a wide variety of functional modules. The digital blocks consist of smaller programmable blocks and are configured to provide different digital functions. The analog blocks are used for development of analog elements, such as analog filters, comparators, inverting amplifiers, as well as analog to digital and digital to analog converters. Current PSoC architectures provide only a coarse grained programmability where only a few fixed functions are available with only a small number of connection options.
A programmable interconnect matrix includes horizontal channels that programmably couple different groups of one or more digital blocks together. The interconnect matrix can include segmentation elements that programmably interconnect different horizontal channels together. The segmentation elements can include horizontal segmentation switches that programmably couple together the horizontal channels for different groups of digital blocks in a same row. Vertical segmentation switches can programmably couple together the horizontal channels for different groups of digital blocks in different rows.
Vertical channels can programmably connect the horizontal channels in different rows. The horizontal channels provide more connectivity between the digital blocks located in the same rows than connectivity provided by the vertical channels connecting the digital blocks in different rows. Two digital blocks in a same digital block pair can be tightly coupled together to common routes in a same associated horizontal channel and different digital block pairs can be less tightly coupled together through the segmentation elements.
Programmable switches are configured to connect different selectable signals from the digital bocks to their associated horizontal channels. Programmable tri-state buffers in the segmentation elements can be configured to selectively couple together and drive signals between different horizontal channels.
A Random Access Memory (RAM) can be configured to programmably control how the different digital blocks are coupled together through the interconnection matrix. Undedicated Inputs and Outputs (I/Os) can be programmably coupled to different selectable signals in different selectable digital blocks through different selectable routes in the interconnection matrix. The undedicated Inputs and Outputs refer to the connections on the Integrated Circuit (IC) to external signals.
A micro-controller system is programmably coupled to the different digital blocks through the interconnect matrix and is programmably coupled to the different programmable Inputs/Outputs (I/Os) through the interconnect matrix. The micro-controller system can include a micro-controller, an interrupt controller, and Direct Memory Access (DMA) controller. Interrupt requests can be programmably coupled between the interrupt controller and different selectable digital blocks or different selectable I/Os through the interconnect matrix. DMA requests can also be programmably coupled between the DMA controller and different selectable digital blocks or different selectable I/Os through the interconnect matrix. In one embodiment, the micro-controller, digital blocks, I/Os, and interconnect are all located in a same integrated circuit.
In one embodiment, the digital blocks comprise a first group of uncommitted logic elements that are programmable into different logic functions and also include a second group of structural logic elements that together form a programmable arithmetic sequencer.
A new programmable routing scheme provides improved connectivity both between Universal Digital Blocks (UDBs) and between the UDBs and other micro-controller elements, peripherals and external Inputs and Outputs (I/Os) in the same Integrated Circuit (IC). The routing scheme increases the number of functions and the overall routing efficiency for programmable architectures. The UDBs can be grouped in pairs and share associated horizontal routing channels. Bidirectional horizontal and vertical segmentation elements extend routing both horizontally and vertically between different UDB pairs and to the other peripherals and I/O.
UDB Array
The UDB array 110 is arranged into UDB pairs 122 that each include two UDBs 120 that can be tightly coupled to a shared horizontal routing channel 132. The UDB pairs 122 can also be programmably connected to the horizontal routing channels 132 of other UDB pairs 122 either in the same horizontal row or in different rows through vertical routing channels 134. The horizontal and vertical routing channels and other switching elements are all collectively referred to as the interconnect matrix 130.
A Digital System Interconnect (DSI) routing interface 112 connects a micro-controller system 170 and other fixed function peripherals 105 to the UDB array 110. The micro-controller system 170 includes a micro-controller 102, an interrupt controller 106, and a Direct Memory Access (DMA) controller 108. The other peripherals 105 can be any digital or analog functional element in PSoC 100. The DSI 112 is an extension of the interconnect matrix 130 at the top and bottom of the UDB array 110.
The interconnect matrix 130 also includes Horizontal/Vertical (H/V) segmentation elements 125 that programmably interconnect the different horizontal routing channels 132 together. The segmentation elements 125 couple together the horizontal routing channels 132 for the different digital block pairs 122 in the same rows. The segmentation elements 125 also programmably couple together the horizontal routing channels 132 for digital block pairs 122 in different rows through vertical routing channels 134.
The two UDBs 120A and 120B in UDB pair 122 are tightly coupled together to common routes in the same associated horizontal routing channel 132. Tight coupling refers to the UDB I/O signals 127 in the upper UDB 120A and the corresponding signals 128 in the lower UDB 120B all being directly connected to the same associated horizontal routing channel 132. This tight coupling provides high performance signaling between the two UDBs 120A and 120B. For example, relatively short connections 127 and 128 can be programmably established between the upper UDB 120A and the lower UDB 120B.
In one embodiment, the horizontal routing channels 132 can also have a larger number of routes and connections to the UDBs 120A and 120B than the vertical routing channels 134 shown in
Thus, the interconnect matrix 130 in
At the switch points, RAM bits operate RAM cells 136 and 138 which in turn control Complementary Metal Oxide Semi-conductor (CMOS) transmission gate switches 142 and 144, respectively. The switches 142 and 144 when activated connect the UDB output 127A and the UDB input 128A to horizontal routing channel wire 132A.
The RAM cells 136 and 137 are programmably selectable by the micro-controller 102 (
In addition to the segmentation elements 125, the interconnect matrix 130 includes the switching elements 145 previously shown in
Referring to
When bit 162A is set, the buffer 164A drives one of the horizontal or vertical channel lines 166 from left to right. When bit 162B is set, the buffer 164B drives the same horizontal or vertical channel line 166 from right to left. If neither bit 162A or bit 162B is set, the buffers 164A and 164B drive line 166 to a high impedance state.
Configuration and Programmability
Any combination of the switching elements 145, horizontal segmentation switches 152, and vertical segmentation switches 154 can be programmably configured to connect together almost any combination of external I/O pins 104 (
A first set of bits in RAM section 412 are associated with the RAM cells 136 and 137 shown in
Pursuant to the micro-controller 102 programming RAM 410, the interconnect matrix 130 is configured with a first interconnect path 176 that connects a UDB 120C to the interrupt controller 106. The UDB 1200 can then send interrupt requests to the DMA controller 108 over interconnect path 176. A second interconnect path 178 is established between a peripheral (not shown) in the PSoC chip 100 (
A third interconnect path 180 is also configured by the micro-controller 102 by loading bits into RAM sections 412 and 414. The DMA controller 108 uses the interconnect path 180 to send a DMA terminate signal to UDB 120D. A fourth interconnect path 182 is programmably configured between one of the PSoC I/O pins 104 and a fixed digital peripheral, such as the micro-controller 102. The interconnect path 182 is used to send I/O signals between the micro-controller 102 and the I/O pin 104.
Interconnect paths 176-182 are of course just a few examples of the many different interconnect configurations that can be simultaneously provided by the interconnect matrix 130. This example also shows how different I/O pins 104, UDBs 120, and other peripherals can be connected to the same interrupt line on the interrupt controller 106 or connected to the same DMA line on the DMA controller 108.
Typically, interrupt requests received by an interrupt controller and DMA requests received by a DMA controller can only be connected to one dedicated pin. The interconnect matrix 130 allows any variety of different selectable functional elements or I/O pins to be connected to the same input or output for the interrupt controller 106 or DMA controller 108 according to the programming of RAM 410 by micro-controller 102.
The programmability of the interconnect matrix 130 also allows any number, or all, of the I/O pins 104 to be undedicated and completely programmable to connect to any functional element in PSoC 100. For example, the pin 104 can operate as an input pin for any selectable functional element in
Universal Digital Block
The PLD blocks 200 implement state machines, perform input or output data conditioning, and create look-up tables. The PLDs 200 can also be configured to perform arithmetic functions, sequence datapath 210, and generate status. PLDs are generally known to those skilled in the art and are therefore not described in further detail.
The datapath block 210 contains highly structured dedicated logic that implements a dynamically programmable ALU, comparators, and condition generation. A status and control block 204 allows micro-controller firmware to interact and synchronize with the UDB 120 by writing to control inputs and reading status outputs.
A clock and reset control block 202 provides global clock selection, enabling, and reset selection. The clock and reset block 202 selects a clock for each of the PLD blocks 200, the datapath block 210, and status and control block 204 from available global system clocks or a bus clock. The clock and reset block 202 also supplies dynamic and firmware resets to the UDBs 120.
Routing channel 130 connects to UDB I/O through a programmable switch matrix and provides connections between the different UDBs in
The PLDs 200 and the datapath 210 have chaining signals 212 and 214, respectively, that enable neighboring UDBs 120 to be linked to create higher precision functions. The PLD carry chain signals 212 are routed from the previous adjacent. UDB 120 in the chain, and routed through each macrocell in both of the PLDs 200. The carry out is then routed to the next UDB 120 in the chain. A similar connectivity is provided by the datapath chain 214 between datapath blocks 210 in adjacent UDBs 120.
Referring to
The datapath 210 comprises highly structured logic elements 254 that include a dynamically programmable ALU 304, conditional comparators 310, accumulators 302, and data buffers 300. The ALU 304 is configured to perform instructions on accumulators 302, and to update the sequence controlled by a sequence memory. The conditional comparators 310 can operate in parallel with the ALU 304. The datapath 210 is further optimized to implement typical embedded functions, such as timers, counters, etc.
The combination of uncommitted PLDs 200 with a dedicated datapath module 210 allow the UDBs 120 to provide embedded digital functions with more efficient higher speed processing. The dedicated structural arithmetic elements 254 more efficiently implement arithmetic sequencer operations, as well as other datapath functions. Since the datapath 210 is structural, fewer gates are needed to implement the structural elements 254 and fewer interconnections are needed to connect the structural elements 254 together into an arithmetic sequencer. Implementing the same datapath 210 with PLDs could require additional combinational logic and additional interconnections.
The structured logic in the datapath 210 is also highly programmable to provide a wide variety of different dynamically selectable arithmetic functions. Thus, the datapath 210 not only conserves space on the integrated circuit 100 (
The functional configurability of the datapath 210 is provided through the control registers 250 and allow the micro-controller 102 to arbitrarily write into a system state and selectively control different arithmetic functions. The status registers 256 allow the micro-controller 102 to also identify different states associated with different configured arithmetic operations.
The flexible connectivity scheme provided by the routing channel 130 selectively interconnects the different functional element 250, 200, 254, and 256 together as well as programmably connecting these functional element to other UDBs, I/O connections, and peripherals. Thus, the combination of uncommitted logic 200, structural logic 254, and programmable routing channel 130 provides more functionality, flexibility, and more efficiently uses less integrated circuit space.
The interconnect matrix 130 also requires little or no dedicated UDB block routing. All data, state, control, signaling, etc, can be routed through the interconnect matrix 130 in the UDB array 110. The array routing is efficient because there is little or no difference between a local UDB net and a net that spans the UDB array. Horizontal and vertical segmentation allow the array to be partitioned for increased efficiency and random access to the RAM 410 allow high speed configuration or on the fly reconfigurability.
The system described above can use dedicated processor systems, micro controllers, programmable logic devices, or microprocessors that perform some or all of the operations. Some of the operations described above can be implemented in software and other operations can be implemented in hardware.
For the sake of convenience, the operations are described as various interconnected functional blocks or distinct software modules. This is not necessary, however, and there can be cases where these functional blocks or modules are equivalently aggregated into a single logic device, program or operation with unclear boundaries. In any event, the functional blocks and software modules or features of the flexible interface can be implemented by themselves, or in combination with other operations in either hardware or software.
Having described and illustrated the principles of the invention in a preferred embodiment thereof, it should be apparent that the invention can be modified in arrangement and detail without departing from such principles. Claim is made to all modifications and variation coming within the spirit and scope of the following claims.
The present application is a continuation of U.S. patent application Ser. No. 13/099,334, filed May 2, 2011, which is a continuation of U.S. patent application Ser. No. 12/786,412, filed May 24, 2010, which is a continuation of U.S. patent application Ser. No. 11/965,291, filed Dec. 27, 2007, now U.S. Pat. No. 7,737,724, issued Jun. 15, 2010, which claims the benefit of U.S. Provisional Patent Application No. 60/912,399, filed Apr. 17, 2007, all of which are herein incorporated by reference in their entirety.
Number | Name | Date | Kind |
---|---|---|---|
3805245 | Brooks et al. | Apr 1974 | A |
4454589 | Miller | Jun 1984 | A |
4926355 | Boreland | May 1990 | A |
5341267 | Whitten et al. | Aug 1994 | A |
5497498 | Taylor | Mar 1996 | A |
5542055 | Amini et al. | Jul 1996 | A |
5594876 | Getzlaff et al. | Jan 1997 | A |
5617041 | Lee et al. | Apr 1997 | A |
5760612 | Ramirez | Jun 1998 | A |
5790882 | Silver et al. | Aug 1998 | A |
6002268 | Sasaki et al. | Dec 1999 | A |
6003107 | Ranson et al. | Dec 1999 | A |
6006321 | Abbott | Dec 1999 | A |
6006322 | Muramatsu | Dec 1999 | A |
6014723 | Tremblay et al. | Jan 2000 | A |
6018559 | Azegami et al. | Jan 2000 | A |
6055584 | Bridges et al. | Apr 2000 | A |
6121791 | Abbott | Sep 2000 | A |
6130553 | Nakaya | Oct 2000 | A |
6215326 | Jefferson et al. | Apr 2001 | B1 |
6218859 | Pedersen | Apr 2001 | B1 |
6253250 | Evans et al. | Jun 2001 | B1 |
6260087 | Chang | Jul 2001 | B1 |
6404224 | Azegami et al. | Jun 2002 | B1 |
6449628 | Wasson | Sep 2002 | B1 |
6473825 | Worley et al. | Oct 2002 | B1 |
6476634 | Bilski | Nov 2002 | B1 |
6496971 | Lesea et al. | Dec 2002 | B1 |
6614320 | Sullam et al. | Sep 2003 | B1 |
6691193 | Wang et al. | Feb 2004 | B1 |
6745369 | May et al. | Jun 2004 | B1 |
6757761 | Smith et al. | Jun 2004 | B1 |
6864710 | Lacey et al. | Mar 2005 | B1 |
6960936 | Cambonie | Nov 2005 | B2 |
7043710 | Reese et al. | May 2006 | B2 |
7274212 | Burney et al. | Sep 2007 | B1 |
7305510 | Miller | Dec 2007 | B2 |
7373437 | Seigneret et al. | May 2008 | B2 |
7389487 | Chan et al. | Jun 2008 | B1 |
7472155 | Simkins et al. | Dec 2008 | B2 |
7737724 | Snyder et al. | Jun 2010 | B2 |
7741865 | Sharpe-Geisler et al. | Jun 2010 | B1 |
7882165 | Simkins et al. | Feb 2011 | B2 |
8024678 | Taylor et al. | Sep 2011 | B1 |
8183881 | Stassart et al. | May 2012 | B1 |
8476928 | Sullam et al. | Jul 2013 | B1 |
8482313 | Snyder et al. | Jul 2013 | B2 |
8516025 | Synder et al. | Aug 2013 | B2 |
8572297 | Swindle et al. | Oct 2013 | B2 |
20010006347 | Jefferson et al. | Jul 2001 | A1 |
20030055852 | Wojko | Mar 2003 | A1 |
20040000928 | Cheng et al. | Jan 2004 | A1 |
20040017222 | Betz et al. | Jan 2004 | A1 |
20040034843 | Osann | Feb 2004 | A1 |
20050066152 | Garey | Mar 2005 | A1 |
20050091472 | Master et al. | Apr 2005 | A1 |
20050134308 | Okada et al. | Jun 2005 | A1 |
20060066345 | Leijten-Nowak | Mar 2006 | A1 |
20070139074 | Reblewski | Jun 2007 | A1 |
20070258458 | Kapoor | Nov 2007 | A1 |
20080042687 | Mori et al. | Feb 2008 | A1 |
20080094102 | Osann | Apr 2008 | A1 |
20080186052 | Needham et al. | Aug 2008 | A1 |
20080258759 | Snyder et al. | Oct 2008 | A1 |
20080263319 | Snyder et al. | Oct 2008 | A1 |
20080263334 | Synder et al. | Oct 2008 | A1 |
Entry |
---|
USPTO Notice of Allowance for U.S. Appl. No. 12/104,391 dated Dec. 1, 2011; 5 pages. |
USPTO Notice of Allowance for U.S. Appl. No. 13/099,334 dated Nov. 23, 2012; 7 pages. |
USPTO Notice of Allowance for U.S. Appl. No. 13/197,624 dated Nov. 30, 2012; 7 pages. |
Vixel, “InSpeed SOC 320 Embedded Storage Switch,” 2003, Vixel, pp. 1-5; 5 pages. |
Written Opinion of the International Searching Authority for International Application No. PCT/US08/60680 dated Aug. 15, 2008; 4 pages. |
Written Opinion of the International Searching Authority for International Application No. PCT/US08/60685 dated Sep. 17, 2008; 4 pages. |
Written Opinion of the International Searching Authority for International Application No. PCT/US08/60695 mailed Jul. 22, 2009; 6 pages. |
Written Opinion of the International Searching Authority for International Application No. PCT/US08/60696 mailed Sep. 22, 2008; 4 pages. |
A.F. Harvey, “DMA Fundamentals on Various PC Platforms,” 2001, 2004, National Instruments Corporation, pp. 1-19; 19 pages. |
Balough et al., “White Paper: Comparing IP Integration Approaches for FPGA Implementation,” Feb. 2007, Version 1.1, Altera, pp. 1-7; 7 pages. |
International Search Report for International Application No. PCT/US08/60680 dated Aug. 15, 2008; 2 pages. |
International Search Report for International Application No. PCT/US08/60685 dated Sep. 17, 2008; 5 pages. |
International Search Report for International Application No. PCT/US08/60695 dated Jul. 22, 2009; 3 pages. |
International Search Report for International Application No. PCT/US08/60696 dated Sep. 22, 2008; 5 pages. |
John Mangino, “Using DMA with High Performance Peripherals to Maximize System Performance,” 2007, Texas Instruments, pp. 1-23; 23 pages. |
SIPO 2 month Office Action for Application No. 200880012232.1 dated Apr. 23, 2012; 3 pages. |
SIPO 4 month Office Action for Application No. 200880012232.1 dated May 6, 2011; 2 pages. |
SIPO Office Action for Application No. 200880012232.1 dated Aug. 8, 2013; 3 pages. |
SIPO Office Action for Application No. 200880012232.1 dated Nov. 19, 2012; 3 pages. |
USPTO Advisory Action for U.S. Appl. No. 11/963,661 dated Jun. 30, 2011; 3 pages. |
USPTO Advisory Action for U.S. Appl. No. 11/963,661 dated Aug. 27, 2010; 3 pages. |
USPTO Advisory Action for U.S. Appl. No. 11/968,145 dated May 30, 2014; 3 pages. |
USPTO Advisory Action for U.S. Appl. No. 11/968,145 dated Oct. 6, 2011; 3 pages. |
USPTO Advisory Action for U.S. Appl. No. 12/060,176 dated Sep. 7, 2012; 3 pages. |
USPTO Final Rejection for U.S. Appl. No. 11/963,661 dated May 6, 2011; 7 pages. |
USPTO Final Rejection for U.S. Appl. No. 11/963,661 dated Jun. 22, 2010; 11 pages. |
USPTO Final Rejection for U.S. Appl. No. 11/963,661 dated Sep. 4, 2012; 26 pages. |
USPTO Final Rejection for U.S. Appl. No. 11/963,661 dated Nov. 26, 2014; 28 pages. |
USPTO Final Rejection for U.S. Appl. No. 11/968,145 dated Mar. 31, 2014; 5 pages. |
USPTO Final Rejection for U.S. Appl. No. 11/968,145 dated Jul. 29, 2011; 5 pages. |
USPTO Final Rejection for U.S. Appl. No. 11/968,145 dated Aug. 2, 2010; 6 pages. |
USPTO Final Rejection for U.S. Appl. No. 12/060,176 dated Jan. 24, 2012; 25 pages. |
USPTO Final Rejection for U.S. Appl. No. 12/060,176 dated Apr. 9, 2013; 26 pages. |
USPTO Final Rejection for U.S. Appl. No. 12/060,176 dated Jun. 21, 2012; 26 pages. |
USPTO Final Rejection for U.S. Appl. No. 12/060,176 dated Oct. 12, 2010; 22 pages. |
USPTO Final Rejection for U.S. Appl. No. 12/060,176 dated Nov. 8, 2011; 24 page. |
USPTO Final Rejection for U.S. Appl. No. 13/099,334 dated Oct. 17, 2012; 5 pages. |
USPTO Non Final Rejection for U.S. Appl. No. 11/965,291 dated Dec. 17, 2008; 8 pages. |
USPTO Non Final Rejection for U.S. Appl. No. 12/786,412 dated Jan. 31, 2011; 8 pages. |
USPTO Non-Final Rejection for U.S. Appl. No. 11/963,661 dated Feb. 4, 2010; 11 pages. |
USPTO Non-Final Rejection for U.S. Appl. No. 11/963,661 dated May 15, 2012; 19 pages. |
USPTO Non-Final Rejection for U.S Appl. No. 11/963,661 dated Aug. 28, 2014; 27 pages. |
USPTO Non-Final Rejection for U.S. Appl. No. 11/963,661 dated Dec. 3, 2010; 18 pages. |
USPTO Non-Final Rejection for U.S. Appl. No. 11/963,661 dated Dec. 29, 2011; 16 pages. |
USPTO Non-Final Rejection for U.S. Appl. No. 11/965,677 dated Mar. 10, 2009; 10 pages. |
USPTO Non-Final Rejection for U.S. Appl. No. 11/968,145 dated Jan. 5, 2011; 8 pages. |
USPTO Non-Final Rejection for U.S. Appl. No. 11/968,145 dated Jan. 14, 2014; 8 pages. |
USPTO Non-Final Rejection for U.S. Appl. No. 11/968,145 dated Mar. 4, 2010; 11 pages. |
USPTO Non-Final Rejection for U.S. Appl. No. 12/060,176 dated Mar. 30, 2010; 22 pages. |
USPTO Non-Final Rejection for U.S. Appl. No. 12/060,176 dated Apr. 6, 2011; 23 pages. |
USPTO Non-Final Rejection for U.S. Appl. No. 12/060,176 dated May 1, 2012; 25 pages. |
USPTO Non-Final Rejection for U.S. Appl. No. 12/060,176 dated Nov. 20, 2012; 26 pages. |
USPTO Non-Final Rejection for U.S. Appl. No. 12/104,391 dated Oct. 20, 2011; 4 pages. |
USPTO Non-Final Rejection for U.S. Appl. No. 13/099,334 dated May 25, 2012; 12 pages. |
USPTO Non-Final Rejection for U.S. Appl. No. 13/197,624 dated Aug. 3, 2012; 8 pages. |
USPTO Notice of Allowance for U.S. Appl. No. 11/965,291 dated May 5, 2009; 7 pages. |
USPTO Notice of Allowance for U.S. Appl. No. 11/965,677 dated Sep. 10, 2009; 6 pages. |
USPTO Notice of Allowance for U.S. Appl. No. 12/060,176 dated Jul. 9, 2013; 9 pages. |
USPTO Non-Final Rejection for U.S. Appl. No. 13/914,308 dated Feb. 25, 2015; 5 pages. |
Number | Date | Country | |
---|---|---|---|
20140013022 A1 | Jan 2014 | US |
Number | Date | Country | |
---|---|---|---|
60912399 | Apr 2007 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 13099334 | May 2011 | US |
Child | 13930756 | US | |
Parent | 12786412 | May 2010 | US |
Child | 13099334 | US | |
Parent | 11965291 | Dec 2007 | US |
Child | 12786412 | US |