US7058881B2 - Distributed 4-bits diagonal interleaved parity (DIP4) checker - Google Patents
Distributed 4-bits diagonal interleaved parity (DIP4) checker Download PDFInfo
- Publication number
- US7058881B2 US7058881B2 US10/234,165 US23416502A US7058881B2 US 7058881 B2 US7058881 B2 US 7058881B2 US 23416502 A US23416502 A US 23416502A US 7058881 B2 US7058881 B2 US 7058881B2
- Authority
- US
- United States
- Prior art keywords
- circumflex over
- bit
- parity
- error detection
- data stream
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Expired - Fee Related, expires
Links
Images
Classifications
-
- H—ELECTRICITY
- H03—ELECTRONIC CIRCUITRY
- H03M—CODING; DECODING; CODE CONVERSION IN GENERAL
- H03M13/00—Coding, decoding or code conversion, for error detection or error correction; Coding theory basic assumptions; Coding bounds; Error probability evaluation methods; Channel models; Simulation or testing of codes
- H03M13/33—Synchronisation based on error coding or decoding
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L1/00—Arrangements for detecting or preventing errors in the information received
- H04L1/004—Arrangements for detecting or preventing errors in the information received by using forward error control
- H04L1/0056—Systems characterized by the type of code used
- H04L1/0061—Error detection codes
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L1/00—Arrangements for detecting or preventing errors in the information received
- H04L1/0078—Avoidance of errors by organising the transmitted data in a format specifically designed to deal with errors, e.g. location
- H04L1/0079—Formats for control data
- H04L1/008—Formats for control data where the control data relates to payload of a different packet
Definitions
- This invention relates to an error detection method and apparatus.
- the invention is directed to a method and apparatus for detecting errors that may occur during a data transmission to an electronic device.
- information is represented in binary format as “ones” and “zeroes”.
- binary information is transmitted from one electronic device to another device, there is a chance that the bits of the binary information may become corrupted. Corruption to the binary information may be caused by electronic noise, poor cable connections, media defects, component failures, as well as other factors.
- home or office appliances having motors, such as fans, garbage disposals, blenders, and other devices can generate this type of noise, which adversely impacts the reception of an incoming digital signal.
- noise or any other corruption affects an incoming digital signal such as a packet, the corrupted packet will typically be dropped and may need to be retransmitted by the source network device.
- Error detection is the process of detecting bit errors within a signal.
- information is represented in binary format as “ones” and “zeroes” .
- binary information is transmitted from one electronic device to another device, there is a chance that the bits of the binary information may become corrupted. Corruption to the binary information may be caused by electronic noise, poor cable connections, media defects, component failures, as well as other factors.
- home or office appliances having motors, such as fans, garbage disposals, blenders, and other devices can generate this type of noise, which adversely impacts the reception of an incoming digital signal.
- noise or any other corruption affects an incoming digital signal such as a packet, the corrupted packet will typically be dropped and may need to be retransmitted by the source network device.
- Error detection is the process of detecting bit errors within a signal.
- a parity bit is appended to a block of data for the purpose of identifying whether the bits arrived at the destination device successfully. For example, with a single parity check, before the bits are sent, the “one” bits are counted and if the total of “one” bits is even, the parity bit is set to “one” so that the total number of “one” bits transmitted will form an odd number. If the total number of “one” bits is already an odd number, the parity bit remains or is set to “zero”.
- each group of incoming bits is checked to determine if the number of “ones” in the group totals to an odd number. If the total is an even number, a transmission error has occurred and the transmission is typically retried.
- a logic circuit which includes an interface and an error detection unit.
- the interface is configured to receive and transmit a data stream, wherein the data stream includes at least one of a variable length format packet or burst and a fixed length format packet or burst.
- the error detection unit is configured to detect an error detection code when a misalignment occurs within the data stream by reursively calculating parity terms.
- a method of error detection within a logic circuit includes a step of interfacing a first device having a first transfer rate with a second device having a second transfer rate.
- the method also includes the steps of receiving a data stream, detecting an error detection code error within the data stream; and recursively calculating parity terms.
- a system having a logic circuit which includes an interface means and an error detection means.
- the interface means is for receiving and transmitting a data stream, wherein the data stream includes at least one of a variable length format packet or burst and a fixed length format packet or burst.
- the error detection means is for detecting an error detection code error by recursively calculating a parity term.
- FIG. 1 is a block diagram of a network device according to an embodiment of the invention.
- FIG. 2 is a block diagram of a chip boundary according to an embodiment of the invention.
- FIGS. 3A–3B illustrate the timing relationship between an internal bus and an external bus according to an embodiment of the invention
- FIG. 4 illustrates canalization according to an embodiment of the invention
- FIGS. 5A–5B illustrate examples of data streams that may be transmitted to a logic device according to the invention
- FIGS. 6A–6C illustrate examples of control words that may be inserted within a data stream according to an embodiment of the invention
- FIG. 7 depicts an exemplary range over which parity bits within a data stream may be computed according to an embodiment of the invention
- FIG. 8 is a block diagram of error detection according to an embodiment of the invention.
- FIGS. 9A–9B illustrate the detection of a parity DIP4 code word according to an embodiment of the invention
- FIG. 10 shows a bit map builder according to an embodiment of the invention.
- FIG. 11 is an example of an application of a bit map according to an embodiment of the invention.
- the invention is directed to a method and apparatus for a distributed parity bit checker and generator.
- the invention is also directed to a bit error detection method and apparatus to detect errors within a misaligned data stream and to locate a parity DIP4 code word for a misaligned data stream.
- system 100 may include an interface between an external device 102 and an internal device 105 , which may be a SPI-4 (System Packet Interface Level 4 Phase 2: OC-192 System Interface for Physical and Link Layer Devices) interface.
- SPI-4 may be an interface for packet and cell transfer between a physical layer (PHY) device and a link layer device, for aggregate bandwidths of OC-192 ATM and Packet over SONET/SDH (POS), as well as 10 Gb/s Ethernet applications.
- PHY physical layer
- POS Packet over SONET/SDH
- the SPI-4 interface may operate at a speed ranging from 622 MHz to 800 MHz.
- the components of internal device 105 may be an ASIC (Application-Specific Integrated Circuit).
- the clock rate may be half of the data rate (311 MHz 400 MHz) as shown in FIG. 1 .
- the processing operation within internal device 105 may not be able to achieve the clock speed of the external device. Therefore, a circuit designer may increase the width of the internal data bus, which serves as a common pathway or channel between the internal and external device, to compensate for the clock speed.
- the internal bus width is expanded to be four times the width of the external bus size.
- the invention provides a method and apparatus so that external device 102 may interface with the internal device 105 so that both devices are capable of operating in a synchronized and coordinated manner.
- internal device 105 includes an analog circuit 110 to synchronize the internal and external device.
- FIG. 1 depicts the interface signals on the receiving side of internal device 105 .
- the receive interface signals for internal device 105 may include a clock signal (RCLK), a control signal (RCTL) and a data signal (RDAT).
- RCLK may be a clock signal associated with transmitting data signals and control signals between a PHY device and a link layer device. The data and control lines may be driven off the rising and falling edges of the clock signal.
- RDAT may carry the payload data and the control word from the PHY to the link layer device.
- RCTL In mapping the incoming signals, RCTL may be configured so that it is set to a high level when a control word is present in RDAT. Otherwise, RCTL may be set to a low level.
- FIG. 2 provides a further detailed illustration of the interface at internal device 105 , which may be a chip.
- Analog circuit 110 may include a phase locked loop (PLL) 125 and shift registers 130 .
- PLL phase locked loop
- RDAT which is a 16-bit data signal
- RCTL which is a 1-bits control signal
- FIGS. 2–3 illustrate how the external 16-bit bus data received by chip 110 may be converted into 64-bit bus data.
- PLL 125 or some other frequency multiplication circuit may be used to generate the clock signals for the internal device 105 .
- the internal and external devices In order for the internal and external devices to synchronously communicate with each other, they need to have the correct cycle time relationship between their respective clocks and the clocks on the devices that they are communicating to.
- FIGS. 3A–3B show the timing relationship between the internal and external devices.
- analog circuit 110 includes a demultiplexer 145 which directs the incoming bits of one clock cycle of the data stream from the external device to one of several registers 130 a–d . For example, in FIG.
- 3A demultiplexer 145 directs the incoming data and control signals so that 16 bits of data signal RDAT and a 1-bit control signal RCTL for each clock cycle are directed to a respective one of four shift register 130 a–d .
- PLL 125 may lock onto the external clock signal RCLK and generate a clock signal for shift registers 130 a–d and latch 135 which will synchronize the internal and external devices.
- Shift registers 130 a–d may receive an input from PLL 125 so that the shift registers 130 a–d are clocked by a 2XRCLK clock signal transmitted from PLL 125 .
- the 2XRCLK clock signal shifts each set of 16-bit data signals and 1-bit control signal into and out of shift registers 130 a–d .
- the clock signal 2XRCLK transmitted from PLL 125 may be set to at least twice the frequency of the clock, RCLK, of external device 102 .
- Each set of 17bits (which includes the 16-bit data signal and the 1-bit control signal) from shift registers 130 a–d are then transmitted to a latch circuit 135 .
- Another clock signal RXCLK may be transmitted by PLL 125 to latch circuit 135 to achieve synchronization of the external and internal device's clock signals.
- the speed of RXCLK may be set equal to half of the speed of the external clock RCLK.
- the output of the latch 135 is a 4-bit control signal and a 64-bit data signal, which are synchronized with the input data from external device 102 .
- FIG. 3B illustrates a timing diagram of the mapping of the 16bits of the RDAT from external device to the 64 bits of RXDAT in the internal device.
- the external device timing diagram 170 shows the receipt of the 16-bit data at internal device 105 .
- the invention accumulates the data (D 0 , D 1 , D 2 , D 3 ) from the previous four cycles (C 0 , C 1 , C 2 , C 3 ) and outputs this grouping of data as the 64-bit data signal RXDAT (63:0) from latch 135 for the C 4 clock period as shown in FIG. 3A .
- the invention accumulates the data (D 4 , D 5 , D 6 , D 7 ) and outputs this grouping of 64-bit data as RXDAT for the C 8 cycle in the internal device timing diagram 175 .
- the invention also maps the control signal from external device 102 to internal device 105 .
- the mapping of the control signal, RXCTL, which corresponds to the C 4 clock period is shown by the term 'b0011, which represent four bit fields.
- the four bit fields indicate the level of control signal RCTL during cycles C 1 , C 2 , C 3 , and C 4 in the external device timing diagram 170 .
- RCTL may be a high level when a control word is present, and a low level otherwise.
- the RCTL signal level for cycle C 0 and C 1 corresponds to “0”
- the RCTL signal level for the C 2 and C 3 cycles are “1”. Therefore, the control signal from the external device to internal device maps to a representation of the binary number 'b0011 as shown in the internal timing diagram 175 .
- the 4-bit control signals and the 64-bit data signals are converted to a digital signal using an analog-to-digital converter (not shown), which may be a component of analog circuit 110 .
- an analog-to-digital converter (not shown), which may be a component of analog circuit 110 .
- the digital signal is applied to input registers 700 , as shown in FIG. 1 .
- analog device 110 may select and retrieve one or more groups of data from one of several input channels (not shown) of internal device 105 and interleave the selected groups into a 64-bit grouping. Canalization occurs when data that belongs to different channels are transmitted in an interleaved manner. Canalization may be supported in an embodiment of the invention that employs a SPI-4 interface. An example of canalization, which is discussed below, is shown in FIG. 4 .
- the invention may be designed to receive several types of input, for example, as shown in TABLE I.
- the binary information is transferred into internal device 105 as a data stream 200 having minimum and maximum length as determined by a particular application.
- FIG. 5A provides an illustration of variable-length format packets, mapped onto cell payloads of the data stream.
- cell payloads carrying complete packets or shorter bursts may be transferred in data stream 200 .
- Control words may be inserted between the burst or packet transfers. These control words contain the error control coding, also referred to as the parity bits.
- the parity bits may inform internal device 105 if an error has occurred. Once an error is detected, the destination device may request a retransmission of the corrupted data from the source device.
- the control word may be an idle control word, payload control and/or training control word.
- the control words shown in FIG. 5A are payload control words that may separate two adjacent burst or packet transfers, and the control words may contain the status information pertaining to the previous transfer and the following transfer. Once a transfer has begun, data words may be sent uninterrupted until the end-of-packet (EOP) or a multiple of a predetermined number of 16 bytes is reached. The system may be designed so that the cell payload is a multiple of 16 bytes.
- the interval between the end of a given transfer and the next payload control word, which may mark the start of another transfer or start-of-packet (SOP), may consist of zero or idle control words and/or training patterns.
- the gap between shorter packets may be filled with idle control words.
- the control word may be appended to the end of a burst.
- each packet may be divided into multiples of 16 bytes, with the possible exception of the end-of-the packet data.
- the end-of-the packet data may be of any length, with an integer number of bytes.
- FIG. 6A describes some of the fields that may be included in the control word.
- FIG. 6B shows a list of sample control word types.
- FIG. 6C shows examples of valid control words.
- Analog device 110 may select the input of the incoming data stream from the input channels (not shown) so that the input may be arranged in the pipeline as shown in FIG. 4 . In mapping the data input as shown in FIG.
- the term “dij” may be used, where the symbol “d” represents a “data” input, the symbol “i” represents the channel number and the symbol “j” represents the “jth” 16-bit data belonging to channel “i.”
- “d 15 ” in the column of cycle c 2 may be read as the 5 th data bit transmitted from channel 1 .
- a payload control word PC and channel 1 data are being transmitted.
- cycle C 2 only channel 1 data is being transmitted.
- cycle C 4 only channel 2 data is being transmitted.
- cycle C 5 channel 1 data (1 a ), channel 2 data (d 24 ) and two payload control words (PC) are being transmitted.
- cycle C 5 the end of the packet for channel 1 data is provided, and channel 2 data begins to be transmitted.
- cycle C 6 channel 2 data, an idle control word (IC) and a payload control word (PC) are being transmitted.
- cycle C 6 this is the end of the packet for channel 2 data, and channel 3 data begins in cycle c 7 .
- cycles C 7 and C 8 only channel 3 data is being transmitted.
- cycle C 9 only idle control words (IC) are being transmitted.
- cycle C 5 where data that belongs to both channel 1 and channel 2 is being transmitted, there is a chance that data misalignment may occur due to the fact that cycle C 5 includes the end of the packet for channel 1 , which may be a variable-length formet packet, and the end of the packet for channel 1 is followed by a payload control word PC. Due to the data misalignment, which may be caused by the variable-length formet packets, a problem may also arise in locating the parity bits and detecting whether an error has occurred within the data stream.
- the invention provides a method and apparatus for generating a parity DIP4 code word and for detecting whether an error has occurred during a data stream transmission to a destination device although data misalignment may have occurred within the data stream.
- FIG. 7 depicts an example of the range over which the DIP4 parity bits within data stream 200 may be computed. The invention may be employed in locating DIP4 parity.
- FIG. 8 depicts a block diagram of a system and method for detecting errors within a data stream according to an embodiment of the invention.
- the 4-bit control signal, RXCTL, and the 64-bit data signal, RXDAT are applied to input registers 700 .
- Input registers 700 latch the 4-bit control signals and the 64-bit data signals within the incoming data stream.
- Input registers 700 may divide the 64 bits of the data signal, for example, into four groupings as a, b, c, and d. Each of the outputs a, b, c, and d constitutes a 16-bit grouping having a relationship as defined in TABLE II below:
- inputs a, b, c, and d may be received by input registers 700 and then transmitted to logic operations module 710 .
- the logic operations module 710 may perform several logic operations on the incoming 64 bits to reduce the 64 bits into a smaller, more manageable array of intermediate parity terms, which will require less mathematical computations to complete the parity check summing than the original 64 bits input.
- the logic operations performed by logic operation module 710 may be performed on any size data stream. Thus, the number and size of the rows calculated and arranged by logic operations module 710 may be determined based upon detection capabilities of the particular application.
- the invention may include a central processing unit or a processor (both not shown) to perform the mathematical computations, control instructions and provide timings signals and implement other operations.
- Logic operations module 710 may include one or more exclusive-or (XOR) logic circuits 712 .
- XOR circuit 712 may use inputs a, b, c, and d to recursively calculate a term using a diagonal interleaved parity (DIP4) technique as shown in FIGS. 9A–9B .
- DIP4 diagonal interleaved parity
- FIG. 9A the generation of, for example, an odd parity DIP4 code word may be calculated using the (DIP4) technique.
- the 64 bits that have been grouped as a, b, c, and d of the incoming data stream may be arranged so that the first word of input “d” received is positioned in the bottom row of the matrix and the last word of input “a” is at the top of the matrix.
- the DIP4 code may be generated by summing diagonally along the dashed lines to generate a 16-bit parity sum.
- each bit of the 16-bit parity sum is the result of an XOR operation along the corresponding dashed lines.
- the XOR operation is indicated in the tables of this discussion by an “ ⁇ ” symbol.
- the 16-bits parity sum may be represented as r-vector, r(15:0).
- the 64-bit data signal is defined according to r(15:0) as illustrated in TABLE III below.
- the first 16-bit checksum may be split into two bytes, which are added to each other modulo-2 to produce an 8-bit checksum.
- modulo describes the maximum number of states for the counter performing the addition of the 8-bit checksum.
- the 8-bit checksum may then be divided into two 4-bit nibbles. A nibble is a sequence of 4-bits that is operated upon as a unit. The two 4-bit nibbles are added bitwise to the modulo-2 to produce the DIP4 code, as defined in TABLE IV below and shown in FIG. 9A .
- DIP4(3) r(15) ⁇ circumflex over ( ) ⁇ r(11) ⁇ circumflex over ( ) ⁇ r(7) ⁇ circumflex over ( ) ⁇ r(3)
- DIP4(2) r(14) ⁇ circumflex over ( ) ⁇ r(10) ⁇ circumflex over ( ) ⁇ r(6) ⁇ circumflex over ( ) ⁇ r(2)
- DIP4(1) r(13) ⁇ circumflex over ( ) ⁇ r(9) ⁇ circumflex over ( ) ⁇ r(5) ⁇ circumflex over ( ) ⁇ r(1)
- DIP4(0) r(12) ⁇ circumflex over ( ) ⁇ r(8) ⁇ circumflex over ( ) ⁇ r(4) ⁇ circumflex over ( ) ⁇ r(0)
- Logic operations module 710 may calculate each DIP4(i) by performing XOR operations using XOR circuits 712 .
- the DIP4(3) may be determined by performing an XOR operation on the vectors of the r(15), r(11), r(7) and r(3).
- the respective terms for determining r(15), r(11), r(7) and r(3) are shown in TABLE III.
- r(15) equals the XOR operation of d(15), c(0), b(1), and a(2).
- r(11) equals the XOR operation of d(11), c(12), b(13), and a(14).
- the terms r(7) and r(3) can be selected and XOR-ed in a similar manner.
- the state of the previously calculated parity bits may be latched or retained to aid in the calculation of the next parity bits (NDIP).
- the calculation of the NDIP bits is an iterative process.
- each parity bit may be used as feedback into the subsequent calculation of the next parity bit in an iterative routine.
- Intermediate parity bit terms may be generated as a flag to determine whether the PDIP will be used in performing the calculation of the subsequent NDIP, as discussed below with regards to logic operations module 740 .
- the invention may generate intermediate parity in accordance with a matrix key.
- logic operation module 710 may generate intermediate parity in accordance with a corresponding matrix key, which includes four rows of bits (labeled as 1, 2, 3,) and four columns as shown in TABLE V(a).
- the four rows of bits in Column 1 may be numbered from 3, 2, 1, 0 wherein 3 is positioned at the top right hand-column and 0 is positioned in the last row of the first column.
- the four rows of bits may be arranged such that the numbers are shifted vertically by one bit in comparison to the bits in column 1 .
- the rows of bits in column 2 are arranged vertically as 0, 3, 2, and 1.
- logic operations module 710 may then re-label the columns in TABLE V(a) to include vectors A, B, C, and D as shown in TABLE V(b).
- Column 1 which includes the bits arranged as 3, 2, 1, 0, in TABLE V(a) may be relabeled as D column, which includes D 3 , D 2 , D 1 , D 0 , respectively.
- the remaining columns may be relabeled as C column, B column, and A column, respectively.
- Logic operations module 710 may now use the “D,” “C,” “B,” and “A”—column groupings shown in TABLE V(b) to calculate the DIP(i) terms in TABLE IV.
- row 1 of TABLE VI may be set to equal DIP4(3).
- DIP4(3) now equals the XOR operation of D 3 ⁇ C 0 ⁇ B 1 ⁇ A 2 .
- DIP4(2), DIP4(1) and DIP4(0) can be calculated in a similar manner by logic operations module 710 .
- Logic operations module 710 may then substitute and combine the terms of TABLE III, IV, and VI to generate the matrix key, shown in TABLE VII.
- the system may use the matrix key in TABLE VII to select the relevant bits for each DIP4(i) term.
- the DIP4(i) code for the original 64-bit data signal can be expressed according to the equations shown in TABLE VIII below.
- the D 3 term of DIP4(3), in TABLE VII equals the XOR operation of d(15), d(11), d(7) and d(3) as shown in TABLE VIII.
- the A1 term of DIP4(2) equals the XOR operation of a(1), a(3), a(9) and a(5) as shown in TABLE VIII.
- TABLE VII illustrates that the original 64-bits data input have been reduced to a smaller, more manageable array having sixteen indices.
- the P-terms listed in TABLE VII can be assigned as the PDIP in determining whether the current DIP4 terms will be used in performing the calculation of the subsequent NDIP.
- the DIP4(i) calculation generated by XOR circuits 712 renders sixteen variables, A 0 , A 1 , A 2 , A 3 , B 0 , B 1 , B 2 , B 3 , C 0 , C 1 , C 2 , C 3 , D 0 , D 1 , D 2 , and D 3 .
- A3 a(15) ⁇ circumflex over ( ) ⁇ a(11) ⁇ circumflex over ( ) ⁇ a(7) ⁇ circumflex over ( ) ⁇ a(3)
- A2 a(14) ⁇ circumflex over ( ) ⁇ a(10) ⁇ circumflex over ( ) ⁇ a(6) ⁇ circumflex over ( ) ⁇ a(2)
- A1 a(13) ⁇ circumflex over ( ) ⁇ a(9) ⁇ circumflex over ( ) ⁇ a(5) ⁇ circumflex over ( ) ⁇ a(1)
- A0 a(12) ⁇ circumflex over ( ) ⁇ a(8) ⁇ circumflex over ( ) ⁇ a(4) ⁇ circumflex over ( ) ⁇ a(0)
- B3 b(15) ⁇ circumflex over ( ) ⁇ b(11) ⁇ circumflex over ( ) ⁇ b(7) ⁇ circumflex over ( ) ⁇ b(3)
- B2 b(14) ⁇ circumflex over ( ) ⁇ b(10) ⁇ circ
- D-flop 715 also includes a PDIP register (not shown), which holds the PDIP information, which is discussed below.
- FIG. 9B illustrates another example of an embodiment of the invention where internal device 105 receives two 64-bit input data, which may be noted as (a, b, c, d) and (a′, b′, c′, d′).
- the two 64-bits inputs in FIG. 9B may be generated using the same procedures discussed regarding FIG. 9A .
- logic operations module 710 and XOR circuit 712 may generate TABLE IX, which corresponds to TABLE III.
- TABLE X may be generated using the procedures discussed regarding TABLE IV
- TABLE XI may be generated using the procedures discussed regarding TABLE VII.
- DIP4(3) D′(3) ⁇ circumflex over ( ) ⁇ C′(0) ⁇ circumflex over ( ) ⁇ B′(1) ⁇ circumflex over ( ) ⁇ A′(2) ⁇ circumflex over ( ) ⁇ D(3) ⁇ circumflex over ( ) ⁇ C(0) ⁇ circumflex over ( ) ⁇ B(1) ⁇ circumflex over ( ) ⁇ A(2)
- DIP4(2) D′(2) ⁇ circumflex over ( ) ⁇ C′(3) ⁇ circumflex over ( ) ⁇ B′(0) ⁇ circumflex over ( ) ⁇ A′(1) ⁇ circumflex over ( ) ⁇ D(2) ⁇ circumflex over ( ) ⁇ C(3) ⁇ circumflex over ( ) ⁇ B(0) ⁇ circumflex over ( ) ⁇ A(1)
- DIP4(1) D′(1) ⁇ circumflex over ( ) ⁇ C′(2) ⁇ circumflex over ( ) ⁇ B′(3) ⁇ circumflex over ( ) ⁇ A′(0) ⁇ circumflex over ( ) ⁇ D(1)
- P(3), P(2), P(1), P(0) shown in TABLE XII may be set as a recursive term of the DIP4 codeword P(3:0) of the previous 64-bits input data determined in TABLE VII.
- DIP4(3) D′(3) ⁇ circumflex over ( ) ⁇ C′(0) ⁇ circumflex over ( ) ⁇ B′(1) ⁇ circumflex over ( ) ⁇ A′(2) ⁇ circumflex over ( ) ⁇ P(3)
- DIP4(2) D′(2) ⁇ circumflex over ( ) ⁇ C′(3) ⁇ circumflex over ( ) ⁇ B′(0) ⁇ circumflex over ( ) ⁇ A′(1) ⁇ circumflex over ( ) ⁇ P(2)
- DIP4(1) D′(1) ⁇ circumflex over ( ) ⁇ C′(2) ⁇ circumflex over ( ) ⁇ B′(3) ⁇ circumflex over ( ) ⁇ A′(0) ⁇ circumflex over ( ) ⁇ P(1)
- DIP4(0) D′(0) ⁇ circumflex over ( ) ⁇ C′(1) ⁇ circumflex over ( ) ⁇ B′(2) ⁇ circumflex over ( ) ⁇ A′(3) ⁇ circumflex over ( ) ⁇ P(0)
- input registers 700 ( FIGS. 1–3 and 8 ) outputs bits of the 64-bits data signal, RXDAT(63:0), and the 4-bits control signal, RXCTL(3:0), to a decoder 720 .
- Decoder 720 may be used to determine the type of information that is being transmitted within the data stream.
- One reason that the invention checks to determine the classification of the type of information that is being received into internal device 105 is because based upon the determination of whether the incoming information is either data or a control words, the invention will know whether or not to check that portion of the data stream in order to locate the DIP4 parity bits within the data stream.
- FIG. 10 indicates that when data is the current input, the invention may be configured so that this portion of the data stream is not inspected for DIP4 parity bits since the parity bits are included in the control words and not within the data input.
- the invention may, for example, transfer the portion of the 4-bits control signal after the control signal has been transferred through input registers 700 . After the control signal passes through input registers 700 , the control signal may be referred to as the latched portion q(3:0).
- Input registers 700 latch the 64-bits data signal and the 4-bits control signal as shown below in TABLE XIII:
- decoder 720 may decode the latched portion q(3:0) and every 16 th bit of the 64-bits data signal as shown in TABLE XIV below. This invention is not limited to only this bit identification technique. Other bit identification techniques may be employed by the invention.
- Decoder 720 inspects the RXCTL produced in the internal device timing determine the type of information contained within the incoming data stream.
- Decoder 720 decodes the RXCTLW and RDAT(15) to determine whether the information transmitted within each 16-bits grouping of a, b, c, d is data, an idle control word (IC), a training control word (TCW) or a payload control word (PLCW).
- IC idle control word
- TCW training control word
- PLCW payload control word
- Decoder 720 may use TABLE XIV to determine the type of information being transmitted within the data stream. For example, if the binary number in the control word RXCTL data field is set equal “0” and the 16 th bit RXDAT(15) is set to a “1”, then decoder 720 will determine that the information is “data.” As another example, if the binary number in the control word RXCTL data field is set equal to “1” and the RXDAT is also set equal to “1” based upon TABLE XV above, decoder 720 will determine that the information is a “PLCW.”
- the system may perform this operation on each 16-bit group.
- the invention may perform this operation, for example, four times to generate a decode(i) output, which is transferred from decoder 720 to a bit map builder 730 .
- the decode(i) information shown in TABLE XIV above may be used as the input to generate a bit map 730 , as shown in FIG. 8 .
- the bit map builder 730 may include two terms, a check enable bit and a mask bit.
- the check enable term may be used by the system to indicate in which position of the data stream the system will check for the parity bits, DIP4(i).
- the check enable bit may indicate to the system to check the DIP4(i) at a 16-bit location within the 64-bit data signal.
- the mask of the bit map assists the system in determining whether the previous parity bit, PDIP, will be used to calculate the next parity bit, NDIP. If the mask term is set equal to “1”, this may indicate that the incoming data stream is the beginning of a new data burst. If the mask term is set equal to “0”, this may indicate that data stream is still transmitting in a data burst phase.
- logic operations module 740 may use the mask term, and the 16-variables transferred from D-flop 715 to calculate an intermediate terms DIP4_ERR(i) and to determine what terms will be used to calculate NPID.
- the intermediate term DIP4_ERR may or may not be used in the calculation of NPID.
- the determination of whether either the intermediate terms DIP4_ERR(i) or the 16-variable input will be used to calculate NDIP may depend upon a bit map decision calculation performed by logic operations module 740 .
- logic operations module 740 performs a bit map decision as shown in FIG. 11 .
- the logic operations module 740 performs a bit map decision on a(15:0).
- the logic operations module 740 determines if the mask for a(15:0) equals “0.” If the mask equals “0”, then the NDIP4 may be calculated using PDIP4. If the mask equals “1”, the logic operations module 740 may not use PDIP4 in the calculation of NDIP4.
- the DIP4_ERR(0) calculation may be performed using the logic operation of (P 3 , P 2 , P 1 , P 0 ,) ⁇ (A 3 , A 2 , A 1 , A 0 ).
- the operation of (P 3 , P 2 , P 1 , P 0 ) ⁇ (A 3 , A 2 , A 1 , A 0 ) is read as the bits of P 3 , P 2 , P 1 , and P 0 are XORed with the bits of A 3 , A 2 , A 1 , A 0 .
- PDIP may be set equal to “0.”
- the mask equals “1”
- the DIP4_ERR(0) calculation is performed using the terms (A 3 , A 2 , A 1 , A 0 ).
- the check enable bit may be flagged as “0” and the mask may be set to equal “0” as shown in FIG. 10 . Since the mask equals “0”, then the logic operation of (P 3 , P 2 , P 1 , P 0 ,) ⁇ (A 3 , A 2 , A 1 , A 0 ) may be used to generate an output of (PA 3 , PA 2 , PA 1 , PA 0 ). A NAND operation may be performed on (PA 3 , PA 2 , PA 1 , PA 0 ), and the resultant is latched into a register (not shown) as DIP4_ERR(0). Since a(15:0) contains “data,” the mask term and check enable term may be set to indicate that a DIP4 parity bit check will not be performed on this 16-bit portion of the data stream.
- logic operations module 740 may inspect the 16-bits of b(15:0), which include “data.” Therefore, the check enable may be set equal to “0” and, the mask data field of b(15:0) may be set equal to “0.” Since the mask equals “0,” logic operations module 740 may select the logic operation of (PA 0 , PA 3 , PA 2 , PA 1 ) ⁇ (B 3 , B 2 , B 1 , B 0 ).
- the logic operation of (PA 0 , PA 3 , PA 2 , PA) ⁇ (B 3 , B 2 , B 1 , B 0 ) may generate an output of (PB 3 , PB 2 , PB 1 , PB 0 ).
- a NAND operation is performed on (PB 3 , PB 2 , PB 1 , PB 0 ), and the output is latched into a register (not shown) as DIP4_ERR(1).
- the map bit rules of FIG. 10 may be applied to c(15:0).
- the decoder 720 may determine the type of information which was stored in the previous 16-bits.
- the previous 16-bits was b(15:0), which contained “data.” Since the previous 16-bits, b(15:0), contained “data” and the current input is a “control word,” the bit map rules of FIG.
- logic operations module 740 may select (PB 0 , PB 3 , PB 2 , PB) ⁇ (C 3 , C 2 , C 1 , C 0 ) to generate the DIP4_ERR(2) calculation.
- the logic operation of (PB 0 , PB 3 , PB 2 , PB 1 ) ⁇ (C 3 , C 2 , C 1 , C 0 ) produces an output of (PC 3 , PC 2 , PC 1 , PC 0 ).
- Logic operations module 740 then performs a NAND operation on (PC 3 , PC 2 , PC 1 , PC 0 ) and latches the output into DIP4_ERR(2).
- d(15:0) contains a control word.
- the system may apply the bit map rules of FIG. 10 . Therefore, the logic operations module 740 may examine the previous 16-bits to determine the type of input. In this example, the previous 16-bits was c(15:0), which contain a “control word.”
- the rules of FIG. 10 serve as a key to instruct the program to set the check enable to equal “1” and the mask term equal to “1” since the previous input is “not data” and the current input includes a “control word.” Based upon the mask term of the bit map, the program may then perform the bit map decision.
- the system may select (D 3 , D 2 , D 1 , D 0 ) to generate the DIP4_ERR 3 .
- the terms of (D 3 , D 2 , D 1 , D 0 ) may also be set as NDIP4 (P 3 , P 2 , P 1 , P 0 ).
- the NDIP may be calculated, in this example, using the new input terms of D 3 , D 2 , D 1 and D 0 terms from the 16-variables transferred from D-flop 715 .
- Logic operations module 740 then sets (D 3 , D 2 , D 1 , D 0 ) equal to (P 3 , P 2 , P 1 , P 0 ).
- Logic operations module 740 inputs (P 3 , P 2 , P 1 , P 0 ) as a feedback into D-flop 715 , as shown in FIG. 8 . Then, the reiterative process of calculating NDIP may begin again.
- the DIP4_ERR(i) from logic operations module 740 may be transmitted through a D-flop 750 to a DIP4 error checker 760 . If the DIP4_ERR calculation performed by logic operations module 740 indicates that one of the 16-bit data includes a DIP4 error, DIP4 error checker 760 may generate a final DIP4_ERR.
- the invention may be configured so that DIP4 error checker 760 may check for an error only at the end of a payload data burst or individual control word (Idle control word or Training control word).
- the chk_en(i) transferred from the bit map builder 730 to DIP4 error checker 760 may function to indicate the 16-bit grouping within the data stream to check for an error.
- the following logic equation (Eq. 1) may be used to generate the final DIP4_ERR.
- Final DIP4_ERR DIP4_ERR(i) ⁇ chk_en(i) Eq. 1
- the final DIP4_ERR may be checked as follows: For example, in FIG. 4 , in cycle C 1 , only one DIP-4 codeword may be checked because there is only one payload control word (PC) in cycle C 1 .
- the DIP4 error checker 760 may not perform a DIP4 error check in cycles C 2 , C 4 , C 7 and C 8 , since these cycles only contain data.
- DIP4 error checker 760 may check for one DIP-4 codeword because there is only one payload control word (PC) included in cycle C 3 .
- DIP4 error checker 760 may check for two DIP-4 code words since cycle C 5 contains two payload control words (PC).
- DIP4 error checker 760 will also check for two control words in cycle C 6 since cycle C 6 includes an idle control word (IC) and a payload control word (PC). In cycle C 9 , DIP4 error checker 760 will check for four DIP-4 code words since cycle C 9 contains four idle control words (IC).
- the invention provides a method and apparatus for locating parity bits and determining whether an error has occurred within a misaligned data stream.
- the parity checker according to the invention may be used in the 16-bits data path of an interface of a SPI-4 chip.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Physics & Mathematics (AREA)
- Probability & Statistics with Applications (AREA)
- Theoretical Computer Science (AREA)
- Detection And Prevention Of Errors In Transmission (AREA)
- Error Detection And Correction (AREA)
- Dc Digital Transmission (AREA)
- Detection And Correction Of Errors (AREA)
Abstract
Description
TABLE I | |||
CW | control word | ||
PCLW | payload control word | ||
IC | Idle control word | ||
TCW | training control word | ||
Data word | control bit is inactivated | ||
TDW | training data word | ||
Data | payload data | ||
TABLE II | ||
a=RXDAT(63:48) | ||
b=RXDAT(47:32) | ||
c=RXDAT(31:16) | ||
d=RXDAT(15:0) | ||
TABLE III | ||||||
r(15) = | d(15) | {circumflex over ( )}c(0) | {circumflex over ( )}b(1) | {circumflex over ( )}a(2) | ||
r(14) = | d(14) | {circumflex over ( )}c(15) | {circumflex over ( )}b(0) | {circumflex over ( )}a(1) | ||
r(13) = | d(13) | {circumflex over ( )}c(14) | {circumflex over ( )}b(15) | {circumflex over ( )}a(0) | ||
r(12) = | d(12) | {circumflex over ( )}c(13) | {circumflex over ( )}b(14) | {circumflex over ( )}a(15) | ||
r(11) = | d(11) | {circumflex over ( )}c(12) | {circumflex over ( )}b(13) | {circumflex over ( )}a(14) | ||
r(10) = | d(10) | {circumflex over ( )}c(11) | {circumflex over ( )}b(12) | {circumflex over ( )}a(13) | ||
r(9) = | d(9) | {circumflex over ( )}c(10) | {circumflex over ( )}b(11) | {circumflex over ( )}a(12) | ||
r(8) = | d(8) | {circumflex over ( )}c(9) | {circumflex over ( )}b(10) | {circumflex over ( )}a(11) | ||
r(7) = | d(7) | {circumflex over ( )}c(8) | {circumflex over ( )}b(9) | {circumflex over ( )}a(10) | ||
r(6) = | d(6) | {circumflex over ( )}c(7) | {circumflex over ( )}b(8) | {circumflex over ( )}a(9) | ||
r(5) = | d(5) | {circumflex over ( )}c(6) | {circumflex over ( )}b(7) | {circumflex over ( )}a(8) | ||
r(4) = | d(4) | {circumflex over ( )}c(5) | {circumflex over ( )}b(6) | {circumflex over ( )}a(7) | ||
r(3) = | d(3) | {circumflex over ( )}c(4) | {circumflex over ( )}b(5) | {circumflex over ( )}a(6) | ||
r(2) = | d(2) | {circumflex over ( )}c(3) | {circumflex over ( )}b(4) | {circumflex over ( )}a(5) | ||
r(1) = | d(1) | {circumflex over ( )}c(2) | {circumflex over ( )}b(3) | {circumflex over ( )}a(4) | ||
r(0) = | d(0) | {circumflex over ( )}c(1) | {circumflex over ( )}b(2) | {circumflex over ( )}a(3) | ||
TABLE IV | ||||||
DIP4(3) = | r(15){circumflex over ( )} | r(11){circumflex over ( )} | r(7){circumflex over ( )} | r(3) | ||
DIP4(2) = | r(14){circumflex over ( )} | r(10){circumflex over ( )} | r(6){circumflex over ( )} | r(2) | ||
DIP4(1) = | r(13){circumflex over ( )} | r(9){circumflex over ( )} | r(5){circumflex over ( )} | r(1) | ||
DIP4(0) = | r(12){circumflex over ( )} | r(8){circumflex over ( )} | r(4){circumflex over ( )} | r(0) | ||
TABLE V(a) | |||||
|
|
|
|
||
3 | 0 | 1 | 2 | ||
2 | 3 | 0 | 1 | ||
1 | 2 | 3 | 0 | ||
0 | 1 | 2 | 3 | ||
TABLE V(b) | |||||
D column | C column | B column | A column | ||
D3 | C0 | B1 | A2 | ||
D2 | C3 | B0 | A1 | ||
D1 | C2 | B3 | A0 | ||
D0 | C1 | B2 | A3 | ||
TABLE VI | |||||
D column | C column | B column | A column | ||
DIP4(3) = | D3{circumflex over ( )} | C0{circumflex over ( )} | B1{circumflex over ( )} | A2 |
DIP4(2) = | D2{circumflex over ( )} | C3{circumflex over ( )} | B0{circumflex over ( )} | A1 |
DIP4(1) = | D1{circumflex over ( )} | C2{circumflex over ( )} | B3{circumflex over ( )} | A0 |
DIP4(0) = | D0{circumflex over ( )} | C1{circumflex over ( )} | B2{circumflex over ( )} | A3 |
TABLE VII | ||||||
P column | D column | C column | B column | A column | ||
dip4(3) = | = P(3) = | D3 {circumflex over ( )} | C0 {circumflex over ( )} | B1 {circumflex over ( )} | A2 |
dip4(2) = | = P(2) = | D2 {circumflex over ( )} | C3 {circumflex over ( )} | B0 {circumflex over ( )} | A1 |
dip4(1) = | = P(1) = | D1 {circumflex over ( )} | C2 {circumflex over ( )} | B3 {circumflex over ( )} | A0 |
dip4(0) = | = P(0) = | D0 {circumflex over ( )} | C1 {circumflex over ( )} | B2 {circumflex over ( )} | A3 |
TABLE VIII | ||||||
A3 = | a(15) | {circumflex over ( )}a(11) | {circumflex over ( )}a(7) | {circumflex over ( )}a(3) | ||
A2 = | a(14) | {circumflex over ( )}a(10) | {circumflex over ( )}a(6) | {circumflex over ( )}a(2) | ||
A1 = | a(13) | {circumflex over ( )}a(9) | {circumflex over ( )}a(5) | {circumflex over ( )}a(1) | ||
A0 = | a(12) | {circumflex over ( )}a(8) | {circumflex over ( )}a(4) | {circumflex over ( )}a(0) | ||
B3 = | b(15) | {circumflex over ( )}b(11) | {circumflex over ( )}b(7) | {circumflex over ( )}b(3) | ||
B2 = | b(14) | {circumflex over ( )}b(10) | {circumflex over ( )}b(6) | {circumflex over ( )}b(2) | ||
B1 = | b(13) | {circumflex over ( )}b(9) | {circumflex over ( )}b(5) | {circumflex over ( )}b(1) | ||
B0 = | b(12) | {circumflex over ( )}b(8) | {circumflex over ( )}b(4) | {circumflex over ( )}b(0) | ||
C3 = | c(15) | {circumflex over ( )}c(11) | {circumflex over ( )}c(7) | {circumflex over ( )}c(3) | ||
C2 = | c(14) | {circumflex over ( )}c(10) | {circumflex over ( )}c(6) | {circumflex over ( )}c(2) | ||
C1 = | c(13) | {circumflex over ( )}c(9) | {circumflex over ( )}c(5) | {circumflex over ( )}c(1) | ||
C0 = | c(12) | {circumflex over ( )}c(8) | {circumflex over ( )}c(4) | {circumflex over ( )}c(0) | ||
D3 = | d(15) | {circumflex over ( )}d(11) | {circumflex over ( )}d(7) | {circumflex over ( )}d(3) | ||
D2 = | d(14) | {circumflex over ( )}d(10) | {circumflex over ( )}d(6) | {circumflex over ( )}d(2) | ||
D1 = | d(13) | {circumflex over ( )}d(9) | {circumflex over ( )}d(5) | {circumflex over ( )}d(1) | ||
D0 = | d(12) | {circumflex over ( )}d(8) | {circumflex over ( )}d(4) | {circumflex over ( )}d(0) | ||
TABLE IX | ||||||||
r(15) = | d′(15) | {circumflex over ( )}c′(0) | {circumflex over ( )}b′(1) | {circumflex over ( )}a′(2) | {circumflex over ( )}d(3) | {circumflex over ( )}c(4) | {circumflex over ( )}b(5) | {circumflex over ( )}a(6) |
r(14) = | d′(14) | {circumflex over ( )}c′(15) | {circumflex over ( )}b′(0) | {circumflex over ( )}a′(1) | {circumflex over ( )}d(2) | {circumflex over ( )}c(3) | {circumflex over ( )}b(4) | {circumflex over ( )}a(5) |
r(13) = | d′(13) | {circumflex over ( )}c′(14) | {circumflex over ( )}b′(15) | {circumflex over ( )}a′(0) | {circumflex over ( )}d(1) | {circumflex over ( )}c(2) | {circumflex over ( )}b(3) | {circumflex over ( )}a(4) |
r(12) = | d′(12) | {circumflex over ( )}c′(13) | {circumflex over ( )}b′(14) | {circumflex over ( )}a′(15) | {circumflex over ( )}d(0) | {circumflex over ( )}c(1) | {circumflex over ( )}b(2) | {circumflex over ( )}a(3) |
r(11) = | d′(11) | {circumflex over ( )}c′(12) | {circumflex over ( )}b′(13) | {circumflex over ( )}a′(14) | {circumflex over ( )}d(15) | {circumflex over ( )}c(0) | {circumflex over ( )}b(1) | {circumflex over ( )}a(2) |
r(10) = | d′(10) | {circumflex over ( )}c′(11) | {circumflex over ( )}b′(12) | {circumflex over ( )}a′(13) | {circumflex over ( )}d(14) | {circumflex over ( )}c(15) | {circumflex over ( )}b(0) | {circumflex over ( )}a(1) |
r(9) = | d′(9) | {circumflex over ( )}c′(10) | {circumflex over ( )}b′(11) | {circumflex over ( )}a′(12) | {circumflex over ( )}d(13) | {circumflex over ( )}c(14) | {circumflex over ( )}b(15) | {circumflex over ( )}a(0) |
r(8) = | d′(8) | {circumflex over ( )}c′(9) | {circumflex over ( )}b′(10) | {circumflex over ( )}a′(11) | {circumflex over ( )}d(12) | {circumflex over ( )}c(13) | {circumflex over ( )}b(14) | {circumflex over ( )}a(15) |
r(7) = | d′(7) | {circumflex over ( )}c′(8) | {circumflex over ( )}b′(9) | {circumflex over ( )}a′(10) | {circumflex over ( )}d(11) | {circumflex over ( )}c(12) | {circumflex over ( )}b(13) | {circumflex over ( )}a(14) |
r(6) = | d′(6) | {circumflex over ( )}c′(7) | {circumflex over ( )}b′(8) | {circumflex over ( )}a′(9) | {circumflex over ( )}d(10) | {circumflex over ( )}c(11) | {circumflex over ( )}b(12) | {circumflex over ( )}a(13) |
r(5) = | d′(5) | {circumflex over ( )}c′(6) | {circumflex over ( )}b′(7) | {circumflex over ( )}a′(8) | {circumflex over ( )}d(9) | {circumflex over ( )}c(10) | {circumflex over ( )}b(11) | {circumflex over ( )}a(12) |
r(4) = | d′(4) | {circumflex over ( )}c′(5) | {circumflex over ( )}b′(6) | {circumflex over ( )}a′(7) | {circumflex over ( )}d(8) | {circumflex over ( )}c(9) | {circumflex over ( )}b(10) | {circumflex over ( )}a(11) |
r(3) = | d′(3) | {circumflex over ( )}c′(4) | {circumflex over ( )}b′(5) | {circumflex over ( )}a′(6) | {circumflex over ( )}d(7) | {circumflex over ( )}c(8) | {circumflex over ( )}b(9) | {circumflex over ( )}a(10) |
r(2) = | d′(2) | {circumflex over ( )}c′(3) | {circumflex over ( )}b′(4) | {circumflex over ( )}a′(5) | {circumflex over ( )}d(6) | {circumflex over ( )}c(7) | {circumflex over ( )}b(8) | {circumflex over ( )}a(9) |
r(1) = | d′(1) | {circumflex over ( )}c′(2) | {circumflex over ( )}b′(3) | {circumflex over ( )}a′(4) | {circumflex over ( )}d(5) | {circumflex over ( )}c(6) | {circumflex over ( )}b(7) | {circumflex over ( )}a(8) |
r(0) = | d′(0) | {circumflex over ( )}c′(1) | {circumflex over ( )}b′(2) | {circumflex over ( )}a′(3) | {circumflex over ( )}d(4) | {circumflex over ( )}d(5) | {circumflex over ( )}c(6) | {circumflex over ( )}a(7) |
TABLE X | |||||
DIP4(3) | = | r(15) | {circumflex over ( )}r(11) | {circumflex over ( )}r(7) | {circumflex over ( )}r(3) |
= | d′(15) | {circumflex over ( )}d′(11) | {circumflex over ( )}d′(7) | {circumflex over ( )}d′(3) | |
{circumflex over ( )}c′(12) | {circumflex over ( )}c′(8) | {circumflex over ( )}c′(4) | {circumflex over ( )}c′(0) | ||
{circumflex over ( )}b′(1) | {circumflex over ( )}b′(13) | {circumflex over ( )}b′(9) | {circumflex over ( )}b′(5) | ||
{circumflex over ( )}a′(14) | {circumflex over ( )}a′(10) | {circumflex over ( )}a′(6) | {circumflex over ( )}a′(2) | ||
{circumflex over ( )}d(3) | {circumflex over ( )}d(4) | {circumflex over ( )}d(11) | {circumflex over ( )}d(15) | ||
{circumflex over ( )}c(4) | {circumflex over ( )}c(8) | {circumflex over ( )}c(12) | {circumflex over ( )}c(16) | ||
{circumflex over ( )}b(5) | {circumflex over ( )}b(9) | {circumflex over ( )}b(13) | {circumflex over ( )}b(1) | ||
{circumflex over ( )}a(6) | {circumflex over ( )}a(10) | {circumflex over ( )}a(14) | {circumflex over ( )}a(2) | ||
DIP4(2) | = | r(14) | {circumflex over ( )}r(10) | {circumflex over ( )}r(6) | {circumflex over ( )}r(2) |
= | d′(14) | {circumflex over ( )}d′(10) | {circumflex over ( )}d′(6) | {circumflex over ( )}d′(2) | |
{circumflex over ( )}c′(15) | {circumflex over ( )}c′(11) | {circumflex over ( )}c′(7) | {circumflex over ( )}c′(3) | ||
{circumflex over ( )}b′(0) | {circumflex over ( )}b′(4) | {circumflex over ( )}b′(8) | {circumflex over ( )}b′(12) | ||
{circumflex over ( )}a′(1) | {circumflex over ( )}a′(5) | {circumflex over ( )}a′(9) | {circumflex over ( )}a′(13) | ||
{circumflex over ( )}d(2) | {circumflex over ( )}d(6) | {circumflex over ( )}d(10) | {circumflex over ( )}d(14) | ||
{circumflex over ( )}c(3) | {circumflex over ( )}c(7) | {circumflex over ( )}c(11) | {circumflex over ( )}c(15) | ||
{circumflex over ( )}b(4) | {circumflex over ( )}b(8) | {circumflex over ( )}b(12) | {circumflex over ( )}b(0) | ||
{circumflex over ( )}a(5) | {circumflex over ( )}a(9) | {circumflex over ( )}a(13) | {circumflex over ( )}a(1) | ||
DIP4(1) | = | r(13) | {circumflex over ( )}r(9) | {circumflex over ( )}r(5) | {circumflex over ( )}r(1) |
= | d′(13) | {circumflex over ( )}d′(9) | {circumflex over ( )}d′(5) | {circumflex over ( )}d′(1) | |
{circumflex over ( )}c′(14) | {circumflex over ( )}c′(10) | {circumflex over ( )}c′(6) | {circumflex over ( )}c′(2) | ||
{circumflex over ( )}b′(15) | {circumflex over ( )}b′(11) | {circumflex over ( )}b′(7) | {circumflex over ( )}b′(3) | ||
{circumflex over ( )}a′(0) | {circumflex over ( )}a′(4) | {circumflex over ( )}a′(8) | {circumflex over ( )}a′(12) | ||
{circumflex over ( )}d(1) | {circumflex over ( )}d(5) | {circumflex over ( )}d(9) | {circumflex over ( )}d(13) | ||
{circumflex over ( )}c(2) | {circumflex over ( )}c(6) | {circumflex over ( )}c(10) | {circumflex over ( )}c(14) | ||
{circumflex over ( )}b(3) | {circumflex over ( )}b(7) | {circumflex over ( )}b(11) | {circumflex over ( )}b(15) | ||
{circumflex over ( )}a(4) | {circumflex over ( )}a(8) | {circumflex over ( )}a(12) | {circumflex over ( )}a(0) | ||
DIP4(0) | = | r(12) | {circumflex over ( )}r(8) | {circumflex over ( )}r(4) | {circumflex over ( )}r(0) |
= | d′(12) | {circumflex over ( )}d′(8) | {circumflex over ( )}d′(4) | {circumflex over ( )}d′(0) | |
{circumflex over ( )}c′(13) | {circumflex over ( )}c′(9) | {circumflex over ( )}c′(5) | {circumflex over ( )}c′(1) | ||
{circumflex over ( )}b′(14) | {circumflex over ( )}b′(10) | {circumflex over ( )}b′(6) | {circumflex over ( )}b′(2) | ||
{circumflex over ( )}a′(15) | {circumflex over ( )}a′(11) | {circumflex over ( )}a′(7) | {circumflex over ( )}a(3) | ||
{circumflex over ( )}d(12) | {circumflex over ( )}d(8) | {circumflex over ( )}d(4) | {circumflex over ( )}d(0) | ||
{circumflex over ( )}c(13) | {circumflex over ( )}c(9) | {circumflex over ( )}c(5) | {circumflex over ( )}c(1) | ||
{circumflex over ( )}b(14) | {circumflex over ( )}b(10) | {circumflex over ( )}b(6) | {circumflex over ( )}b(2) | ||
{circumflex over ( )}a(15) | {circumflex over ( )}a(11) | {circumflex over ( )}a(7) | {circumflex over ( )}a(3) | ||
TABLE XI | |||||||||
DIP4(3) | = | D′(3) | {circumflex over ( )}C′(0) | {circumflex over ( )}B′(1) | {circumflex over ( )}A′(2) | {circumflex over ( )}D(3) | {circumflex over ( )}C(0) | {circumflex over ( )}B(1) | {circumflex over ( )}A(2) |
DIP4(2) | = | D′(2) | {circumflex over ( )}C′(3) | {circumflex over ( )}B′(0) | {circumflex over ( )}A′(1) | {circumflex over ( )}D(2) | {circumflex over ( )}C(3) | {circumflex over ( )}B(0) | {circumflex over ( )}A(1) |
DIP4(1) | = | D′(1) | {circumflex over ( )}C′(2) | {circumflex over ( )}B′(3) | {circumflex over ( )}A′(0) | {circumflex over ( )}D(1) | {circumflex over ( )}C(2) | {circumflex over ( )}B(3) | {circumflex over ( )}A(0) |
DIP4(0) | = | D′(0) | {circumflex over ( )}C′(1) | {circumflex over ( )}B′(2) | {circumflex over ( )}A′(3) | {circumflex over ( )}D(0) | {circumflex over ( )}C(1) | {circumflex over ( )}B(2) | {circumflex over ( )}A(3) |
TABLE XII | |||||||
DIP4(3) = | D′(3) | {circumflex over ( )}C′(0) | {circumflex over ( )}B′(1) | {circumflex over ( )}A′(2) | {circumflex over ( )}P(3) | ||
DIP4(2) = | D′(2) | {circumflex over ( )}C′(3) | {circumflex over ( )}B′(0) | {circumflex over ( )}A′(1) | {circumflex over ( )}P(2) | ||
DIP4(1) = | D′(1) | {circumflex over ( )}C′(2) | {circumflex over ( )}B′(3) | {circumflex over ( )}A′(0) | {circumflex over ( )}P(1) | ||
DIP4(0) = | D′(0) | {circumflex over ( )}C′(1) | {circumflex over ( )}B′(2) | {circumflex over ( )}A′(3) | {circumflex over ( )}P(0) | ||
TABLE XIII | |
a= | RXDAT(63:48) |
b= | RXDAT(47:32) |
c= | RXDAT(31:16) |
d= | RXDAT(15:0) |
q(3:0)= | RXCTL(3:0) |
TABLE XIV | ||
Decode (3) = f(RXCTL (3), a(15)) | ||
Decode (2) = f(RXCTL (2), b(15)) | ||
Decode (1) = f(RXCTL (1), c(15)) | ||
Decode (0) = f(RXCTL (0), d(15)) | ||
TABLE XV | ||
RXCTL | RXDAT(15) | Type of |
0 | 0 | |
0 | 1 | |
1 | 0 | IC or |
1 | 1 | PLCW |
Final DIP4_ERR=DIP4_ERR(i)^chk_en(i) Eq. 1
Claims (20)
P(3)=D(3)^C(0)^B(1)^A(2)
P(2)=D(2)^C(3)^B(0)^A(1)
P(1)=D(1)^C(2)^B(3)^A(0)
P(0)=D(0)^C(1)^B(2)^A(3)
P(3)=D(3)^C(0)^B(1)^A(2)
P(2)=D(2)^C(3)^B(0)^A(1)
P(1)=D(1)^C(2)^B(3)^A(0)
P(0)=D(0)^C(1)^B(2)^A(3)
P(3)=D(3)^C(0)^B(1)^A(2)
P(2)=D(2)^C(3)^B(0)^A(1)
P(1)=D(1)^C(2)^B(3)^A(0)
P(0)=D(0)^C(1)^B(2)^A(3)
Priority Applications (3)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US10/234,165 US7058881B2 (en) | 2002-03-15 | 2002-09-05 | Distributed 4-bits diagonal interleaved parity (DIP4) checker |
EP03005935A EP1345122B1 (en) | 2002-03-15 | 2003-03-17 | A distributed 4-bits diagonal interleaved parity (DIP4) checker |
DE60301420T DE60301420T2 (en) | 2002-03-15 | 2003-03-17 | Distributed 4-bit diagonal nested parity checker (DIP4) |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US36405102P | 2002-03-15 | 2002-03-15 | |
US10/234,165 US7058881B2 (en) | 2002-03-15 | 2002-09-05 | Distributed 4-bits diagonal interleaved parity (DIP4) checker |
Publications (2)
Publication Number | Publication Date |
---|---|
US20030182613A1 US20030182613A1 (en) | 2003-09-25 |
US7058881B2 true US7058881B2 (en) | 2006-06-06 |
Family
ID=27767492
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US10/234,165 Expired - Fee Related US7058881B2 (en) | 2002-03-15 | 2002-09-05 | Distributed 4-bits diagonal interleaved parity (DIP4) checker |
Country Status (3)
Country | Link |
---|---|
US (1) | US7058881B2 (en) |
EP (1) | EP1345122B1 (en) |
DE (1) | DE60301420T2 (en) |
Cited By (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20050245194A1 (en) * | 2004-04-28 | 2005-11-03 | Electrolux Home Products, Inc. | Wireless appliance communication with detection and capture algorithm |
US7191388B1 (en) * | 2004-03-01 | 2007-03-13 | Lattice Semiconductor Corporation | Fast diagonal interleaved parity (DIP) calculator |
Families Citing this family (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6954466B1 (en) * | 2002-03-05 | 2005-10-11 | Modelware, Inc. | Link-layer receiver |
US7533286B2 (en) * | 2005-06-29 | 2009-05-12 | Intel Corporation | Regulating application of clock to control current rush (DI/DT) |
KR100833604B1 (en) | 2007-01-09 | 2008-05-30 | 삼성전자주식회사 | Parity error detecting circuit |
US9559882B2 (en) * | 2014-04-01 | 2017-01-31 | Apple Inc. | Apparatus and methods for flexible provision of control data in large data structures |
Citations (6)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5367544A (en) * | 1989-05-04 | 1994-11-22 | Northern Telecom Limited | Data stream frame synchronisation |
US5479416A (en) | 1993-09-30 | 1995-12-26 | Micron Technology, Inc. | Apparatus and method for error detection and correction in radio frequency identification device |
US5636208A (en) | 1996-04-12 | 1997-06-03 | Bell Communications Research, Inc. | Technique for jointly performing bit synchronization and error detection in a TDM/TDMA system |
US5751745A (en) | 1995-12-11 | 1998-05-12 | International Business Machines Corporation | Memory implemented error detection and correction code with address parity bits |
US5771249A (en) * | 1994-09-02 | 1998-06-23 | Toyo Communication Equipment Co., Ltd. | ATM cell synchronous system |
US5923653A (en) | 1995-04-21 | 1999-07-13 | Tektronix, Inc. | SONET/SDH receiver processor |
Family Cites Families (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP3671595B2 (en) * | 1997-04-01 | 2005-07-13 | 株式会社日立製作所 | Compound computer system and compound I / O system |
US6247103B1 (en) * | 1998-01-06 | 2001-06-12 | International Business Machines Corporation | Host storage management control of outboard data movement using push-pull operations |
US6173374B1 (en) * | 1998-02-11 | 2001-01-09 | Lsi Logic Corporation | System and method for peer-to-peer accelerated I/O shipping between host bus adapters in clustered computer network |
US6697367B1 (en) * | 2000-06-12 | 2004-02-24 | Emc Corporation | Multihop system calls |
-
2002
- 2002-09-05 US US10/234,165 patent/US7058881B2/en not_active Expired - Fee Related
-
2003
- 2003-03-17 DE DE60301420T patent/DE60301420T2/en not_active Expired - Lifetime
- 2003-03-17 EP EP03005935A patent/EP1345122B1/en not_active Expired - Lifetime
Patent Citations (6)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5367544A (en) * | 1989-05-04 | 1994-11-22 | Northern Telecom Limited | Data stream frame synchronisation |
US5479416A (en) | 1993-09-30 | 1995-12-26 | Micron Technology, Inc. | Apparatus and method for error detection and correction in radio frequency identification device |
US5771249A (en) * | 1994-09-02 | 1998-06-23 | Toyo Communication Equipment Co., Ltd. | ATM cell synchronous system |
US5923653A (en) | 1995-04-21 | 1999-07-13 | Tektronix, Inc. | SONET/SDH receiver processor |
US5751745A (en) | 1995-12-11 | 1998-05-12 | International Business Machines Corporation | Memory implemented error detection and correction code with address parity bits |
US5636208A (en) | 1996-04-12 | 1997-06-03 | Bell Communications Research, Inc. | Technique for jointly performing bit synchronization and error detection in a TDM/TDMA system |
Non-Patent Citations (1)
Title |
---|
"Pos-Phy Level 4, A Saturn Packet and Cell Interface Specification for OC192 Sonet/SDH and 10 Gigabit Ethernet", Interface Specification, PMC-Sierra, Inc., Nr. 6, pp. 1-49, XP002247175, Feb. 2001. |
Cited By (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US7191388B1 (en) * | 2004-03-01 | 2007-03-13 | Lattice Semiconductor Corporation | Fast diagonal interleaved parity (DIP) calculator |
US7430706B1 (en) | 2004-03-01 | 2008-09-30 | Lattice Semiconductor Corporation | Diagonal interleaved parity calculator |
US20050245194A1 (en) * | 2004-04-28 | 2005-11-03 | Electrolux Home Products, Inc. | Wireless appliance communication with detection and capture algorithm |
US7392044B2 (en) * | 2004-04-28 | 2008-06-24 | Electrolux Home Products, Inc. | Wireless appliance communication with detection and capture algorithm |
Also Published As
Publication number | Publication date |
---|---|
DE60301420T2 (en) | 2006-06-29 |
EP1345122B1 (en) | 2005-08-31 |
EP1345122A3 (en) | 2004-03-10 |
DE60301420D1 (en) | 2005-10-06 |
EP1345122A2 (en) | 2003-09-17 |
US20030182613A1 (en) | 2003-09-25 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US4809273A (en) | Device for verifying operation of a checking code generator | |
EP0950300B1 (en) | Secondary channel using code violations | |
US6119263A (en) | System and method for transmitting data | |
JPH09507118A (en) | Cyclic redundancy check method and apparatus | |
US5204859A (en) | Method and apparatus for detecting a frame alignment word in a data system | |
JPH04284753A (en) | Crc arithmetic method and hec synchronization device in atm exchange system | |
CN101529775A (en) | Forward error correction encoding for multiple link transmission compatible with 64b/66b scrambling | |
WO1998034413A2 (en) | Data encoder/decoder for a high speed serial link | |
US6732317B1 (en) | Apparatus and method for applying multiple CRC generators to CRC calculation | |
JP4071879B2 (en) | Error detector, communication system including the error detector, and error detection method | |
US7103822B2 (en) | Method and apparatus for computing ‘N-bit at a time’ CRC's of data frames of lengths not multiple of N | |
US7058881B2 (en) | Distributed 4-bits diagonal interleaved parity (DIP4) checker | |
US20050257113A1 (en) | Cyclic redundancy check circuit for use with self-synchronous scramblers | |
US6748567B1 (en) | Method and system for error correction over serial link | |
US7895499B2 (en) | Method and apparatus for checking pipelined parallel cyclic redundancy | |
AU611820B2 (en) | Method and apparatus for transmitting and receiving characters using a balanced weight error correcting code | |
US20030233609A1 (en) | Parallel error checking for multiple packets | |
US11804855B2 (en) | Pipelined forward error correction for vector signaling code channel | |
US7047479B1 (en) | Parallel CRC formulation | |
JPH02248120A (en) | Coder/decoder system for errar connection of digital transmitter | |
KR20020033227A (en) | Circuit for parallel cyclic redundancy check in data communication | |
TWI795901B (en) | Serial link system with an embedded test function | |
US7970962B2 (en) | Method and apparatus utilizing a tail bus to solve back-to-back data burst problems | |
US6981206B1 (en) | Method and apparatus for generating parity values | |
Hammons | CRC-based techniques for combined burst synchronization and error detection in TDMA PCS systems |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: BROADCOM CORPORATION, CALIFORNIA Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:CHU, NGOK YING;REEL/FRAME:013264/0342 Effective date: 20020830 |
|
FEPP | Fee payment procedure |
Free format text: PAYOR NUMBER ASSIGNED (ORIGINAL EVENT CODE: ASPN); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY |
|
FPAY | Fee payment |
Year of fee payment: 4 |
|
FPAY | Fee payment |
Year of fee payment: 8 |
|
AS | Assignment |
Owner name: BANK OF AMERICA, N.A., AS COLLATERAL AGENT, NORTH CAROLINA Free format text: PATENT SECURITY AGREEMENT;ASSIGNOR:BROADCOM CORPORATION;REEL/FRAME:037806/0001 Effective date: 20160201 Owner name: BANK OF AMERICA, N.A., AS COLLATERAL AGENT, NORTH Free format text: PATENT SECURITY AGREEMENT;ASSIGNOR:BROADCOM CORPORATION;REEL/FRAME:037806/0001 Effective date: 20160201 |
|
AS | Assignment |
Owner name: AVAGO TECHNOLOGIES GENERAL IP (SINGAPORE) PTE. LTD., SINGAPORE Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:BROADCOM CORPORATION;REEL/FRAME:041706/0001 Effective date: 20170120 Owner name: AVAGO TECHNOLOGIES GENERAL IP (SINGAPORE) PTE. LTD Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:BROADCOM CORPORATION;REEL/FRAME:041706/0001 Effective date: 20170120 |
|
AS | Assignment |
Owner name: BROADCOM CORPORATION, CALIFORNIA Free format text: TERMINATION AND RELEASE OF SECURITY INTEREST IN PATENTS;ASSIGNOR:BANK OF AMERICA, N.A., AS COLLATERAL AGENT;REEL/FRAME:041712/0001 Effective date: 20170119 |
|
FEPP | Fee payment procedure |
Free format text: MAINTENANCE FEE REMINDER MAILED (ORIGINAL EVENT CODE: REM.) |
|
LAPS | Lapse for failure to pay maintenance fees |
Free format text: PATENT EXPIRED FOR FAILURE TO PAY MAINTENANCE FEES (ORIGINAL EVENT CODE: EXP.) |
|
STCH | Information on status: patent discontinuation |
Free format text: PATENT EXPIRED DUE TO NONPAYMENT OF MAINTENANCE FEES UNDER 37 CFR 1.362 |
|
FP | Lapsed due to failure to pay maintenance fee |
Effective date: 20180606 |
|
AS | Assignment |
Owner name: AVAGO TECHNOLOGIES INTERNATIONAL SALES PTE. LIMITE Free format text: MERGER;ASSIGNOR:AVAGO TECHNOLOGIES GENERAL IP (SINGAPORE) PTE. LTD.;REEL/FRAME:047642/0417 Effective date: 20180509 |
|
AS | Assignment |
Owner name: AVAGO TECHNOLOGIES INTERNATIONAL SALES PTE. LIMITE Free format text: CORRECTIVE ASSIGNMENT TO CORRECT THE EXECUTION DATE OF THE MERGER PREVIOUSLY RECORDED ON REEL 047642 FRAME 0417. ASSIGNOR(S) HEREBY CONFIRMS THE ASSIGNMENT,;ASSIGNOR:AVAGO TECHNOLOGIES GENERAL IP (SINGAPORE) PTE. LTD.;REEL/FRAME:048521/0395 Effective date: 20180905 |