SCAS891A February 2010 – May 2025 CDCE949-Q1
PRODUCTION DATA
The device supports Byte Write and Byte Read and Block Write and Block Read operations.
For Byte Write/Read operations, the system controller can individually access addressed bytes.
For Block Write/Read operations, the bytes are accessed in sequential order from lowest to highest byte (with most significant bit first) with the ability to stop after any complete byte has been transferred. The number of bytes read out is defined by the Byte Count field in the Generic Configuration Register. During a Block Read instruction, the entire number of bytes defined in Byte Count must be read out to correctly finish the read cycle.
When a byte is sent to the device, the byte is written into the internal register and immediately takes effect. This applies to each transferred byte, whether in a Byte Write or a Block Write sequence.
If the EEPROM write cycle is initiated, the internal registers are written into the EEPROM. Data can be read out during the programming sequence (Byte Read or Block Read). The programming status can be monitored by EEPIP, Byte 01–Bit [6]. Before beginning EEPROM programming, pull CLKIN LOW. CLKIN must be held LOW for the duration of EEPROM programming. After initiating EEPROM programming with EEWRITE, Byte 06–Bit [0], do not write to the device registers until EEPIP is read back as a 0.
The offset of the indexed byte is encoded in the command code, as described in Table 7-6.
| Device | A6 | A5 | A4 | A3 | A2 | A1(1) | A0(1) | R/ W |
|---|---|---|---|---|---|---|---|---|
| CDCE913/CDCEL913 | 1 | 1 | 0 | 0 | 1 | 0 | 1 | 1/0 |
| CDCE925/CDCEL925 | 1 | 1 | 0 | 0 | 1 | 0 | 0 | 1/0 |
| CDCE937/CDCEL937 | 1 | 1 | 0 | 1 | 1 | 0 | 1 | 1/0 |
| CDCE949 | 1 | 1 | 0 | 1 | 1 | 0 | 0 | 1/0 |
| BIT | DESCRIPTION |
|---|---|
| 7 | 0 = Block Read or Block Write operation 1 = Byte Read or Byte Write operation |
| (6:0) | Byte Offset for Byte Read, Block Read, Byte Write and Block Write operation. |