Soft error detection logic testing systems and methods

[0001] The present invention relates generally to electrical circuits and, more particularly, to testing memory and associated logic within programmable logic devices.

[0002] A soft error upset (SEU), also known as a single event upset, refers generally to a change of state or a transient induced in one or more signal values in a semiconductor device (e.g., when struck by an ionizing particle, such as a neutron or an alpha particle). For example, a programmable logic device (PLD), such as a field programmable gate array (FPGA) or a complex PLD (CPLD), are configured by data stored in configuration memory cells (e.g., SRAM cells), which are susceptible to SEUs that change the originally programmed data state (e.g., programmed a “1” but SEU changes value to “0”). One or more SEUs within the PLD may be particularly noticeable because the data stored in the configuration memory cells determines the PLD's functionality.

[0003] Consequently for example, a conventional PLD typically includes soft error detection (SED) logic (e.g., soft error intellectual property (IP)) that will read the configuration memory cells, such as in the background of a user mode of operation, and calculate a cyclic redundancy code (CRC) value to compare with a pre-calculated CRC value (e.g., CRC checksum). If the CRC values match, then there is no error in the values stored in the configuration memory cells. However, if the CRC values do not match, an error flag may be provided, which may for example trigger a reconfiguration of the PLD.

[0004] To test the SED logic's ability to detect a soft error (e.g., SED logic functionality), a typical procedure is to simulate a soft error in the PLD as it is may be difficult to produce a real soft error in the hardware. For example, associated logic may be provided to the SED logic to simulate a soft error from one or more configuration memory cells, such as by changing a data value after it has been read from the configuration memory cell but before the CRC calculation is performed. However, the simulated soft error is not a true soft error condition and thus, may not accurately simulate and properly emulate a real (i.e., true) soft error, such as for example with respect to timing or other considerations.

[0005] As a result, there is a need for improved techniques for testing SED logic of programmable logic devices.

[0006] In accordance with one embodiment of the present invention, a programmable logic device includes a plurality of configuration memory cells, wherein at least one configuration memory cell is adapted to function as random access memory; read/write circuitry adapted to write to and read from a corresponding first port of the configuration memory cells, wherein the read/write circuitry is further adapted to read from the at least one configuration memory cell adapted to function as random access memory; and soft error detection logic adapted to check for an error in data values stored by the plurality of configuration memory cells, including the at least one configuration memory cell adapted to function as random access memory.

[0007] In accordance with another embodiment of the present invention, a programmable logic device includes a plurality of configuration memory cells; a plurality of logic blocks, wherein the logic blocks include a first set of the configuration memory cells to provide lookup table logic and a distributed memory function; means via a first port for writing to and reading from the configuration memory cells; and means for performing soft error detection of the configuration memory cells, wherein the performing means is tested by reading during a user mode of operation via the first port from at least one of the first set of the configuration memory cells providing the distributed memory function.

[0008] In accordance with another embodiment of the present invention, a method of testing soft error detection logic within a programmable logic device includes storing data values within configuration memory cells of the programmable logic device; changing a data value of a first one of the configuration memory cells, wherein the first one of the configuration memory cells functions as random access memory; reading back the data values from the configuration memory cells; and comparing the data values from the reading back to the stored data values to determine if the soft error detection logic detects the changing of the data value of the first one of the configuration memory cells.

[0009] 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.

[0014] 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.

[0015] FIG. 1 shows a block diagram illustrating a programmable logic device (PLD) 100 in accordance with an embodiment of the present invention. PLD 100 (e.g., an FPGA, a CPLD, or a field programmable system on a chip (FPSC)) includes input/output (I/O) blocks 102, logic blocks 104 (e.g., also referred to as programmable logic blocks (PLBs), configurable logic blocks (CLBs), logic array blocks (LABs), programmable functional units (PFUs), or programmable logic cells (PLCs)), and configuration logic 110 (e.g., for startup, encryption, and/or error detection). I/O blocks 102 provide I/O functionality (e.g., supports one or more I/O and/or memory interface standards) for PLD 100, while programmable logic blocks 104 provide logic functionality (e.g., LUT-based logic) for PLD 100. Configuration logic 110 provides the general configuration functions for PLD 100, which may include for example controlling the loading of configuration data along with encryption and/or decryption of the configuration data (e.g., such as during start up, programming, or reconfiguration) and error detection (soft error detection logic) to detect errors in the configuration data stored in PLD 100, as would be understood by one skilled in the art.

