RC400 Datasheet
RC400 Datasheet
RC400 Datasheet
I•CODE
SL RC400
I•CODE Reader IC
Philips
Semiconductors
Philips Semiconductors Product Specification Rev. 3.2 December 2005
CONTENTS
2
Philips Semiconductors Product Specification Rev. 3.2 December 2005
3
Philips Semiconductors Product Specification Rev. 3.2 December 2005
14 RECEIVER CIRCUITRY............................................................................................................ 92
14.1 General .................................................................................................................................... 92
14.2 Block Diagram .......................................................................................................................... 92
14.3 Putting the Receiver into Operation ............................................................................................ 93
14.3.1 Automatic Clock-Q Calibration ................................................................................................... 93
14.3.2 Amplifier ................................................................................................................................... 94
14.3.3 Correlation Circuitry ................................................................................................................... 95
14.3.4 Evaluation and Digitizer Circuitry ................................................................................................ 95
4
Philips Semiconductors Product Specification Rev. 3.2 December 2005
5
Philips Semiconductors Product Specification Rev. 3.2 December 2005
6
Philips Semiconductors Product Specification Rev. 3.2 December 2005
1 GENERAL INFORMATION
1.1 Scope
This document describes the functionality of the SL RC400. It includes the functional and electrical
specifications and gives details on how to design-in this device from system and hardware viewpoint.
The SL RC400 is member of a new family of highly integrated reader ICs for contactless communication at
13.56 MHz. This new reader IC family utilises an outstanding modulation and demodulation concept
completely integrated for all kinds of passive contactless communication methods and protocols at
13.56 MHz.
The internal transmitter part is able to drive an antenna designed for proximity operating distance (up to
100 mm) directly without additional active circuitry.
The receiver part provides a robust and efficient implementation of a demodulation and decoding circuitry for
signals from I•CODE1 and ISO 15693 compatible transponders.
The digital part handles I•CODE1 and ISO 15693 framing and error detection (CRC).
A comfortable parallel interface which can be directly connected to any 8-bit µ-Processor gives high flexibility
for the reader/terminal design.
7
Philips Semiconductors Product Specification Rev. 3.2 December 2005
1.3 Features
• Buffered output drivers to connect an antenna with minimum number of external components
• Parallel µ-Processor interface with internal address latch and IRQ line
• Programmable timer
• Independent power supply pins for digital, analog and transmitter part
• Internal oscillator buffer to connect 13.56 MHz quartz, optimised for low phase jitter
Package
Type Number
Name Description
SL RC400 01T SO32 Small Outline Package; 32 leads
8
Philips Semiconductors Product Specification Rev. 3.2 December 2005
2 BLOCK DIAGRAM
Voltage DVDD
Parallel Interface Control
(incl. Automatic Interface Detection & Synchronisation) Monitor
&
Power On DVSS
Detect
FIFO Control State Machine
Reset
Command Register
64 Byte FIFO Control
Power Down
Programable Timer RSTPD
Control
CRC16/CRC8
EEPROM Generation & Check
8 x 16 Byte EEPROM Access
Control
Parallel/Seriell Converter
Bit Counter
Level Shifters
Clock OSCIN
Generation,
Amplitude Oscillator
Filtering and
Rating Distribution OSCOUT
Correlation and Bit Decoding
Reference
Voltage AVDD
Q-Clock Power On
Generation Detect AVSS
I-Channel Q-Channel
Transmitter Control
Amplifier Amplifier
Analog Test
MUX
I-Channel Q-Channel
Demodulator Demodulator
GND
V+
GND
V+
VMID AUX RX
TVSS TX1 TX2 TVDD
9
Philips Semiconductors Product Specification Rev. 3.2 December 2005
3 PINNING INFORMATION
Pins denoted by bold letters are supplied by AVDD and AVSS. Pins drawn with bold lines are supplied by
TVSS and TVDD. All other pins are supplied by DVDD and DVSS.
OSCIN 1 32 OSCOUT
IRQ 2 31 RSTPD
RFU 3 30 VMID
SIGOUT 4 29 RX
TX1 5 28 AVSS
TVDD 6 27 AUX
TX2 7 26 AVDD
TVSS 8 25 DVDD
SL RC400
NCS 9 SO32 24 A2
NWR 10 23 A1
NRD 11 22 A0
DVSS 12 21 ALE
D0 13 20 D7
D1 14 19 D6
D2 15 18 D5
D3 16 17 D4
10
Philips Semiconductors Product Specification Rev. 3.2 December 2005
4 SIGOUT O I•CODE Interface Output: delivers a serial data stream according to I•CODE1 and
ISO 15693
5 TX1 O Transmitter 1: delivers the modulated 13.56 MHz carrier frequenzy
6 TVDD PWR Transmitter Power Supply: supplies the output stage of TX1 and TX2
7 TX2 O Transmitter 2: delivers the modulated 13.56 MHz carrier frequenzy
8 TVSS PWR Transmitter Ground: supplies the output stage of TX1 and TX2
9 NCS I Not Chip Select: selects and activates the µ-Processor interface of the SL RC400
NWR I Not Write: strobe to write data (applied on D0 to D7) into the SL RC400 register
1
10 R/NW I Read Not Write: selects if a read or write cycle shall be performed.
nWrite I Not Write: selects if a read or write cycle shall be performed
NRD I Not Read: strobe to read data from the SL RC400 register (applied on D0 to D7)
111 NDS I Not Data Strobe: strobe for the read and the write cycle
nDStrb I Not Data Strobe: strobe for the read and the write cycle
12 DVSS PWR Digital Ground
13 D0 to D7 I/O 8 Bit Bi-directional Data Bus
…
201 AD0 to AD7 I/O 8 Bit Bi-directional Address and Data Bus
Address Latch Enable: strobe signal to latch AD0 to AD5 into the internal address
ALE I
latch when HIGH.
Address Strobe: strobe signal to latch AD0 to AD5 into the internal address latch
211 AS I when HIGH.
Not Address Strobe: strobe signal to latch AD0 to AD5 into the internal address latch
nAStrb I when LOW.
A0 I Address Line 1: Bit 0 of register address
221 Not Wait: signals with LOW that an access-cycle may started and with HIGH that it
nWait O may be finished.
23 A1 I Address Line 1: Bit 1 of register address
24 A2 I Address Line 2: Bit 2 of register address
25 DVDD PWR Digital Power Supply
26 AVDD PWR Analog Power Supply
1
These pins offer different functionality according to the selected µ-Processor interface type. For detailed information
refer to chapter 4.
11
Philips Semiconductors Product Specification Rev. 3.2 December 2005
12
Philips Semiconductors Product Specification Rev. 3.2 December 2005
4 PARALLEL INTERFACE
The SL RC400 supports direct interfacing of various µ-Processor. Alternatively the Enhanced Parallel Port
(EPP) of personal computers can be connected directly.
The following table shows the parallel interface signals supported by the SL RC400:
Bus Control Signals Bus Separated Address and Data Bus Multiplexed Address and Data Bus
After each Power-On or Hard Reset, the SL RC400 also resets its parallel µ-Processor interface mode and
checks the current µ-Processor interface type.
The SL RC400 identifies the µ-Processor interface by means of the logic levels on the control pins after the
Reset Phase. This is done by a combination of fixed pin connections (see below) and a dedicated
initialisation routine (see 11.4).
13
Philips Semiconductors Product Specification Rev. 3.2 December 2005
Table 4-2: Connection Scheme for Detecting the Parallel Interface Type
SL RC400 SL RC400
Address Address
Address Bus (A3...An)
Decoder NCS Non Multiplexed Address
Decoder NCS
LOW
A2
Address Bus (A0...A2) A0...A2 HIGH
A1
HIGH
A0
14
Philips Semiconductors Product Specification Rev. 3.2 December 2005
SL RC400 SL RC400
Address Address
Address Bus (A3...An)
Decoder
NCS Non Multiplexed Address
Decoder
NCS
LOW
A2
HIGH
Address Bus (A0...A2) A0...A2 A1
LOW
A0
15
Philips Semiconductors Product Specification Rev. 3.2 December 2005
SL RC400
LOW
NCS
HIGH
A2
HIGH
A1
nWait
A0
Read/Write (nWrite)
NWR
Figure 4-3: Connection to µ-Processors with Common Read/Write Strobes and Hand-Shake
After each Power-On or Hard Reset the nWait signal (delivered at pin A0) is high impedance. nWait will be
defined at the first negative edge applied to nAStrb after the Reset Phase.
16
Philips Semiconductors Product Specification Rev. 3.2 December 2005
11 TxControl controls the logical behaviour of the antenna driver pins TX1 and TX2
12 CwConductance selects the conductance of the antenna driver pins TX1 and TX2
selects the conductance of the antenna driver pins TX1 and TX2 during
Control
13 ModConductance
modulation
14 CoderControl Selects the bit coding mode and the framing during transmission
15 ModWidth selects the width of the modulation pulse
16 ModWidthSOF selects the width of the modulation pulse for SOF (I•CODE Fast-Mode)
17 PreSet17 these values shall not be changed
17
Philips Semiconductors Product Specification Rev. 3.2 December 2005
21 RxWait selects the time interval after transmission, before receiver starts
selects the kind and mode of checking the data integrity on the RF-
22 ChannelRedundancy
channel
Redundancy
18
Philips Semiconductors Product Specification Rev. 3.2 December 2005
Bits and flags for different registers behave differently, depending on their functions. In principle bits with
same behaviour are grouped in common registers.
19
Philips Semiconductors Product Specification Rev. 3.2 December 2005
Name: Page Address: 0x00, 0x08, 0x10, 0x18, Reset value: 10000000, 0x80
0x20, 0x28, 0x30, 0x38
7 6 5 4 3 2 1 0
UsePage 0 0 0 0 PageSelect
Select
Access r/w r/w r/w r/w r/w r/w r/w r/w
Rights
20
Philips Semiconductors Product Specification Rev. 3.2 December 2005
21
Philips Semiconductors Product Specification Rev. 3.2 December 2005
7 6 5 4 3 2 1 0
FIFOData
Access dy dy dy dy dy dy dy dy
Rights
22
Philips Semiconductors Product Specification Rev. 3.2 December 2005
7 6 5 4 3 2 1 0
0 ModemState IRq Err HiAlert LoAlert
Access r r r r r r r r
Rights
010 TxData Transmitting data from the FIFO buffer (or redundancy
check bits).
011 TxEOF Transmitting the ‘End Of Frame’ Pattern.
100 GoToRx1 Mean-State passed, when receiver starts.
GoToRx2 Mean-State passed, when receiver finishes.
101 PrepareRx Waiting until the time period selected in the RxWait
Register has expired.
110 AwaitingRx Receiver activated; Awaiting an input signal at pin Rx.
3 IRq This bit shows, if any interrupt source requests attention (with respect to the
setting of the interrupt enable flags in the InterruptEn Register).
2 Err This bit is set to 1, if any error flag in the ErrorFlag Register is set.
1 HiAlert Is set to 1, when the number of bytes stored in the FIFO buffer fulfil the following
equation: HiAlert = (64 − FIFOLength) ≤ WaterLevel
0 LoAlert Is set to 1, when the number of bytes stored in the FIFO buffer fulfil the following
equation: LoAlert = FIFOLength ≤ WaterLevel
23
Philips Semiconductors Product Specification Rev. 3.2 December 2005
7 6 5 4 3 2 1 0
0 FIFOLength
Access
r r r r r r r r
Rights
24
Philips Semiconductors Product Specification Rev. 3.2 December 2005
7 6 5 4 3 2 1 0
TRunning E2Ready CRCReady 0 0 RxLastBits
Access r r r r r r r r
Rights
25
Philips Semiconductors Product Specification Rev. 3.2 December 2005
7 6 5 4 3 2 1 0
SetIEn 0 TimerIEn TxIEn RxIEn IdleIEn HiAlertIEn LoAlertIEn
Access w r/w r/w r/w r/w r/w r/w r/w
Rights
26
Philips Semiconductors Product Specification Rev. 3.2 December 2005
7 6 5 4 3 2 1 0
SetIRq 0 TimerIRq TxIRq RxIRq IdleIRq HiAlertIRq LoAlertIRq
Access w r/w dy dy dy dy dy dy
Rights
27
Philips Semiconductors Product Specification Rev. 3.2 December 2005
7 6 5 4 3 2 1 0
0 0 StandBy PowerDown 0 TStopNow TStartNow FlushFIFO
Access r/w r/w dy dy dy w w w
Rights
28
Philips Semiconductors Product Specification Rev. 3.2 December 2005
Error flags showing the error status of the last executed command.
7 6 5 4 3 2 1 0
0 0 AccessErr FIFOOvfl CRCErr FramingErr 0 CollErr
Access r r r r r r r r
Rights
29
Philips Semiconductors Product Specification Rev. 3.2 December 2005
Bit position of the first bit collision detected on the RF- interface.
Name: CollPos Address: 0x0B Reset value: 00000000, 0x00
7 6 5 4 3 2 1 0
CollPos
Access r r r r r r r r
Rights
30
Philips Semiconductors Product Specification Rev. 3.2 December 2005
7 6 5 4 3 2 1 0
TimerValue
Access r r r r r r r r
Rights
31
Philips Semiconductors Product Specification Rev. 3.2 December 2005
7 6 5 4 3 2 1 0
CRCResultLSB
Access r r r r r r r r
Rights
32
Philips Semiconductors Product Specification Rev. 3.2 December 2005
7 6 5 4 3 2 1 0
CRCResultMSB
Access r r r r r r r r
Rights
7 6 5 4 3 2 1 0
0 RxAlign 0 TxLastBits
Access r/w dy dy dy r/w dy dy dy
Rights
33
Philips Semiconductors Product Specification Rev. 3.2 December 2005
34
Philips Semiconductors Product Specification Rev. 3.2 December 2005
Controls the logical behaviour of the antenna pin TX1 and TX2
7 6 5 4 3 2 1 0
0 ModulatorSource Force100 TX2Inv TX2Cw TX2RFEn TX1RFEn
ASK
Access r/w r/w r/w r/w r/w r/w r/w r/w
Rights
35
Philips Semiconductors Product Specification Rev. 3.2 December 2005
Selects the conductance of the antenna driver pins TX1 and TX2.
7 6 5 4 3 2 1 0
0 0 GsCfgCW
Access r/w r/w r/w r/w r/w r/w r/w r/w
Rights
7 6 5 4 3 2 1 0
0 0 GsCfgMod
Access r/w r/w r/w r/w r/w r/w r/w r/w
Rights
36
Philips Semiconductors Product Specification Rev. 3.2 December 2005
7 6 5 4 3 2 1 0
SendOne 0 CoderRate TxCoding
Pulse
Access r/w r/w r/w r/w r/w r/w r/w r/w
Rights
37
Philips Semiconductors Product Specification Rev. 3.2 December 2005
7 6 5 4 3 2 1 0
ModWidth
Access r/w r/w r/w r/w r/w r/w r/w r/w
Rights
7 6 5 4 3 2 1 0
ModWidthSOF
38
Philips Semiconductors Product Specification Rev. 3.2 December 2005
7 6 5 4 3 2 1 0
0 0 0 0 0 0 0 0
Access r/w r/w r/w r/w r/w r/w r/w r/w
Rights
7 6 5 4 3 2 1 0
SubCPulses 0 1 0 Gain
Access r/w r/w r/w r/w r/w r/w r/w r/w
Rights
39
Philips Semiconductors Product Specification Rev. 3.2 December 2005
1-0 Gain This register defines the receivers signal voltage gain factor:
00: 27 dB
01: 31 dB
10: 38 dB
11: 42 dB
7 6 5 4 3 2 1 0
0 Rx ZeroAfter RxFraming RxInvert 0 0
Multiple Coll
Access r/w r/w r/w r/w r/w r/w r/w r/w
Rights
40
Philips Semiconductors Product Specification Rev. 3.2 December 2005
7 6 5 4 3 2 1 0
BitPhase
Access r/w r/w r/w r/w r/w r/w r/w r/w
Rights
41
Philips Semiconductors Product Specification Rev. 3.2 December 2005
7 6 5 4 3 2 1 0
MinLevel CollLevel
Access r/w r/w r/w r/w r/w r/w r/w r/w
Rights
7 6 5 4 3 2 1 0
0 0 0 0 0 0 0 0
Access r/w r/w r/w r/w r/w r/w r/w r/w
Rights
42
Philips Semiconductors Product Specification Rev. 3.2 December 2005
controls decoder behaviour and defines the input source for the receiver.
7 6 5 4 3 2 1 0
RcvClkSelI RxAutoPD 0 0 0 0 DecoderSource
Access R/w r/w r/w r/w r/w r/w r/w r/w
Rights
43
Philips Semiconductors Product Specification Rev. 3.2 December 2005
controls clock generation for the 90° phase shifted Q-channel clock.
7 6 5 4 3 2 1 0
ClkQ180Deg ClkQCalib 0 ClkQDelay
Access r r/w r/w dy dy dy dy dy
Rights
44
Philips Semiconductors Product Specification Rev. 3.2 December 2005
7 6 5 4 3 2 1 0
RxWait
Access r/w r/w r/w r/w r/w r/w r/w r/w
Rights
45
Philips Semiconductors Product Specification Rev. 3.2 December 2005
Selects kind and mode of checking the data integrity on the RF-channel.
7 6 5 4 3 2 1 0
0 CRCMSB CRC CRC8 RxCRCEn TxCRCEn 0 0
First 3309
Access r/w r/w r/w r/w r/w r/w r/w r/w
Rights
46
Philips Semiconductors Product Specification Rev. 3.2 December 2005
7 6 5 4 3 2 1 0
CRCPresetLSB
Access r/w r/w r/w r/w r/w r/w r/w r/w
Rights
7 6 5 4 3 2 1 0
CRCPresetMSB
Access r/w r/w r/w r/w r/w r/w r/w r/w
Rights
47
Philips Semiconductors Product Specification Rev. 3.2 December 2005
7 6 5 4 3 2 1 0
TimeSlotPeriod
Access r/w r/w r/w r/w r/w r/w r/w r/w
Rights
48
Philips Semiconductors Product Specification Rev. 3.2 December 2005
7 6 5 4 3 2 1 0
0 0 0 TimeSlot 0 SIGOUTSelect
Period
MSB
Access r/w r/w r/w r/w r/w r/w r/w r/w
Rights
49
Philips Semiconductors Product Specification Rev. 3.2 December 2005
7 6 5 4 3 2 1 0
0 0 0 0 0 0 0 0
Access r/w r/w r/w r/w r/w r/w r/w r/w
Rights
7 6 5 4 3 2 1 0
0 0 WaterLevel
Access r/w r/w r/w r/w r/w r/w r/w r/w
Rights
50
Philips Semiconductors Product Specification Rev. 3.2 December 2005
7 6 5 4 3 2 1 0
0 0 TAutoRestart TPreScaler
Access r/w r/w r/w r/w r/w r/w r/w r/w
Rights
51
Philips Semiconductors Product Specification Rev. 3.2 December 2005
7 6 5 4 3 2 1 0
0 0 0 0 TStopRxEnd TStopRxBegin TStartTxEnd TStartTxBegin
Access r/w r/w r/w r/w r/w r/w r/w r/w
Rights
52
Philips Semiconductors Product Specification Rev. 3.2 December 2005
7 6 5 4 3 2 1 0
TReloadValue
Access r/w r/w r/w r/w r/w r/w r/w r/w
Rights
53
Philips Semiconductors Product Specification Rev. 3.2 December 2005
7 6 5 4 3 2 1 0
0 0 0 0 0 0 IRQInv IRQPushPull
Access r/w r/w r/w r/w r/w r/w r/w r/w
Rights
5.2.6.7 PreSet2E
7 6 5 4 3 2 1 0
0 0 0 0 0 0 0 0
Access r/w r/w r/w r/w r/w r/w r/w r/w
Rights
5.2.6.8 Preset2F
7 6 5 4 3 2 1 0
0 0 0 0 0 0 0 0
Access r/w r/w r/w r/w r/w r/w r/w r/w
Rights
54
Philips Semiconductors Product Specification Rev. 3.2 December 2005
Page 6: RFU
Name: RFU Address: 0x31, 0x32, 0x33, 0x34, Reset value:00000000, 0x00
0x35, 0x36, 037
7 6 5 4 3 2 1 0
0 0 0 0 0 0 0 0
Access r/w r/w r/w r/w r/w r/w r/w r/w
Rights
55
Philips Semiconductors Product Specification Rev. 3.2 December 2005
7 6 5 4 3 2 1 0
0 0 0 0 0 0 0 0
Access w w w w w w w w
Rights
Note: These registers are reserved for future use.
56
Philips Semiconductors Product Specification Rev. 3.2 December 2005
7 6 5 4 3 2 1 0
0 0 0 0 TestAnaOutSelect
Access w w w w w w w w
Rights
57
Philips Semiconductors Product Specification Rev. 3.2 December 2005
5.2.7.4 PreSet3B
7 6 5 4 3 2 1 0
0 0 0 0 0 0 0 0
Access w w w w w w w w
Rights
5.2.7.5 PreSet3C
7 6 5 4 3 2 1 0
0 0 0 0 0 0 0 0
Access w w w w w w w w
Rights
58
Philips Semiconductors Product Specification Rev. 3.2 December 2005
7 6 5 4 3 2 1 0
SignalTo TestDigiSignalSel
SIGOUT
Access w w w w w w w w
Rights
7 6 5 4 3 2 1 0
0 0 0 0 0 0 0 0
Access r/w r/w r/w r/w r/w r/w r/w r/w
Rights
Note: These registers are reserved for future use.
59
Philips Semiconductors Product Specification Rev. 3.2 December 2005
Address
Flag(s) Register
Register, Bit Position
AccessErr ErrorFlag 0x0A, bit 5
BitPhase BitPhase 0x1B, bits 7:0
ClkQ180Deg ClockQControl 0x1F, bit 7
ClkQCalib ClockQControl 0x1F, bit 6
ClkQDelay ClockQControl 0x1F, bits 4:0
CollErr ErrorFlag 0x0A, bit 0
CollLevel RxThreshold 0x1C, bits 3:0
CollPos CollPos 0x0B, bits 7:0
Command Command 0x01, bits 5:0
CRC3309 ChannelRedundancy 0x22, bit 5
CRC8 ChannelRedundancy 0x22, bit 4
CRCErr ErrorFlag 0x0A, bit 3
CRCMSBFirst ChannelRedundancy 0x22, bit 6
CRCPresetLSB CRCPresetLSB 0x23, bits 7:0
CRCPresetMSB CRCPresetMSB 0x24, bits 7:0
CRCReady SecondaryStatus 0x05 , bit 5
CRCResultMSB CRCResultMSB 0x0E, bits 7:0
CRCResultLSB CRCResultLSB 0x0D, , bits 7:0
DecoderSource RxControl2 0x1E, bits 1:0
E2Ready SecondaryStatus 0x05, bit 6
Err PrimaryStatus 0x03, bit 2
FIFOData FIFOData 0x02, bits 7:0
FIFOLength FIFOLength 0x04, bits 7:0
FIFOOvfl ErrorFlag 0x0A, bit 4
FlushFIFO Control 0x09, bit 0
FramingErr ErrorFlag 0x0A, bit 2
Gain RxControl1 0x19, bits 1:0
GsCfgCW CWConductance 0x12, bits 5:0
GsCfgMod ModConductance 0x13, bits 5:0
HiAlert PrimaryStatus 0x03, bit 1
HiAlertIEn InterruptEn 0x06, bit 1
HiAlertIRq InterruptRq 0x07, bit 1
60
Philips Semiconductors Product Specification Rev. 3.2 December 2005
Address
Flag(s) Register
Register, Bit Position
IdleIEn InterruptEn 0x06, bit 2
IdleIRq InterruptRq 0x07, bit 2
IFDetectBusy Command 0x01, bit 7
IRq PrimaryStatus 0x03, bit 3
IRQInv IRQPinConfig 0x2D, bit 1
IRQPushPull IRQPinConfig 0x2D, bit 0
LoAlert PrimaryStatus 0x03, bit 0
LoAlertIEn InterruptEn 0x06, bit 0
LoAlertIRq InterruptRq 0x07, bit 0
SIGOUTSelect SIGOUTSelect 0x26, bits 2:0
MinLevel RxThreshold 0x1C, bits 7:4
ModemState PrimaryStatus 0x03 , bit 6:4
ModulatorSource TxControl 0x11, bits 6:5
ModWidth ModWidth 0x15, bits /:0
Page 0x00, 0x08, 0x10, 0x18, 0x20,
PageSelect
0x28, 0x30, 0x38, bits 2:0
PowerDown Control 0x09, bit4
RcvClkSelI RxControl2 0x1E, bit 7
RxAutoPD RxControl2 0x1E, bit 6
RxCRCEn ChannelRedundancy 0x22, bit 3
RxIEn InterruptEn 0x06, bit 3
RxIRq InterruptRq 0x07, bit 3
RxLastBits SecondaryStatus 0x05, bits 2:0
RxWait RxWait 0x21, bits 7:0
SetIEn InterruptEn 0x06, bit 67
SetIRq InterruptRq 0x07, bit 7
SignalToSIGOUT TestDigiSelect 0x3D, bit 7
StandBy Control 0x09, bit 5
TAutoRestart TimerClock 0x2A, bit 5
TestAnaOutSel TestAnaSelect 0x3A, bits 6:4
TestDigiSignalSel TestDigiSelect 0x3D, bit 6:0
TimerIEn InterruptEn 0x06, bit 5
TimerIRq InterruptRq 0x07, bit 5
TimerValue TimerValue 0x0C, bits 7:0
61
Philips Semiconductors Product Specification Rev. 3.2 December 2005
Address
Flag(s) Register
Register, Bit Position
TPreScaler TimerClock 0x2A, bits 4:0
TReloadValue TimerReload 0x2C, bits 7:0
TRunning SecondaryStatus 0x05, bit 7
TStartTxBegin TimerControl 0x2B, bit 0
TStartTxEnd TimerControl 0x2B, bit 1
TStartNow Control 0x09, bit 1
TStopRxBegin TimerControl 0x2B, bit 2
TStopRxEnd TimerControl 0x2B, bit 3
TStopNow Control 0x09, bit 2
TX1RFEn TxControl 0x11, bit 0
TX2Cw TxControl 0x11, bit 3
TX2Inv TxControl 0x11, bit 3
TX2RFEn TxControl 0x11, bit 1
TxCRCEn ChannelRedundancy 0x22, bit 2
TxIEn InterruptEn 0x06, bit 4
TxIRq InterruptRq 0x07, bit 4
TxLastBits BitFraming 0x0F, bits 2:0
Page 0x00, 0x08, 0x10, 0x18, 0x20,
UsePageSelect
0x28, 0x30, 0x38, bit 7
WaterLevel FIFOLevel 0x29, bits 5:0
ZeroAfterColl DecoderControl 0x1A, bit 5
62
Philips Semiconductors Product Specification Rev. 3.2 December 2005
The commands, configurations bits and flags are accessed via the µ-Processor interface.
The SL RC400 can internally address 64 registers. This basically requires six address lines.
The SL RC400 register set is segmented into 8 pages with 8 register each. The Page-Register can always
be addressed, no matter which page is currently selected.
Using the SL RC400 with dedicated address bus, the µ-Processor defines three address lines via the
address pins A0, A1, and A2. This allows addressing within a page. To switch between registers in different
pages the paging mechanism needs then to be used.
Using the SL RC400 with multiplexed address bus, the µ-Processor may define all six address lines at once.
In this case either the paging mechanism or linear addressing may be used.
Register Bit:
Interface Bus Type Register-Address
UsePageSelect
Multiplexed Address Bus
(paging mode) 1 PageSelect2 PageSelect1 PageSelect0 AD2 AD1 AD0
63
Philips Semiconductors Product Specification Rev. 3.2 December 2005
Byte 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15
Meaning Product Type Identification RFU Product Serial Number Internal RsMaxP CRC
The SL RC400 is a member of a new family for highly integrated reader IC’s. Each member of the product
family has its unique Product Type Identification. The value of the Product Type Identification is shown in the
table below:
64
Philips Semiconductors Product Specification Rev. 3.2 December 2005
The SL RC400 holds a four byte serial number that is unique for each device.
INTERNAL:
RsMaxP:
Maximum Source Resistance for the p-Channel Driver Transistor of pin TX1 and TX2.
The source resistance of the p-channel driver transistors of pin TX1 and TX2 may be adjusted via the
GsConfCW Register (see chapter 13.2.1). The mean value of the maximum adjustable source resistance of
the pins TX1 and TX2 is stored as an integer value in Ohms in byte RsMaxP. The typical value for RsMaxP
is between 60 to 140 Ohm.
This value is denoted as maximum adjustable source resistance Rs ref,max,n and is measured with GsConfCW
Register set to 01hex .
CRC
The content of the product information field is secured via a CRC-byte, which is checked during start up.
Register initialisation in the register address range from 10hex to 2Fhex is done automatically during the
Initialising Phase (see 11.3), using the Start Up Register Initialisation File.
Furthermore, the user may initialise the SL RC400 registers with values from the Register Initialisation File
executing the LoadConfig-Command (see 16.6.1).
Notes:
• The Page-Register (addressed with 10hex , 18hex , 20hex , 28hex ) is skipped and not initialised.
• Make sure, that all register bits that are reserved for future use (RFU) are set to 0.
65
Philips Semiconductors Product Specification Rev. 3.2 December 2005
The content of the E²PROM memory block address 1 and 2 are used to initialise the SL RC400 registers
10hex to 2Fhex during the Initialising Phase automatically. The default values written into the E²PROM during
production are shown in chapter 6.3.2.
… … …
66
Philips Semiconductors Product Specification Rev. 3.2 December 2005
During production test, the Start Up Register Initialisation File is initialised with the values shown in the table
below. With each power up these values are written into the SL RC400 register during the Initialising Phase.
67
Philips Semiconductors Product Specification Rev. 3.2 December 2005
The content of the E²PROM memory from block address 3 to 7 may be used to initialise the SL RC400
registers 10hex to 2Fhex by execution of the LoadConfig-Command (see 16.6.1). It requires a two byte
argument, that is used as the two byte long E²PROM starting byte address for the initialisation procedure.
… … …
The Register Initialisation File is big enough to hold the values for two initialisation sets and leaves one more
block (16 bytes) for the user.
Note: The Register Initialisation File is read- and write-able for the user. Therefore, these bytes may also be
used to store user specific data for other purposes.
68
Philips Semiconductors Product Specification Rev. 3.2 December 2005
7 FIFO BUFFER
7.1 Overview
An 8x64 bit FIFO buffer is implemented in the SL RC400 acting as a parallel-to-parallel converter. It buffers
the input and output data stream between the µ-Processor and the internals of the SL RC400. Thus, it is
possible to handle data streams with lengths of up to 64 bytes without taking timing constraints into account.
The FIFO-buffer input and output data bus is connected to the FIFOData Register. Writing to this register
stores one byte in the FIFO-buffer and increments the internal FIFO-buffer write-pointer. Reading from this
register shows the FIFO-buffer content stored at the FIFO-buffer read-pointer and increments the FIFO-
buffer read-pointer. The distance between the write- and read-pointer can be obtained by reading the
FIFOLength Register.
When the µ-Processor starts a command, the SL RC400 may, while the command is in progress, access the
FIFO-buffer according to that command. Physically only one FIFO-buffer is implemented, which can be used
in input- and output direction. Therefore the µ-Processor has to take care, not to access the FIFO-buffer in
an unintended way.
The following table gives an overview on FIFO access during command processing:
µ-Processor is allowed to
Active Command Remark
Write to FIFO Read from FIFO
StartUp - -
Idle - -
Transmit ü -
Receive - ü
µ-Processor has to know the actual state of the command
Transceive ü ü
(transmitting or receiving)
WriteE2 ü -
The µ-Processor has to prepare the arguments,
ReadE2 ü ü
then only reading is allowed
LoadConfig ü -
CalcCRC ü -
Besides writing and reading the FIFO-buffer, the FIFO-buffer pointers may be reset by setting the bit
FlushFIFO. The consequence is, that FIFOLength becomes zero, FIFOOvfl is cleared, the actually stored
bytes are not accessible anymore and the FIFO-buffer can be filled with another 64 bytes again.
69
Philips Semiconductors Product Specification Rev. 3.2 December 2005
The µ-Processor may obtain the following data about the FIFO-buffers status:
The flag HiAlert is set to 1 if only WaterLevel bytes or less can be stored in the FIFO-buffer. It is generated
by the following equation:
The flag LoAlert is set to 1 if WaterLevel bytes or less are actually stored in the FIFO-buffer. It is generated
by the following equation:
70
Philips Semiconductors Product Specification Rev. 3.2 December 2005
The following table shows the related flags of the FIFO buffer in alphabetic order.
71
Philips Semiconductors Product Specification Rev. 3.2 December 2005
8.1 Overview
The SL RC400 indicates certain events by setting bit IRq in the PrimaryStatus-Register and, in addition, by
activating pin IRQ. The signal on pin IRQ may be used to interrupt the µ-Processor using its interrupt
handling capabilities. This allows the implementation of efficient µ-Processor software.
The following table shows the integrated interrupt flags, the related source and the condition for its setting.
The interrupt flag TimerIRq indicates an interrupt set by the timer unit. The setting is done when the timer
decrements from 1 either down to zero (TAutoRestart flag disabled) or to the TPreLoad value if TAutoRestart
is enabled.
The TxIRq bit indicates interrupts from different sources. If the transmitter is active and the state changes
from sending data to transmitting the end of frame pattern, the transmitter unit sets automatically the interrupt
bit. The CRC coprocessor sets TxIRq after having processed all data from the FIFO buffer. This is indicated
2
by the flag CRCReady = 1. If the E Prom programming has finished the TxIRq bit is set, indicated by the bit
E2Ready = 1.
The RxIRq flag indicates an interrupt when the end of the received data is detected.
The flag IdleIRq is set if a command finishes and the content of the command register changes to idle.
The flag HiAlertIRq is set to 1 if the HiAlert bit is set to one, that means the FIFO buffer has reached the level
indicated by the bit WaterLevel, see chapter 7.4.
The flag LoAlertIRq is set to 1 if the LoAlert bit is set to one, that means the FIFO buffer has reached the
level indicated by the bit WaterLevel, see chapter 7.4.
72
Philips Semiconductors Product Specification Rev. 3.2 December 2005
The SL RC400 informs the µ-Processor about the interrupt request source by setting the according bit in the
InterruptRq Register. The relevance of each interrupt request bit as source for an interrupt may be masked
with the interrupt enable bits of the InterruptEn Register.
The interrupt request bits are set automatically by the internal state machines of the SL RC400. Additionally
the µ-Processor has access in order to set or to clear them.
A special implementation of the InterruptRq and the InterruptEn Register allows to change the status of a
single bit without influencing the other ones. If a specific interrupt register shall be set to one, the bit SetIxx
has to be set to 1 and simultaneously the specific bit has to be set to 1 too. Vice versa, if a specific interrupt
flag shall be cleared, a zero has to be written to the SetIxx and simultaneously the specific address of the
interrupt register has to be set to 1. If a bit content shall not be changed during the setting or clearing phase
a zero has to be written to the specific bit location.
Example: writing 3Fhex to the InterruptRq Register clears all bits as SetIRq in this case is set to 0 and all
other bits are set to 1. Writing 81hex sets bit LoAlertIRq to 1 and leaves all other bits untouched.
The logic level of the status flag IRq is visible at pin IRQ. In addition, the signal on pin IRQ may be controlled
by the following bits of the IRQPinConfig Register:
• IRQInv: if set to 0, the signal on pin IRQ is equal to the logic level of bit IRq.
If set to 1, the signal on pin IRQ is inverted with respect to bit IRq.
• IRQPushPull: if set to 1, pin IRQ has standard CMOS output characteristics
otherwise it is an open drain output and an external resistor is necessary to achieve a HIGH level at this
pin.
Note: During the Reset Phase (see 11.2) IRQInv is set 1 and IRQPushPull to 0. This results in a high
impedance at pin IRQ.
73
Philips Semiconductors Product Specification Rev. 3.2 December 2005
The following table shows the related flags of the Interrupt Request System in alphabetic order.
74
Philips Semiconductors Product Specification Rev. 3.2 December 2005
9 TIMER UNIT
9.1 Overview
A timer is implemented in the SL RC400. It derives its clock from the 13.56 MHz chip-clock. The µ-Processor
may use this timer to manage timing relevant tasks.
• Timeout -Counter
• Watch-Dog Counter
• Stop Watch
• Programmable One-Shot
• Periodical Trigger
The timer unit can be used to measure the time interval between two events or to indicate that a specific
event occurred after a specific time. The timer can be triggered by events which will be explained in the
following, but the timer itself does not influence any internal event. A timeout during data receiving does not
influence the receiving process automatically. Furthermore, several timer related flags are set and these
flags can be used to generate an interrupt.
75
Philips Semiconductors Product Specification Rev. 3.2 December 2005
TStartTxBegin
TReloadValue [7:0]
TxBegin Event
TStartTxEnd
parallel in
TxEnd Event
TRunning Q R
TStopNow
stop counter
RxBegin Event
TStopRxBegin
Clock
TPreScaler [4:0] Divider
13.56 MHz
>clock
parallel out
Counter = 0 ?
The timer unit is designed in a way, that several events in combination with enabling flags start or stop the
counter. For example, setting the bit TstartTxEnd to 1 enables to control the receiving of data using the timer
unit. In addition the first received bit is indicated by TxEndEvent. This combination starts the counter at the
defined TReloadValue.
The timer stops either automatically if the counter value is equal to zero, or if a defined stop event happens
(TautoRestart not enabled).
76
Philips Semiconductors Product Specification Rev. 3.2 December 2005
The main part of the timer unit is a down-counter. As long as the down-counter value is unequal zero, it
decrements its value with each timer clock.
If TAutoRestart is enabled the timer does not decrement down to zero. Having reached the value 1 the timer
reloads with the next clock with the TimerReload value.
The timer is started by loading a value from the TimerReload Register into the counter module. This may be
triggered by one of the following events:
• Transmission of the first bit to the label (TxBegin Event) and bit TStartTxBegin is 1
• Transmission of the last bit to the label (TxEnd Event) and bit TStartTxEnd is 1
• The counter module decrements down to zero and bit TAutoRestart is 1
• Bit TStartNow is set to 1 (by the µ-Processor)
Note: Every start-event re-loads the timer from the TimerReload Register. Thus, the timer unit is re-triggered.
The timer can be configured to stop with one of the following events:
• Reception of the first valid bit from the label (RxBegin Event)and bit TStopRxBegin is set to 1
• Reception of the last bit from the label (RxEnd event) and bit TStopRxEnd is set to 1
• The counter module has decremented down to zero and bit TAutoRestart is set to 0
• Bit TStopNow is set to 1 (by the µ-Processor)
Loading a new value, e.g. zero, into the TimerReload Register does not immediately influence the counter,
since the TimerReload Register affects the counter units content only with the next start-event. Thus, the
TimerReload Register may be changed even if the timer unit is already counting. The consequence of
changing the TimerReload Register will be visible after the next start-event.
The clock of the timer unit is derived from the 13.56 MHz chip clock via a programmable divider. The clock
selection is done with the TPreScaler Register, that defines the timer unit clock frequency according to the
following formula:
1 2T PreScaler
TTimerClock = =
f TimerClock 13.56MHz
The possible values for the TPreScaler Register range from 0 up to 21. This results in minimum time
TTimerClock of about 74 ns up to about 150 ms.
The time period elapsed since the last start event is calculated with
TReLoadVal ue − TimerValue
TTimer =
f TimerClock
77
Philips Semiconductors Product Specification Rev. 3.2 December 2005
The TRunning bit in the SecondaryStatus Register shows the timer’s current status. Any configured start
event starts the timer at the TReloadValue and changes the status flag TRunning to 1, any configured stop
event stops the timer and sets the status flag TRunning back to 0. As long as status flag TRunning is set to
1, the TimerValue Register changes with the next timer unit clock.
The actual timer unit content can be read on-the-fly via the TimerValue Register.
9.2.5 TIMESLOTPERIOD
For sending of I•CODE1-Quit-Frames it is necessary to generat a exact chronological relation to the begin of
the command frame.
Is TimeSlotPeriod > 0, with the end of command transmission the TimeSlotPeriod starst.
If there are Data in the FIFO after reaching the end of TimeSlotPeriod, these data were sent at that moment.
If the FIFO is empty nothing happens.
As long as the contend of TimeSlotPeriod is > 0 the counter for the TimeSlotPeriod will start automatically
after reaching the end.
This allows a exact time relation to the end (as well as to the beginning) of the command frame for the
generation and sending of the I•CODE1-Quit-Frames
Is TimeSlotPeriod > 0 the next Frame starts exact with the interval
TimeSlotPeriod/CoderRate
delayed after each previous Send Frame. CoderRate (see 5.2.3.5) defines the clock frequency of the coder.
If TimeSlotPeriod = 0, the send function will not be triggered automatically.
The contend of the register TimeSlotPeriod can be changed during the active mode. The modification take
effect at the next restart of the TimeSlotPeriod.
78
Philips Semiconductors Product Specification Rev. 3.2 December 2005
Example:
Note: The MSB of the TimeSlotPeriod is in the SIGOUTSelect register see 5.2.5.7
Response1 Response2
TSP1 TSP2
Note: The MSB of the TimeSlotPeriod is in the SIGOUTSelect register see 5.2.5.7
Note: It is strictly recommended that bit TxCRCEn is set to 0 (see 5.2.5.3) before the Quit-Frame is sent. If
the TxCRCEn is not set to 0 a CRC value is calculated and sent with the Quit-Frame.
To calculate the Quit value a CRC8 algorithm has to be used.
79
Philips Semiconductors Product Specification Rev. 3.2 December 2005
Having started the timer by setting TReloadValue the timer unit decrements the TimerValue Register
beginning with a certain start event. If a certain stop event occurs e.g. a bit is received from the label, the
timer unit stops (no interrupt is generated).
On the other hand, if no stop event occurs, e.g. the label does not answer in the expected time, the timer unit
decrements down to zero and generates a timer interrupt request. This signals indicate the µ-Processor that
the expected event has not occurred in the given time TTimer.
The time TTimer between a certain start- and stop event may be measured by the µ-Processor by means of
the SL RC400 timer unit. Setting TReloadValue the timer starts to decrement. If the defined stop event
occurs the timers stops. The time between start and stop can be calculated by
The µ-Processor starts the timer unit and waits for the timer interrupt. After the specified time TTimer the
interrupt will occur (TautoRestart = 0).
If the µ-Processor sets bit TautoRestart and TreloadValue not equal 0, it will generate an interrupt request
periodically after every TTimer.
80
Philips Semiconductors Product Specification Rev. 3.2 December 2005
The following table shows the related flags of the Timer Unit in alphabetic order.
81
Philips Semiconductors Product Specification Rev. 3.2 December 2005
A Hard Power Down is enabled with HIGH on pin RSTPD. This turns off all internal current sinks including
the oscillator. All digital input buffers are separated from the input pads and defined internally (except pin
RSTPD itself). The output pins are frozen at a certain value.
This mode is immediately entered by setting bit PowerDown in the Control-Register. All internal current sinks
are switched off (including the oscillator buffer).
Different from the Hard Power Down Mode, the digital input buffers are not separated from the input pads but
keep their functionality. The digital output pins do not change their state.
After resetting bit PowerDown in the Control-Register it needs 512 clocks until the Soft Power Down mode is
left. This is indicated by the PowerDown bit itself. Resetting it does not immediately clear it, but it is cleared
automatically by the SL RC400 when the Soft Power Down Mode is left.
Note: If the internal oscillator is used, you have to take into account that it is supplied by AVDD and it will
take a certain time tosc until the oscillator is stable.
82
Philips Semiconductors Product Specification Rev. 3.2 December 2005
This mode is immediately entered by setting bit StandBy in the Control-Register. All internal current sinks are
switched off (including the internal digital clock buffer but except the oscillator buffer).
Different from the Hard Power Down Mode, the digital input buffers are not separated from the input pads but
keep their functionality. The digital output pins do not change their state.
Different from the Soft Power Down Mode, the oscillator does not need time to wake up.
After resetting bit StandBy in the Control-Register it needs 4 clocks on pin OSCIN until the Stand By Mode is
left. This is indicated by the StandBy bit itself. Resetting it does not immediately clear it, but it is cleared
automatically by the SL RC400 when the Stand By Mode is left.
It is power saving to switch off the receiver circuit when it is not needed and switched it on again right before
data is to be received from the label. This is done automatically by setting bit RxAutoPD to 1. If it is set to 0
the receiver is continuously switched on.
83
Philips Semiconductors Product Specification Rev. 3.2 December 2005
11 START UP PHASE
The phases executed during the start up are shown in the following figure:
Start Up Phase
The Hard Power Down Phase is active during the following cases:
• Power On Reset caused by power up at pin DVDD
(active while DVDD is below the digital reset threshold)
• Power On Reset caused by power up at pin AVDD
(active while AVDD is below the analog reset threshold)
• A HIGH level on pin RSTPD
(active while pin RSTPD is HIGH)
Note:
In case three, HIGH level on pin RSTPD, has to be at least 100µs long (t PD >= 100µs). Shorter phases will
not necessarily result in the reset phase tReset.
The slew rate of rising/falling edge on pin RSTPD is not critical because pin RSTPD is a schmitt-trigger input.
The Reset Phase follows the Hard Power Down Phase automatically. It takes 512 clocks. During the Reset
Phase, some of the register bits are preset by hardware. The respective reset values are given in the
description of each register (see 5.2.).
Note: If the internal oscillator is used, you have to take into account that it is supplied by AVDD and that it will
take a certain time tosc until the oscillator is stable.
The Initialising Phase follows the Reset Phase automatically. It takes 128 clocks. During the Initialising
Phase the content of the E²PROM blocks 1 and 2 is copied into the registers 10hex to 2Fhex (see 6.3.).
Note: At production test, the SL RC400 is initialised with default configuration values. This reduces the
µ-Processors effort for configuring the device to a minimum.
84
Philips Semiconductors Product Specification Rev. 3.2 December 2005
For the different connections for the different µ-Processor interface types (see 4.3), a certain initialising
sequence shall be applied to enable a proper µ-Processor interface type detection and to synchronise the
µ-Processor’s and the SL RC400’s Start Up.
During the Start Up Phase the Command value reads as 3Fhex , after the oscillator delivers a stable clock
frequency with an amplitude of >90% of the nominal 13.56MHz clock. At the end of the Initialising Phase the
SL RC400 enters the Idle Command automatically. Consequently the Command value changes to 00hex .
To ensure proper detection of the µ-Processor interface, the following sequence shall be executed:
• Read from the Command-Register until the six bit register value for Command is 00hex .
The internal initialisation phase is now completed and the SL RC400 is ready to be controlled.
• Write the value 80hex to the Page-Register to initialise the µ-Processor interface.
• Read the Command-Register. If its value is 00hex the µ-Processor interface initialisation was
successful.
After interface initialisation, the linear addressing mode can be activated by writing 0x00 to the page
register(s).
85
Philips Semiconductors Product Specification Rev. 3.2 December 2005
12 OSCILLATOR CIRCUITRY
SL RC400
OSCOUT OSCIN
13.56 MHz
15 pF 15 pF
The clock applied to the SL RC400 acts as time basis for the coder and decoder of the synchronous system.
Therefore stability of clock the frequency is an important factor for proper performance. To obtain highest
performance, clock jitter has to be as small as possible. This is best achieved by using the internal oscillator
buffer with the recommended circuitry. If an external clock source is used, the clock signal has to be applied
to pin OSCIN. In this case special care for clock duty cycle and clock jitter is needed and the clock quality
has to be verified. It needs to be in accordance with the specifications in chapter 19.5.3.
86
Philips Semiconductors Product Specification Rev. 3.2 December 2005
The signal delivered on TX1 and TX2 is the 13.56 MHz carrier frequency modulated by an envelope signal. It
can be used to drive an antenna directly, using a few passive components for matching and filtering (see
chapter 17). For that, the output circuitry is designed with an very low impedance source resistance. The
signal of TX1 and TX2 can be controlled via the TxControl Register.
The user has the possibility to find a trade-off between maximum achievable operating distance and power
consumption by using different antenna matching circuits as described in Error! Reference source not
found. and/or by varying the supply voltage at the antenna driver supply pin TVDD.
87
Philips Semiconductors Product Specification Rev. 3.2 December 2005
The output source conductance of TX1 and TX2 for driving a HIGH level may be adjusted via the value
GsCfgCW in the CwConductance Register in the range from about 1 up to 100 Ohm. The values given are
relative to the reference resistance Rs rel, that is measured during production test and stored in the SL RC400
E²PROM. It can be obtained from the Product Information Field (see chapter 6.2).
The electrical specification can be found in chapter 19.4.3.
GsConfCW EXPGsConfCW MANT GsConfCW Rs rel GsConfCW EXPGsConfCW MANT GsConfCW Rs rel
0 0 0 8 24 1 8 0,0652
16 1 0 8 25 1 9 0,0580
32 2 0 8 37 2 5 0,0541
48 3 0 8 26 1 A 0,0522
1 0 1 1,0000 27 1 B 0,0474
17 1 1 0,5217 51 3 3 0,0467
2 0 2 0,5000 38 2 6 0,0450
3 0 3 0,3333 28 1 C 0,0435
33 2 1 0,2703 29 1 D 0,0401
18 1 2 0,2609 39 2 7 0,0386
4 0 4 0,2500 30 1 E 0,0373
5 0 5 0,2000 52 3 4 0,0350
19 1 3 0,1739 31 1 F 0,0348
6 0 6 0,1667 40 2 8 0,0338
7 0 7 0,1429 41 2 9 0,0300
49 3 1 0,1402 53 3 5 0,0280
34 2 2 0,1351 42 2 A 0,0270
20 1 4 0,1304 43 2 B 0,0246
8 0 8 0,1250 54 3 6 0,0234
9 0 9 0,1111 44 2 C 0,0225
21 1 5 0,1043 45 2 D 0,0208
10 0 A 0,1000 55 3 7 0,0200
11 0 B 0,0909 46 2 E 0,0193
35 2 3 0,0901 47 2 F 0,0180
22 1 6 0,0870 56 3 8 0,0175
12 0 C 0,0833 57 3 9 0,0156
13 0 D 0,0769 58 3 A 0,0140
23 1 7 0,0745 59 3 B 0,0127
14 0 E 0,0714 60 3 C 0,0117
50 3 2 0,0701 61 3 D 0,0108
36 2 4 0,0676 62 3 E 0,0100
15 0 F 0,0667 63 3 F 0,0093
Table 13-3: Source Resistance of n-Channel Driver Transistor of TX1 and TX2 vs. GsConfCW
88
Philips Semiconductors Product Specification Rev. 3.2 December 2005
1
Rs rel =
MANTGsConfCW ⋅ ( 77
EXPGsConfCW
40
)
Wiring and bonding adds a constant offset to the driver resistance, that is relevant if TX1 and TX2 are
switched to low impedance.
Rs wire,TX 1 ≈ 500 mΩ
The source resistances of the driver transistors found in the Product Information Field (see 6.2) are
measured at production test with GsModCW set to 01hex . To get the driver resistance for a specific value set
in GsModCW the following formula may be used:
89
Philips Semiconductors Product Specification Rev. 3.2 December 2005
The following table shows the modulation index, if a 50 ohm antenna is used and GsCfgCW is set to 0x3F.
To change the modulation index the GsCfgMod register has to be changed similar as the GsCfgCW register.
GsCfgMod rel. resistance Mod. index GsCfgMod rel. resistance Mod. index
Rrel(during modulation) Rant=50Ω Rrel(during modulation) Rant=50Ω
0x00 Infite 0x18 0,065 4,15%
0x10 Infite 0x19 0,058 3,63%
0x20 Infite 0x25 0,054 3,35%
0x30 Infite 0x1A 0,052 3,22%
0x01 1,000 43,45% 0x1B 0,047 2,87%
0x11 0,522 28,44% 0x33 0,047 2,82%
0x02 0,500 27,57% 0x26 0,045 2,69%
0x03 0,333 20,08% 0x1C 0,043 2,58%
0x21 0,270 16,83% 0x1D 0,040 2,33%
0x12 0,261 16,33% 0x27 0,039 2,22%
0x04 0,250 15,73% 0x1E 0,037 2,12%
0x05 0,200 12,88% 0x34 0,035 1,95%
0x13 0,174 11,32% 0x1F 0,035 1,93%
0x06 0,167 10,88% 0x28 0,034 1,86%
0x07 0,143 9,38% 0x29 0,030 1,58%
0x31 0,140 9,21% 0x35 0,028 1,43%
0x22 0,135 8,89% 0x2A 0,027 1,35%
0x14 0,130 8,59% 0x2B 0,025 1,17%
0x08 0,125 8,23% 0x36 0,023 1,08%
0x09 0,111 7,32% 0x2C 0,023 1,01%
0x15 0,104 6,86% 0x2D 0,021 0,88%
0x0A 0,100 6,57% 0x37 0,020 0,82%
0x0B 0,091 5,95% 0x2E 0,019 0,77%
0x23 0,090 5,89% 0x2F 0,018 0,67%
0x16 0,087 5,68% 0x38 0,018 0,63%
0x0C 0,083 5,43% 0x39 0,016 0,48%
0x0D 0,077 4,98% 0x3A 0,014 0,36%
0x17 0,075 4,81% 0x3B 0,013 0,26%
0x0E 0,071 4,59% 0x3C 0,012 0,18%
0x32 0,070 4,50% 0x3D 0,011 0,11%
0x24 0,068 4,32% 0x3E 0,010 0,05%
0x0F 0,067 4,26% 0x3F 0,009 0,00%
Note: If the output source conductance (GsCfgCW) has been changed GsCfgMod must also be changed to
get the same modulation index.
90
Philips Semiconductors Product Specification Rev. 3.2 December 2005
The envelope carries the information of the data signal, that shall be transmitted to the label. This is done by
coding the data signal according to the 1 out of 256, RZ or 1 out of 4 code. Furthermore, each pause of the
coded signal again is coded as a pulse of certain length. The width of this pulse can be adjusted by means of
the ModWidth Register. The pulse length is calculated by
ModWidth + 1
TPulse = 2
fC
where fc = 13.56MHz.
91
Philips Semiconductors Product Specification Rev. 3.2 December 2005
14 RECEIVER CIRCUITRY
14.1 General
The SL RC400 employs an integrated quadrature-demodulation circuit which extracts the sub-carrier signal
from the 13.56 MHz ASK-modulated signal applied to pin RX. The quadrature-demodulator uses two
different clocks, Q- and I-clock, with a phase shift of 90° between them. Both resulting subcarrier signals are
amplified, filtered and forwarded to the correlation circuitry. The correlation results are evaluated, digitised
and passed to the digital circuitry.
For all processing units various adjustments can be made to obtain optimum performance.
Figure 14-1 shows the block diagram of the receiver circuitry. The receiving process includes several steps.
First the quadrature demodulation of the carrier signal of 13.56 MHz is done. To achieve an optimum in
performance an automatic clock Q calibration is recommended (see 14.3.1). The demodulated signal is
amplified by an adjustable amplifier. A correlation circuit calculates the degree of similarity between the
expected and the received signal. The bit phase register allows to align the position of the correlation
intervals with the bit grid of the received signal. In the evaluation and digitizer circuitry the valid bits are
detected and the digital results are send to the FIFO register. Several tuning steps in this circuit are possible.
I-clock Q-clock
s_valid
13.56 MHz Correlation Evaluation and Digitizer s_data
RX
Demodulator Circuitry Circuitry s_coll
s_clock
to
TestAna
OutSel
The user may observe the signal on its way through the receiver as shown in the block diagram above. One
signal at a time may be routed to pin AUX using the TestAnaSelect-Register as described in 18.3.
92
Philips Semiconductors Product Specification Rev. 3.2 December 2005
In general, the default settings programmed into the Start Up Initialisation File are suitable to use the
SL RC400 for data communication with I•CODE labels. However, in some environments specific user
settings may achieve better performance.
The quadrature demodulation concept of the receiver generates a phase signal I-clock and a 90° shifted
quadrature signal Q-clock. To achieve an optimum demodulator performance, the Q- and the I-clock have to
have a difference in phase of 90°. After the reset phase of the SL RC400, a calibration procedure is done
automatically. It is possible to have an automatic calibration done at the ending of each Transceive
command. To do so, the ClkQCalib bit has to be configured to a value of 0.
Configuring this bit to a constant value of 1 disables all automatic calibrations except the one after the reset
sequence.
It is also possible to initiate one automatic calibration by software. This is done with a 0 to 1 transition of bit
ClkQCalib.
The details:
calibration impulse
from reset sequence a rising edge initiates
a clock Q calibration
calibration impulse
from ending of
TRANSEIVE command
Note: The duration of the automatic clock Q calibration is at most 65 oscillator periods which is approx.
4,8µs.
The value of ClkQDelay is proportional to the phase shift between the Q- and the I-clock. The status flag
ClkQ180Deg shows, that the phase shift between the Q- and the I-clock is greater than 180°.
Notes:
• The startup confi guration file enables an automatically Q-clock calibration after the reset.
• While ClkQCalib is 1, no automatic calibration is done. Therefore leaving this bit 1 can be used to
permanently disable the automatic calibration.
• It is possible to write data to ClkQDelay via the µ-Processor. The aim could be a disabling of the
automatic calibration and to pre-set the delay by software. But notice, that configuring the delay value by
software requires that bit ClkQCalib has already been set to 1 before and that a time interval of at least
4.8µs has elapsed since then. Each delay value must be written with the ClkQCalib bit set to 1. If
ClkQCalib is 0 the configured delay value will be overwritten by the next interval automatic calibration.
93
Philips Semiconductors Product Specification Rev. 3.2 December 2005
14.3.2 AMPLIFIER
The demodulated signal has to be amplified with the variable amplifier to achieve the best performance. The
gain of the amplifiers can be adjusted by means of the register bits Gain[1:0]. The following gain factors are
selectable:
94
Philips Semiconductors Product Specification Rev. 3.2 December 2005
The correlation circuitry calculates the degree of matching between the received and an expected signal.
The output is a measure for the amplitude of the expected signal in the received signal. This is done for both,
the Q- and the I-channel. The correlator delivers two outputs for each of the two input channels, resulting in
four output signals in total.
For optimum performance, the correlation circuitry needs the phase information for the signal coming from
the label. This information has to be defined by the µ-Processor by means of the register BitPhase[7:0]. This
value defines the phase relation between the transmitter and receiver clock in multiples of
tBitPhase = 1/13.56 MHz.
For each bit-half of the Manchester coded signal the correlation results are evaluated. The evaluation and
digitizer circuit decides from the signal strengths of both bit-halves, whether the current bit is valid, and, if it is
valid, the value of the bit itself or whether the current bit-interval contains a collision.
To do this in an optimum way, the user may select the following levels:
• MinLevel: Defines the minimum signal strength of the stronger bit-half’s signal for being considered valid.
• CollLevel: Defines the minimum signal strength that has to be exceeded by the weaker half-bit of the
Manchester-coded signal to generate a bit-collision. If the signal’s strength is below this value, a 1 and 0
can be determined unequivocally.
CollLevel defines the minimum signal strength relative to the amplitude of the stronger half-bit.
After transmission of data, the label is not allowed to send its response before a certain time period, called
frame guard time in the standard ISO 15693 (similar to I•CODE1). The length of this time period after
transmission shall be set in the RxWait-Register. The RxWait-Register defines when the receiver is switched
on after data transmission to the label in multiples of one bit-duration.
If register bit RcvClkSelI is set to 1, the I-clock is used to clock the correlator and evaluation circuits. If set to
0, the Q-clock is used.
95
Philips Semiconductors Product Specification Rev. 3.2 December 2005
15.1 General
Two main blocks are implemented in the SL RC400. A digital circuitry, comprising state machines, coder and
decoder logic and so on and an analog circuitry with the modulator and antenna drivers, receiver and
amplification circuitry. The interface between these two blocks can be configured in the way, that the
interfacing signals may be routed to the pin SIGOUT.
Figure 15-1 describes the serial signal switches. Three different switches are implemented in the serial signal
switch in order to use the SL RC400 in different configurations.
The serial signal switch may also be used during the design In phase or for test purposes to check the
transmitted and received data. Chapter 18.2, describes analog test signals as well as measurements at the
serial signal switch.
0
0
1 Tx1
1 out of 256 1
or Envelope 2 Modulator Driver
Serial Data Out Tx2
RZ or
RFU 3
1 out of 4
2
Modulator
Source (Part of)
(Part of) Analog Circuitry
Serial Data Processing
0
0
1 Internal Manchester Out Subcarrier Carrier
Rx
Serial Data In
Manchester Demodulator Demodulator
Manchester with Subcarrier
Decoder 2 RFU
3 RFU
2
Transmitt NRZ
Manchester
Decoder
Envelope
Source
RFU
RFU
0
1
0
SigOut
Select
3
SignalTo
SigOut
Serial Signal Switch
SIGOut
The following chapters describe the relevant registers used to configure and control the serial signal switch.
96
Philips Semiconductors Product Specification Rev. 3.2 December 2005
The flags DecoderSource define the input signal for the internal Manchester decoder in the following way:
ModulatorSource defines the signal that modulates the transmitted 13.56 MHz carrier frequenzy. The
modulated signal drives the pins TX1 and TX2.
SIGOUTSelect defines the input signal for the internal Manchester decoder in the following way:
Note: To use SIGOUTSelect, the value of test signal control bit SignalToSIGOUT has to be 0.
97
Philips Semiconductors Product Specification Rev. 3.2 December 2005
The SL RC400 behaviour is determined by an internal state machine that is capable to perform a certain set
of commands. These commands are started by writing the according command-code to the Command-
Register.
Arguments and/or data necessary to process a command are exchanged via the FIFO buffer.
• Each command, that needs a data stream (or data byte stream) as input will immediately process the
data it finds in the FIFO buffer.
• Each command, that needs a certain number of arguments will start processing only when it has
received the correct number of arguments via the FIFO buffer.
• The FIFO buffer is not cleared automatically at command start. Therefore, it is also possible to write the
command arguments and/or the data bytes into the FIFO buffer and start the command afterwards.
• Each command (except the StartUp-Command) may be interrupted by the µ-Processor by writing a new
command code into the Command-Register e.g.: the Idle-Command.
98
Philips Semiconductors Product Specification Rev. 3.2 December 2005
99
Philips Semiconductors Product Specification Rev. 3.2 December 2005
The StartUp-Command runs the Reset- and Initialisation Phase. It does not need or return any data. It can
not be activated by the µ-Processor but is started automatically after one of the following events:
• Power On Reset caused by power up at Pin DVDD
• Power On Reset caused by power up at Pin AVDD
• Negative Edge at Pin RSTPD
The Reset-Phase defines certain register bits by an asynchronous reset. The Initialisation-Phase defines
certain registers with values taken from the E²PROM.
Notes:
• The µ-Processor must not write to the SL RC400 as long as the SL RC400 is busy executing the
StartUp-Command. To ensure this, the µ-Processor shall poll for the Idle-Command to determine the
end of the Initialisation Phase (see also chapter 11.4).
• As long as the StartUp-Command is active, only reading from page 0 of the SL RC400 is possible.
The Idle-Command switches the SL RC400 to its inactive state. In this Idle-state it waits for the next
command. It does not need or return any data. The device automatically enters the Idle-state when a
command finishes. In this case the SL RC400 simultaneously initiates an interrupt request by setting bit
IdleIRq. Triggered by the µ-Processor, the Idle-Command may be used to stop execution of all other
commands (except the StartUp Command). In that case no IdleIRq is generated.
Remark: Stopping a command with the Idle Command does not clear the FIFO buffer content.
100
Philips Semiconductors Product Specification Rev. 3.2 December 2005
The SL RC400 is a fully ISO 15693 and I•CODE1 compliant reader IC. The following chapter describe the
command set for label communication in general.
Transmit 1A Transmits data from FIFO buffer to the label Data Stream -
The Transmit-Command takes data from the FIFO buffer and forwards it to the transmitter. It does not return
any data. The Transmit-Command can only be started by the µ-Processor.
1. All data, that shall be transmitted to the label is written to the FIFO while the Idle-Command is active.
After that, the command code for the Transmit-Command is written to the Command-Register.
Note: This is possible for transmission of data with a length of up to 64 bytes.
2. The command code for the Transmit-Command is written to Command-Register first. Since no data is
available in the FIFO, the command is only enabled but transmission is not triggered yet.
Data transmission really starts with the first data byte written to the FIFO. To generate a continuous data
stream on the RF-interface, the µ-Processor has to put the next data bytes to the FIFO in time.
Note: This allows transmission of data of any length but requires that data is available in the FIFO in
time.
3. A part of the data, that shall be transmit to the label is written to the FIFO while the Idle-Command is
active. After that, the command code for the Transmit-Command is written to the Command-Register.
While the Transmit-Command is active, the µ-Processor may feed further data to the FIFO, causing the
transmitter to append it to the transmitted data stream.
Note: This enables transmission of data of any length but requires that data is available in the FIFO in
time.
When the transmitter requests the next data byte to keep the data stream on the RF-interface continuous but
the FIFO buffer is empty, the Transmit-Command automatically terminates. This causes the internal state
machine to change its state from Transmit to Idle.
If data transmission to the label is finished, the SL RC400 sets the flag TxIRq to signal it to the µ-Processor.
Remark: If the µ-Processor overwrites the transmit code in the Command-Register with the Idle-Command or
any other command, transmission stops immediately with the next clock cycle. This may produce output
signals that are not according to the standard ISO 15693 or the I•CODE1 protocol.
101
Philips Semiconductors Product Specification Rev. 3.2 December 2005
Each transmitted ISO 15693 frame consists of a SOF (start of frame) pattern, followed by the data stream
and is closed by an EOF (end of frame) pattern. All I•CODE1 command frames consists of a START PULSE
followed by the data stream. The I•CODE1 commands have a fix length and no EOF is needed. These
different phases of the transmit sequence may be monitored by watching ModemState of PrimaryStatus-
Register (see 16.4.4).
Depending on the setting of bit TxCRCEn in the ChannelRedundancy-Register a CRC is calculated and
appended to the data stream. The CRC is calculated according the settings in the ChannelRedundancy
Register.
To generate frames with more than 64 bytes, the µ-Processor has to write data into the FIFO buffer while the
Transmit Command is active. The state machine checks the FIFO status when it starts transmitting the last
bit of the actual data stream (the check time is marked below with arrows).
TxLastBits TxLastBits = 0
FIFO empty
As long as the internal signal ‘Accept Further Data’ is 1 further data may be loaded into the FIFO. The
SL RC400 appends this data to the data stream transmitted via the RF-interface.
If the internal signal ‘Accept Further Data’ is 0 the transmission will terminate. All data written into the FIFO
buffer after ‘Accept Further Data’ went 0 will not be transmitted anymore, but remain in the FIFO buffer.
102
Philips Semiconductors Product Specification Rev. 3.2 December 2005
The Receive-Command activates the receiver circuitry. All data received from the RF interface is returned via
the FIFO buffer. The Receive-Command can be started either by the µ-Processor or automatically during
execution of the Transceive-Command.
Note: This command may be used for test purposes only, since there is no timing relation to the Transmit-
Command.
After starting the Receive Command the internal state machine decrements the value set in the RxWait-
Register with every bit-clock. From 3 down to 1 the analog receiver circuitry is prepared and activated. When
the counter reaches 0, the receiver starts monitoring the incoming signal at the RF-interface. If the signal
strength reaches a level higher than the value set in the MinLevel-Register it finally starts decoding. The
decoder stops, if no more signal can be detected on the receiver input pin Rx. The decoder indicates
termination of operation by setting bit RxIRq.
The different phases of the receive sequence may be monitored by watching ModemState of the
PrimaryStatus-Register (see 16.4.4).
Note: Since the counter values from 3 to 0 are necessary to initialise the analog receiver circuitry the
minimum value for RxWait is 3.
For ISO 15693 the decoder expects a SOF pattern at the beginning of each data stream. If a SOF is
detected, it activates the serial to parallel converter and gathers the incoming data bits. For I•CODE1 the
decoder do not expects a SOF pattern at the beginning of each data stream. It activates the serial to parallel
converter with the first received bit of the data. Every completed byte is forwarded to the FIFO. If an EOF
pattern (ISO15693) is detected or the signal strength falls below MinLevel set in the RxThreshold Register,
the receiver and the decoder stop, the Idle-Command is entered and an appropriate response for the µ-
Processor is generated (interrupt request activated, status flags set).
If bit RxCRCEn in the ChannelRedundancy Register is set a CRC block is expected. The CRC block may be
one byte or two bytes according to bit CRC8 in the ChannelRedundancy Register.
Remark: The received CRC block is not forwarded to the FIFO buffer if it is correct. This is realised by
shifting the incoming data bytes through an internal buffer of either one or two bytes (depending on the
defined CRC). The CRC block remains in this internal buffer. As a consequence all data bytes are available
in the FIFO buffer one or two bytes delayed.
If the CRC fails all received bytes are forwarded to the FIFO buffer (including the faulty CRC itself).
103
Philips Semiconductors Product Specification Rev. 3.2 December 2005
If more than one label is within the RF-field during the label selection phase, they will respond
simultaneously. The SL RC400 supports the algorithm defined in ISO 15693 as well as the I•CODE1 anti-
collision algorithm to resolve data-collisions of label serial numbers by doing the so-called anti-collision
procedure. The basis for this is the ability to detect bit-collisions.
Bit-collision detection is supported by the used bit-coding scheme, namely the Manchester-coding. If in the
first and second half-bit of a bit a sub-carrier modulation is detected, instead of forwarding a 1 or a 0 a bit
collision will be signalled. To distinguish a 1 or 0-bit from a bit-collision, the SL RC400 uses the setting of
CollLevel. If the amplitude of the half-bit with smaller amplitude is larger than defined by CollLevel, the
SL RC400 indicates a bit-collision.
Independent from the detected collision the receiver continues receiving the incoming data stream. In case of
a bit-collision, the decoder forwards 1 at the collision position.
Note: As an exception, if bit ZeroAfterColl is set, all bits received after the first bit-collision are forced to zero,
regardless whether a bit-collision or an unequivocal state has been detected. This feature eases for the
software to carry out the anti-collision procedure defined in ISO 15693.
When the first bit collision in a frame is detected, the bit position of this collision is stored in the CollPos
Register.
If a collision is detected in the SOF a frame error is reported and no data is forwarded to the FIFO buffer. In
this case the receiver continues to monitor the incoming signal and generates the correct notifications to the
µ-Processor when the ending of the faulty input stream is detected. This helps the µ-Processor to determine
the time when it is allowed next to send anything to the label.
104
Philips Semiconductors Product Specification Rev. 3.2 December 2005
The following table shows which event causes the setting of error flags:
Transceive 1E Transmits data from FIFO buffer to the label Data Stream Data Stream
and then activates automatically the receiver
The Transceive-Command first executes the Transmit-Command (see 16.4.1) and then automatically starts
the Receive-Command (see 16.4.2). All data that shall be transmitted is forwarded via the FIFO buffer and all
data received is returned via the FIFO buffer. The Transceive-Command can be started only by the
µ-Processor.
Note: To adjust the timing relation between transmitting and receiving, the RxWait Register is used to define
the time delay from the last bit transmitted until the receiver is activated. Furthermore, the BitPhase Register
determines the phase-shift between the transmitter and the receiver clock.
The actual state of the transmitter and receiver state machine can be fetched from ModemState in the
PrimaryStatus Register.
The assignment of ModemState to the internal action is shown in the following table:
105
Philips Semiconductors Product Specification Rev. 3.2 December 2005
Command =
(Transmit OR
Receive OR
Transceive)
Idle
(000)
Co
m
Re man
D
ce d =
AN
)
ive
ive
ce
sm d = pty
ns
an an m
Tra
(Tr mm not e
R
it O
Co IFO
F
GoToRx1
TxSOF (100)
(001)
TxData PrepareRx
(010) (101)
TxEOF AwaitingRx
(011) (110)
GoToRx2
End of Receive frame && (100)
RxMultiple = 0 &&
TimeSlotPeriod = 0
Preparing to
send the Quit
value
106
Philips Semiconductors Product Specification Rev. 3.2 December 2005
16.5.1.1 Overview
The WriteE2-Command interprets the first two bytes in the FIFO buffer as E²PROM starting byte-address.
Any further bytes are interpreted as data bytes and are programmed into the E²PROM, starting from the
given E²PROM starting byte-address. This command does not return any data.
The WriteE2-Command can only be started by the µ-Processor. It will not stop automatically but has to be
stopped explicitly by the µ-Processor by issuing the Idle-Command.
The state machine copies all data bytes prepared in the FIFO buffer to the E²PROM input buffer. The internal
E²PROM input buffer is 16 byte long which is equal the block size of the E²PROM. A programming cycle is
started either if the last position of the E²PROM input buffer is written or if the last byte of the FIFO buffer has
been fetched.
As long as there are unprocessed bytes in the FIFO buffer or the E²PROM programming cycle still is in
progress, the flag E2Ready is 0. If all data from the FIFO buffer are programmed into the E²PROM, the flag
E2Ready is set to1. Together with the rising edge of E2Ready the interrupt request flag TxIRq indicates a 1.
This may be used to generate an interrupt when programming of all data is finished.
After the E2Ready bit is set to 1, the WriteE2-Command may be stopped by the µ-Processor by issuing the
Idle-Command.
Important: The WriteE2-Command must not be stopped by starting another command before the E2Ready
flag is set to 1. Otherwise the content of the currently processed E²PROM block will not be defined or in
worst case the SL RC400 functionality is in-reversibly reduced.
107
Philips Semiconductors Product Specification Rev. 3.2 December 2005
t prg,del
NWrite
WriteE2
command active t prog t prog t prog
E²PROM Programming Byte0 Programming Byte1, Byte2, and Byte3 Programming Byte4
Programming
E2Ready
TxIRq
Explanation: It is assumed, that the SL RC400 finds and reads Byte 0 before the µ-Processor is able to write
Byte 1 (t prog,del = 300 ns). This causes the SL RC400 to start the programming cycle, which needs about
tprog = 2.9 ms. In the meantime the µ-Processor stores Byte 1 to Byte 4 to the FIFO buffer. Assuming, that the
E²PROM starting byte-address is e.g. 4Chex then Byte 0 is stored exactly there. The SL RC400 copies the
following data bytes into the E²PROM input buffer. Copying Byte 3, it detects, that this data byte has to be
programmed at the E²PROM byte-address 4Fhex . Since this is the end of the memory block, the SL RC400
automatically starts a programming cycle. In the next turn, Byte 4 will be programmed at the E²PROM byte-
address 50hex . Since this is the last data byte, the flags (E2Ready and TxIRq) that indicate the end of the
E²PROM programming activity will be set.
Although all data has been programmed into the E2PROM, the SL RC400 stays in the WriteE2-Command.
Writing further data to the FIFO would lead to further E²PROM programming, continuing at the E²PROM
byte-address 51hex . The command is stopped using the Idle-Command.
Programming is inhibited for the E²PROM blocks 0 (E²PROM’s byte-address 00hex to 0Fhex ). Programming to
these addresses sets the flag AccessErr. No programming cycle is started (for the E²PROM memory
organisation refer to chapter 6.). It is strictly recommended to use only the described E²PROM address area.
108
Philips Semiconductors Product Specification Rev. 3.2 December 2005
16.5.2.1 Overview
The ReadE2-Command interprets the first two bytes found in the FIFO buffer as E²PROM starting
byte-address. The next byte specifies the number of data bytes that shall be returned.
When all three argument -bytes are available in the FIFO buffer, the specified number of data bytes is copied
from the E²PROM into the FIFO buffer, starting from the given E²PROM starting byte-address.
The ReadE2-Command can be triggered only by the µ-Processor. It stops automatically when all data has
been delivered.
Note: It is strictly recommended to use only the described E²PROM address area.
109
Philips Semiconductors Product Specification Rev. 3.2 December 2005
16.6.1.1 Overview
Reads data from E²PROM and initialises the Start Address LSB
LoadConfig 07 -
registers Start Address MSB
The LoadConfig-Command interprets the first two bytes found in the FIFO buffer as E²PROM starting
byte-address. When the two argument -bytes are available in the FIFO buffer, 32 bytes from the E²PROM are
copied into the SL RC400 control and configuration registers, starting at the given E²PROM starting
byte-address. The LoadConfig-Command can only be started by the µ-Processor. It stops automatically
when all relevant registers have been copied.
Note: It is strictly recommended to use only the described E²PROM address area.
The 32 bytes of E²PROM content, beginning with the E²PROM starting byte-address, is written to the
SL RC400 register 10hex up to register 2Fhex (for the E²PROM memory organisation see 6).
Note: The procedure for the register assignment is the same as it is for the Start Up Initialisation (see 11.3).
The difference is, that the E²PROM starting byte-address for the Start Up Initialisation is fixed to 10hex
(Block 1, Byte 0). With the LoadConfig-Command it can be chosen.
Valid E²PROM starting byte-addresses are in the range from 10hex up to 60hex .
16.6.2.1 Overview
The CalcCRC-Command takes all data from the FIFO buffer as input bytes for the CRC-Coprocessor. All
data stored in the FIFO buffer before the command is started will be processed. This command does not
return any data via the FIFO buffer, but the content of the CRC-register can be read back via the
CRCResultLSB-register and the CRCResultMSB-register. The CalcCRC-Command can only be started by
the µ-Processor. It does not stop automatically but has to be stopped explicitly by the µ-Processor with the
Idle-Command. If the FIFO buffer is empty, the CalcCRC-Command waits for further input from the FIFO
buffer.
Note: Do not use this command to calculate the Quit value for I?CODE1 tag’s because this would terminate
the Transceive command.
110
Philips Semiconductors Product Specification Rev. 3.2 December 2005
The status flag CRCReady indicates, that the CRC-Coprocessor has finished processing of all data bytes
found in the FIFO buffer. With the CRCReady flag setting to 1, an interrupt is requested with TxIRq being set.
This supports interrupt driven usage of the CRC-Coprocessor.
When CRCReady and TxIRq are set to 1, respectively, the content of the CRCResultLSB- and
CRCResultMSB-register and the flag CRCErr is valid.
The CRCResultLSB- and CRCResultMSB-register hold the content of the CRC register, the CRCErr flag
indicates CRC validity for the processed data.
If any error is detected during command execution, this is shown by setting the status flag Err in the
PrimaryStatus Register. For information about the cause of the error, the µ-Processor may evaluate the
status flags in the ErrorFlag Register.
111
Philips Semiconductors Product Specification Rev. 3.2 December 2005
17 TYPICAL APPLICATION
The figure below shows a typical application, where the antenna is direct connected to the SL RC400:
C0 C2a
µProcessor
Data Bus TVSS
IRQ
IRQ
SL RC400
C0 C2b
TX2
L0 C1 R1'
RX
R1
C3
DVSS OSCIN OSCOUT AVSS VMID
R2
C4
100 nF
13.56 MHz
15 pF 15 pF
Figure 17-1: Circuit Diagram for Application Example: Direct Matched Antenna
112
Philips Semiconductors Product Specification Rev. 3.2 December 2005
The matching circuit consists of an EMC low pass filter (L0 and C0), a matching circuitry (C1 and C2), and a
receiving circuit (R1, R2, C3 and C4), and the antenna itself.
For more detailed information about designing and tuning an antenna please refer to the Application Note
’MIFARE and I?CODE MICORE reader IC family; Directly Matched Antenna Design’
The I?CODE system operates at a frequency of 13.56 MHz. This frequency is generated by a quartz
oscillator to clock the SL RC400 and is also the basis for driving the antenna with the 13.56 MHz energy
carrier. This will not only cause emitted power at 13.56 MHz but will also emit power at higher harmonics.
The international EMC regulations define the amplitude of the emitted power in a broad frequency range.
Thus, an appropriate filtering of the output signal is necessary to fulfil these regulations.
A multi-layer board it is recommended to implement a low pass filter as shown in the circuit above. The low
pass filter consists of the components L0 and C0. The recommended values are given in the above
mentioned application notes.
Note: To achieve best performance all components shall have at least the quality of the recommended ones.
Note: The layout has a major influence on the overall performance of the filter.
Due to the impedance transformation of the given low pass filter, the antenna coil has to be matched to a
certain impedance. The matching elements C1 and C2 can be estimated and have to be fine tuned
depending on the design of the antenna coil.
The correct impedance matching is important to provide the optimum performance. The overall Quality factor
has to be considered to guarantee a proper I?CODE communication scheme. Environmental influences have
to considered as well as common EMC design rules.
Note: Do not exceed the current limits ITVDD, otherwise the chip might be destroyed.
Note: The overall 13.56MHz RFID proximity antenna design with the SL RC400 chip is straight forward and
doesn’t require a special RF-know how. However, all relevant parameters have to be considered to
guarantee an overall optimum performance together with international EMC compliance.
113
Philips Semiconductors Product Specification Rev. 3.2 December 2005
The internal receiving concept of the SL RC400 makes use of both side-bands of the sub-carrier load
modulation of the label response. No external filtering is required.
It is recommended to use the internally generated VMID potential as the input potential of pin RX. This DC
voltage level of VMID has to be coupled to the Rx-pin via R2. To provide a stable DC reference voltage a
capacitance C4 has to be connected between VMID and ground.
Considering the (AC) voltage limits at the Rx-pin the AC voltage divider of R1 + C3 and R2 has to be
designed. Depending on the antenna coil design and the impedance matching the voltage at the antenna coil
varies from antenna design to antenna design. Therefore the recommended way to design the receiving
circuit is to use the given values for R1, R2, and C3 from the above mentioned Application Note, and adjust
the voltage at the Rx-pin by varying R1 within the given limits.
The precise calculation of the antenna coils’ inductance is not practicable but the inductance can be
estimated using the following formula. We recommend designing an antenna either with a circular or
rectangular shape.
l 1, 8
L1 [nH ] = 2 ⋅ l 1 [cm ] ⋅ ln 1 − K N 1
D1
l1 ............. Length of one turn of the conductor loop
D1 ............ Diameter of the wire or width of the PCB conductor respectively
K ............. Antenna Shape Factor (K = 1,07 for circular antennas and K = 1,47 for square antennas)
N1 ............ Number of turns
ln............. Natural logarithm function
The actual values of the antenna inductance, resistance, and capacitance at 13.56 MHz depend on
various parameters like:
Therefore a measurement of those parameters under real life conditions, or at least a rough measurement
and a tuning procedure is recommended to guarantee the optimum performance. For details refer to the
above mentioned application notes.
114
Philips Semiconductors Product Specification Rev. 3.2 December 2005
18 TEST SIGNALS
18.1 General
The SL RC400 allows different kind of signal measurements. These measurements can be used to check the
internally generated and received signals using the possibilities of the serial signal switch as described in
chapter 15.
Furthermore, with the SL RC400 the user may select internal analog signals to measure them at pin AUX
and internal digital signals to observe them on pin SIGOUT by register selections. These measurements can
be helpful during the design-in phase to optimise the receiver’s behaviour or for test purpose.
Using the serial signal switch at pin SIGOUT the user may observe data send to the label or data received
from the label. The following tables give an overview of the different signals available.
115
Philips Semiconductors Product Specification Rev. 3.2 December 2005
The analog test signals may be routed to pin AUX by selecting them with the register bits TestAnaOutSel.
116
Philips Semiconductors Product Specification Rev. 3.2 December 2005
Digital test signals may be routed to pin SIGOUT by setting bit SignalToSIGOUT to 1. A digital test signal
may be selected via the register bits TestDigiSignalSel in Register TestDigiSelect.
The signals selected by a certain TestDigiSignalSel setting is shown in the table below:
If no test signals are used, the value for the TestDigiSel-Register shall be 00hex .
Note: All other values of TestDigiSignalSel are for production test purposes only.
117
Philips Semiconductors Product Specification Rev. 3.2 December 2005
Fig. 17 shows the answer of an I•CODE1 Label IC to a unselected read command using the Qclock
receiving path.
RX –Reference is given to show the Manchester modulated signal at the RX pin. This signal is demodulated
and amplified in the receiver circuitry VRXAmpQ shows the amplified side band signal having used the Q-
Clock for demodulation. The signals VCorrDQ and VCorrNQ generated in the correlation circuitry are
evaluated and digitised in the evaluation and digitizer circuitry. VEvalR and VEvalL show the evaluation
signal of the right and left half bit. Finally, the digital test-signal S_data shows the received data which is
send to the internal digital circuit and S_valid indicates that the received data stream is valid.
VrxAmpQ
VcorrDQ
VcorrNQ
VevalR
VevalL
Sdata
50µsec/Dev.
SValid
500µsec/Dev.
118
Philips Semiconductors Product Specification Rev. 3.2 December 2005
19 ELECTRICAL CHARACTERISTICS
119
Philips Semiconductors Product Specification Rev. 3.2 December 2005
Pins D0 to D7, A0 and A1 have TTL input characteristics and behave as defined in the following table.
The digital input pins NCS, NWR, NRD, ALE and A2 have Schmitt-Trigger characteristics, and behave as
defined in the following table.
Pin RSTPD has Schmitt-Trigger CMOS characteristics. In addition, it is internally filtered with an RC-low-
pass filter, which causes a relevant propagation delay for the reset signal:
120
Philips Semiconductors Product Specification Rev. 3.2 December 2005
Pins D0 to D7, SIGOUT and IRQ have TTL output characteristics and behave as defined in the following
table.
The source conductance of the antenna driver pins TX1 and TX2 for driving the HIGH level can be
configured via GsCfgCW in the CwConductance Register, while their source conductance for driving the
LOW level is constant.
121
Philips Semiconductors Product Specification Rev. 3.2 December 2005
19.5.1 AC SYMBOLS
Each timing symbol has five characters. The first character is always 't' for time. The other characters
indicate the name of a signal or the logic state of that signal (depending on position):
122
Philips Semiconductors Product Specification Rev. 3.2 December 2005
tLHLL
ALE
tCLWL
tWHCH
NCS
tLLWL
NWR
NRD
tWLDV tWHDX
tAVLL tLLAX
tRLDV tRHDZ
tAVWL t WHAX
Separated Addressbus
A0 ... A2 A0 ... A2
Note: For separated address and data bus the signal ALE is not relevant and the multiplexed addresses on the data bus
don’t care.
For the multiplexed address and data bus the address lines A0 to A2 have to be connected as described in 4.3.
123
Philips Semiconductors Product Specification Rev. 3.2 December 2005
tLHLL
ALE
tCLSL tSHCH
NCS
tRVSL tSHRX
R/NW
tLLSL
NDS
tSLDV,R tSHDX
tAVLL tLLAX
tSLDV,W tSHDZ
tAVSL tSHAX
Separated Addressbus
A0 ... A2 A0 ... A2
124
Philips Semiconductors Product Specification Rev. 3.2 December 2005
t CLSL tSHCH
NCS
tRVSL tSHRX
nWrite
t SLSH
nDStrb
nAStrb
t SLDV,R tSHDX
t SLDV,W tSHDZ
D0 ... D7
D0 ... D7
A0 ... A7
tSLWH tSHWL
nWait
125
Philips Semiconductors Product Specification Rev. 3.2 December 2005
The clock applied to the SL RC400 acts as time basis for the coder and decoder of the synchronous system.
Therefore stability of clock frequency is an important factor for proper performance. To obtain highest
performance, clock jitter shall be as small as possible. This is best achieved using the internal oscillator
buffer with the recommended circuitry (see 12).
126
Philips Semiconductors Product Specification Rev. 3.2 December 2005
2
20 E PROM CHARACTERISTICS
127
Philips Semiconductors Product Specification Rev. 3.2 December 2005
21 PACKAGE OUTLINES
21.1 SO32
SO32: plastic small outline package; 32 leads; body width 7.5 mm SOT287-1
D E A
X
c
y HE v M A
32 17
Q
A2 A
A1 (A3 )
pin 1 index
θ
Lp
1 16 L
wM detail X
e bp
0 5 10 mm
scale
mm 2.65 0.3 2.45 0.25 0.49 0.27 20.7 7.6 10.65 1.1 1.2 0.95
1.27 1.4 0.25 0.25 0.1 o
0.1 2.25 0.36 0.18 20.3 7.4 10.00 0.4 1.0 0.55 8
0.012 0.096 0.02 0.011 0.81 0.30 0.419 0.043 0.047 0.037 0o
inches 0.10 0.01 0.050 0.055 0.01 0.01 0.004
0.004 0.086 0.01 0.007 0.80 0.29 0.394 0.016 0.039 0.022
Note
1. Plastic or metal protrusions of 0.15 mm maximum per side are not included.
Designation: Description:
µ-Processor Micro Processor
E²PROM Electrically Erasable Programmable Read Only Memory
EOF End of Frame
FWT Frame Waiting Time: maximum time delay between last bit transmitted by
the reader and first bit received from the label’s response.
I?CODE A family of hard-wired logic contactless label ICs. The protocol of these
labels is according to I•CODE1 and ISO 15693. On top they use a fixed set
of commands.
POR Power On Reset: triggers a reset, caused by a rising edge on a supply pin.
ROM Read Only Memory
SOF Start of Frame
129
Philips Semiconductors Product Specification Rev. 3.2 December 2005
23 DEFINITIONS
Objective specification This data sheet contains target or goal specifications for product development.
Preliminary specification This data sheet contains preliminary data; supplementary data may be
published later.
Product specification This data sheet contains final product specifications.
Limiting values
Limiting values given are in accordance with the Absolute Maximum Rating System (IEC 134). Stress
above one or more of the limiting values may cause permanent damage to the device. These are stress
ratings only and operation of the device at these or at any other conditions above those given in the
Characteristics section of the specification is not implied. Exposure to limiting values for extended
periods may affect device reliability.
Application information
Where application information is given, it is advisory and does not form part of the specification.
These products are not designed for use in life support appliances, devices, or systems where malfunction of
these products can reasonably be expected to result in personal injury. Philips customers using or selling
these products for use in such applications do so on their own risk and agree to fully indemnify Philips for
any damages resulting from such improper use or sale.
130
Philips Semiconductors Product Specification Rev. 3.2 December 2005
25 REVISION HISTORY
131
Philips Semiconductors - a worldwide company
Contact Information
All rights are reserved. Reproduction in whole or in part is prohibited without the prior written consent of the copyright owner.
The information presented in this document does not form part of any quotation or contract, is believed to be accurate and reliable and may be changed
without any notice. No liability will be accepted by the publisher for any consequence of its use. Publication thereof does not convey nor imply any license
under patent - or other industrial or intellectual property rights.
PHILIPS
SEMICONDUCTORS