CYNSE10512A-133FGC Cypress Semiconductor Corp, CYNSE10512A-133FGC Datasheet - Page 20

• Manufacturer Part Number: CYNSE10512A-133FGC
• Manufacturer: Cypress Semiconductor Corp

Specifications of CYNSE10512A-133FGC

• Operating Supply Voltage (typ): 1.2V
• Operating Temp Range: 0C to 70C
• Operating Temperature Classification: Commercial
• Mounting: Surface Mount
• Lead Free Status / RoHS Status: Not Compliant

Document #: 38-02110 Rev. *B
Core Parity
The Core includes a one-bit parity for each 72-bit entry in the data and mask arrays. When writing into the data or mask array,
the NSE will calculate and generate the one-bit parity for each 72-bit data. Each block also has a block-associated internal register
to enable the parity checking for the block (BPAR). When disabled, the block will ignore the Read Parity command.
To issue the Read Parity command, the ASIC issues a Read command and sets the Parity field in the parameters sent through
the DQ bus as described in Table 5-28. Core parity checking is performed in parallel on four adjacent 72-bit entries per pair of
blocks. At the beginning of each parity operation, an internal address counter is incremented. The new incremented address is
then used for the parity check operation.
It will cycle through the data and mask arrays as well as odd and even blocks for both arrays for each Read Parity issued. If one
or more parity errors are detected, the error is reported in the block’s BPAR register. Then all errors are prioritized through an
arbiter to select the highest priority parity error, which is then reported in the PARITY register. PARERR_L will also be set to 0
when there is a parity error. PARERR_L is valid on the (5+TLSZ)
the command is issued at Cycle1, PARERR_L will be valid on Cycle8. Read Parity also responds to broadcast CHIPID selection.
Figure 5-5 shows the timing diagram of a Core Parity error during a Read Parity instruction. The PARERR_L signal goes Low
five cycles after the error is detected.
There are two basic flows for parity error recovery. The first flow is by reading the highest priority parity error address stored in
the PARITY register, fix the error, decrement the internal address counter and reissue Read Parity. The second flow is by reading
the PARITY register to obtain the location, reading the BPAR registers to locate blocks that has the error and then fixing those
locations.
CMD[10:2]
PARERR_L
CMD[1:0]
Even DQ
Odd DQ
PAR[0]
PHS_L
CLK2X
CMDV
PAR[1]
bits
bits
Odd
Even
cycle
A
1
288-bit SEARCH
Figure 5-4. Timing Diagram of a DQ Bus Parity Error (288-bit Search, TLSZ=10)
Even
Odd
B
T
cycle
Odd
Odd
A
2
Odd
T+1
Even
B
cycle
CONFIDENTIAL
3
incorrect value for PAR[1]
T+2
cycle
4
T+3
cycle
5
T+4
th
cycle of latency. For example, with TLSZ = 10 (binary) and
cycle
6
T+5
cycle
7
T+6
cycle
8
CYNSE10512A
CYNSE10256A
CYNSE10128A
cycle
9
Page 20 of 145
cycle
10