[0016] PLD 100 may also include blocks of memory 106 (e.g., blocks of EEPROM, block SRAM, and/or flash memory), clock-related circuitry 108 (e.g., PLL and/or DLL circuits), a configuration port 112, configuration memory 114, special function blocks 116 (e.g., DSP blocks or other forms of multiply and accumulate circuit functionality), and/or routing resources 118 (e.g., a conventional general interconnect routing fabric).

[0017] Configuration port 112 may be optionally implemented and used for programming memory 106 and/or configuration memory 114 of PLD 100 as would be understood by one skilled in the art. For example, configuration port 112 may include a programming port, such as a central processing unit (CPU) port (also referred to as a peripheral data port or a sysCONFIG programming port) and/or a programming port such as a joint test action group (JTAG) port (e.g., by employing standards such as Institute of Electrical and Electronics Engineers (IEEE) 1149.1 or 1532 standards). Configuration port 112 typically may be included to receive configuration data and commands.

[0018] It should be understood that the number and placement of the various elements, such as I/O blocks 102, logic blocks 104, memory 106, clock-related circuitry 108, configuration logic 110, configuration port 112, configuration memory 114, special function blocks 116, and routing resources 118, is not limiting and may depend upon the desired application. For example, special function blocks 116 are optional as are various other elements (e.g., memory 106) and may not be required for a desired application. Furthermore, it should be understood that the elements are illustrated in block form for clarity and that certain elements, such as configuration memory 114 for example, would typically be distributed throughout PLD 100, such as in and between logic blocks 104, to perform their conventional functions (e.g., storing configuration data that configures PLD 100).

[0019] PLD 100, as discussed herein, includes SED logic 120 (e.g., within configuration logic 110 as shown) that will monitor configuration memory 114 to detect for SEUs or other types of data errors. For example, PLD 100 may read back configuration memory 114 to perform a CRC calculation and comparison operation to a pre-calculated CRC value using SED logic 120. In accordance with one or more embodiments of the present invention, PLD 100 may also test SED logic 120 to verify correct operation by changing one or more configuration memory data values and then comparing to the previously stored expected value (e.g., based on CRC operations) to properly simulate (emulate) true SEUs associated with configuration memory 114.

[0020] For example, FIG. 2 shows a block diagram illustrating a PLD 200 in accordance with an embodiment of the present invention. PLD 200 may represent a portion of PLD 100 (FIG. 1) to illustrate, as a specific implementation example, the reading and writing of configuration memory 114 and the testing of SED logic 120. PLD 200 includes configuration memory cells 202 (e.g., eight SRAM cells of configuration memory 114), an address shift register (ASR) 204, and a data shift register (DSR) 206. ASR 204 and DSR 206 may be viewed as an example of read/write circuitry for programming configuration memory cells 202 and reading back configuration memory cells 202 (e.g., during a user mode of operation).

[0021] Configuration memory cells 202 may be arranged in a two-dimensional fashion (e.g., within routing resources 118, logic blocks 104, and other parts of PLD 100) and may number in the thousands or millions, but for clarity only two rows and four columns (e.g., partial rows and columns) of configuration memory cells 202 are shown. Configuration memory cells 202 may represent SRAM cells or any other type of volatile or non-volatile memory, depending upon the desired application, as would be understood by one skilled in the art.

[0022] ASR 204 controls wordlines 208 (e.g., labeled W0 through W3), while DSR 206 controls bitlines 210 (e.g., complementary bitlines labeled B and BN). As a conventional programming example, ASR 204 drives a logical low signal on wordlines 208, while DSR 206 drives a data signal for one column on bitlines 210 (i.e., complementary data signals on B and BN). ASR 204 then drives a logical high signal on one wordline 208 (e.g., wordline 208 labeled W0), while maintaining the logical low signal on the remaining wordlines 208 so that the data on bitlines 210 is written into configuration memory cells 202 associated with the one wordline 208 (wordline 208 labeled W0). After the data is written for the one column, ASR 204 drives a logical low signal on wordlines 208 and the process repeats for each column of data to be written.

