The present disclosure relates to semiconductor components, in particular to memories and semiconductor components containing memories.
There is an ongoing need to store ever-increasing amounts of data in semiconductor memories. For example, non-volatile memories (NVM) retain stored data even after being powered off.
Errors can occur in the stored data and in many applications it is necessary to identify and if possible correct such errors.
Data present in the form of bytes may be detected byte by byte and corrected byte by byte. In this case, a byte can comprise at least two bits. At least one error in at least one bit of a byte is referred to as a byte error. If at least one bit of a byte is erroneous, a byte error is present. If only at least one bit of a single byte is erroneous, this corresponds to a 1-byte error.
The correction of 1-byte errors is described for example in [Bossen, D.: b-Adjacent Error Correction, IBM J. Res. Dev., July 1970, pages 402 to 408].
If bits of two different bytes are erroneous, this corresponds to a 2-byte error. Accordingly it holds true that a k-byte error is present if bits in k bytes are erroneous (i.e. at least one bit in each of the k bytes has an error) .
The byte error correction can be effected by means of a Reed-Solomon code, for example.
A circuit arrangement for correcting two-byte errors using a Reed-Solomon code is described in OKANO [Okano, H., Imai, H.: A Construction Method of High-Speed Decoders Using ROM’s for Bose-Chaudhuri-Hocquengiem and Reed-Solomon Codes, IEEE TRANSACTIONS ON COMPUTERS, VOL. C-36, NO. 10, OCTOBER 1987, pages 1165 to 1171]. In this case, it is disadvantageous that the correction of 2-byte errors described in OKANO is comparatively slow.
An error code may in general be used to correct bytes. For example, 43 data bytes may be stored together with 3 bytes of error code. Should a failure occur and the data become corrupted in one of the data bytes the data in the error code may be used to identify which of the data bytes are incorrect and to correct that data byte. Such an error code will be referred to as a first error code in the following.
A further code, referred to as a second error code may also be provided. Such a second error code may be linked to the physical structure of the memory which accordingly will now be further described, purely by way of example.
In an embodiment, a memory 100 includes a plurality of physical storage bytes 102 each of 8 bits 104. Note that in this example the term “byte” is used for a data size. In other examples, the byte may be 6 or 10 bits for example, or indeed any desired number of bits.
The memory may be a resistive random access memory, RRAM, in which each bit of data is stored using a material that can exist in a plurality of different resistance states. For example, a high resistance may indicate a 0 bit and a low resistance a 1 bit.
Node 122 is connected to one input of a read-out comparator 108 and also to capacitor 116. The other input of comparator 108 is connected to a voltage reference at voltage VREF. One PMOS transistor 118 connects node 122 to a positive precharge voltage VPRE, and NMOS transistor 120 connects node 122 to the bit line 106. Thus, single bit 104 is coupled to the one input of the read-out comparator 108.
In use, a signal on word line 114 selects a specific bit 104 using the respective select transistor 112.
Capacitor 116 is charged to precharge voltage VPRE by switching transistor 118 on. Then, transistor 118 is switched off and the capacitor discharges through transistor 120, storage element 110 and select transistor 112 towards ground.
In the event that the storage element 110 is in a low resistance state the capacitor 116 will discharge faster than if the storage element 110 is in the high resistance state. This means that the voltage will fall below voltage VREF more quickly and so comparator 108 will be triggered more quickly.
The data stored in the byte 102 is stored using a second code in which all data is represented by a byte with four bits having the value 1 and four bits having the value 0. In this example, with 8 bits in each byte, this means that 6 bits of input data may be stored. For example, input data 000000 may be represented by 11110000, input data 000001 by 11100001, and so on, so that each possible 6 bit input data value has a different value in the second code. This allows the data to be read as will now be described.
The circuit of decoder 130 is illustrated in
Since it is known that the codeword stored in byte 102 must have four 1 and four 0 values, the four bits that have discharged most quickly may be identified as the four “1” values of the codeword and the other four bits as “0”. Accordingly this value (all eight bits) may be output as the data read from the memory. If the output is correct, the eight bits will include four 1 bits and four 0 bits, for example 10101010, which is a codeword of the second code.
It takes a finite time for the output 601 to stop the read operation and it is possible therefore that a further bit triggers. In this case, the output may include a different number of 1 and 0 bits, for example 10101110. In this case, this value is not a codeword of the second code.
Note that in this way the memory may store a plurality j of physical bytes. Each physical byte in the memory includes a number k of bits, where k is a positive integer. In the example described above k=8. Each physical byte represents a logical byte with m bits, where m is a positive integer less than k. In the example m is 4. Thus, each 8 bit codeword, for example 10101010, stored as a physical byte, represents a 6 bit logical byte, for example 110110. There is a one to one correspondence between physical and logical bytes, but the difference is that because of the use of the second code the number of bits of each logical byte is lower than the number of bits of each physical byte.
The j logical bytes in this case may be selected from a first error code such as a Reed-Solomon code. Only certain combinations of j logical bytes are codewords of this first error code. If the j logical bytes read from the memory are not a codeword of the first error code, an error has occurred which may in some cases be corrected.
The additional information from the second error code which in this example is related to the physical structure of the decoder 130 of the memory may be combined with information from the first error code to improve error detection and error correction, as will now be described in more detail.
Byte-error-detecting and byte-error-correcting codes (also referred to as error code s) can be used for error correction and error detection in respect of data stored in memory cells, for example. One example of an error code is the Reed-Solomon code (in this respect, also see explanations below).
In the case of a byte error, the position of the erroneous bytes is to be determined and, if the byte error is intended to be corrected, the correct value of the byte is also to be ascertained.
The position of the erroneous byte is determined on the basis of the byte error position (also referred to as byte error position value, indicating which byte or which bytes is or are (possibly) erroneous). By way of example, a value 1 for the byte error position can indicate that the byte is erroneous, and a value 0 can indicate that the byte is not erroneous.
A byte error value indicates the value by which an erroneous byte differs from its correct value. If each byte comprises m bits, then the byte error value also comprises m bits. By way of example, a correction can be carried out by exclusive-ORing (XORing) the bits of the erroneous byte component by component with the associated bits of the byte error value.
A t-byte error states that a number of t bytes is erroneous. In order to correct a t-byte error, t byte error positions and t byte error values are required.
For a byte having m bits, the byte can be described as an element of the Galois field GF(2m). The following generally holds true: if m p-order values where p > 2 form a byte and if p is a prime number, a byte can be described as an element of the Galois field GF(pm). In this case, m is for example a positive integer greater than 2.
In the present example, bytes having m bits are used. Accordingly, there are 2m different m-bit bytes.
By way of example, the intention is for a first number of N byte errors to be corrected. Accordingly, an N byte error (N ≥ 1) is corrected.
For a second number N1 of byte errors, the corresponding byte error position at which a byte error has occurred may already have been determined. During a correction, it is then necessary only to determine the byte error value for these N1 byte errors at the known byte error positions.
For a third number N2 of byte errors, it may be necessary to determine both the byte error value and the byte error position. In this case, N1 + N2 = N may hold true. In this case, N2 ≥ 1 and it may hold true that N2 = 1.
By way of example, the m-bit byte in the error-free case forms a code word of the Reed-Solomon code. The Reed-Solomon code here serves as a first error code.
In addition, the m-bit byte can be transformed into a code word of a second error code before it is stored in a memory. The second error code can be an n1 out-of-n code.
In a first example with m = 4 a plurality of 4 bit bytes in the error-free case form the code word of a Reed-Solomon code, the first error code. By way of example, at least one byte of the code word may be a check byte of the Reed-Solomon code. There are 2m = 24 = 16 different values per byte in this example.
In this example, the second error code is a 3-out-of-6 code having 20 code words. A 3-bit byte of the Reed-Solomon code can for example be transformed into a code word of the second error code and be stored in six memory cells of a memory (in this respect, cf. e.g. US 10,903,859 B2). In this case, each 6-bit byte of the first error code is reversibly uniquely transformed into one of the 20 code words of the 3-out-of-6 code of the second error code. These code words represent the m bit logical byte. This example corresponds with the example of
Those skilled in the art will realise that different values of m may be used, to allow more data to be stored in each byte.
In a further example with m = 6 a plurality of 6-bit bytes in the error-free case form the code word of a Reed-Solomon code. By way of example, at least one byte of the code word may be a check byte of the Reed-Solomon code. There are 2m = 26 = 64 different values per byte in this example.
In this example, the second error code is a 4-out-of-8 code having 70 code words. A 6-bit byte of the Reed-Solomon code can for example be transformed into a code word of the second error code and be stored in eight memory cells of a memory. In this case, each 6-bit byte of the first error code is reversibly uniquely transformed into one of the 70 code words of the 4-out-of-8 code of the second error code.
In the course of reading out from the memory, in the error-free case, code words of the 4-out-of-8 code are read out and transformed back into 6-bit bytes. In the error-free case, the 6-bit bytes present after the inverse transformation once again yield a code word of the first error code.
As early as in the course of reading out from the memory, it is possible to check whether a code word of the 4-out-of-8 code is present: if 4 ones and 4 zeros have not been read, a code word of the 4-out-of-8 code is not involved. In this case, the byte read out is erroneous, i.e. a byte error position was determined for this byte by means of the 4-out-of-8 code.
The read-out non-code word of the 4-out-of-8 code is transformed back into an (erroneous) m-bit byte. A predefined value from the 64 possible values (e.g. the value 0) can be used for this purpose. It is advantageous, however, for information that this byte is erroneous to be provided with detection of a non-code word of the 4-out-of-8 code. The inverse-transformed 6-bit value then no longer occurs because it has to be assumed that this byte has to be corrected by means of the second error code. In accordance with the explanations above, only the byte error value has to be determined for this erroneous byte.
Consequently, the checking of the values of the second error code that are read out from the memory cells makes it possible to determine at least one byte error position for the bytes of the first error code. In this case, it is advantageous that the differentiability of the bytes is maintained by the transformation and the inverse transformation: each 6-bit byte is assigned an 8-bit byte, and vice versa. The byte error position thus uniquely identifies the byte, irrespective of whether it has 6 bits or 8 bits.
The fact that the first error code does not have to be used to determine this byte error position is an advantage. Check bytes can thus be saved in the first error code.
In a next step, each of the bytes of the code word of the RS code is transformed into a code word of the second code. In the present example, the second code is a 4-out-of-8 code: the code words of the 4-out-of-8 code have 4 ones and 4 zeros. Each byte is thus a physical byte with k=8 bits. 46 bytes arise once again after the transformation. These bytes are stored in the memory as j 8-bit codewords of the second error code.
Each of the 46 codewords is thus stored in a physical byte of k=8 bits representing the structure of the memory.
To read data from the memory, j=46 bytes of physical bytes of 8 bits are read from the memory. In the course of this, a check is made as to whether each of the bytes read is a code word of the 4-out-of-8 code.
In accordance with one exemplary implementation, and as explained above, the individual bytes can be read from the memory using time. In this case, the read operation can advantageously already be ended when 4 bits of the same type, i.e. either 4 times the value 0 or 4 times the value 1, have been read. For the remaining bits that have not arrived, the respective other value is then assumed. This approach uses the property of the 4-out-of-8 code, in which code words have 4 ones or 4 zeros. Errors may occur here such that five instead of four identical values are read and a code word of the second code is thus no longer present. For details with regard to reading memory cells in the time domain, reference should be made to US 9,805,771 B2, for example: in this case, a read current formed in the course of reading out depending on a resistance value stored in the memory cell is integrated in a capacitor. The memory cells that reach a specific voltage of the capacitor the fastest in the temporal order can each be assigned the value 1, and the cells that reach the specific voltage the slowest can each be assigned the value 0.
If the 8-bit byte read from the memory is a code word of the second error code, i.e. of the 4-out-of-8 code, then the inverse transformation of this code word into a 6-bit value (more generally, into m bits) is effected in accordance with the assignment mentioned above. If all 46 bits are code words of the second error code, the inverse transformation into 46 6-bit bytes takes place, which are a code word of the first error code, i.e. of the RS code, in the error-free case.
If at least one of the 8-bit bytes read is not a code word of the 4-out-of-8 code, then there is at least one byte error position, which is communicated to the subsequent correction step in order to initiate the correction of this at least one erroneous byte by means of the first error code.
The approach described here also allows the detection of the further byte error position by way of the first error code (with subsequent correction), which position is associated with a 4-out-of-8 code word that was corrupted into a further 4-out-of-8 code by means of a plurality of errors. This incorrect 4-out-of-8 code word is not detectable by the second error code and the byte error position for this code word thus also cannot be ascertained by way of the second error code. However, an additional byte error may be present which is detected by the second error code. The second error code yields the byte error position for this additional byte error. On the basis of this byte error position, the first error code can then ascertain and correct the further byte error position (corresponding to the corrupted 4-out-of-8 code word).
The invention is not restricted to the second error code being an n1-out-n code. By way of example, an m-bit byte of the first error code can be mapped onto an (m + 1)-bit byte of the second error code by a parity bit additionally being formed from the m bits of the byte of the first error code and being appended to the m bits of the first error code. A code word of the second error code may be an (m + 1)-bit word having an even number of ones.
In accordance with a further example, the m bits of a byte of the first error code can also be stored in duplicated fashion and thus redundantly in the memory. In the course of reading, the second error code can be used to monitor whether the same m-bit byte was obtained twice.
Moreover, different m-bit bytes of the first error code can be transformed into code words of the second error code (e.g. different error codes) according to different specifications. In this regard, for example, a first 6-bit byte can be transformed into a code word of an 4-out-of-8 code and a second 6-bit byte is transformed into a 7-bit byte (6 bits with an additional parity bit).
The second error code is not absolutely necessary for the approach described here. All that is necessary is that, for an erroneous byte, a byte error position is determinable which can be used in the determination of a further byte error position by the first error code and does not have to be determined by the latter.
By way of example, measured values that are in a specific previously known range of values can be stored for each payload data byte. The measured value can be e.g. temperature, air pressure, length of components or the like.
The payload data bytes can be stored together with check bytes in a memory, the payload data bytes and the check bytes (in the error-free case) forming a code word of the first error code. If, in the course of reading from the memory, it is found that a payload data byte is not in the known range values, then a byte error position can be detected for this byte.
The examples described here make it possible in particular to improve the error correction and error detection of a first error code. In this case, the further byte error position is intended to be determined efficiently and with low complexity.
Some terms and properties of Reed-Solomon codes are explained below.
By way of example,
By way of example, known Reed-Solomon codes can be used as byte-error-correcting codes. For Reed-Solomon codes reference should be made for example to [Lin, S., Costello, D.: Error Control Coding, Prentice Hall, 1983, pages 170 to 177] or [Wicker, S.: Error Control Systems for Digital Communication and Storage, Prentice Hall, 1995, pages 214 to 224].
A 1-byte-error-correcting and 2-byte-error-detecting Reed-Solomon code has an H matrix
as follows:
In this case, αi are elements of the Galois field GF(2m). They are present for example in an exponential representation. α can be a primitive element of the Galois field GF(2m). The exponents j of αj should be interpreted modulo 2m - 1.
It is possible to derive from the H matrix in accordance with equation (1) an H matrix
by multiplying, for i = 0,..., (2m - 2) the i-th column by α-i. This changes only the shape of the H matrix, and not the code, since α-i ≠ 0. This is also described for example in [Fujiwara, E.: Code Design for Dependable Systems, Wiley, 2006, page 65], wherein the value “1” is used for α0 since α0 is the unity of the Galois field used.
The following H matrix is used for a 2-byte-error-correcting and 3-byte-error-detecting code:
Each column of the H matrix specified in equation (3) corresponds to one byte.
If the length of the code is equal to N bytes or m • N bits (wherein each byte has m bits), only N columns of the H matrices in accordance with equation (1) or equation (3) are used. By way of example, the remaining (last) 2m - 2 - N columns can then be deleted.
Generally, for a t-byte-error-correcting and t + 1-byte-error-detecting code, the H matrix can be specified as follows:
A code that can correct 2-byte errors and detect 3-byte errors is considered by way of example below.
If an error occurs, a correct vector v=v0,...,vN-1 is disturbed to an erroneous vectorv1=v0,...,vN-1.
The components v0,...,vN-1 of the vector v are bytes that each comprise m bits, such that
holds true for i = 0, ..., N - 1. The
are thus the m bits of the i-th byte.
An m-bit byte can also be referred to as an element of the Galois field GF(2m).
If a 1-byte error is present, only a single byte is erroneous, that is to say that for a specific i ∈ {0, ...,N - 1} the associated i-th byte is erroneous.
If the correct i-th byte is designated by
and the erroneous i-th byte is designated by
, 1 or 2 or up to m bits of the correct i-th byte can differ from the erroneous i-th byte.
A byte error in the i-th byte can be described by
In this case, it should be noted that “⊕” denotes the exclusive-OR operation.
The position of an i-th byte can also be designated by αi.
If the intention is to correct a byte error having the byte error value ei in the byte position i, then a byte error correction value that is equal to the byte error value is to be determined for the byte position i.
In this example, for a byte error to be corrected, the byte error value is equal to the byte error correction value; in this respect, the terms byte error value and byte error correction value can be used synonymously.
In order to avoid a confusing number of indices, hereinafter byte error values are designated by the alphabetic letters a, b, c.
A byte error correction value for the i-th byte can also be designated by a(i).
Byte positions can be designated by i, j, k, ... or by α1, αj, αk, ..., wherein a is a generating element of the Galois field GF(2m).
An error syndrome s has syndrome components (also referred to as components, error syndrome components, partial error syndromes or partial syndromes) s1, s2, s3, s4, s5, which are determined for the H matrix in accordance with equation (4) as:
In this case,
is a column vector having a number of M components each having m bits. This column vector can also be referred to as a transposed vector of the row vector
Each of the syndrome components s1, s2, ... s2 t+1 is a byte having m bits.
If a 1-byte error is present, then it holds true that s1 # 0 and
If a 2-byte error is present, then it holds true that
and
If a 3-byte error is present, then it holds true that
and
This can be correspondingly continued up to a t-byte error: in this regard, a t-byte error is present if it holds true that:
and
The number of byte errors can be determined by the determination of the values of the specified determinant. This is complex as the number of possible errors increases: in this regard, for establishing whether a t-byte error is present according to equations (10) and (11), it is necessary to determine the value of a determinant having 2 · t syndrome components as elements. These are to be stored in addition to the payload data bytes. Each syndrome component corresponds to a byte having m bits.
A byte error position can be determined for example as zeros of the locator polynomial.
A zero of a locator polynomial can be described as an element of the corresponding Galois field GF(2m).
In this case, a first, second, third element, etc. of the Galois field is designated by α1, α2, α3, etc. This does not stipulate which element of the Galois field is specifically involved.
If
is for example the set of the 2m - 1 elements of the Galois field not equal to 0 in their exponential representation, then α1, α2, α3, etc. are elements of this set. By way of example,
or some other assignment can hold true.
The locator polynomials result as follows for the different numbers of byte errors:
In this case, the coefficient σ(j)i of a locator polynomial for j = 1, ...,n and i = 1, ...,n denotes a known elementary symmetric function of j variables α1 to aj. This can be verified by multiplying out
In this regard, it holds true for example that
In this case, as illustrated in the examples, a symmetric function σ(k)i where 1 ≤ i ≤ k is dependent on k variables α1, ...., αk. It contains all possible
different products of its variables which are combined by way of the operation “+” in the Galois field GF(2m). If i = 1, the
products each consist only of one of the variables. The addition is effected in the Galois field GF(2m) . It corresponds here to component-by-component addition modulo 2. The variables α1, α2, α3, etc. are used here as variables of the symmetric functions.
Between the components of the error syndromes and the components of the corresponding locator polynomials, the following relationship is known for a t-byte error:
This is described for example in [Wicker, S.: Error Control Systems for Digital Communication and Storage, Prentice Hall, 1995, pages 215], where the designation Si is used for the syndrome component si and the designation Λi is used for the coefficient σ(t)i.
If, by way of example, a Galois field GF(qm) where q = 2 is used, the negative signs in equation (17) can be omitted since addition and subtraction are identical in a Galois field GF(2m). By way of example, hereinafter the Galois field GF(2m) is used and the negative signs in equation (17) are omitted.
An explanation is given below by way of example of how
In this case, the number of byte errors N1 is greater than or equal to 1.
It is taken into account that one byte error or a plurality of byte errors has/have already occurred beforehand. The at least one further byte error may then occur in accordance with the above formulation.
If, for example, N1 byte error positions have been determined, then a further (N1 + 1)-th byte error position can be determined if a byte error has occurred at this position. If no further byte error position is erroneous, then no further byte error has occurred either.
It should be noted here that a byte error that has occurred is a byte error that is detectable by means of an error code. It is conceivable for a non-detectable byte error to be present, which remains undetected and in this respect is regarded as not having occurred in accordance with the present explanations.
For example, a first byte error position α1 is given. The byte error position states that an error was detected for this byte comprising a plurality of bits.
If a further byte error has occurred in a different byte, a second byte error position α2 can be determined. Moreover, it can be determined that no further byte error position is present if no second byte error has occurred.
In the case of a 1-byte error with the predefined byte error position α1 and with a byte error value α, it holds true that
It is not necessary for the byte error value α to be known.
In the case of a 2-byte error with
it holds true that
and thus
It is not necessary for the values α2, a and b to be known.
Given a known byte error position α1, on the basis of
it can be determined that no 2-byte error is present, and on the basis of
it can be established that no 1-byte error is present.
If no 1-byte error is present, rather a 2-byte error with a known byte error position α1 and a byte error position α2 to be determined is present, then it holds true that
where
and
and thus
Equation (27) is solvable with respect to the byte error position α2 to be determined:
The byte error position α2 is determinable from the three syndrome components s1, s2 and s3 and the symmetric functions σ(1)1 = α1. As explained, the byte error position α1 is previously known. It is therefore not necessary to determine the solutions of the corresponding locator polynomial.
Alternatively, a description is given of how, in the case of two known byte error positions α1 and α2, it is determined whether a third byte error is present and, if a third byte error is present, how a third byte error position can then be determined. In this case, the byte error positions α1, α2 and α3 differ from one another.
If a 2-byte error is present, it holds true that
This results from:
In this case, a and b are the corresponding byte error values and α1 and α1 are the byte error positions. If equation (29) holds true, then no 3-byte error is present.
If a 3-byte error with the byte error values a, b and c and the byte error positions α1, α2, α3 is present then it holds true that:
This yields the following:
A value D = 0 is only possible if (at least) one of the following conditions is met:
A 3-byte error can thus be detected from the validity of the inequality
If a 3-byte error is present, then the third byte error position α3 can be determined using the known byte error positions α1, α2 and from the syndrome components s1, s2, s3 and s4 in accordance with the relationship
where
The byte error position α3 is the erroneous further (i.e. additional) byte error position to be determined. It follows from equation (30) that
and thus for the byte error position α3 to be determined:
The byte error position α3 is determinable from the four syndrome components s1, s2, s3, s4 and the symmetric functions σ(2)1, σ(2)2 which emerge from the known byte error positions α1 and α2. It is not necessary to ascertain the solutions of the corresponding locator polynomial (here: third degree) or to use more than four syndrome components. This reduces the complexity to a considerable extent.
This approach can be extended accordingly: A further byte error position can be determined if three or more byte error positions are previously known. If k byte error positions are known, then k + 2 error syndrome components are known.
For example, the following hold true for the byte error positions to be determined
In general, for N1 known byte error positions α1, ..., αN1, the further byte error position αN1 + 1 results as:
It can be advantageous to use the following symmetric functions σ(j)i where j ≥ 1 and i ≤ j: the function σ(j)i for j > 1 arises from the functions σ(j - 1)k where k ≤ j - 1 and a further variable αk:
Consequently, from already ascertained symmetric functions σ(j)i and an additional variable, further symmetric functions can be determined step by step and used for ascertaining the further byte error position.
An adder 21 having two m-bit-wide inputs and an m-bit-wide output enables the component-by-component addition modulo 2 (XORing) of the byte error positions α1 and α2 present at the inputs. A Galois field multiplier 22 having two m-bit-wide inputs and an m-bit-wide output enables the multiplication α1 · α2.
These examples proposed herein can be based on at least one of the following solutions. In particular, combinations of the following features can be used in order to achieve a desired result. The features of the method can be combined with (any) arbitrary feature(s) of the device or of the circuit, or vice versa.
In order to achieve the object, a method for error processing is proposed,
In one development, the further byte error position is determined by way of the n byte error positions and the n + 1 error syndrome components of the first error code.
In one development, the first error code is a byte error code, in particular a Reed-Solomon code.
One development involves detecting that no further byte error is present if no further byte error position is determinable.
In one development, the further byte error position is determined depending on at least one symmetrical function of the n byte error positions.
In one development,
In one development, the second error code is an n1-out-of-n code, wherein 1 ≤ n1 < n ≤ 2 holds true.
In one development, code words of the second error code are stored in a memory.
In one development, in the error-free case code words of the second error code are read out from the memory and transformed back into bytes of the first error code.
In one development, the reading out from the memory is effected taking account of a temporal order.
In one development, if a non-code word of the second error code is detected in the course of the reading out from the memory, a byte error position is determined for this byte of the first error code.
In one development, the further byte error position α2 is determinable such that the following holds true:
wherein α1 denotes the predefined byte error position and s1, s2, s3 denote syndrome components.
Moreover, a device for error processing is proposed, which is configured to determine whether there is a further byte error position on the basis of n byte error positions and on the basis of n + 1 error syndrome components of a first error code, wherein the n byte error positions of n byte errors are predefined and wherein n is a positive integer.
In one development, the device is furthermore configured to determine the further byte error position by way of the n byte error positions and the n + 1 error syndrome components of the first error code.
A circuit arrangement is also specified, comprising at least one of the devices described herein.
The device and/or circuit arrangement can be embodied as parts of an integrated circuits or memory chip or separately therefrom.
An method for error processing is further described, including reading a memory, the memory including a plurality of physical bytes, each physical byte containing k physical bits, the memory containing data stored in the memory in a format comprising a plurality j of logical bytes each having m bits of a first error code, wherein only certain possible values of the j bytes represent codewords of the first error code, the data of each logical byte of m bits being stored in each physical byte using a second error code, whereby only 2 m codewords of the second error code are allowed values to be stored in the k bits of the physical bytes, wherein j, k and m are all integers and m < k,
the method comprising: reading a plurality of j bytes from the memory,
Number | Date | Country | Kind |
---|---|---|---|
102022101798.2 | Jan 2022 | DE | national |