CR14_10 STMICROELECTRONICS | Alldatasheet
Document overview
- Manufacturer or author: Provided By ALLDATASHEET.COM(FREE DATASHEET DOWNLOAD SITE)
- PDF pages: 47
Technical content
Datasheet sections
- 1 Summary description
- 2 Signal description
- 2.1 Oscillator (OSC1, OSC2)
- 2.2 Antenna output driver (RF OUT)
- 2.3 Antenna input filter (RF IN)
- 2.4 Transmitter reference voltage (V REF)
- 2.5 Serial clock (SCL)
- 2.6 Serial data (SDA)
- 2.7 Chip enable (E0, E1, E2)
- 2.8 Power supply (V
- 3 CR14 registers
- 3.1 Parameter register (00h)
- 3.2 Input/Output Frame Register (01h)
- 3.3 Slot marker register (03h)
- 4 CR14 I²C protocol description
- 4.1 I²C start condition
- 4.2 I²C stop condition
- 4.3 I²C acknowledge bit (ACK)
- 4.4 I²C data input
- 4.5 I²C memory addressing
- 4.6 CR14 I²C write operations
- 4.7 CR14 I²C read operations
- 5 Applying the I²C protocol to the CR14 registers
- 5.1 I²C parameter register protocol
- 5.2 I²C input/output frame register protocol
- 5.3 I²C slot marker register protocol
- 5.4 Addresses above location 06h
Features
■ Single 5 V ±500 mV supply voltage ■ SO16N package ■ Contactless communication – ISO14443 type-B protocol – 13.56MHz carrier frequency using an external oscillator – 106 Kbit/s data rate – 36-byte input/output frame register – Supports frame answer with/without SOF/EOF – CRC generation and check – Automated ST anti-collision exchange ■ I²C communication – Two-wire I²C serial interface – Supports 400 kHz protocol – 3 chip enable pins – Up to 8 CR14 connected on the same bus SO16 (MQ) 150 mils width
6.1 Output RF data transfer from the CR14 to the PICC (request frame) . . . 26
Table 13. RF Table 15. SO16 narrow - 16 lead plastic small outline, 150 mils body width,
1 Summary description
The CR14 is a contactless coupler that is compliant with the short range ISO14443 type-B standard. It is controlled using the two wire I²C bus. The CR14 generates a 13.56 MHz signal on an external antenna. Transmitted data are modulated using Amplitude Shift Keying (ASK). Received data are demodulated from the PICC (Proximity integrated Coupling Card) load variation signal, induced on the antenna, using Bit Phase Shift Keying (BPSK) of a 847kHz sub-carrier. The Transmitted ASK wave is 10% modulated. The Data transfer rate between the CR14 and the PICC is 106 Kbit/s in both transmission and reception modes. The CR14 follows the ISO14443 type-B recommendation for Radio frequency power and signal interface. The CR14 is specifically designed for short range applications that need disposable and reusable products. The CR14 includes an automated anti-collision mechanism that allows it to detect and select any ST short range memories that are present at the same time within its range. The anti-collision mechanism is based on the STMicroelectronics probabilistic scanning method. The CR14 provides a complete analog interface, compliant with the ISO14443 type-B recommendations for Radio-Frequency power and signal interfacing. With it, any ISO14443 type-B PICC products can be powered and have their data transmission controlled via a simple antenna. The CR14 is fabricated in STMicroelectronics High Endurance Single Poly-silicon CMOS technology. The CR14 is organized as 4 different blocks (see Figure 2):
- The I²C bus controller. It handles the serial connection with the application host. It is compliant with the 400kHz I²C bus specification, and controls the read/write access to all the CR14 registers.
- The RAM buffer. It is bi-directional. . It stores all the request frame Bytes to be transmitted to the PICC, and all the received Bytes sent by the PICC on the answer frame.
- The transmitter. It powers the PICCs by generating a 13.56MHz signal on an external antenna. The resulting field is 10% modulated using ASK (amplitude shift keying) for outgoing data.
- The receiver. It demodulates the signal generated on the antenna by the load variation of the PICC. The resulting signal is decoded by a 847kHz BPSK (binary phase shift keying) sub-carrier decoder. The CR14 is designed to be connected to a digital host (Microcontroller or ASIC). This host has to manage the entire communication protocol in both transmit and receive modes, through the I²C serial bus.
Figure 1. Logic diagram Table 1. Signal names
2 Signal description
See Figure 1: Logic diagram, and Table 1: Signal names, for an overview of the signals connected to this device.
2.1 Oscillator (OSC1, OSC2)
The OSC1 and OSC2 pins are internally connected to the on-chip oscillator circuit. The OSC1 pin is the input pin, the OSC2 is the output pin. For correct operation of the CR14, it is required to connect a 13.56MHz quartz crystal across OSC1 and OSC2. If an external clock is used, it must be connected to OSC1 and OSC2 must be left open.
2.2 Antenna output driver (RF OUT)
The Antenna Output Driver pin, RFOUT, generates the modulated 13.56MHz signal on the antenna. Care must be taken as it will not withstand a short-circuit. RFOUT has to be connected to the antenna circuitry as shown in Figure 4: CR14 application schematic The LRC antenna circuitry must be connected across the RFOUT pin and GND.
2.3 Antenna input filter (RF IN)
The antenna input filter of the CR14, RFIN, has to be connected to the external antenna through an adapter circuit, as shown in Figure 4. The input filter demodulates the signal generated on the antenna by the load variation of the PICC. The resulting signal is then decoded by the 847kHz BPSK decoder.
2.4 Transmitter reference voltage (V REF)
The Transmitter Reference Voltage input, VREF, provides a reference voltage used by the output driver for ASK modulation. The Transmitter Reference Voltage input should be connected to an external capacitor, as shown in Figure 4.
2.5 Serial clock (SCL)
The SCL input pin is used to strobe all I²C data in and out of the CR14. In applications where this line is used by slave devices to synchronize the bus to a slower clock, the master must have an open drain output, and a pull-up resistor must be connected from the Serial Clock (SCL) to V CC. (Figure 5 indicates how the value of the pull-up resistor can be calculated). In most applications, though, this method of synchronization is not employed, and so the pull-up resistor is not necessary, provided that the master has a push-pull (rather than open drain) output.
2.6 Serial data (SDA)
indicates how the value of the pull-up resistor can be calculated).
2.7 Chip enable (E0, E1, E2)
(note that the VIL and VIH levels for the inputs are CMOS compatible, not TTL compatible). down resistors connected to each inputs.
2.8 Power supply (V CC, GND, GND_RF)
Power is supplied to the CR14 using the VCC, GND and GND_RF pins. VCC is the Power Supply pin that supplies the power (+5V) for all CR14 operations. The GND and GND_RF pins are ground connections. They must be connected together. Ground pin and the GND_REF Ground pin to filter the power line, as shown in Figure 4. Figure 4. CR14 application schematic
Figure 5. Maximum R L value versus bus capacitance (CBUS) for an I²C bus
3 CR14 registers
- Parameter Register
- Input/Output Frame Register
- Slot Marker Register The other 3 registers are located at addresses 02h, 04h and 05h. They are “ST Reserved”, and must not be used in end-user applications. In the I²C protocol, all data Bytes are transmitted Most Significant Byte first, with each Byte transmitted Most significant bit first.
3.1 Parameter register (00h)
standard ISO14443 type-B configuration. Table 2. CR14 control registers W Store and send request frame to the PICC. ST Reserved, must not be used. Table 3. Parameter register bits description
0 ISO14443 type-B frame management
1 RFU(1)
3.2 Input/Output Frame Register (01h)
through to Byte 35 (see Table 4). It is located at the I²C address 01h. Register is used to store the frame length for both transmission and reception. is not sent back on the I²C bus. set to FFh, and the data Bytes are discarded and not appended in the register.
0 Answer PICC Frames are delimited by SOF and EOF
1 Answer PICC Frames do not provide SOF and EOF
- RFU = Reserved for Future Use.
Table 3. Parameter register bits description (continued)
3.3 Slot marker register (03h)
Slot Bit is set to ‘0’, and the corresponding Slot_Register is set to FFh. and Bytes 3 to 18 store the corresponding Chip_ID or error code. can be accessed by reading the Input/Output Frame Register at the I²C address 01h. Table 4. Input/output frame register description Table 5. Slot marker register description
1: No error detected. The Chip_ID stored in the Slot register is valid. Table 5. Slot marker register description (continued)
4 CR14 I²C protocol description
interface that uses a bi-directional data bus and serial clock. synchronized to the serial clock.
- the Device Code (first four bits)
- plus three bits corresponding to the states of the three Chip Enable inputs, E2, E1 and E0, respectively When data is written to the CR14, the device inserts an acknowledge bit (9th bit) after the bus master’s 8-bit transmission. When the bus master reads data, it also acknowledges the receipt of the data Byte by inserting an acknowledge bit (9th bit). Data transfers are terminated by a STOP condition after an ACK for Write, or after a NoACK for Read. The CR14 supports the I²C protocol, as summarized in Figure 6. Any device that sends data on to the bus, is defined as a transmitter, and any device that reads the data, as a receiver. The device that controls the data transfer is known as the master, and the other, as the slave. A data transfer can only be initiated by the master, which also provides the serial clock for synchronization. The CR14 is always a slave device in all I²C communications. All data are transmitted Most Significant Bit (MSB) first.
4.1 I²C start condition
Table 6. Device select code
CR14 CR14 I²C protocol description Doc ID 11922 Rev 2 17/47 The CR14 continuously monitors the SDA and SCL lines for a START condition (except during Radio Frequency data exchanges), and will not respond unless one is sent.
4.2 I²C stop condition
STOP is identified by a Low-to-High transition of the Serial Data line, SDA, while the Serial Clock, SCL, is stable in the High state. A STOP condition terminates communications between the CR14 and the bus master. A STOP condition at the end of an I²C Read command, after (and only after) a NoACK, forces the CR14 into its stand-by state. A STOP condition at the end of an I²C Write command triggers the Radio Frequency data exchange between the CR14 and the PICC.
4.3 I²C acknowledge bit (ACK)
An acknowledge bit is used to indicate a successful data transfer on the I²C bus. The bus transmitter, either master or slave, releases the Serial Data line, SDA, after sending 8 bits of data. During the 9th clock pulse the receiver pulls the SDA line Low to acknowledge the receipt of the 8 data bits.
4.4 I²C data input
During data input, the CR14 samples the SDA bus signal on the rising edge of the Serial Clock, SCL. For correct device operation, the SDA signal must be stable during the Low-to- High Serial Clock transition, and the data must change only when the SCL line is Low.
Figure 6. I²C bus protocol
4.5 I²C memory addressing
To start up communication with the CR14, the bus master must initiate a START condition. are the Device Type Identifier. For the CR14, these bits are defined as shown in Table 6. corresponding device returns an acknowledgment on the SDA bus during the 9th bit time. generate a No-ACK. They deselect themselves from the bus and go into stand-by mode.
4.6 CR14 I²C write operations
the data Bytes that are to be written. the transfer by generating a STOP condition. the Radio Frequency data exchange between the CR14 and the PICC to be started. During the Radio Frequency data exchange, the CR14 disconnects itself from the I²C bus.
- Initial condition: a Radio Frequency data exchange is in progress.
- Step 1: the master issues a START condition followed by the first Byte of the new instruction (Device Select Code plus R/W bit).
- Step 2: if the CR14 is busy, no ACK is returned and the master goes back to Step 1. If the CR14 has completed the Radio Frequency data exchange, it responds with an ACK, indicating that it is ready to receive the second part of the next instruction (the first Byte of this instruction being sent during Step 1).
Figure 7. CR14 I²C write mode sequence
Figure 8. I²C polling flowchart using ACK
4.7 CR14 I²C read operations
Select Code and the R/W bit set to ’1’. data Byte of the addressed register. immediately follows the dummy Write command.
transfer and switches to stand-by mode. Figure 9. CR14 I²C read modes sequences
5 Applying the I²C protocol to the CR14 registers
5.1 I²C parameter register protocol
becomes active after the I²C STOP condition. sends the Parameter Register contents until it receives a NoACK from the I²C Host. register where the Read is to take place. Figure 10. Host-to-CR14 transfer: I²C write to parameter register Figure 11. CR14-to-host transfer: I²C random address read from parameter register Figure 12. CR14-to-host transfer: I²C current address read from parameter register
1010 XXX 0 0 h data
1010 XXX
5.2 I²C input/output frame register protocol
Input/Output Frame Register. Input/Output Frame Register. The request frame is over-written by the answer frame. Figure 14 shows how to read an N-Byte PICC answer frame. The two CRC Bytes generated by the PICC are not stored. and starts outputting from the start of the Input/Output Frame Register again. register where the Read is to take place. Figure 13. Host-to-CR14 transfer: I²C write to I/O frame register for ISO14443B Figure 14. CR14-to-host transfer: I²C random address read from I/O frame register for
1010 X X X 0 1 h N
Figure 15. CR14-to-host transfer: I²C current address read from I/O frame register for ISO14443B
5.3 I²C slot marker register protocol
command loop (See Figure 16 for a description of the command). the Input/Output Frame Register. Address and Current Address Read modes until NoACK is generated by the I²C Host. Register can be read by the host by using I²C Random Address Read. Figure 16. Host-to-CR14 transfer: I²C write to slot marker register Figure 17. CR14-to-host transfer: I²C random address read from slot marker register
1010 XXX 0 0 h F F h
Figure 18. CR14-to-host transfer: I²C current address read from slot marker register
5.4 Addresses above location 06h
a NoACK during the 9th bit time. The SDA line stays High until the STOP condition is issued. the Device Select Code after the START condition, and deselects itself from the bus.
6 CR14 ISO14443 type-B radio frequency data transfer
6.1 Output RF data transfer from the CR14 to the PICC (request
in Figure 19. The data transfer rate is 106 kbit/s. Figure 19. Wave transmitted using ASK modulation
6.2 Transmission format of request frame characters
Frame (EOF), constitute a Request Frame, as shown in Figure 26. defined in the ISO14443 type-B.
Figure 20. CR14 request frame character format
6.3 Request start of frame
- a falling edge,
- followed by ten Elementary Time Units (ETU) each containing a logical ‘0’
- followed by a single rising edge
- followed by two ETUs, each containing a logical ‘1’.
Figure 21. Request start of frame
6.4 Request end of frame
- a falling edge,
- followed by ten Elementary Time Units (ETU) containing each a logical ‘0’,
- followed by a single rising edge.
Figure 22. Request end of frame Table 7. CR14 request frame character format
6.5 Input RF data transfer from the PICC to the CR14 (answer
decoded by the RFIN circuitry. The modulation is obtained by modifying the PICC current consumption (load modulation). and decodes the information received from the PICC. (from ‘0’ to ‘1’ or from ‘1’ to ‘0’) are encoded by phase shift keying the sub-carrier. Figure 23. Wave received using BPSK sub-carrier modulation
6.6 Transmission format of answer frame characters
data transfer rate is 106 kbit/s. provided that these Frames are correctly set in the Parameter Register. (See Figure 26).
6.7 Answer start of frame
- Ten or eleven Elementary Time Units (ETU) each containing a logical ‘0’,
- Two ETUs containing a logical ‘1’.
Figure 24. Answer start of frame
6.8 Answer end of frame
- Ten or eleven Elementary Time Units (ETU) each containing a logical ‘0’,
- Two ETUs containing a logical ‘1’
Figure 25. Answer end of frame
6.9 Transmission frame
Figure 26. Example of a complete transmission frame
6.10 CRC
further information, please see Appendix A on page 44. The two CRC Bytes are present in all Request and Answer Frames, just before the EOF . The CRC is calculated on all the Bytes between the SOF and the CRC Bytes. valid. If it is invalid, it discards the frame and does not answer the CR14. it is invalid, it stores the value FFh in the Input/Output Frame Register. Figure 27. CRC tr ansmission rules
7 Tag access using the CR14 coupler
These values are linked to the logic levels applied to the E2, E1 and E0 pads of the CR14.
7.1 Standard TAG comm and access description
Input/Output Frame Register. adds them during the RF transmission. CR14 waits for the PICC to send an answer frame. the CR14 checks the CRC and reconnects itself to the I²C bus. Read on the I²C bus, as specified in Figures 14 and 15. 5 and b6), the Input/Output Frame Register is set as specified in Table 4. Figure 28. Standard TAG command: request frame transmission
Figure 29. Standard TAG command: answer frame reception Figure 30. Standard TAG command: complete TAG access description
7.2 Anti-collision TAG sequence
The CR14 can identify an ST short range memory using a proprietary anti-collision system. in the Input/Output Frame Register, as specified in Table 4.
Figure 31. Anti-collision ST short range memory sequence (1)
Figure 32. Anti-collision ST short range memory sequence continued
8 Maximum rating
SURE Program and other relevant quality documents. Table 8. Absolute maximum ratings
9 DC and AC parameters
match the measurement conditions when relying on the quoted parameters. Figure 33. I²C AC testing I/O waveform
- Sampled only, not 100% tested.
Table 9. I²C AC measurement conditions Table 10. I²C Input Parameters (1,2) Table 11. I²C DC characteristics
Figure 34. I²C AC waveforms Table 11. I²C DC characteristics (continued)
Table 12. I²C AC characteristics
- Sampled only, not 100% tested.
- For a reSTART condition, or following a write cycle.
Figure 35. CR14 synchronous timing Table 13. RF OUT AC characteristics
- Data specified in the table above are estimat ed or target values. All values can be updated
during product qualification. Table 13. RF OUT AC characteristics (continued) Table 14. RF IN AC characteristics
- Data specified in the table above are estimated or target values. All values can be updated during product qualification.
In order to meet environmental requirements, ST offers these devices in different grades of ECOPACK® packages, depending on their level of environmental compliance. ECOPACK® specifications, grade definitions and product status are available at: www.st.com. ECOPACK® is an ST trademark.
Figure 36. SO16 narrow - 16 lead plastic small outline, 150 mils body width, Package
of this device, please contact your nearest ST Sales Office. Table 16. Ordering information scheme
ISO14443 type B CRC calculation CR14 44/47 Doc ID 11922 Rev 2 Appendix A ISO14443 type B CRC calculation #include <stdio.h> #include <stdlib.h> #include <string.h> #include <ctype.h> #define BYTEunsigned char #define USHORTunsigned short unsigned short UpdateCrc(BYTE ch, USHORT *lpwCrc) ch = (ch^(BYTE)((*lpwCrc) & 0x00FF)); ch = (ch^(ch<<4)); *lpwCrc = (*lpwCrc >> 8)^((USHORT)ch << 8)^((USHORT)ch<<3)^((USHORT)ch>>4); return(*lpwCrc); void ComputeCrc(char *Data, int Length, BYTE *TransmitFirst, BYTE *TransmitSecond) BYTE chBlock; USHORTt wCrc; wCrc = 0xFFFF; // ISO 3309 do chBlock = *Data++; UpdateCrc(chBlock, &wCrc); } while (--Length); wCrc = ~wCrc; // ISO 3309 *TransmitFirst = (BYTE) (wCrc & 0xFF); *TransmitSecond = (BYTE) ((wCrc >> 8) & 0xFF); return; int main(void) BYTE BuffCRC_B[10] = {0x0A, 0x12, 0x34, 0x56}, First, Second, i; printf("Crc-16 G(x) = x^16 + x^12 + x^5 + 1");
CR14 ISO14443 type B CRC calculation Doc ID 11922 Rev 2 45/47 printf("CRC_B of [ "); for(i=0; i<4; i++) printf("%02X ",BuffCRC_B[i]); ComputeCrc(BuffCRC_B, 4, &First, &Second); printf("] Transmitted: %02X then %02X.", First, Second); return(0);
Revision history
Table 17. Document revision history 16-Dec-2005 1 Initial release.