[0023] After the configuration data is programmed into configuration memory cells 202, PLD 200 begins its normal operation (often referred to as “user mode”) to perform the logic functions and operate as intended for the particular design. Typically, during user mode, ASR 204 maintains a logical low signal on wordlines 208 and DSR 206 maintains a logical high signal on bitlines 210. The data may also be read out of configuration memory cells 202 during a user mode of operation via DSR 206 by controlling DSR 206 and ASR 204 in a similar fashion as discussed above, as would be understood by one skilled in the art, and as discussed further herein.

[0024] In general with respect to conventional approaches, the configuration memory is read during a user mode of operation (e.g., in the background to check for SEUs). If a manufacturer, for example, desires to test the SED logic's ability to detect a SEU, a typical procedure is to simulate a soft error in the PLD such as through additional logic provided to introduce an error into the data to be checked by the SED logic after the data has been read from the configuration memory. However, as noted above, such a simulated soft error may not accurately simulate and properly emulate a real (i.e., true) soft error being read from the configuration memory.

[0025] In contrast in accordance with one or more embodiments of the present invention, a data value stored in one or more of the configuration memory cells may be changed (e.g., to a predetermined value during a user mode of operation) so that the SED logic may be properly tested (e.g., verify that the SED logic detects the changed data value as an SEU). Specifically for example, configuration memory (e.g., of lookup tables within logic blocks 104), which may be used as distributed memory during a user mode of operation, may be used to test SED logic 120 by intentionally changing the stored data value in one or more of these configuration memory cells and monitoring SED logic 120 to determine whether the simulated SEU is detected.

[0026] As an example, FIG. 3 shows a circuit diagram illustrating a PLD 300 in accordance with an embodiment of the present invention. PLD 300 may represent a portion of PLD 200 (FIG. 2) to illustrate, as a specific implementation example, techniques for testing of SED logic 120. For example for clarity, PLD 300 is shown with one configuration memory cell 202 (e.g., one configuration SRAM cell), but the techniques disclosed herein may be applied to any number of configuration memory cells as would be understood by one skilled in the art.

[0027] Configuration memory cell 202 may represent, for example, a memory cell of a lookup table within logic block 104 (FIG. 1), with the memory cell optionally available for use as distributed memory within PLD 300. For example, configuration memory cell 202 may provide a first port 314 (indicated generally by circled regions identified as first port 314), for reading from or writing to configuration memory cell 202 via bitlines 210, and a second port 312 (indicated generally by a circled region identified as second port 312), an example of a read/write circuit for reading from or writing to configuration memory cell 202 as random access memory.

[0028] First port 314 couples to DSR 206 (not shown) via bitlines 210, as discussed in reference to FIG. 2, for programming configuration memory cell 202 and reading from configuration memory cell 202 (e.g., reading in the background during a user mode of operation, such as for checking for SEUs by the SED logic). Second port 312 couples to circuitry within PLD 300 (e.g., to other logic blocks 104) to use configuration memory as random access memory during user mode of operation, as would be understood by one skilled in the art.

[0029] In conventional approaches, the data value stored by configuration memory cell 202, if used as distributed memory, would be unable to be read by the SED logic. For example, first port 314 would be prevented (e.g., associated wordline 208 held low) from providing the data value stored in configuration memory cell 202 and thus, during read back for the SED logic, a certain data value (e.g., a constant) would be provided (e.g., by DSR 206) for use by the SED logic regardless of the data value stored in configuration memory cell 202 (i.e., the SED logic would not include the distributed memory data for the SEU test).

[0030] In contrast and in accordance with some embodiments of the present invention, configuration memory cell 202, when functioning in distributed memory mode, may be used to test SED logic 120. For example, the actual data value stored in configuration memory cell 202, in distributed memory mode, may be provided to SED logic 120. Thus, during user mode of operation, the data value may be changed (e.g., to a predetermined value) and then read to test SED logic 120 for proper operation (e.g., detection of the simulated SEU as represented by the change in the data value of configuration memory cell 202).

