X1203
9
Figure 6. Byte Write Sequence
Figure 7. Page Write Sequence
S
t
a
r
t
S
t
o
p
Slave
Address
CCR
Address 1
Data
A
C
K
A
C
K
A
C
K
SDA Bus
Signals from
the Slave
Signals from
the Master
0
A
C
K
CCR
Address 0
1
1
1
1
0
1
1
0 0 0 0 0 0 0 0
CRR
Address 0
S
t
a
r
t
S
t
o
p
Slave
Address
CCR
Address 1
Data
(n)
A
C
K
A
C
K
A
C
K
SDA Bus
Signals from
the Slave
Signals from
the Master
0
Data
(1)
A
C
K
(1
<
n
<
8)
1
1
1
1
0
1
1
0 0 0 0 0 0 0 0
After the receipt of each byte, the X1203 responds
with an acknowledge, and the address is internally
incremented by one. When the counter reaches the
end of the page, it “rolls over” and goes back to the
first address on the same page. If the master supplies
more than 8 bytes of data, then the previously loaded
data is over written by the new data, one byte at a
time. The master terminates the Data Byte loading by
issuing a stop condition, which causes the device to
begin the non volatile write cycle. As with the byte
write operation, all inputs are disabled until completion
of the internal write cycle. Refer to Figure 7 for the
address, acknowledge, and data transfer sequence.
Stops and Write Modes
Stop conditions that terminate write operations must
be sent by the master after sending at least 1 full data
byte and it’s associated ACK signal. If a stop is issued
in the middle of a data byte, or before 1 full data byte +
ACK is sent, then the device will reset itself without
performing the write. The contents of the array will not
be affected.
Acknowledge Polling
The disabling of the inputs during non volatile write
cycles can be used to take advantage of the typical
5mS write cycle time. Once the stop condition is
issued to indicate the end of the master’s byte load
operation, the device initiates the internal non volatile
write cycle. Acknowledge polling can be initiated
immediately. To do this, the master issues a start con-
dition followed by the Slave Address Byte for a write or
read operation. If the device is still busy with the non
volatile write cycle then no ACK will be returned. If the
device has completed the write operation, an ACK will
be returned and the host can then proceed with the
read or write operation. Refer to the flow chart in Figure 8.