
Philips Semiconductors
Product Specification Rev. 3.0; May 2003
Multiple Protocol Contactless Reader IC
CL RC632
131
Confidential
18.6.1.3 Timing Diagram
The following diagram shows programming of 5 bytes into the E2PROM:
Explanation: It is assumed, that the CL RC632 finds and reads Byte 0 before the μ-Processor is able to write
Byte 1 (t
prog,del
= 300 ns). This causes the CL RC632 to start the programming cycle, which needs about
t
prog
= 5.8 ms. In the meantime the μ-Processor stores Byte 1 to Byte 4 to the FIFO buffer. Assuming, that the
E2PROM starting byte-address is e.g. 16C
hex
then Byte 0 is stored exactly there. The CL RC632 copies the
following data bytes into the E2PROM input buffer. Copying Byte 3, it detects, that this data byte has to be
programmed at the E2PROM byte-address 16F
hex
. Since this is the end of the memory block, the CL RC632
automatically starts a programming cycle. In the next turn, Byte 4 will be programmed at the E2PROM byte-
address 170
hex
. Since this is the last data byte, the flags (
E2Ready
and
TxIRq
) that indicate the end of the
E2PROM programming activity will be set.
Although all data has been programmed into the E2PROM, the CL RC632 stays in the
WriteE2-Command
.
Writing further data to the FIFO would lead to further E2PROM programming, continuing at the E2PROM
byte-address 171
hex
. The command is stopped using the
Idle-Command
.
18.6.1.4 Error Flags for the WriteE2 Command
Programming is inhibited for the E2PROM blocks 0 (E2PROM’s byte-address 00
hex
to 0F
hex
). Programming to
these addresses sets the flag
AccessErr
. No programming cycle is started. Addresses above 1FF
hex
are
taken modulo 200
hex
(for the E2PROM memory organisation, refer to chapter 6.).
NWrite
Data
WriteE2
command active
E2PROM
Programming
E2Ready
TxIRq
Write
E2
Adr
LSB
Adr
MSB
Byte0
Byte1
Byte2
Byte3
Byte4
Programming Byte0
Programming Byte1, Byte2, and Byte3
Programming Byte4
t
prog
t
prog
t
prog
t
prg,del
Idle
Cmd
Figure 18-7: Timing Diagram for E2PROM programming