This application claims the benefit under 35 U.S.C. §119(e) of U.S. Provisional Application Ser. No. 60/906,000, filed Mar. 9, 2007 (“the '000 application”). This application also relates to the subject matter disclosed in U.S. patent application Ser. No. 11/818,449, filed Jun. 14, 2007 (“the '449 application). The entire contents of each of the '000 and '449 applications are incorporated herein by reference.
Charge coupled devices (CCDs) are used in a large variety of digital imaging applications. There are a number of different manufacturers of such devices and each manufacturer typically has numerous models. The large variety of CCDs and the continuously evolving CCD control requirements have caused challenges in designing the analog front end/CCD controller circuits that will have significant longevity in the market place. This problem is ameliorated to a large extent by the software programmable pattern generator described in the '000 and '449 applications, incorporated by reference above. That software programmable pattern generator utilizes a compact and flexible assembly programmable Reduced Instruction Set Computer (RISC) that is optimized for generating high precision timing pulses and low power control functions. The architecture has a variable bit wide instruction set that includes: vector toggling instructions, jump instructions, conditional instructions, arithmetic instructions, and load/store instructions. The pattern generator can fetch and execute one instruction per clock cycle, and is parameter scalable to allow for easy optimization in different applications.
To allow every chip output to be set simultaneously at a pixel clock resolution, a large number of bits may be stored in parallel within the program memory, with each bit in a vector word corresponding to an output pin that can be selectively toggled, depending on the state of the bit. In the case of Analog Device's model number ADDI9000, this meant that every instruction was “64” bits wide. An advantage of this model was in the simple control and design logic required. We have since recognized, however, that the use of such large instructions consumes a significant amount of memory, thus imposing limits on the utility of the timing generator for certain applications.
According to one aspect of the present invention, a method for generating a digital signal pattern at M outputs involves retrieving a first instruction from memory comprising a first set of bits identifying a first group of N outputs that includes fewer than all of the M outputs, and a second set of N bits each corresponding to a respective output included in the first group of N outputs identified by the first set of bits included in the first instruction. For each of the M outputs that is included in the first group of N outputs identified by the first set of bits included in the first instruction, the signal at the output is toggled if the one of the N bits corresponding to that output is in a first state and is kept in the same state if the one of the N bits corresponding to that output is in a second state. For each of the M outputs that is not included in the first group of N outputs identified by the first set of bits included in the first instruction, the signal at that output is kept in the same state.
According to another aspect of the invention, an apparatus for generating a digital signal pattern at M outputs comprises a circuit configured and arranged to retrieve at least instructions of a first type from memory and to control the toggling of signals at the M outputs in response thereto, wherein each of the instructions of the first type comprises a first set of bits identifying a first group of N outputs that includes fewer than all of the M outputs, and a second set of N bits each corresponding to a respective output included in the first group of N outputs identified by the first set of bits included in the first instruction. The circuit is further configured and arranged to process each retrieved instruction of the first type such that, for each of the M outputs that is included in the first group of N outputs identified by the first set of bits included in the instruction, the signal at the output is toggled if the one of the N bits corresponding to that output is in a first state and is kept in the same state if the one of the N bits corresponding to that output is in a second state, and, for each of the M outputs that is not included in the first group of N outputs identified by the first set of bits included in the instruction, the signal at that output is kept in the same state.
According to another aspect, a method for generating a digital signal pattern at M outputs involves retrieving a first instruction from memory that consists of N bits, and retrieving a second instruction from memory that consists of fewer than N bits. Based on the first instruction, first ones of the M outputs are identified and the signals on those outputs are toggled. Based on the second instruction, second ones of the M outputs are identified and signals on those outputs are toggled.
This disclosure is directed to improvements to certain components and features of the system disclosed in the '449 application (incorporated by reference above). Familiarity with the entirety of the disclosure of the '449 application will thus be assumed. For ease of understanding, to the extent practicable this disclosure will use the same reference numerals as those used in the '449 application to describe similar components and features. It should be appreciated, moreover, that the components and features in this disclosure that are similarly named or that are designated using the same reference numerals as the components or features described in the '449 application may be used in the system described in the '449 application in the same or similar manner as such similarly named or labeled components and features are used therein.
That only certain key components of the system disclosed in the '449 application are re-described herein should not be understood to mean that such components and features are incompatible in any way with the new or modified components or features disclosed herein. Rather, it is simply for conciseness that only those components and features of the system disclosed in the '449 application that are directly impacted or modified by this disclosure are re-described herein.
As illustrated, the program sequencer 106 may comprise an instruction decoder 302 and program sequencer logic 304 that together are responsible for fetching instructions from the memory 108, decoding the fetched instructions, and controlling the synchronous timer 114 and channel control circuitry 118 so as to appropriately generate a pattern of digital signals at the outputs 120. In the example shown, the synchronous timer 114 comprises a toggle counter 306 and a comparator 308. The comparator 308 may, for example, determine when the toggle counter 114 has reached a specified “toggle count” value. The toggle counter 306 may, for example, comprise a sixteen-bit free-running clock cycle counter. An illustrative example of an execution flow that may be employed by these components to generate a pattern of pulses by toggling the signals at the outputs 120 and/or forcing the signals at the outputs 120 to particular values is discussed below in connection with
Once the toggle counter 306 has reached the specified toggle count, the flow proceeds to a step 810, where certain outputs 120 of the DPP are simultaneously toggled or forced to particular values in the manner specified by the instruction. The flow then returns to the steps 802 and 804 where the next program instruction is fetched and decoded.
If, at the step 806, it is determined that the fetched instruction is not a toggle instruction, then the routine proceeds to a step 812, where the instruction is carried out to as to control the program flow in the manner specified. (Examples of the manner in which particular toggle instructions and program flow instructions may be configured and carried out in various embodiments are described in detail in the '449 application and thus will not be repeated here). Accordingly, by employing the configuration and functionality illustrated in
As noted in the '449 application, one application of the DPP may be as a timing generator for an image sensor. Examples of environments in which such a timing generator may operate are described in U.S. Pat. No. 6,512,546, U.S. Pat. No. 6,570,615, and U.S. Patent Application Publication No. 2006/0077275 A1, each of which is incorporated herein by reference in its entirety.
Although the instructions 312, 314, 316 in the illustrated example are eight bytes, four bytes, and two bytes wide, respectively, it should be appreciated instructions of different lengths and relative sizes could additional or alternatively be employed. In some embodiments, for example, the short toggle instructions may be two and four bytes long, respectively, just as in the primary example described herein, but the long toggle instructions may be ten rather than eight bytes wide, with the two extra bytes containing additional bits of the vector field. Such a configuration would allow the generation of a digital pattern on “57” output pins, rather than on only “41” pins as in the primary example described herein.
To simply the implementation of hardware components in the system, it may be useful to align the longer instructions in memory so as to allow each instruction to be fetched in a single memory access. For example, if a memory including one thousand lines of sixty four bits is employed, each 64-bit instruction may be aligned so that it starts at the beginning of a line, rather than wrapping from one line to another. It may also be advantageous to align the 32-bit instructions in the above example so that they also do not wrap around from one memory line to another. For instructions that are aligned in such a manner, appropriate instructions may be inserted into the program code that cause the program counter to be incremented by a specific amount to account for the adjusted alignment (e.g., by skipping over one or more of the sections W1, W2, W3 of the memory line, which may simply remain unused).
In some embodiments, it can be advantageous to use instructions having lengths that are integer multiples of one another. In one of the examples above, for instance, the length of the 32-bit short toggle instruction is twice (or a power of two) greater than the length of the 16-bit short toggle instruction, and length of the 64-bit long toggle instruction is twice (or a power of two) greater than the length of the 32-bit short toggle instruction. The use of such “power of two” differences between instruction lengths may, for example, simply the process of fetching and decoding of instructions. For instance, in some embodiments, the mechanism used for fetching may only have to choose between incrementing the program counter by “1,” “2,” or “4,” which in binary becomes “001,” “010,” and “100,” respectively.
The opcode in each instruction may identify not only whether the instruction is a “toggle instruction,” as opposed to one of the other types of instructions described in the '449 application, e.g., a program flow instruction, a load/store instruction, an arithmetic instruction, etc., but also the particular length and content of the toggle instruction. For example, the opcode may indicate whether the instruction is a long toggle instruction 312 (which may be either an instruction to toggle certain bits or instruction to force certain bits to particular values), a 32-bit short toggle instruction 314, or a 16-bit short toggle instruction.
In the examples of
As shown, the long toggle instructions 312 and the 32-bit short toggle instructions 314 may also each include an “immediate count” field. This field may, for example, be used to identify the “toggle count” value that the toggle counter 306 must reach for an output event (e.g., a toggling of specified output bits or forcing of output bits to particular values) to occur. Alternatively, some or all of the same bits may be used to identify a particular register (e.g., one of the general purpose registers R0-R7 identified in Table 1 of the '449 application) that contains the toggle count value that is to be used for such a purpose. In the examples shown in
In the illustrated example, the channel control circuitry 118 includes a separate circuit 1180, 1181, 118N for each nibble (i.e., group of four bits) that is provided at a respective group of four output pads 1200, 1201, 120N of the DPP. As shown, each of the channel control circuits 1180, 1181, 118N may be provided with toggle control signals 310 from the decoder 302, as well as a “toggle match” signal from the comparator 308 of the synchronous timer 114. Vector data from a particular part of the instruction being executed is also supplied to each channel control circuit 1180, 1181, 118N as indicated by blocks 318, 320, and 322. For example, with reference to
A sufficient number of channel select circuits 1180, 1181, 118N may be employed to provide four different bits from the long instruction vector field (e.g., bits “23” to “63” in the example of
In the example shown, when the short toggle line 310b is low (indicating that the decoded instruction is not a short toggle instruction 314, 316), the multiplexer 326 is controlled (via the inverter 340) to provide the contents of the block 318 to one of the inputs of the AND gate 334. (If the opcodes shown in
In the illustrated example, the short toggle width select line 310a from the decoder 302 controls the multiplexer 324 to select either the four bits from the block 320 or the four bits from block 322 as an input to the multiplexer 326. As noted above, the four bits from the block 322 may be selected when a 16-bit toggle instruction is being processed, and the four bits from the block 320 may be selected when a 32-bit toggle instruction is being processed. (If the opcodes shown in
The “nibble select line” for each channel select circuit (e.g., nibble select line0 310d for channel select circuit 1180) may be asserted when the decoder 302 determines (e.g., by examining the bits in the nibble select field 316a or the byte select field 314a) that the particular output nibble for which the channel control circuit is responsible has been selected for toggling. With reference to
As shown in
When the toggle/force line 310 is low, the inverter 342 supplies a high signal to one of the inputs of the AND gate 336. Thus, when a toggle match signal is received from the synchronous timer 114, the AND gate 336 causes the multiplexer 328 to select the long vector nibble block 318, rather than the output of the XOR gate 344, as the input to the flip-flop 346, and thus causes the values of the long vector nibble block 318 to be forced upon the output pads 1200 rather than allowing the four bits from the multiplexer 326 to determine how the outputs should be toggled. (If the opcodes of
In the example circuit shown, receipt of a toggle match signal will cause the AND gate 334 to provide the four bits from the multiplexer 326 to one of the inputs of the XOR gate 344. The XOR gate 344, in turn, causes the four bits held by the “Q” output of the flip-flop 346 to be toggled as specified by those four bits (provided the toggle/force line 310c is high). If the nibble select0 line 310d is low when the short toggle select line 310b is high (indicating that the instruction is either a 16-bit short toggle instruction 316 or a 32-bit short toggle instruction 314) and the toggle/force select line 310c is also high, then the multiplexer 326 provides four zeros to the input of the AND gate 334, thus causing the outputs of that particular nibble to maintain their current state, and not be toggled, when the toggle match signal is received. If, however, the nibble select0 line 310d is high (indicating that the decoder has determined that the particular output nibble for which the channel control circuit 1180 is responsible has been selected for toggling) when the short toggle select line 310b and toggle/force select line 310c are both high, then the multiplexer 326 provides the four output bits of multiplexer 324 to the input of the AND gate 344, thus resulting in the output bits of that particular output nibble being toggled as indicated by those bits when the toggle match signal is received.
In some embodiments, a pattern generation program may be written using only “long” toggle instructions (several examples of such programs were disclosed in the '449 application, incorporated by reference above) and the determination of which long toggle instructions can be converted into either 16-bit or 32-bit short toggle instructions can be left to the timing generator assembler (TGASM). For example, any toggle instructions that require the toggling of one or more bits from only a single byte may be compressed into a 32-bit toggle instruction. Similarly, any toggle instructions that require the toggling of one or more bits from only a single nibble may be compressed into 16-bit toggle instructions. The TGASM may also automatically align the remaining longer instructions in memory and insert appropriate “align” instructions in the code so as to ensure that each such instruction can be fetched in a single memory access.
Having described several embodiments of the invention in detail, various modifications and improvements will readily occur to those skilled in the art. Such modifications and improvements are intended to be within the spirit and scope of the invention. Accordingly, the foregoing description is by way of example only, and is not intended as limiting. The invention is limited only as defined by the following claims and the equivalents thereto.
Number | Name | Date | Kind |
---|---|---|---|
3671875 | Pento | Jun 1972 | A |
3671945 | Maggio | Jun 1972 | A |
3811092 | Charbonnier | May 1974 | A |
3889104 | Smith | Jun 1975 | A |
3974484 | Struger et al. | Aug 1976 | A |
3976980 | Hertz | Aug 1976 | A |
4025868 | Miki et al. | May 1977 | A |
4257044 | Fukuoka | Mar 1981 | A |
4306482 | Kashio | Dec 1981 | A |
4380802 | Segar et al. | Apr 1983 | A |
4431926 | Mayumi | Feb 1984 | A |
4525803 | Vidalin et al. | Jun 1985 | A |
4587415 | Tsunekawa et al. | May 1986 | A |
4644469 | Sumi | Feb 1987 | A |
4719339 | Mizuno | Jan 1988 | A |
4843617 | Marshall et al. | Jun 1989 | A |
5027315 | Agrawal et al. | Jun 1991 | A |
5127010 | Satoh | Jun 1992 | A |
5129067 | Johnson | Jul 1992 | A |
5134484 | Willson | Jul 1992 | A |
5202844 | Kamio et al. | Apr 1993 | A |
5214669 | Zarembowitch | May 1993 | A |
5220215 | Douglas et al. | Jun 1993 | A |
5254984 | Wakeland | Oct 1993 | A |
5269007 | Hanawa et al. | Dec 1993 | A |
5283863 | Guttag et al. | Feb 1994 | A |
5295188 | Wilson et al. | Mar 1994 | A |
5313644 | Matsuo et al. | May 1994 | A |
5337415 | DeLano et al. | Aug 1994 | A |
5424668 | Kohsaka | Jun 1995 | A |
5432853 | Yamamoto | Jul 1995 | A |
5481549 | Tokuyama | Jan 1996 | A |
5489918 | Mosier | Feb 1996 | A |
5602855 | Whetsel, Jr. | Feb 1997 | A |
5751984 | Chang et al. | May 1998 | A |
5838896 | Han | Nov 1998 | A |
5850533 | Panwar et al. | Dec 1998 | A |
5883592 | Schepps et al. | Mar 1999 | A |
5898853 | Panwar et al. | Apr 1999 | A |
5954811 | Garde | Sep 1999 | A |
5954816 | Tran et al. | Sep 1999 | A |
5968196 | Ramamurthy et al. | Oct 1999 | A |
5974500 | Maletsky et al. | Oct 1999 | A |
6026141 | Lo | Feb 2000 | A |
6035378 | James | Mar 2000 | A |
6097721 | Goody | Aug 2000 | A |
6119220 | Sato | Sep 2000 | A |
6285310 | Michaelis et al. | Sep 2001 | B1 |
6378022 | Moyer et al. | Apr 2002 | B1 |
6427024 | Bishop | Jul 2002 | B1 |
6449710 | Isaman | Sep 2002 | B1 |
6560754 | Hakewill et al. | May 2003 | B1 |
6651176 | Soltis, Jr. et al. | Nov 2003 | B1 |
6841983 | Thomas | Jan 2005 | B2 |
6856527 | Srinivasan et al. | Feb 2005 | B1 |
6976123 | Regev et al. | Dec 2005 | B2 |
7111152 | Cofler et al. | Sep 2006 | B1 |
7171631 | Hakewill et al. | Jan 2007 | B2 |
7266005 | Syed et al. | Sep 2007 | B2 |
7281119 | Cofler et al. | Oct 2007 | B1 |
7281147 | Soltis, Jr. et al. | Oct 2007 | B2 |
7318145 | Stribaek et al. | Jan 2008 | B1 |
7418580 | Campbell et al. | Aug 2008 | B1 |
7493470 | Cumplido et al. | Feb 2009 | B1 |
20020036765 | McCaffrey et al. | Mar 2002 | A1 |
20030039135 | Srinivasan et al. | Feb 2003 | A1 |
20030046520 | Dulong | Mar 2003 | A1 |
20030145216 | Nakane et al. | Jul 2003 | A1 |
20030194003 | Wittig | Oct 2003 | A1 |
20040078551 | Lichtenfels | Apr 2004 | A1 |
20040128436 | Regev et al. | Jul 2004 | A1 |
20040199745 | Schlansker et al. | Oct 2004 | A1 |
20040264617 | Goko | Dec 2004 | A1 |
20050099877 | Dybsetter et al. | May 2005 | A1 |
20050114629 | Altman et al. | May 2005 | A1 |
20050169353 | An et al. | Aug 2005 | A1 |
20050172180 | Damodaran et al. | Aug 2005 | A1 |
20050257030 | Langhammer | Nov 2005 | A1 |
20060077275 | Pan et al. | Apr 2006 | A1 |
20060123295 | Tanaka | Jun 2006 | A1 |
20060152980 | Chiueh et al. | Jul 2006 | A1 |
20060233005 | Schaefer et al. | Oct 2006 | A1 |
20070107774 | Jin et al. | May 2007 | A1 |
20070234150 | Jain et al. | Oct 2007 | A1 |
20070292103 | Candelore | Dec 2007 | A1 |
20090006800 | Bellofatto et al. | Jan 2009 | A1 |
20090066790 | Hammadou | Mar 2009 | A1 |
20090077109 | Paris | Mar 2009 | A1 |
20100329673 | Duan et al. | Dec 2010 | A1 |
Number | Date | Country |
---|---|---|
0 715 252 | Jun 1996 | EP |
Entry |
---|
Adelman, Y. et al., “600MHz DSP with 24Mb Embedded DRAM with an Enhanced Instruction Set for Wireless Communication,” International Solid State Circuits Conference 2004. |
Dixon, J.D. et al., “Programmable Instruction Cycle Time” IBM Technical Disclosure Bulletin, vol. 25, No. 5, p. 2705 (Oct. 1982). |
Hennessy, J. et al., “Computer Architecture—A Quantitative Approach,” Fourth Edition, Morgan Kauffman 2007. |
Olofsson, A. et al., “A 4.32GOPS 1W General-Purpose DSP with an Enhanced Instruction Set for Wireless Communication,” International Solid State Circuits Conferences 2002. |
“Selective Register Bit Set/Reset Mechanism” IBM Technical Disclosure Bulletin, vol. 30, No. 12, pp. 402-405 (May 1988). |
AD9920 12-Bit CCD Signal Processor with V-Driver and Precision Timing™ Generator. |
Blackfin DSP Users Guide, http://www.analog.com/en/embedded-processing-dsp/blackfin/processors/manuals/resources/index.html. |
TigerSharc DSP Users Guide, http://www.analog.com/en/embedded-processing-dsp/tigersharc/processors/manuals/resources/index.html. |
Number | Date | Country | |
---|---|---|---|
20080222444 A1 | Sep 2008 | US |
Number | Date | Country | |
---|---|---|---|
60906000 | Mar 2007 | US |