[0031] As a specific implementation example, PLD 300 (FIG. 3) illustrates a circuit implementation for testing the SED logic. Switches 308 are switched on by a RAM mode signal (labeled RAM Mode Fuse) if configuration memory cell 202 is to be used as distributed memory (e.g., distributed memory mode) to provide the ability to read and write data through second port 312. The RAM mode signal, for example, may be a global signal or provided on an individual configuration memory cell lookup table basis. Switches 310 are controlled by a RAM address signal (labeled RAM Addr) to control read/write addressing through second port 312 of configuration memory cell 202 during a user mode of operation as would be understood by one skilled in the art. As an example, fuse 302(2) (e.g., configuration memory cell of configuration memory 114 of FIG. 1) may be employed to provide the RAM mode signal.

[0032] During a normal (conventional) SED logic read back test of configuration memory cell 202, an associated wordline 306 (labeled ADDR_S) is held low to prevent the data value stored in configuration memory cell 202 from being read (as discussed above for the conventional SED logic operation). However, to test SED logic 120, for example, wordline 306 is held high (first port 314 enabled) to allow the read back via bitlines 210 of the data value stored in configuration memory cell 202 (e.g., the distributed memory data value). Thus, as an example, the data value stored in configuration memory cell 202 may be changed to a different value than used for the pre-calculated CRC value so that the calculated CRC value of SED logic 120 will differ and serve as a test of the SED logic's ability to detect a true SEU.

[0033] The logic for controlling wordline 306 (e.g., representing one of wordlines 208 of FIG. 2) may be implemented within ASR 204 or external to ASR 204. For example as shown in FIG. 3, a multiplexer 304 may be controlled with a multiplexer control signal (e.g., provided by fuse 302(1) and labeled SED block fuse) to select either a logical low value (e.g., ground) to prevent read back via first port 314 or to select an address signal (labeled ADDR) on wordline 208, which may provide a logical high value to enable read back via first port 314. Multiplexer 304, for example, may be incorporated into ASR 204.

[0034] In general for example, to test SED logic 120, a user of PLD 300 may select one or more of the configuration memory cells 202 for testing purposes. Thus, this logic and circuitry within PLD 300 may be implemented for all, one, or a few of configuration memory cells 202 that may be used as RAM during a user mode of operation. For example, only a few of configuration memory cells 202 may be provided with the capability to test the SED logic, as discussed herein.

[0035] During a normal SED logic read back test, configuration memory cells 202 operating as distributed memory will not be read back, but rather a constant will be provided (e.g., by DSR 206) in a conventional fashion, as discussed previously, and the resulting CRC value should match the pre-calculated CRC value (e.g., no error flag indicating no SEU). In contrast, a method of testing the SED logic according to the invention includes reading back data values from distributed memory. FIG. 4 illustrates an embodiment of the method. After writing a different data value (or previously programming with the different data value) into configuration memory cells 202 operating as distributed memory and designated for testing SED logic 120, this data value is then read back from these configuration memory cells 202 (e.g., through first port 314 and DSR 206) and provided to SED logic 120. Consequently, the calculated CRC value should differ from the pre-calculated CRC value, resulting in an SEU error flag to be set or other indication given of an SEU (simulated as discussed herein) and verifying that SED logic 120 is operating properly.

[0036] Systems and methods are disclosed herein to provide test techniques for SED logic for a programmable logic device. For example, in accordance with an embodiment of the present invention, techniques are disclosed for testing SED logic under a real soft error condition with correct timing, while not adding significantly to the hardware overhead (e.g., software based and may use existing fuses and distributed memory SRAM bits in logic block to emulate the soft error for testing purposes). For example, during a normal SED logic read back to check for SEUs, an SED block fuse (e.g., fuse 302(1)) is set (e.g., logical high value), wordlines to distributed RAM are tied to ground to disable read ports to DSR, and the SED logic ignores the user-controlled distributed RAM data values (e.g., using a forced constant provided by DSR for the SEU test). However for example, during an SED logic check to test the SED logic, the SED block fuse is not set (e.g., logical low value), the read ports to DSR are enabled to allow the SED logic to read back the user-controlled distributed RAM data values (instead of the DSR constant), and thus a “real” soft error may be detected by the SED logic (e.g., and provide an error flag) by proper selection of the data value written to the user-controlled distributed RAM.

[0037] 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.