OM966302HNQL

OM9663 High performance NFC reader solution Rev. 3.0 — 9 December 2013 Product data sheet COMPANY PUBLIC 1. Introduction This document describes the functionality and electrical specifications of the contactless reader/writer IC OM9663. 2. General description The OM9663 is a highly integrated transceiver IC for contactless communication at 13.56 MHz. The OM9663 transceiver IC supports the following operating modes • Read/write mode supporting ISO/IEC 14443A/MIFARE • Read/write mode supporting ISO/IEC 14443B • Read/write mode supporting JIS X 6319-4 (comparable with FeliCa1 (see Section 21.5) scheme) • • • • Passive initiator mode according to ISO/IEC 18092 Read/write mode supporting ISO/IEC 15693 Read/write mode supporting ICODE EPC UID/ EPC OTP Read/write mode supporting ISO/IEC 18000-3 mode 3/ EPC Class-1 HF The OM9663’s internal transmitter is able to drive a reader/writer antenna designed to communicate with ISO/IEC 14443A/MIFARE cards and transponders without additional active circuitry. The digital module manages the complete ISO/IEC 14443A framing and error detection functionality (parity and CRC). The OM9663 supports MIFARE Classic 1K, MIFARE Classic 4K, MIFARE Ultralight, MIFARE Ultralight C, MIFARE PLUS and MIFARE DESFire products. The OM9663 supports MIFARE higher transfer speeds of up to 848 kbit/s in both directions. The OM9663 supports layer 2 and 3 of the ISO/IEC 14443B reader/writer communication scheme except anticollision. The anticollision needs to be implemented in the firmware of the host controller as well as in the upper layers. The OM9663 is able to demodulate and decode FeliCa coded signals.The FeliCa receiver part provides the demodulation and decoding circuitry for FeliCa coded signals. The OM9663 handles the FeliCa framing and error detection such as CRC. The OM9663 supports FeliCa higher transfer speeds of up to 424 kbit/s in both directions. 1. In the following the word FeliCa is used for JIS X 6319-4 OM9663 NXP Semiconductors High performance NFC reader solution The OM9663 is supporting the P2P passive initiator mode in accordance with ISO/IEC 18092. The OM9663 supports the vicinity protocol according to ISO/IEC15693, EPC UID and ISO/IEC 18000-3 mode 3/ EPC Class-1 HF. The following host interfaces are supported: • Serial Peripheral Interface (SPI) • Serial UART (similar to RS232 with voltage levels dependent on pin voltage supply) • I2C-bus interface (two versions are implemented: I2C and I2CL) The OM9663 supports the connection of a secure access module (SAM). A dedicated separate I2C interface is implemented for a connection of the SAM. The SAM can be used for high secure key storage and acts as a very performant crypto coprocessor. A dedicated SAM is available for connection to the OM9663. 3. Features and benefits                 OM9663 Product data sheet COMPANY PUBLIC High RF output power frontend IC for transfer speed up to 848 kbit/s Supports ISO/IEC 14443 A/MIFARE, ISO/IEC 14443 B and FeliCa P2P passive initiator mode in accordance with ISO/IEC 18092 Supports ISO/IEC15693, ICODE EPC UID and ISO/IEC 18000-3 mode 3/ EPC Class-1 HF Supports MIFARE Classic encryption in read/write mode Low-Power Card Detection Compliance to “EMV contactless protocol specification V2.0.1” on RF level can be achieved Antenna connection with minimum number of external components Supported host interfaces:  SPI up to 10 Mbit/s  I2C-bus interfaces up to 400 kBd in Fast mode, up to 1000 kBd in Fast mode plus  RS232 Serial UART up to 1228.8 kBd, with voltage levels dependent on pin voltage supply Separate I2C-bus interface for connection of a secure access module (SAM) FIFO buffer with size of 512 byte for highest transaction performance Flexible and efficient power saving modes including hard power down, standby and low-power card detection Cost saving by integrated PLL to derive system CPU clock from 27.12 MHz RF quartz crystal 3 V to 5.5 V power supply Up to 8 free programmable input/output pins Typical operating distance in read/write mode for communication to a ISO/IEC 14443A/MIFARE Card up to 12 cm, depending on the antenna size and tuning All information provided in this document is subject to legal disclaimers. © NXP B.V. 2013. All rights reserved. Rev. 3.0 — 9 December 2013 2 of 137 OM9663 NXP Semiconductors High performance NFC reader solution 4. Quick reference data Table 1. Quick reference data Symbol Parameter VDD supply voltage VDD(TVDD) TVDD supply voltage VDD(PVDD) PVDD supply voltage Ipd power-down current IDD supply current IDD(TVDD) TVDD supply current Tamb ambient temperature Tstg storage temperature Conditions [1] PDOWN pin pulled HIGH [2] [3][4] no supply voltage applied Min Typ Max Unit 3 5 5.5 V 3 5 5.5 V 3 5 5.5 V - 8 40 nA - 17 20 mA - 100 200 mA 25 +25 +85 C 40 +25 +100 C [1] VDD(PVDD) must always be the same or lower voltage than VDD. [2] Ipd is the sum of all supply currents [3] IDD(TVDD) depends on VDD(TVDD) and the external circuitry connected to TX1 and TX2. [4] Typical value: Assumes the usage of a complementary driver configuration and an antenna matched to 40  between pins TX1, TX2 at 13.56 MHz. 5. Ordering information Table 2. Ordering information Type number OM966301HN/TRAYB[1] OM966301HN/TRAYM[2] OM966302HN/TRAYB[1] OM966302HN/TRAYBM[2] OM966302HN/T/R[3] [1] Delivered in one tray [2] Delivered in five trays [3] Delivered on reel with 6000 pieces OM9663 Product data sheet COMPANY PUBLIC Package Name Description Version HVQFN32 plastic thermal enhanced very thin quad flat package; no SOT617-1 leads; MSL2, 32 terminals + 1 central ground; body 5  5  0.85 mm plastic thermal enhanced very thin quad flat package; no SOT617-1 leads; MSL1, 32 terminals + 1 central ground; body 5  5  0.85 mm All information provided in this document is subject to legal disclaimers. © NXP B.V. 2013. All rights reserved. Rev. 3.0 — 9 December 2013 3 of 137 OM9663 NXP Semiconductors High performance NFC reader solution 6. Block diagram The analog interface handles the modulation and demodulation of the antenna signals for the contactless interface. The contactless UART manages the protocol dependency of the contactless interface settings managed by the host. The FIFO buffer ensures fast and convenient data transfer between host and the contactless UART. The register bank contains the settings for the analog and digital functionality. REGISTER BANK ANTENNA ANALOG INTERFACE CONTACTLESS UART FIFO BUFFER SERIAL UART SPI I2C-BUS HOST 001aaj627 Fig 1. Simplified block diagram of the OM9663 25 PVDD 26 IFSEL0 27 IFSEL1 28 IF0 29 IF1 30 IF2 terminal 1 index area 31 IF3 32 IRQ 7. Pinning information TDO 1 24 SDA TDI 2 23 SCL TMS 3 22 CLKOUT TCK 4 SIGIN 5 SIGOUT 6 19 XTAL1 DVDD 7 18 TVDD VDD 8 17 TX1 21 PDOWN TVSS 16 TX2 15 20 XTAL2 VMID 14 RXN 13 RXP 12 AUX2 11 9 AVDD AUX1 10 33 VSS 001aam004 Transparent top view (1) Pin 33 VSS - heatsink connection Fig 2. OM9663 Product data sheet COMPANY PUBLIC Pinning configuration HVQFN32 (SOT617-1) All information provided in this document is subject to legal disclaimers. © NXP B.V. 2013. All rights reserved. Rev. 3.0 — 9 December 2013 4 of 137 OM9663 NXP Semiconductors High performance NFC reader solution 7.1 Pin description Table 3. Pin description Pin Symbol Type Description 1 TDO O test data output for boundary scan interface 2 TDI I test data input boundary scan interface 3 TMS I test mode select boundary scan interface 4 TCK I test clock boundary scan interface 5 SIGIN I Contactless communication interface output. 6 SIGOUT O Contactless communication interface input. 7 DVDD PWR digital power supply buffer [1] 8 VDD PWR power supply 9 AVDD PWR analog power supply buffer [1] 10 AUX1 O auxiliary outputs: Pin is used for analog test signal 11 AUX2 O auxiliary outputs: Pin is used for analog test signal 12 RXP I receiver input pin for the received RF signal. 13 RXN I receiver input pin for the received RF signal. 14 VMID PWR internal receiver reference voltage [1] 15 TX2 O transmitter 2: delivers the modulated 13.56 MHz carrier 16 TVSS PWR transmitter ground, supplies the output stage of TX1, TX2 17 TX1 O transmitter 1: delivers the modulated 13.56 MHz carrier 18 TVDD PWR transmitter voltage supply 19 XTAL1 I crystal oscillator input: Input to the inverting amplifier of the oscillator. This is pin is also the input for an externally generated clock (fosc = 27,12 MHz) 20 XTAL2 O crystal oscillator output: output of the inverting amplifier of the oscillator 21 PDOWN I Power Down 22 CLKOUT O clock output 23 SCL O Serial Clock line 24 SDA I/O Serial Data Line 25 PVDD PWR pad power supply 26 IFSEL0 I host interface selection 0 27 IFSEL1 I host interface selection 1 28 IF0 I/O interface pin, multifunction pin: Can be assigned to host interface RS232, SPI, I2C, I2C-L 29 IF1 I/O interface pin, multifunction pin: Can be assigned to host interface SPI, I2C, I2C-L 30 IF2 I/O interface pin, multifunction pin: Can be assigned to host interface RS232, SPI, I2C, I2C-L 31 IF3 I/O interface pin, multifunction pin: Can be assigned to host interface RS232, SPI, I2C, I2C-L 32 IRQ O interrupt request: output to signal an interrupt event 33 VSS PWR ground and heatsink connection [1] This pin is used for connection of a buffer capacitor. Connection of a supply voltage might damage the device. OM9663 Product data sheet COMPANY PUBLIC All information provided in this document is subject to legal disclaimers. © NXP B.V. 2013. All rights reserved. Rev. 3.0 — 9 December 2013 5 of 137 xxxxxxxxxxxxxxxxxxxxx xxxxxxxxxxxxxxxxxxxxxxxxxx xxxxxxx x x x xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx xxxxxxxxxxxxxxxxxxx xx xx xxxxx xxxxxxxxxxxxxxxxxxxxxxxxxxx xxxxxxxxxxxxxxxxxxx xxxxxx xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx xxxxxxxxxxxx x x xxxxxxxxxxxxxxxxxxxxx xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx xxxxx xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx xxxxxxxx xxxxxxxxxxxxxxxxxxxxxxxxx xxxxxxxxxxxxxxxxxxxx xxx NXP Semiconductors OM9663 Product data sheet COMPANY PUBLIC 8. Functional description SAM interface SDA SCL I2C, LOGICAL FIFO 512 Bytes EEPROM 8 kByte SPI host interfaces RESET LOGIC Rev. 3.0 — 9 December 2013 All information provided in this document is subject to legal disclaimers. IFSEL1 IFSEL0 PDOWN I2C IF0 REGISTERS IF1 RS232 IF2 STATEMACHINES IF3 SPI ANALOGUE FRONT-END VDD BOUNDARY SCAN VOLTAGE REGULATOR 3/5 V => 1.8 V AVDD POR RNG VSS PVDD TVDD TVSS AVDD DVDD TIMER0..3 INTERRUPT CONTROLLER TIMER4 (WAKE-UP TIMER) CRC Fig 3. Detailed block diagram of the OM9663 SIGIN/ SIGOUT CONTROL SIGIN SIGOUT RX DECOD ADC LFO PLL CLCOPRO SIGPRO CLKOUT AUX1 RX TX RXP VMID RXN TX2 TX1 OSC XTAL2 XTAL1 AUX2 001aam005 OM9663 6 of 137 © NXP B.V. 2013. All rights reserved. IRQ TX CODEC High performance NFC reader solution TCK TDI TMS TDO VOLTAGE REGULATOR 3/5 V => 1.8 V DVDD OM9663 NXP Semiconductors High performance NFC reader solution 8.1 Interrupt controller The interrupt controller handles the enabling/disabling of interrupt requests. All of the interrupts can be configured by firmware. Additionally, the firmware has possibilities to trigger interrupts or clear pending interrupt requests. Two 8-bit interrupt registers IRQ0 and IRQ1 are implemented, accompanied by two 8-bit interrupt enable registers IRQ0En and IRQ1En. A dedicated functionality of bit 7 to set and clear bits 0 to 6 in this interrupt controller registers is implemented. The OM9663 indicates certain events by setting bit IRQ in the register Status1Reg and additionally, if activated, by pin IRQ. The signal on pin IRQ may be used to interrupt the host using its interrupt handling capabilities. This allows the implementation of efficient host software. The following table shows the available interrupt bits, the corresponding source and the condition for its activation. The interrupt bit TimernIrq in register IRQ1 indicates an interrupt set by the timer unit. The setting is done if the timer underflows. The TxIrq bit in register IRq0 indicates that the transmission is finished. If the state changes from sending data to transmitting the end of the frame pattern, the transmitter unit sets the interrupt bit automatically. The bit RxIrq in register IRQ0 indicates an interrupt when the end of the received data is detected. The bit IdleIrq in register IRQ0 is set if a command finishes and the content of the command register changes to idle. The waterlevel defines both - minimum and maximum warning levels - counting from top and from bottom of the FIFO by a single value. The bit HiAlertIrq in register IRQ0 is set to logic 1 if the HiAlert bit is set to logic 1, that means the FIFO data number has reached the top level as configured by the bit WaterLevel. The bit LoAlertIrq in register IRQ0 is set to logic 1 if the LoAlert bit is set to logic 1, that means the FIFO data number has reached the bottom level as configured by the bit WaterLevel. The bit ErrIrq in register IRQ0 indicates an error detected by the contactless UART during receive. This is indicated by any bit set to logic 1 in register Error. The bit LPCDIrq in register IRQ0 indicates a card detected. The bit RxSOFIrq in register IRQ0 indicates a detection of a SOF or a subcarrier by the contactless UART during receiving. The bit GlobalIRq in register IRQ1 indicates an interrupt occurring at any other interrupt source when enabled. OM9663 Product data sheet COMPANY PUBLIC All information provided in this document is subject to legal disclaimers. © NXP B.V. 2013. All rights reserved. Rev. 3.0 — 9 December 2013 7 of 137 OM9663 NXP Semiconductors High performance NFC reader solution Table 4. OM9663 Product data sheet COMPANY PUBLIC Interrupt sources Interrupt bit Interrupt source Is set automatically, when Timer0Irq Timer Unit the timer register T0 CounterVal underflows Timer1Irq Timer Unit the timer register T1 CounterVal underflows Timer2Irq Timer Unit the timer register T2 CounterVal underflows Timer3Irq Timer Unit the timer register T3 CounterVal underflows TxIrq Transmitter a transmitted data stream ends RxIrq Receiver a received data stream ends IdleIrq Command Register a command execution finishes HiAlertIrq FIFO-buffer pointer the FIFO data number has reached the top level as configured by the bit WaterLevel LoAlertIrq FIFO-buffer pointer the FIFO data number has reached the bottom level as configured by the bit WaterLevel ErrIrq contactless UART a communication error had been detected LPCDIrq LPCD a card was detected when in low-power card detection mode RxSOFIrq Receiver detection of a SOF or a subcarrier GlobalIrq all interrupt sources will be set if another interrupt request source is set All information provided in this document is subject to legal disclaimers. © NXP B.V. 2013. All rights reserved. Rev. 3.0 — 9 December 2013 8 of 137 OM9663 NXP Semiconductors High performance NFC reader solution 8.2 Timer module Timer module overview The OM9663 implements five timers. Four timers -Timer0 to Timer3 - have an input clock that can be configured by register T(x)Control to be 13.56 MHz, 212 kHz, (derived from the 27.12 MHz quartz) or to be the underflow event of the fifth Timer (Timer4). Each timer implements a counter register which is 16 bit wide. A reload value for the counter is defined in a range of 0000h to FFFFh in the registers TxReloadHi and TxReloadLo. The fifth timer Timer4 is intended to be used as a wakeup timer and is connected to the internal LFO (Low Frequency Oscillator) as input clock source. The TControl register allows the global start and stop of each of the four timers Timer0 to Timer3. Additionally, this register indicates if one of the timers is running or stopped. Each of the five timers implements an individual configuration register set defining timer reload value (e.g. T0ReloadHi,T0ReloadLo), the timer value (e.g. T0CounterValHi, T0CounterValLo) and the conditions which define start, stop and clockfrequency (e.g. T0Control). The external host may use these timers to manage timing relevant tasks. The timer unit may be used in one of the following configurations: • • • • • Time-out counter Watch-dog counter Stop watch Programmable one-shot timer Periodical trigger The timer unit can be used to measure the time interval between two events or to indicate that a specific event has occurred after an elapsed time. The timer register content is modified by the timer unit, which can be used to generate an interrupt to allow an host to react on this event. The counter value of the timer is available in the registers T(x)CounterValHi, T(x)CounterValLo. The content of these registers is decremented at each timer clock. If the counter value has reached a value of 0000h and the interrupts are enabled for this specific timer, an interrupt will be generated as soon as the next clock is received. If enabled, the timer event can be indicated on the pin IRQ (interrupt request). The bit Timer(x)Irq can be set and reset by the host controller. Depending on the configuration, the timer will stop counting at 0000h or restart with the value loaded from registers T(x)ReloadHi, T(x)ReloadLo. The counting of the timer is indicated by bit TControl.T(x)Running. The timer can be started by setting bits TControl.T(x)Running and TControl.T(x)StartStopNow or stopped by setting the bits TControl.T(x)StartStopNow and clearing TControl.T(x)Running. Another possibility to start the timer is to set the bit T(x)Mode.T(x)Start, this can be useful if dedicated protocol requirements need to be fulfilled. OM9663 Product data sheet COMPANY PUBLIC All information provided in this document is subject to legal disclaimers. © NXP B.V. 2013. All rights reserved. Rev. 3.0 — 9 December 2013 9 of 137 OM9663 NXP Semiconductors High performance NFC reader solution 8.2.1 Timer modes 8.2.1.1 Time-Out- and Watch-Dog-Counter Having configured the timer by setting register T(x)ReloadValue and starting the counting of Timer(x) by setting bit TControl.T(x)StartStop and TControl.T(x)Running, the timer unit decrements the T(x)CounterValue Register beginning with the configured start event. If the configured stop event occurs before the Timer(x) underflows (e.g. a bit is received from the card), the timer unit stops (no interrupt is generated). If no stop event occurs, the timer unit continues to decrement the counter registers until the content is zero and generates a timer interrupt request at the next clock cycle. This allows to indicate to a host that the event did not occur during the configured time interval. 8.2.1.2 Wake-up timer The wake-up Timer4 allows to wakeup the system from standby after a predefined time. The system can be configured in such a way that it is entering the standby mode again in case no card had been detected. This functionality can be used to implement a low-power card detection (LPCD). For the low-power card detection it is recommended to set T4Control.T4AutoWakeUp and T4Control.T4AutoRestart, to activate the Timer4 and automatically set the system in standby. The internal low frequency oscillator (LFO) is then used as input clock for this Timer4. If a card is detected the host-communication can be started. If bit T4Control.T4AutoWakeUp is not set, the OM9663 will not enter the standby mode again in case no card is detected but stays fully powered. 8.2.1.3 Stop watch The elapsed time between a configured start- and stop event may be measured by the OM9663 timer unit. By setting the registers T(x)ReloadValueHi, T(x)reloadValueLo the timer starts to decrement as soon as activated. If the configured stop event occurs, the timers stops decrementing. The elapsed time between start and stop event can then be calculated by the host dependent on the timer interval TTimer:  T  Treload value  Timer value  * T Timer (1) If an underflow occurred which can be identified by evaluating the corresponding IRQ bit, the performed time measurement according to the formula above is not correct. 8.2.1.4 Programmable one-shot timer The host configures the interrupt and the timer, starts the timer and waits for the interrupt event on pin IRQ. After the configured time the interrupt request will be raised. 8.2.1.5 Periodical trigger If the bit T(x)Control.T(x)AutoRestart is set and the interrupt is activated, an interrupt request will be indicated periodically after every elapsed timer period. OM9663 Product data sheet COMPANY PUBLIC All information provided in this document is subject to legal disclaimers. © NXP B.V. 2013. All rights reserved. Rev. 3.0 — 9 December 2013 10 of 137 OM9663 NXP Semiconductors High performance NFC reader solution 8.3 Contactless interface unit The contactless interface unit of the OM9663 supports the following read/write operating modes: • • • • • • ISO/IEC14443A/MIFARE ISO/IEC14443B FeliCA ISO/IEC15693/ICODE ICODE EPC UID ISO/IEC 18000-3 mode 3/ EPC Class-1 HF BATTERY/POWER SUPPLY READER IC ISO/IEC 14443 A CARD MICROCONTROLLER reader/writer Fig 4. 001aal996 Read/write mode A typical system using the OM9663 is using a microcontroller to implement the higher levels of the contactless communication protocol and a power supply (battery or external supply). 8.3.1 ISO/IEC14443A/MIFARE functionality The physical level of the communication is shown in Figure 5. (1) ISO/IEC 14443 A READER ISO/IEC 14443 A CARD (2) 001aam268 (1) Reader to Card 100 % ASK, Miller Coded, Transfer speed 106 kbit/s to 848 kbit/s (2) Card to Reader, Subcarrier Load Modulation Manchester Coded or BPSK, transfer speed 106 kbit/s to 848 kbit/s Fig 5. ISO/IEC 14443 A/MIFARE read/write mode communication diagram The physical parameters are described in Table 5. OM9663 Product data sheet COMPANY PUBLIC All information provided in this document is subject to legal disclaimers. © NXP B.V. 2013. All rights reserved. Rev. 3.0 — 9 December 2013 11 of 137 OM9663 NXP Semiconductors High performance NFC reader solution Table 5. Communication overview for ISO/IEC 14443 A/MIFARE reader/writer Communication direction Signal type Reader to card (send data from the OM9663 to a card) fc = 13.56 MHz Transfer speed 106 kbit/s 212 kbit/s 424 kbit/s 848 kbit/s reader side modulation 100 % ASK 100% ASK 100% ASK 100% ASK bit encoding modified Miller encoding modified Miller encoding modified Miller encoding modified Miller encoding bit rate [kbit/s] fc / 128 fc / 64 fc / 32 fc / 16 subcarrier load modulation subcarrier load modulation subcarrier load modulation subcarrier load modulation fc / 16 fc / 16 fc / 16 fc / 16 Manchester encoding BPSK BPSK BPSK Card to reader card side (OM9663 receives data modulation from a card) subcarrier frequency bit encoding The OM9663 connection to a host is required to manage the complete ISO/IEC 14443 A/MIFARE protocol. Figure 6 shows the data coding and framing according to ISO/IEC 14443A /MIFARE. ISO/IEC 14443 A framing at 106 kBd start 8-bit data 8-bit data odd parity start bit is 1 8-bit data odd parity odd parity ISO/IEC 14443 A framing at 212 kBd, 424 kBd and 848 kBd start 8-bit data start bit is 0 even parity 8-bit data odd parity burst of 32 subcarrier clocks 8-bit data odd parity even parity at the end of the frame 001aak585 Fig 6. Data coding and framing according to ISO/IEC 14443 A The internal CRC coprocessor calculates the CRC value based on ISO/IEC 14443 A part 3 and handles parity generation internally according to the transfer speed. OM9663 Product data sheet COMPANY PUBLIC All information provided in this document is subject to legal disclaimers. © NXP B.V. 2013. All rights reserved. Rev. 3.0 — 9 December 2013 12 of 137 OM9663 NXP Semiconductors High performance NFC reader solution 8.3.2 ISO/IEC14443B functionality The physical level of the communication is shown in Figure 7. (1) ISO/IEC 14443 B READER ISO/IEC 14443 B CARD (2) 001aal997 (1) Reader to Card NRZ, Miller coded, transfer speed 106 kbit/s to 848 kbit/s (2) Card to reader, Subcarrier Load Modulation Manchester Coded or BPSK, transfer speed 106 kbit/s to 848 kbit/s Fig 7. ISO/IEC 14443 A/MIFARE read/write mode communication diagram The physical parameters are described in Table 6. Table 6. Communication overview for ISO/IEC 14443 B reader/writer Communication direction Signal type Reader to card (send data from the OM9663 to a card) fc = 13.56 MHz reader side modulation Transfer speed 106 kbit/s 212 kbit/s 424 kbit/s 848 kbit/s 10 % ASK 10 % ASK 10 % ASK 10 % ASK bit encoding NRZ NRZ NRZ NRZ bit rate [kbit/s] 128 / fc 64 / fc 32 / fc 16 / fc subcarrier load modulation subcarrier load modulation subcarrier load modulation subcarrier load modulation fc / 16 fc / 16 fc / 16 fc / 16 BPSK BPSK BPSK BPSK Card to reader card side (OM9663 receives data modulation from a card) subcarrier frequency bit encoding The OM9663 connected to a host is required to manage the complete ISO/IEC 14443 B protocol. The following Figure 8 “SOF and EOF according to ISO/IEC 14443 B” shows the ISO/IEC 14443B SOF and EOF. Start of Frame (SOF) sequence 9.44 μs UNMODULATED (SUB) CARRIER ''0'' ''0'' ''0'' ''0'' ''0'' ''0'' ''0'' ''0'' ''0'' ''0'' ''1'' ''1'' DATA End of Frame (EOF) sequence 9.44 μs LAST CHARACTER ''0'' ''0'' ''0'' ''0'' ''0'' ''0'' ''0'' ''0'' ''0'' ''0'' UNMODULATED (SUB) CARRIER 001aam270 Fig 8. OM9663 Product data sheet COMPANY PUBLIC SOF and EOF according to ISO/IEC 14443 B All information provided in this document is subject to legal disclaimers. © NXP B.V. 2013. All rights reserved. Rev. 3.0 — 9 December 2013 13 of 137 OM9663 NXP Semiconductors High performance NFC reader solution 8.3.3 FeliCa functionality The FeliCa mode is the general reader/writer to card communication scheme according to the FeliCa specification. The communication on a physical level is shown in Figure 9. FeliCa READER (PCD) 1. PCD to PICC 8-30 % ASK Manchester Coded, baudrate 212 to 424 kbaud FeliCa CARD (PICC) 2. PICC to PCD, >12 % Loadmodulation Manchester Coded, baudrate 212 to 424 kbaud Fig 9. 001aam271 FeliCa read/write communication diagram The physical parameters are described in Table 7. Table 7. Communication overview for FeliCa reader/writer Communication direction Signal type Transfer speed FeliCa FeliCa higher transfer speeds 212 kbit/s 424 kbit/s Reader to card (send data from the OM9663 to a card) fc = 13.56 MHz reader side modulation 8 % to 30 % ASK 8 % to 30 % ASK bit encoding Manchester encoding Manchester encoding bit rate fc/64 fc/32 Card to reader (OM9663 receives data from a card) card side load modulation 30/H^1.2 30/H^1.2 (H = field strength [A/m]) (H = field strength [A/m]) bit encoding Manchester encoding Manchester encoding The OM9663 needs to be connected to a dedicated host to be able to support the complete FeliCa protocol. 8.3.3.1 FeliCa framing and coding Table 8. FeliCa framing and coding Preamble (Hex.) 00 00 00 Sync (Hex.) 00 00 00 B2 Len n-Data CRC 4D To enable the FeliCa communication a 6 byte preamble (00h, 00h, 00h, 00h, 00h, 00h) and 2 bytes sync bytes (B2h, 4Dh) are sent to synchronize the receiver. The following Len byte indicates the length of the sent data bytes plus the LEN byte itself. The CRC calculation is done according to the FeliCa definitions with the MSB first. To transmit data on the RF interface, the host controller has to send the Len- and databytes to the OM9663's FIFO-buffer. The preamble and the sync bytes are generated by the OM9663 automatically and must not be written to the FIFO by the host controller. The OM9663 performs internally the CRC calculation and adds the result to the data frame. 8.3.4 ISO/IEC15693 functionality The physical parameters are described in Table 9. OM9663 Product data sheet COMPANY PUBLIC All information provided in this document is subject to legal disclaimers. © NXP B.V. 2013. All rights reserved. Rev. 3.0 — 9 December 2013 14 of 137 OM9663 NXP Semiconductors High performance NFC reader solution Table 9. Communication overview for ISO/IEC 15693 reader/writer reader to label Communication direction Signal type Reader to label (send reader side data from the OM9663 modulation to a card) bit encoding data rate Table 10. Transfer speed fc / 8192 kbit/s fc / 512 kbit/s 10 % to 30 % ASK or 100 % ASK 10 % to 30 % ASK 90 % to 100 % ASK 1/256 1/4 1,66 kbit/s 26,48kbit/s Communication overview for ISO/IEC 15693 reader/writer label to reader Communication direction Signal type Transfer speed Label to reader (OM9663 receives data from a card) fc = 13.56 MHz card side modulation 6.62 (6.67) kbit/s 13.24 kbit/s[1] not supported 26.48 52.96 kbit/s (26.69) kbit/s not supported single (dual) subcarrier load modulation single subcarrier load modulation ASK ASK bit length (s) [1] - - 37.76 (37.46) 18.88 bit encoding - - Manchester coding Manchester coding subcarrier frequency [MHz] - fc / 32 (fc / 28) fc / 32 - Fast inventory (page) read command only (ICODE proprietary command). pulse modulated carrier ~9.44 μs ~18.88 μs 0 1 2 3 4 . . . 2 . . . . . . . . . . 2 5 ~4,833 ms . . . . . . . . . . 2 2 2 2 5 5 5 5 2 3 4 5 001aam272 Fig 10. OM9663 Product data sheet COMPANY PUBLIC Data coding according to ISO/IEC 15693. standard mode reader to label All information provided in this document is subject to legal disclaimers. © NXP B.V. 2013. All rights reserved. Rev. 3.0 — 9 December 2013 15 of 137 OM9663 NXP Semiconductors High performance NFC reader solution 8.3.5 EPC-UID/UID-OTP functionality The physical parameters are described in Table 11. Table 11. Communication overview for EPC/UID Communication direction Signal type Transfer speed Reader to card (send data from the OM9663 to a card) reader side modulation 10 % to 30 % ASK Card to reader (OM9663 receives data from a card) card side modulation single subcarrier load modulation bit length 18.88 s bit encoding Manchester coding 26.48 kbit/s bit encoding RTZ bit length 37.76 s 52.96 kbit/s Data coding and framing according to EPC global 13.56 MHz ISM (industrial, scientific and medical) Band Class 1 Radio Frequency Identification Tag Interface Specification (Candidate Recommendation, Version 1.0.0). 8.3.6 ISO/IEC 18000-3 mode 3/ EPC Class-1 HF functionality The ISO/IEC 18000-3 mode 3/ EPC Class-1 HF is not described in this document. For a detailed explanation of the protocol, refer to the ISO/IEC 18000-3 mode 3/ EPC Class-1 HF standard. 8.3.7 ISO/IEC 18092 mode The OM9663 supports Passive Initiator Communication mode at the transfer speeds 106 kbit/s, 212 kbit/s and 424 kbit/s as defined in the ISO/IEC 18092 standard. • Passive communication mode means that the target answers to an initiator command in a load modulation scheme. The initiator is active in terms of generating the RF field. • Initiator: generates RF field at 13.56 MHz and starts the ISO/IEC 18092 communication. • Target: responds to initiator command either in a load modulation scheme in Passive communication mode or using a self generated and self modulated RF field for Active Communication mode. OM9663 Product data sheet COMPANY PUBLIC All information provided in this document is subject to legal disclaimers. © NXP B.V. 2013. All rights reserved. Rev. 3.0 — 9 December 2013 16 of 137 OM9663 NXP Semiconductors High performance NFC reader solution 8.3.7.1 Passive communication mode Passive communication mode means that the target answers to an initiator command in a load modulation scheme. The initiator is active meaning generating the RF field. 1. initiator starts communication at selected transfer speed host host NFC TARGET NFC INITIATOR 2. targets answers using load modulated data at the same transfer speed powered to generate RF field powered for digital processing 001aan217 Fig 11. Passive communication mode Table 12. Communication overview for Passive communication mode Communication direction 106 kbit/s 212 kbit/s 424 kbit/s Initiator  target According to ISO/IEC 14443A 100 % ASK, Modified Miller Coded According to FeliCa, 8 % to 30 % ASK Manchester Coded Target  initiator According to ISO/IEC 14443A subcarrier load modulation, Manchester Coded According to FeliCa, > 12 % ASK Manchester Coded The contactless UART of OM9663 and a dedicated host controller are required to handle the ISO/IEC 18092 passive initiator protocol. OM9663 Product data sheet COMPANY PUBLIC All information provided in this document is subject to legal disclaimers. © NXP B.V. 2013. All rights reserved. Rev. 3.0 — 9 December 2013 17 of 137 OM9663 NXP Semiconductors High performance NFC reader solution 8.3.7.2 ISO/IEC 18092 framing and coding The ISO/IEC 18092 framing and coding in Passive communication mode is defined in the ISO/IEC 18092 standard. Table 13. 8.3.7.3 Framing and coding overview Transfer speed Framing and Coding 106 kbit/s According to the ISO/IEC 14443A/MIFARE scheme 212 kbit/s According to the FeliCa scheme 424 kbit/s According to the FeliCa scheme ISO/IEC 18092 protocol support The ISO/IEC 18092 protocol is not described in this document. For a detailed explanation of the protocol, refer to the ISO/IEC 18092 standard. 8.3.8 EPC Class-1 HF and ICODE 8.3.8.1 Data encoding ICODE The ICODE protocols have mainly three different methods of data encoding: • “1” out of “4” coding scheme • “1” out of “256” coding scheme • “Return to Zero” (RZ) coding scheme Data encoding for all three coding schemes is done by the ICODE generator. The supported EPC Class-1 HF modes are: • • • • 2 pulse for 424 kbit subcarrier 4 pulse for 424 kbit subcarrier 2 pulse for 848 kbit subcarrier 4 pulse for 848 kbit subcarrier 8.4 Host interfaces 8.4.1 Host interface configuration The OM9663 supports direct interfacing of various hosts as the SPI, I2C, I2CL and serial UART interface type. The OM9663 resets its interface and checks the current host interface type automatically having performed a power-up or resuming from power down. The OM9663 identifies the host interface by the means of the logic levels on the control pins after the Cold Reset Phase. This is done by a combination of fixed pin connections.The following table shows the possible configurations defined by IFSEL1,IFSEL0: Table 14. OM9663 Product data sheet COMPANY PUBLIC Connection scheme for detecting the different interface types Pin Pin Symbol UART SPI I2C I2C-L 28 IF0 RX MOSI ADR1 ADR1 29 IF1 - SCK SCL SCL 30 IF2 TX MISO ADR2 SDA All information provided in this document is subject to legal disclaimers. © NXP B.V. 2013. All rights reserved. Rev. 3.0 — 9 December 2013 18 of 137 OM9663 NXP Semiconductors High performance NFC reader solution Table 14. Connection scheme for detecting the different interface types Pin Pin Symbol UART SPI I2C I2C-L 31 IF3 1 NSS SDA ADR2 26 IFSEL0 0 0 1 1 27 IFSEL1 0 1 0 1 8.4.2 SPI interface 8.4.2.1 General READER IC SCK IF1 MOSI IF0 MISO IF2 NSS IF3 001aal998 Fig 12. Connection to host with SPI The OM9663 acts as a slave during the SPI communication. The SPI clock SCK has to be generated by the master. Data communication from the master to the slave uses the Line MOSI. Line MISO is used to send data back from the OM9663 to the master. A serial peripheral interface (SPI compatible) is supported to enable high speed communication to a host. The implemented SPI compatible interface is according to a standard SPI interface. The SPI compatible interface can handle data speed of up to 10 Mbit/s. In the communication with a host OM9663 acts as a slave receiving data from the external host for register settings and to send and receive data relevant for the communication on the RF interface. On both data lines (MOSI, MISO) each data byte is sent by MSB first. Data on MOSI line shall be stable on rising edge of the clock line (SCK) and is allowed to change on falling edge. The same is valid for the MISO line. Data is provided by the OM9663 on the falling edge and is stable on the rising edge.The polarity of the clock is low at SPI idle. 8.4.2.2 Read data To read out data from the OM9663 by using the SPI compatible interface the following byte order has to be used. The first byte that is sent defines the mode (LSB bit) and the address. Table 15. Byte Order for MOSI and MISO byte 0 byte 1 byte 2 byte 3 to n-1 byte n byte n+1 MOSI address 0 address 1 address 2 …….. address n 00h MISO X data 0 data 1 …….. data n  1 data n Remark: The Most Significant Bit (MSB) has to be sent first. OM9663 Product data sheet COMPANY PUBLIC All information provided in this document is subject to legal disclaimers. © NXP B.V. 2013. All rights reserved. Rev. 3.0 — 9 December 2013 19 of 137 OM9663 NXP Semiconductors High performance NFC reader solution 8.4.2.3 Write data To write data to the OM9663 using the SPI interface the following byte order has to be used. It is possible to write more than one byte by sending a single address byte (see.8.5.2.4). The first send byte defines both, the mode itself and the address byte. Table 16. Byte Order for MOSI and MISO byte 0 byte 1 byte 2 3 to n-1 byte n byte n + 1 MOSI address 0 data 0 data 1 …….. data n 1 data n MISO X X X …….. X X Remark: The Most Significant Bit (MSB) has to be sent first. 8.4.2.4 Address byte The address byte has to fulfil the following format: The LSB bit of the first byte defines the used mode. To read data from the OM9663 the LSB bit is set to logic 1. To write data to the OM9663 the LSB bit has to be cleared. The bits 6 to 0 define the address byte. NOTE: When writing the sequence [address byte][data1][data2][data3]..., [data1] is written to address [address byte], [data2] is written to address [address byte + 1] and [data3] is written to [address byte + 2]. Exception: This auto increment of the address byte is not performed if data is written to the FIFO address Table 17. Address byte 0 register; address MOSI 7 6 5 4 3 2 1 0 address 6 address 5 address 4 address 3 address 2 address 1 address 0 1 (read) 0 (write) MSB 8.4.2.5 LSB Timing Specification SPI The timing condition for SPI interface is as follows: Table 18. OM9663 Product data sheet COMPANY PUBLIC Timing conditions SPI Symbol Parameter Min Typ Max Unit tSCKL SCK LOW time 50 - - ns tSCKH SCK HIGH time 50 - - ns th(SCKH-D) SCK HIGH to data input hold time 25 - - ns tsu(D-SCKH) data input to SCK HIGH set-up time 25 - - ns th(SCKL-Q) SCK LOW to data output hold time - - 25 ns t(SCKL-NSSH) SCK LOW to NSS HIGH time 0 - - ns tNSSH NSS HIGH time 50 - - ns All information provided in this document is subject to legal disclaimers. © NXP B.V. 2013. All rights reserved. Rev. 3.0 — 9 December 2013 20 of 137 OM9663 NXP Semiconductors High performance NFC reader solution tNSSH tSCKL tSCKH tSCKL SCK th(SCKL-Q) th(SCKH-D) tsu(D-SCKH) th(SCKL-Q) MOSI MSB LSB MISO MSB LSB t(SCKL-NSSH) NSS 001aaj641 Fig 13. Connection to host with SPI Remark: To send more bytes in one data stream the NSS signal must be LOW during the send process. To send more than one data stream the NSS signal must be HIGH between each data stream. 8.4.3 RS232 interface 8.4.3.1 Selection of the transfer speeds The internal UART interface is compatible to a RS232 serial interface. Table 20 “Selectable transfer speeds” describes examples for different transfer speeds and relevant register settings. The resulting transfer speed error is less than 1.5 % for all described transfer speeds. The default transfer speed is 115.2 kbit/s. To change the transfer speed, the host controller has to write a value for the new transfer speed to the register SerialSpeedReg. The bits BR_T0 and BR_T1 define factors to set the transfer speed in the SerialSpeedReg. Table 19 “Settings of BR_T0 and BR_T1” describes the settings of BR_T0 and BR_T1. Table 19. Settings of BR_T0 and BR_T1 BR_T0 0 1 2 3 4 5 6 7 factor BR_T0 1 1 2 4 8 16 32 64 range BR_T1 1 to 32 33 to 64 33 to 64 33 to 64 33 to 64 33 to 64 33 to 64 33 to 64 Table 20. Selectable transfer speeds Transfer speed (kbit/s) Serial SpeedReg Transfer speed accuracy (%) (Hex.) OM9663 Product data sheet COMPANY PUBLIC 7.2 FA 0.25 9.6 EB 0.32 14.4 DA 0.25 19.2 CB 0.32 All information provided in this document is subject to legal disclaimers. © NXP B.V. 2013. All rights reserved. Rev. 3.0 — 9 December 2013 21 of 137 OM9663 NXP Semiconductors High performance NFC reader solution Table 20. Selectable transfer speeds Transfer speed (kbit/s) Serial SpeedReg Transfer speed accuracy (%) (Hex.) 38.4 AB 0.32 57.6 9A 0.25 115.2 7A 0.25 128 74 0.06 230.4 5A 0.25 460.8 3A 0.25 921.6 1C 1.45 1228.8 15 0.32 The selectable transfer speeds as shown are calculated according to the following formulas: if BR_T0 = 0: transfer speed = 27.12 MHz / (BR_T1 + 1) if BR_T0 > 0: transfer speed = 27.12 MHz / (BR_T1 + 33)/2(BR_T0  1) Remark: Transfer speeds above 1228.8 kBits/s are not supported. 8.4.3.2 Framing Table 21. UART framing Bit Length Value Start bit (Sa) 1 bit 0 Data bits 8 bit Data Stop bit (So) 1 bit 1 Remark: For data and address bytes the LSB bit has to be sent first. No parity bit is used during transmission. Read data: To read out data using the UART interface the flow described below has to be used. The first send byte defines both the mode itself and the address.The Trigger on pin IF3 has to be set, otherwise no read of data is possible. Table 22. OM9663 Product data sheet COMPANY PUBLIC Byte Order to Read Data Mode byte 0 byte 1 RX address - TX - data 0 All information provided in this document is subject to legal disclaimers. © NXP B.V. 2013. All rights reserved. Rev. 3.0 — 9 December 2013 22 of 137 OM9663 NXP Semiconductors High performance NFC reader solution ADDRESS RX Sa A0 A1 A2 A3 A4 A5 A6 RD/ NWR So DATA TX Sa D0 D1 D2 D3 D4 D5 D6 D7 So 001aam298 Fig 14. Timing Diagram for UART Read Data Write data: To write data to the OM9663 using the UART interface the following sequence has to be used. The first send byte defines both, the mode itself and the address. Table 23. Byte Order to Write Data Mode byte 0 byte 1 RX address 0 data 0 TX address 0 DATA ADDRESS RX Sa A0 A1 A2 A3 A4 A5 A6 RD/ NWR So Sa D0 RD/ NWR So D1 D2 D3 D4 D5 D6 D7 So ADDRESS TX Sa A0 A1 A2 A3 A4 A5 A6 001aam299 Fig 15. Timing diagram for UART write data Remark: Data can be sent before address is received. OM9663 Product data sheet COMPANY PUBLIC All information provided in this document is subject to legal disclaimers. © NXP B.V. 2013. All rights reserved. Rev. 3.0 — 9 December 2013 23 of 137 OM9663 NXP Semiconductors High performance NFC reader solution 8.4.4 I2C-bus interface 8.4.4.1 General An Inter IC (I2C) bus interface is supported to enable a low cost, low pin count serial bus interface to the host. The implemented I2C interface is mainly implemented according the NXP Semiconductors I2C interface specification, rev. 3.0, June 2007. The OM9663 can act as a slave receiver or slave transmitter in standard mode, fast mode and fast mode plus. The following features defined by the NXP Semiconductors I2C interface specification, rev. 3.0, June 2007 are not supported: • The OM9663 I2C interface does not stretch the clock • The OM9663 I2C interface does not support the general call. This means that the OM9663 does not support a software reset • The OM9663 does not support the I2C device ID • The implemented interface can only act in slave mode. Therefore no clock generation and access arbitration is implemented in the OM9663. • High speed mode is not supported by the OM9663 PULL-UP NETWORK PULL-UP NETWORK MICROCONTROLLER READER IC SDA SCL 001aam000 Fig 16. I2C-bus interface SDA is a bidirectional line, connected to a positive supply voltage via a pull-up resistor. Both lines SDA and SCL are set to HIGH level if no data is transmitted. Data on the I2C-bus can be transferred at data rates of up to 400 kbit/s in fast mode, up to 1 Mbit/s in the fast mode+. If the I2C interface is selected, a spike suppression according to the I2C interface specification on SCL and SDA is automatically activated. For timing requirements refer to Table 249 “I2C-bus timing in fast mode and fast mode plus” 8.4.4.2 I2C Data validity Data on the SDA line shall be stable during the HIGH period of the clock. The HIGH state or LOW state of the data line shall only change when the clock signal on SCL is LOW. OM9663 Product data sheet COMPANY PUBLIC All information provided in this document is subject to legal disclaimers. © NXP B.V. 2013. All rights reserved. Rev. 3.0 — 9 December 2013 24 of 137 OM9663 NXP Semiconductors High performance NFC reader solution SDA SCL data line stable; data valid change of data allowed 001aam300 Fig 17. Bit transfer on the I2C-bus. 8.4.4.3 I2C START and STOP conditions To handle the data transfer on the I2C-bus, unique START (S) and STOP (P) conditions are defined. A START condition is defined with a HIGH-to-LOW transition on the SDA line while SCL is HIGH. A STOP condition is defined with a LOW-to-HIGH transition on the SDA line while SCL is HIGH. The master always generates the START and STOP conditions. The bus is considered to be busy after the START condition. The bus is considered to be free again a certain time after the STOP condition. The bus stays busy if a repeated START (Sr) is generated instead of a STOP condition. In this respect, the START (S) and repeated START (Sr) conditions are functionally identical. Therefore, the S symbol will be used as a generic term to represent both the START and repeated START (Sr) conditions. SDA SDA SCL SCL S P START condition STOP condition 001aam301 Fig 18. START and STOP conditions 8.4.4.4 I2C byte format Each byte has to be followed by an acknowledge bit. Data is transferred with the MSB first, see Figure 18 “START and STOP conditions”. The number of transmitted bytes during one data transfer is unrestricted but shall fulfil the read/write cycle format. OM9663 Product data sheet COMPANY PUBLIC All information provided in this document is subject to legal disclaimers. © NXP B.V. 2013. All rights reserved. Rev. 3.0 — 9 December 2013 25 of 137 OM9663 NXP Semiconductors High performance NFC reader solution 8.4.4.5 I2C Acknowledge An acknowledge at the end of one data byte is mandatory. The acknowledge-related clock pulse is generated by the master. The transmitter of data, either master or slave, releases the SDA line (HIGH) during the acknowledge clock pulse. The receiver shall pull down the SDA line during the acknowledge clock pulse so that it remains stable LOW during the HIGH period of this clock pulse. The master can then generate either a STOP (P) condition to stop the transfer, or a repeated START (Sr) condition to start a new transfer. A master-receiver shall indicate the end of data to the slave- transmitter by not generating an acknowledge on the last byte that was clocked out by the slave. The slave-transmitter shall release the data line to allow the master to generate a STOP (P) or repeated START (Sr) condition. DATA OUTPUT BY TRANSMITTER not acknowledge DATA OUTPUT BY RECEIVERER acknowledge SCL FROM MASTER 1 2 8 9 S clock pulse for acknowledgement START condition 001aam302 Fig 19. Acknowledge on the I2C- bus P MSB acknowledgement signal from slave acknowledgement signal from receiver Sr byte complete, interrupt within slave clock line held low while interrupts are serviced S or Sr 1 2 7 8 9 ACK 1 2 3-8 9 ACK Sr or P 001aam303 Fig 20. Data transfer on the I2C- bus 8.4.4.6 I2C 7-bit addressing During the I2C-bus addressing procedure, the first byte after the START condition is used to determine which slave will be selected by the master. OM9663 Product data sheet COMPANY PUBLIC All information provided in this document is subject to legal disclaimers. © NXP B.V. 2013. All rights reserved. Rev. 3.0 — 9 December 2013 26 of 137 OM9663 NXP Semiconductors High performance NFC reader solution Alternatively the I2C address can be configured in the EEPROM. Several address numbers are reserved for this purpose. During device configuration, the designer has to ensure, that no collision with these reserved addresses in the system is possible. Check the corresponding I2C specification for a complete list of reserved addresses. For all OM9663 devices the upper 5 bits of the device bus address are reserved by NXP and set to 01010(bin). The remaining 2 bits (ADR_2, ADR_1) of the slave address can be freely configured by the customer in order to prevent collisions with other I2C devices by using the interface pins (refer to Table 14) or the value of the I2C address EEPROM register (refer to Table 35). MSB Bit 6 LSB Bit 5 Bit 4 Bit 3 Bit 2 slave address Bit 1 Bit 0 R/W 001aam304 Fig 21. First byte following the START procedure 8.4.4.7 I2C-register write access To write data from the host controller via I2C to a specific register of the OM9663 the following frame format shall be used. The first byte of a frame indicates the device address according to the I2C rules. The second byte indicates the register address followed by up to n-data bytes. In case the address indicates the FIFO, in one frame all n-data bytes are written to the FIFO register address. This enables for example a fast FIFO access. For any other address, the address pointer is incremented automatically and data is written to the locations [address], [address+1], [address+2]... [address+(n-1)] The read/write bit shall be set to logic 0. 8.4.4.8 I2C-register read access To read out data from a specific register address of the OM9663 the host controller shall use the procedure: First a write access to the specific register address has to be performed as indicated in the following frame: The first byte of a frame indicates the device address according to the I2C rules. The second byte indicates the register address. No data bytes are added. The read/write bit shall be logic 0. Having performed this write access, the read access starts. The host sends the device address of the OM9663. As an answer to this device address the OM9663 responds with the content of the addressed register. In one frame n-data bytes could be read using the same register address. The address pointing to the register is incremented automatically (exception: FIFO register address is not incremented automatically). This enables a fast transfer of register content. The address pointer is incremented automatically and data is read from the locations [address], [address+1], [address+2]... [address+(n-1)] In order to support a fast FIFO data transfer, the address pointer is not incremented automatically in case the address is pointing to the FIFO. OM9663 Product data sheet COMPANY PUBLIC All information provided in this document is subject to legal disclaimers. © NXP B.V. 2013. All rights reserved. Rev. 3.0 — 9 December 2013 27 of 137 OM9663 NXP Semiconductors High performance NFC reader solution The read/write bit shall be set to logic 1. Write Cycle I2C slave address A7-A0 SA 0 (W) Ack CLRC663 register address A6-A0 0 Ack [0..n] DATA [7..0] Ack SO Read Cycle 0 (W) I2C slave address A7-A0 SA Ack 0 CLRC663 register address A6-A0 Ack SO Optional, if the previous access was on the same register address 0..n SA 1 (R) I2C slave address A7-A0 Ack [0..n] sent by master DATA [7..0] Ack DATA [7..0] Nack SO sent by slave 001aam305 Fig 22. Register read and write access 8.4.4.9 I2CL-bus interface The OM9663 provides an interface option according to of a logical handling of an I2C interface. This logical interface fulfills the I2C specification, but the rise/fall timings will not be according the I2C standard. Standard I/O pads are used for communication and the communication speed is limited to 5 MBaud. The protocol itself is equivalent to the fast mode protocol of I2C. The address is 01010xxb, where the last two bits of the address can be defined by the application. The definition of this bits can be done by two options. With a pin, where the higher bit is fixed to 0 or the configuration can be defined via EEPROM. Refer to the EEPROM configuration in Section 8.7. Table 24. OM9663 Product data sheet COMPANY PUBLIC Timing parameter I2CL Parameter Min Max Unit fSCL tHD;STA 0 5 MHz 80 - ns tLOW 100 - ns tHIGH 100 - ns tSU;SDA 80 - ns tHD;DAT 0 50 ns tSU;DAT 0 20 ns tSU;STO 80 - ns tBUF 200 - ns All information provided in this document is subject to legal disclaimers. © NXP B.V. 2013. All rights reserved. Rev. 3.0 — 9 December 2013 28 of 137 OM9663 NXP Semiconductors High performance NFC reader solution The pull-up resistor is not required for the I2CL interface. Instead, a on chip buskeeper is implemented in the OM9663 for SDA of the I2CL interface. This protocol is intended to be used for a point to point connection of devices over a short distance and does not support a bus capability.The driver of the pin must force the line to the desired logic voltage. To avoid that two drivers are pushing the line at the same time following regulations must be fulfilled: SCL: As there is no clock stretching, the SCL is always under control of the Master. SDA: The SDA line is shared between master and slave. Therefore the master and the slave must have the control over the own driver enable line of the SDA pin. The following rules must be followed: • In the idle phase the SDA line is driven high by the master • In the time between start and stop condition the SDA line is driven by master or slave when SCL is low. If SCL is high the SDA line is not driven by any device • To keep the value on the SDA line a on chip buskeeper structure is implemented for the line 8.4.5 SAM interface I2C 8.4.5.1 SAM functionality The OM9663 implements a dedicated I2C interface to integrate a MIFARE SAM (Secure Access Module) in a very convenient way into applications (e.g. a proximity reader). The SAM can be connected to the microcontroller to operate like a cryptographic co-processor. For any cryptographic task, the microcontroller requests a operation from the SAM, receives the answer and sends it over a host interface (e.g. I2C, SPI) interface to the connected reader IC. The MIFARE SAM supports a optimized method to integrate the SAM in a very efficient way to reduce the protocol overhead. In this system configuration, the SAM is integrated between the microprocessor and the reader IC, connected by one interface to the reader IC and by another interface to the microcontroller. In this application the microcontroller accesses the SAM using the T=1 protocol and the SAM accesses the reader IC using an I2C interface. As the SAM is directly communicating with reader IC, the communication overhead is reduced. In this configuration, a performance boost of up to 40% can be achieved for a transaction time. The MIFARE SAM supports applications using MIFARE cards. For multi application purposes an architecture connecting the microcontroller additionally directly to the reader IC is recommended. This is possible by connecting the OM9663 on one interface (SAM Interface SDA, SCL) with the MIFARE SAM AV2.6 (P5DF081XX/T1AR1070) and by connecting the microcontroller to the S2C or SPI interface. OM9663 Product data sheet COMPANY PUBLIC All information provided in this document is subject to legal disclaimers. © NXP B.V. 2013. All rights reserved. Rev. 3.0 — 9 December 2013 29 of 137 OM9663 NXP Semiconductors High performance NFC reader solution T=1 μC SAM AV2.6 I2C READER IC I2C Reader aaa-002963 Fig 23. I2C interface enables convenient MIFARE SAM integration 8.4.5.2 SAM connection The OM9663 provides an interface to connect a SAM dedicated to the OM9663. Both interface options of the OM9663, I2C or I2CL can be used for this purpose. The interface option of the SAM itself is configured by a host command sent from the host to the SAM. The I2CL interface is intended to be used as connection between two IC’s over a short distance. The protocol fulfills the I2C specification, but does support a single device connected to the bus only. 8.4.6 Boundary scan interface The OM9663 provides a boundary scan interface according to the IEEE 1149.1. This interface allows to test interconnections without using physical test probes. This is done by test cells, assigned to each pin, which override the functionality of this pin. To be able to program the test cells, the following commands are supported: Table 25. Boundary scan command Value (decimal) Command Parameter in Parameter out 0 bypass - - 1 preload data (24) - 1 sample - data (24) 2 ID code (default) - data (32) 3 USER code - data (32) 4 Clamp - - 5 HIGH Z - - 7 extest data (24) data (24) 8 interface on/off interface (1) - 9 register access read address (7) data (8) 10 register access write address (7) - data (8) - The Standard IEEE 1149.1 describes the four basic blocks necessary to use this interface: Test Access Port (TAP), TAP controller, TAP instruction register, TAP data register; OM9663 Product data sheet COMPANY PUBLIC All information provided in this document is subject to legal disclaimers. © NXP B.V. 2013. All rights reserved. Rev. 3.0 — 9 December 2013 30 of 137 OM9663 NXP Semiconductors High performance NFC reader solution 8.4.6.1 Interface signals The boundary scan interface implements a four line interface between the chip and the environment. There are three Inputs: Test Clock (TCK); Test Mode Select (TMS); Test Data Input (TDI) and one output Test Data Output (TDO). TCK and TMS are broadcast signals, TDI to TDO generate a serial line called Scan path. Advantage of this technique is that independent of the numbers of boundary scan devices the complete path can be handled with four signal lines. The signals TCK, TMS are directly connected with the boundary scan controller. Because these signals are responsible for the mode of the chip, all boundary scan devices in one scan path will be in the same boundary scan mode. 8.4.6.2 Test Clock (TCK) The TCK pin is the input clock for the module. If this clock is provided, the test logic is able to operate independent of any other system clocks. In addition, it ensures that multiple boundary scan controllers that are daisy-chained together can synchronously communicate serial test data between components. During normal operation, TCK is driven by a free-running clock. When necessary, TCK can be stopped at 0 or 1 for extended periods of time. While TCK is stopped at 0 or 1, the state of the boundary scan controller does not change and data in the Instruction and Data Registers is not lost. The internal pull-up resistor on the TCK pin is enabled. This assures that no clocking occurs if the pin is not driven from an external source. 8.4.6.3 Test Mode Select (TMS) The TMS pin selects the next state of the boundary scan controller. TMS is sampled on the rising edge of TCK. Depending on the current boundary scan state and the sampled value of TMS, the next state is entered. Because the TMS pin is sampled on the rising edge of TCK, the IEEE Standard 1149.1 expects the value on TMS to change on the falling edge of TCK. Holding TMS high for five consecutive TCK cycles drives the boundary scan controller state machine to the Test-Logic-Reset state. When the boundary scan controller enters the Test-Logic-Reset state, the Instruction Register (IR) resets to the default instruction, IDCODE. Therefore, this sequence can be used as a reset mechanism. The internal pull-up resistor on the TMS pin is enabled. 8.4.6.4 Test Data Input (TDI) The TDI pin provides a stream of serial information to the IR chain and the DR chains. TDI is sampled on the rising edge of TCK and, depending on the current TAP state and the current instruction, presents this data to the proper shift register chain. Because the TDI pin is sampled on the rising edge of TCK, the IEEE Standard 1149.1 expects the value on TDI to change on the falling edge of TCK. The internal pull-up resistor on the TDI pin is enabled. 8.4.6.5 Test Data Output (TDO) The TDO pin provides an output stream of serial information from the IR chain or the DR chains. The value of TDO depends on the current TAP state, the current instruction, and the data in the chain being accessed. In order to save power when the port is not being OM9663 Product data sheet COMPANY PUBLIC All information provided in this document is subject to legal disclaimers. © NXP B.V. 2013. All rights reserved. Rev. 3.0 — 9 December 2013 31 of 137 OM9663 NXP Semiconductors High performance NFC reader solution used, the TDO pin is placed in an inactive drive state when not actively shifting out data. Because TDO can be connected to the TDI of another controller in a daisy-chain configuration, the IEEE Standard 1149.1 expects the value on TDO to change on the falling edge of TCK. 8.4.6.6 Data register According to the IEEE1149.1 standard there are two types of data register defined: bypass and boundary scan The bypass register enable the possibility to bypass a device when part of the scan path.Serial data is allowed to be transferred through a device from the TDI pin to the TDO pin without affecting the operation of the device. The boundary scan register is the scan-chain of the boundary cells. The size of this register is dependent on the command. 8.4.6.7 Boundary scan cell The boundary scan cell opens the possibility to control a hardware pin independent of its normal use case. Basically the cell can only do one of the following: control, output and input. TDI TAP TCK IC2 LOGIC Boundary scan cell LOGIC IC1 TDI TDO TAP TCK TMS TDO TMS 001aam306 Fig 24. Boundary scan cell path structure 8.4.6.8 Boundary scan path This chapter shows the boundary scan path of the OM9663. Table 26. OM9663 Product data sheet COMPANY PUBLIC Boundary scan path of the OM9663 Number (decimal) Cell Port Function 23 BC_1 - Control 22 BC_8 CLKOUT Bidir 21 BC_1 - Control 20 BC_8 SCL2 Bidir 19 BC_1 - Control 18 BC_8 SDA2 Bidir 17 BC_1 - Control 16 BC_8 IFSEL0 Bidir 15 BC_1 - Control 14 BC_8 IFSEL1 Bidir All information provided in this document is subject to legal disclaimers. © NXP B.V. 2013. All rights reserved. Rev. 3.0 — 9 December 2013 32 of 137 OM9663 NXP Semiconductors High performance NFC reader solution Table 26. Boundary scan path of the OM9663 Number (decimal) Cell Port Function 13 BC_1 - Control 12 BC_8 IF0 Bidir 11 BC_1 - Control 10 BC_8 IF1 Bidir 9 BC_1 - Control 8 BC_8 IF2 Bidir 7 BC_1 IF2 Output2 6 BC_4 IF3 Bidir 5 BC_1 - Control 4 BC_8 IRQ Bidir 3 BC_1 - Control 2 BC_8 SIGIN Bidir 1 BC_1 - Control 0 BC_8 SIGOUT Bidir Refer to the OM9663 BSDL file. 8.4.6.9 Boundary Scan Description Language (BSDL) All of the boundary scan devices have a unique boundary structure which is necessary to know for operating the device. Important components of this language are: • • • • • available test bus signal compliance pins command register data register boundary scan structure (number and types of the cells, their function and the connection to the pins.) The OM9663 is using the cell BC_8 for the IO-Lines. The I2C Pin is using a BC_4 cell. For all pad enable lines the cell BC1 is used. The manufacturer's identification is 02Bh. • • • • attribute IDCODEISTER of OM9663: entity is "0001" and -- version "0011110010000010b" and -- part number (3C82h) "00000010101b" and -- manufacturer (02Bh) "1b"; -- mandatory The user code data is coded as followed: • product ID (3 bytes) • version These four bytes are stored as the first four bytes in the EEPROM. OM9663 Product data sheet COMPANY PUBLIC All information provided in this document is subject to legal disclaimers. © NXP B.V. 2013. All rights reserved. Rev. 3.0 — 9 December 2013 33 of 137 OM9663 NXP Semiconductors High performance NFC reader solution 8.4.6.10 Non-IEEE1149.1 commands Interface on/off: With this command the host/SAM interface can be deactivated and the Read and Write command of the boundary scan interface is activated. (Data = 1). With Update-DR the value is taken over. Register Access Read: At Capture-DR the actual address is read and stored in the DR. Shifting the DR is shifting in a new address. With Update-DR this address is taken over into the actual address. OM9663 Product data sheet COMPANY PUBLIC All information provided in this document is subject to legal disclaimers. © NXP B.V. 2013. All rights reserved. Rev. 3.0 — 9 December 2013 34 of 137 OM9663 NXP Semiconductors High performance NFC reader solution 8.5 Buffer 8.5.1 Overview An 512  8-bit FIFO buffer is implemented in the OM9663. It buffers the input and output data stream between the host and the internal state machine of the OM9663. Thus, it is possible to handle data streams with lengths of up to 512 bytes without taking timing constraints into account. The FIFO can also be limited to a size of 255 byte. In this case all the parameters (FIFO length, Watermark...) require a single byte only for definition. In case of a 512 byte FIFO length the definition of this values requires 2 bytes. 8.5.2 Accessing the FIFO buffer When the -Controller starts a command, the OM9663 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 -Controller has to take care, not to access the FIFO buffer in a way that corrupts the FIFO data. 8.5.3 Controlling the FIFO buffer Besides writing to and reading from the FIFO buffer, the FIFO-buffer pointers might be reset by setting the bit FIFOFlush in FIFOControl to 1. Consequently, the FIFOLevel bits are set to logic 0, the actually stored bytes are not accessible any more and the FIFO buffer can be filled with another 512 bytes (or 255 bytes if the bit FIFOSize is set to 1) again. 8.5.4 Status Information about the FIFO buffer The host may obtain the following data about the FIFO-buffers status: • Number of bytes already stored in the FIFO-buffer. Writing increments, reading decrements the FIFO level: FIFOLength in register FIFOLength (and FIFOControl Register in 512 byte mode) • Warning, that the FIFO-buffer is almost full: HiAlert in register FIFOControl according to the value of the water level in register WaterLevel (Register 02h bit [2], Register 03h bit[7:0]) • Warning, that the FIFO-buffer is almost empty: LoAlert in register FIFOControl according to the value of the water level in register WaterLevel (Register 02h bit [2], Register 03h bit[7:0]) • FIFOOvl bit indicates, that bytes were written to the FIFO buffer although it was already full: ErrIrq in register Irq0. WaterLevel is one single value defining both HiAlert (counting from the FIFO top) and LoAlert (counting from the FIFO bottom). The OM9663 can generate an interrupt signal if: • LoAlertIRQEn in register IRQ0En is set to logic 1 it will activate pin IRQ when LoAlert in the register FIFOControl changes to 1. • HiAlertIRQEN in register IRQ0En is set to logic 1 it will activate pin IRQ when HiAlert in the register FIFOControl changes to 1. The bit HiAlert is set to logic 1 if maximum water level bytes (as set in register WaterLevel) or less can be stored in the FIFO-buffer. It is generated according to the following equation: OM9663 Product data sheet COMPANY PUBLIC All information provided in this document is subject to legal disclaimers. © NXP B.V. 2013. All rights reserved. Rev. 3.0 — 9 December 2013 35 of 137 OM9663 NXP Semiconductors High performance NFC reader solution HiAlert =  FiFoSize – FiFoLength   WaterLevel (2) The bit LoAlert is set to logic 1 if water level bytes (as set in register WaterLevel) or less are actually stored in the FIFO-buffer. It is generated according to the following equation: LoAlert = FIFOLength  WaterLevel OM9663 Product data sheet COMPANY PUBLIC All information provided in this document is subject to legal disclaimers. (3) © NXP B.V. 2013. All rights reserved. Rev. 3.0 — 9 December 2013 36 of 137 OM9663 NXP Semiconductors High performance NFC reader solution 8.6 Analog interface and contactless UART 8.6.1 General The integrated contactless UART supports the external host online with framing and error checking of the protocol requirements up to 848 kbit/s. An external circuit can be connected to the communication interface pins SIGIN and SIGOUT to modulate and demodulate the data. The contactless UART handles the protocol requirements for the communication schemes in co-operation with the host. The protocol handling itself generates bit- and byte-oriented framing and handles error detection like Parity and CRC according to the different contactless communication schemes. The size, the tuning of the antenna, and the supply voltage of the output drivers have an impact on the achievable field strength. The operating distance between reader and card depends additionally on the type of card used. 8.6.2 TX transmitter The signal delivered on pin TX1 and pin TX2 is the 13.56 MHz carrier modulated by an envelope signal for energy and data transmission. It can be used to drive an antenna directly, using a few passive components for matching and filtering, see Section 14 “Application information”. The signal on TX1 and TX2 can be configured by the register DrvMode, see Section 9.8.1 “TxMode”. The modulation index can be set by the TxAmp. Following figure shows the general relations during modulation influenced by set_clk_mode envelope TX ASK100 TX ASK10 (1) (2) 1: Defined by set_cw_amplitude. 2: Defined by set_residual_carrier. time 001aan355 Fig 25. General dependences of modulation Note: When changing the continuous carrier amplitude, the residual carrier amplitude also changes, while the modulation index remains the same. OM9663 Product data sheet COMPANY PUBLIC All information provided in this document is subject to legal disclaimers. © NXP B.V. 2013. All rights reserved. Rev. 3.0 — 9 December 2013 37 of 137 OM9663 NXP Semiconductors High performance NFC reader solution The registers Section 9.8 and Section 9.10 control the data rate, the framing during transmission and the setting of the antenna driver to support the requirements at the different specified modes and transfer speeds. Table 27. Settings for TX1 and TX2 TxClkMode (binary) Tx1 and TX2 output Remarks 000 High impedance - 001 0 output pulled to 0 in any case 010 1 output pulled to 1 in any case 110 RF high side push open drain, only high side (push) MOS supplied with clock, clock parity defined by invtx; low side MOS is off 101 RF low side pull open drain, only low side (pull) MOS supplied with clock, clock parity defined by invtx; high side MOS is off 111 13.56 MHz clock derived from 27.12 MHz quartz divided by 2 push/pull Operation, clock polarity defined by invtx; setting for 10% modulation Register TXamp and the bits for set_residual_carrier define the modulation index: Table 28. OM9663 Product data sheet COMPANY PUBLIC Setting residual carrier and modulation index by TXamp.set_residual_carrier set_residual_carrier (decimal) residual carrier [%] modulation index [%] 0 99 0.5 1 98 1.0 2 96 2.0 3 94 3.1 4 91 4.7 5 89 5.8 6 87 7.0 7 86 7.5 8 85 8.1 9 84 8.7 10 83 9.3 11 82 9.9 12 81 10.5 13 80 11.1 14 79 11.7 15 78 12.4 16 77 13.0 17 76 13.6 18 75 14.3 19 74 14.9 20 72 16.3 21 70 17.6 22 68 19.0 All information provided in this document is subject to legal disclaimers. © NXP B.V. 2013. All rights reserved. Rev. 3.0 — 9 December 2013 38 of 137 OM9663 NXP Semiconductors High performance NFC reader solution Table 28. Setting residual carrier …continuedand modulation index by set_residual_carrier (decimal) residual carrier [%] modulation index [%] 23 65 21.2 24 60 25.0 25 55 29.0 26 50 33.3 27 45 37.9 28 40 42.9 29 35 48.1 30 30 53.8 31 25 60.0 Note: At VDD(TVDD) 0: transfer speed = 27.12 MHz / (BR_T1 + 33) / 2^(BR_T0  1) 4 to 0 BR_T1 BR_T0 = 0: transfer speed = 27.12 MHz / (BR_T1 + 1) BR_T0 > 0: transfer speed = 27.12 MHz / (BR_T1 + 33) / 2^(BR_T0  1) Table 169. RS232 speed settings Transfer speed (kbit/s) SerialSpeed register content (Hex.) 7,2 FA 9,6 EB 14,4 DA 19,2 CB 38,4 AB 57,6 9A 115,2 7A 128,0 74 230,4 5A 460,8 3A 921,6 1C 1228,8 15 9.13.2 LFO_Trimm Table 170. LFO_Trim register (address 3Ch) Bit 7 6 5 4 3 Symbol LFO_trimm Access rights r/w 2 1 0 Table 171. LFO_Trim bits OM9663 Product data sheet COMPANY PUBLIC Bit Symbol Description 7 to 0 LFO_trimm Trimm value. Refer to Section 8.8.3 “Low Frequency Oscillator (LFO)” Note: If the trimm value is increased, the frequency of the oscillator decreases. All information provided in this document is subject to legal disclaimers. © NXP B.V. 2013. All rights reserved. Rev. 3.0 — 9 December 2013 99 of 137 OM9663 NXP Semiconductors High performance NFC reader solution 9.13.3 PLL_Ctrl Register The PLL_Ctrl register implements the control register for the IntegerN PLL. Two stages exist to create the ClkOut signal from the 27,12MHz input. In the first stage the 27,12Mhz input signal is multiplied by the value defined in PLLDiv_FB and divided by two, and the second stage divides this frequency by the value defined by PLLDIV_Out. Table 172. PLL_Ctrl register (address3Dh) Bit 7 6 5 4 3 2 1 0 Symbol ClkOutSel ClkOut_En PLL_PD PLLDiv_FB Access rights r/w r/w r/w r/w Table 173. PLL_Ctrl register bits Bit Symbol 7 to 4 CLkOutSel Description • • • • • • • • • • • • • 0h - pin CLKOUT is used as I/O 1h - pin CLKOUT shows the output of the analog PLL 2h - pin CLKOUT is hold on 0 3h - pin CLKOUT is hold on 1 4h - pin CLKOUT shows 27.12 MHz from the crystal 5h - pin CLKOUT shows 13.56 MHz derived from the crystal 6h - pin CLKOUT shows 6.78 MHz derived from the crystal 7h - pin CLKOUT shows 3.39 MHz derived from the crystal 8h - pin CLKOUT is toggled by the Timer0 overflow 9h - pin CLKOUT is toggled by the Timer1 overflow Ah - pin CLKOUT is toggled by the Timer2 overflow Bh - pin CLKOUT is toggled by the Timer3 overflow Ch...Fh - RFU 3 ClkOut_En Enables the clock at Pin CLKOUT 2 PLL_PD PLL power down 1-0 PLLDiv_FB PLL feedback divider (see table 174) Table 174. Setting of feedback divider PLLDiv_FB [1:0] Bit 1 Bit 0 Division 0 0 23 (VCO frequency 312Mhz) 0 1 27 (VCO frequency 366MHz) 1 0 28 (VCO frequency 380Mhz) 1 1 23 (VCO frequency 312Mhz) 9.13.4 PLLDiv_Out Table 175. PLLDiv_Out register (address 3Eh) Bit 7 6 5 4 3 Symbol PLLDiv_Out Access rights r/w OM9663 Product data sheet COMPANY PUBLIC All information provided in this document is subject to legal disclaimers. 2 1 0 © NXP B.V. 2013. All rights reserved. Rev. 3.0 — 9 December 2013 100 of 137 OM9663 NXP Semiconductors High performance NFC reader solution Table 176. PLLDiv_Out bits Bit Symbol Description 7 to 0 PLLDiv_Out PLL output divider factor; Refer to Section 8.8.2 Table 177. Setting for the output divider ratio PLLDiv_Out [7:0] Value Division 0 RFU 1 RFU 2 RFU 3 RFU 4 RFU 5 RFU 6 RFU 7 RFU 8 8 9 9 10 10 ... ... 253 253 254 254 9.14 Low-power card detection configuration registers The LPCD registers contain the settings for the low-power card detection. The setting for LPCD_IMax (6 bits) is done by the two highest bits (bit 7, bit 6) of the registers LPCD_QMin, LPCD_QMax and LPCD_IMin each. 9.14.1 LPCD_QMin Table 178. LPCD_QMin register (address 3Fh) Bit 7 6 5 4 3 2 Symbol LPCD_IMax.5 LPCD_IMax.4 LPCD_QMin Access rights r/w r/w r/w 1 0 Table 179. LPCD_QMin bits OM9663 Product data sheet COMPANY PUBLIC Bit Symbol Description 7, 6 LPCD_IMax Defines the highest two bits of the higher border for the LPCD. If the measurement value of the I channel is higher than LPCD_IMax, a LPCD interrupt request is indicated by bit IRQ0.LPCDIrq. 5 to 0 LPCD_QMin Defines the lower border for the LPCD. If the measurement value of the Q channel is higher than LPCD_QMin, a LPCDinterrupt request is indicated by bit IRQ0.LPCDIrq. All information provided in this document is subject to legal disclaimers. © NXP B.V. 2013. All rights reserved. Rev. 3.0 — 9 December 2013 101 of 137 OM9663 NXP Semiconductors High performance NFC reader solution 9.14.2 LPCD_QMax Table 180. LPCD_QMax register (address 40h) Bit 7 6 5 4 3 2 Symbol LPCD_IMax.3 LPCD_IMax.2 LPCD_QMax Access rights r/w r/w r/w 1 0 Table 181. LPCD_QMax bits Bit Symbol Description 7 LPCD_IMax.3 Defines the bit 3 of the high border for the LPCD. If the measurement value of the I channel is higher than LPCD IMax, a LPCD IRQ is raised. 6 LPCD_IMax.2 Defines the bit 2 of the high border for the LPCD. If the measurement value of the I channel is higher than LPCD IMax, a LPCD IRQ is raised. 5 to 0 LPCD_QMax Defines the high border for the LPCD. If the measurement value of the Q channel is higher than LPCD QMax, a LPCD IRQ is raised. 9.14.3 LPCD_IMin Table 182. LPCD_IMin register (address 41h) Bit 7 6 5 Symbol LPCD_IMax.1 LPCD_IMax.0 Access rights r/w r/w 4 3 2 1 0 LPCD_IMin r/w Table 183. LPCD_IMin bits Bit Symbol Description 7 to 6 LPCD_IMax Defines lowest two bits of the higher border for the low-power card detection (LPCD). If the measurement value of the I channel is higher than LPCD IMax, a LPCD IRQ is raised. 5 to 0 LPCD_IMin Defines the lower border for the ow power card detection. If the measurement value of the I channel is lower than LPCD IMin, a LPCD IRQ is raised. 9.14.4 LPCD_Result_I Table 184. LPCD_Result_I register (address 42h) Bit 7 6 Symbol RFU- RFU- 5 4 LPCD_Result_I 3 2 Access rights - - r 1 0 Table 185. LPCD_I_Result bits OM9663 Product data sheet COMPANY PUBLIC Bit Symbol Description 7 to 6 RFU - 5 to 0 LPCD_Result_I Shows the result of the last low-power card detection (I-Channel). All information provided in this document is subject to legal disclaimers. © NXP B.V. 2013. All rights reserved. Rev. 3.0 — 9 December 2013 102 of 137 OM9663 NXP Semiconductors High performance NFC reader solution 9.14.5 LPCD_Result_Q Table 186. LPCD_Result_Q register (address 43h) Bit Symbol 7 6 RFU LPCD_Irq_Clr LPCD_Reslult_Q r/w r Access rights 5 4 3 2 1 0 Table 187. LPCD_Q_Result bits Bit Symbol Description 7 RFU - 6 LPCD_Irq_Clr If set no LPCD IRQ is raised any more until the next low-power card detection procedure. Can be used by software to clear the interrupt source. 5 to 0 LPCD_Result_Q Shows the result of the last ow power card detection (Q-Channel). 9.15 Pin configuration 9.15.1 PinEn Table 188. PinEn register (address 44h) Bit 7 6 5 4 3 2 1 0 Symbol SIGIN_EN CLKOUT_EN IFSEL1_EN IFSEL0_EN TCK_EN TDI_EN TDO_EN TMS_EN Access rights r/w r/w r/w r/w r/w r/w r/w r/w Table 189. PinEn bits OM9663 Product data sheet COMPANY PUBLIC Bit Symbol Description 7 SIGIN_EN Enables the output functionality on SIGIN (pin 5). The pin is then used as I/O. 6 CLKOUT_EN Enables the output functionality of the CLKOUT (pin 22). The pin is then used as I/O. The CLKOUT function is switched off. 5 IFSEL1_EN Enables the output functionality of the IFSEL1 (pin 27). The pin is then used as I/O. 4 IFSEL0_EN Enables the output functionality of the IFSEL0 (pin 26). The pin is then used as I/O. 3 TCK_EN Enables the output functionality of the TCK (pin 4) of the boundary scan interface. The pin is then used as I/O. If the boundary scan is activated in EEPROM, this bit has no function. 2 TDI_EN Enables the output functionality of the TDI (pin 2) of the boundary scan interface. The pin is then used as I/O. If the boundary scan is activated in EEPROM, this bit has no function. 1 TDO_EN Enables the output functionality of the TDO (pin 1) of the boundary scan interface. The pin is then used as I/O. If the boundary scan is activated in EEPROM, this bit has no function. 0 TMS_EN Enables the output functionality of the TMS (pin 3) of the boundary scan interface. The pin is then used as I/O. If the boundary scan is activated in EEPROM, this bit has no function. All information provided in this document is subject to legal disclaimers. © NXP B.V. 2013. All rights reserved. Rev. 3.0 — 9 December 2013 103 of 137 OM9663 NXP Semiconductors High performance NFC reader solution 9.15.2 PinOut Table 190. PinOut register (address 45h) Bit 7 6 5 Symbol SIGIN_OUT CLKOUT_OUT Access rights r/w r/w 4 IFSEL1_OUT IFSEL0_OUT r/w 3 2 TCK_OU T TDI_OUT r/w r/w r/w r/w r/w 1 0 TDO_OUT TMS_OUT Table 191. PinOut bits Bit Symbol Description 7 SIGIN_OUT Output buffer of the SIGIN pin 6 CLKOUT_OUT Output buffer of the CLKOUT pin 5 IFSEL1_OUT Output buffer of the IFSEL1 pin 4 IFSEL0_OUT Output buffer of the IFSEL0 pin 3 TCK_OUT Output buffer of the TCK pin 2 TDI_OUT Output buffer of the TDI pin 1 TDO_OUT Output buffer of the TDO pin 0 TMS_OUT Output buffer of the TMS pin 9.15.3 PinIn Table 192. PinIn register (address 46h) Bit 7 6 5 4 3 2 1 0 Symbol SIGIN_IN CLKOUT_IN IFSEL1_IN IFSEL0_IN TCK_IN TDI_IN TDO_IN TMS_IN Access rights r r r r r r r r 2 1 0 Table 193. PinIn bits Bit Symbol Description 7 SIGIN_IN Input buffer of the SIGIN pin 6 CLKOUT_IN Input buffer of the CLKOUT pin 5 IFSEL1_IN Input buffer of the IFSEL1 pin 4 IFSEL0_IN Input buffer of the IFSEL0 pin 3 TCK_IN Input buffer of the TCK pin 2 TDI_IN Input buffer of the TDI pin 1 TDO_IN Input buffer of the TDO pin 0 TMS_IN Input buffer of the TMS pin 9.15.4 SigOut Table 194. SigOut register (address 47h) Bit 7 6 5 4 3 Symbol Pad Speed RFU SigOutSel Access rights r/w - r/w OM9663 Product data sheet COMPANY PUBLIC All information provided in this document is subject to legal disclaimers. © NXP B.V. 2013. All rights reserved. Rev. 3.0 — 9 December 2013 104 of 137 OM9663 NXP Semiconductors High performance NFC reader solution Table 195. SigOut bits Bit Symbol Description 7 PadSpeed If set, the I/O pins are supporting a fast switching mode.The fast mode for the I/O’s will increase the peak current consumption of the device, especially if multiple I/Os are switching at the same time. The power supply needs to be designed to deliver this peak currents. 6 to 4 RFU - 3 to 0 SIGOutSel 0h, 1h - The pin SIGOUT is 3-state 2h - The pin SIGOUT is 0 3h - The pin SIGOUT is 1 4h - The pin SIGOUT shows the TX-envelope 5h - The pin SIGOUT shows the TX-active signal 6h - The pin SIGOUT shows the S3C (generic) signal 7h - The pin SIGOUT shows the RX-envelope (only valid for ISO/IEC 14443A, 106 kBd) 8h - The pin SIGOUT shows the RX-active signal 9h - The pin SIGOUT shows the RX-bit signal 9.16 Protocol configuration registers 9.16.1 TxBitMod Table 196. TxBitMod register (address 48h) Bit 7 6 5 4 3 2 1 0 Symbol TxMSBFirst RFU TxParity Type RFU TxStopBitType RFU TxStartBitType TxStartBitEn Access rights r/w - r/w - r/w - r/w r/w Table 197. TxBitMod bits OM9663 Product data sheet COMPANY PUBLIC Bit Symbol Description 7 TxMSBFirst If set, data is interpreted MSB first for data transmission. If cleared, data is interpreted LSB first. 6 RFU - 5 TxParityType Defines the type of the parity bit. If set to 1, odd parity is calculated, otherwise even parity is calculated. 4 RFU - 3 TxStopBitType Defines the type of the stop-bit (0b: logic zero / 1b: logic one). 2 RFU 1 TxStartBitType Defines the type of the start-bit (0b: logic zero / 1b: logic one). 0 TxStartBitEn If set to 1, a start-bit will be sent. All information provided in this document is subject to legal disclaimers. © NXP B.V. 2013. All rights reserved. Rev. 3.0 — 9 December 2013 105 of 137 OM9663 NXP Semiconductors High performance NFC reader solution 9.16.2 TxDataCon Table 198. TxDataCon (address 4Ah) Bit 7 6 5 4 3 2 1 Symbol DCodeType DSCFreq DBFreq Access rights r/w r/w r/w 0 Table 199. TxDataCon bits Bit Symbol Description 7 to 4 DCodeType Specifies the type of encoding of data to be used: 0h - no special coding 1h - collider datastream is decoded 2h - RFU 3h - RFU 4h - return to zero code - pulse at first position 5h - return to zero code - pulse at 2nd position 6h - return to zero code - pulse at 3rd position 7h - return to zero code - pulse at 4th position 8h - 1 out of 4 coding 9h - 1 out of 256 code (range 0 - 255) [ICODE SLI] Ah - 1 out of 256 code (range 0 - 255; 00h is encoded with no modulation, value 256 not used) [ICODE 1] Bh - 1 out of 256 code (range 0 - 255; 00h is encoded with a pulse on last position) [I Code quite value] Ch- Pulse internal encoded (PIE) [ISO/IEC 18000-3 mode 3/ EPC Class-1HF] Dh - RFU Eh - RFU Fh - RFU 3 DSCFreq Specifies the subcarrier frequency of the used envelope. 0h - 424 kHz 1h - 848 kHz Note: This setting is only relevant, if an envelope is used which involves a subcarrier, e.g. Manchester with subcarrier coding. 2 to 0 DBFreq Specifies the frequency of the bit stream: 0h - RFU 1h - RFU 2h - 26 kHz 3h - 53 kHz 4h - 106 kHz 5h - 212 kHz 6h - 424 kHz 7h - 848 kHz 9.16.3 TxDataMod Table 200. TxDataMod register (address 4Bh) Bit 7 6 Symbol Frame step DMillerEn DPulseType DInvert DEnvType Access rights r/w r/w r/w r/w r/w OM9663 Product data sheet COMPANY PUBLIC 5 4 3 All information provided in this document is subject to legal disclaimers. 2 1 0 © NXP B.V. 2013. All rights reserved. Rev. 3.0 — 9 December 2013 106 of 137 OM9663 NXP Semiconductors High performance NFC reader solution Table 201. TxDataMod bits Bit Symbol Description 7 Framestep If set to 1, at every start of transmission, each byte of data is sent in a separate frame. SOF and EOF is appended to the data byte according to the framing settings. After one byte is transmitted, the TxEncoder waits for a new start trigger to continue with the next byte (trigger is generated automatically). If set to 0, transmission is done in the used way, where after a start trigger all data bytes are sent and the framing is done for the complete data stream only once. 6 DMillerEn If set, pulse modulation is applied according to modified miller code. 5 to 4 DPulseType Note: This bit is intended to be set if DPulseType is 1h. Specifies which type of pulse modulation is selected. 0h - no pulse modulation 1h - pulse starts at beginning of bit 2h - pulse starts at beginning of second bit half 3h - pulse starts at beginning of third bit quarter Note: If DMillerEn is set, DPulseType must be set to 1h. 3 DInvert If set the envelope of data is inverted. 2 to 0 DEnvType Specifies the type of envelope used for transmission of data packets. The selected envelope type is applied to the pseudo bit stream. 0h - Direct output 1h - Manchester code 2h - Manchester code with subcarrier 3h - BPSK 4h - RZ (pulse of half bit length at beginning of second half of bit) 5h - RZ (pulse of half bit length at beginning of bit) 6h - RFU 7h - RFU 9.16.4 TxSymFreq Table 202. TxSymFreq (address 4Ch) Bit 7 6 5 4 3 2 1 Symbol S32SCFreq S32BFreq S10SCFreq S10BFreq Access rights r/w r/w r/w r/w OM9663 Product data sheet COMPANY PUBLIC All information provided in this document is subject to legal disclaimers. 0 © NXP B.V. 2013. All rights reserved. Rev. 3.0 — 9 December 2013 107 of 137 OM9663 NXP Semiconductors High performance NFC reader solution Table 203. TxSymFreq bits Bit Symbol Description 7 S32SCFreq Specifies the frequency of the subcarrier of symbol2 and symbol3: 0b ... 424 kHz 1b ... 848 kHz 6 to 4 S32BFreq Specifies the frequency of the bit stream of symbol2 and symbole3: 000b ... RFU 001b ... RFU 010b ... 26 kHz 011b ... 53 kHz 100b ... 106 kHz 101b ... 212 kHz 110b ... 424 kHz 111b ... 848 kHz 3 S10SCFreq Specifies the frequency of the subcarrier of symbol0 and symbol1: 0b ...424 kHz 1b ...848 kHz 2 to 0 S10BFreq Specifies the frequency of the bit stream of symbol0 and symbol1: 000b ... RFU 001b ... RFU 010b ... 26 kHz 011b ... 53 kHz 100b ... 106 kHz 101b ... 212 kHz 110b ... 424 kHz 111b ... 848 kHz 9.16.5 TxSym0 The two Registers TxSym0H and TxSym0L create a 16-bit register that contains the pattern for Symbol0. Table 204. TxSym0H (address 4Dh) Bit 7 6 5 4 3 Symbol Symbol0_H Access rights r/w 2 1 0 1 0 Table 205. TxSYM0H bits Bit Symbol Description 7 to 0 Symbol0H Higher 8 bits of symbol definition for Symbol0. Table 206. TxSym0L (address 4Eh) Bit 7 6 5 4 3 Symbol Symbol0_L Access rights r/w 2 Table 207. TxSYM0L bits OM9663 Product data sheet COMPANY PUBLIC Bit Symbol Description 7 to 0 Symbol0_L Lower 8 bits of symbol definition for Symbol0. All information provided in this document is subject to legal disclaimers. © NXP B.V. 2013. All rights reserved. Rev. 3.0 — 9 December 2013 108 of 137 OM9663 NXP Semiconductors High performance NFC reader solution 9.16.6 TxSym The two Registers TxSym1H and TxSym1L create a 16 bit register that contains the pattern for Symbol1. Table 208. TxSym1H (address 4Fh) Bit 7 6 5 4 3 Symbol Symbol1_H Access rights r/w 2 1 0 1 0 2 1 0 2 1 0 Table 209. TxSym1H bits Bit Symbol Description 7 to 0 Symbol1_H Higher 8 bits of symbol definition for Symbol1. Table 210. TxSym1L (address 50h) Bit 7 6 5 4 3 Symbol Symbol1_L Access rights r/w 2 Table 211. TxSym1L bits Bit Symbol Description 7 to 0 Symbol1_L Lower 8 bits of symbol definition for Symbol1. 9.16.7 TxSym2 Table 212. TxSYM2 (address 51h) Bit 7 6 5 4 3 Symbol Symbol2 Access rights r/w Table 213. TxSym2 bits Bit Symbol Description 7 to 0 Symbol2 Symbol definition for Symbol2. 9.16.8 TxSym3 Table 214. TxSym3 (address 52h) Bit 7 6 5 4 3 Symbol Symbol3 Access rights r/w Table 215. TxSym3 bits OM9663 Product data sheet COMPANY PUBLIC Bit Symbol Description 7 to 0 Symbol3 Symbol definition for Symbol3. All information provided in this document is subject to legal disclaimers. © NXP B.V. 2013. All rights reserved. Rev. 3.0 — 9 December 2013 109 of 137 OM9663 NXP Semiconductors High performance NFC reader solution 9.16.9 TxSym10Len Table 216. TxSym10Len (address 53h) Bit 7 6 5 4 3 2 1 Symbol Sym1Len Sym0Len Access rights r/w r/w 0 Table 217. TxSym10Len bits Bit Symbol Description 7 to 4 Sym1Len Specifies the number of valid bits of the symbol definition of Symbol1. The range is from 1 bit (0h) to 16 bits (Fh). 3 to 0 Sym0Len Specifies the number of valid bits of the symbol definition of Symbol0. The range is from 1 bit (0h) to 16 bits (Fh). 9.16.10 TxSym32Len Table 218. TxSym32Len (address 54h) Bit 7 Symbol RFU Access rights - 6 5 4 3 Sym3Len r/w 2 RFU r/w r/w 1 0 Sym2Len - r/w r/w r/w Table 219. TxSym32Len bits Bit Symbol Description 7 RFU - 6 to 4 Sym3Len Specifies the number of valid bits of the symbol definition of Symbol3. The range is from 1-bit (0h) to 8-bits (7h). 3 RFU - 2 to 0 Sym2Len Specifies the number of valid bits of the symbol definition of Symbol2. The range is from 1-bit (0h) to 8-bits (7h). 9.16.11 TxSym10BurstCtrl Table 220. TxSym10BurstCtrl register (address 55h) Bit 7 6 5 4 3 2 1 0 Symbol RFU Sym1BurstType Sym1BurstOnly Sym1BurstEn RFU Sym0Burst Type Sym0Burst Only Sym0Burst En Access rights - r/w r/w r/w - r/w r/w r/w Table 221. TxSym10BurstCtrl bits OM9663 Product data sheet COMPANY PUBLIC Bit Symbol Description 7 RFU - 6 Sym1BurstType Specifies the type of the burst of Symbol1 (logical zero / logical one). 5 Sym1BurstOnly If set to 1 Symbol1 consists only of a burst and no symbol pattern. All information provided in this document is subject to legal disclaimers. © NXP B.V. 2013. All rights reserved. Rev. 3.0 — 9 December 2013 110 of 137 OM9663 NXP Semiconductors High performance NFC reader solution Table 221. TxSym10BurstCtrl bits …continued Bit Symbol Description 4 Sym1BurstEn Enables the burst of symbol 1 of the length defined in TxSym10BurstLen. 3 RFU - 2 Sym0BurstType Specifies the type of the burst of symbol 0 (logical zero / logical one). 1 Sym0BurstOnly If set to 1, symbol 0 consists only of a burst and no symbol pattern. 0 Sym0BurstEn Enables the burst of symbol 0 of the length defined in TxSym10BurstLen. 9.16.12 TxSym10Mod Reg Table 222. TxSym10Mod register (address 56h) Bit 7 6 Symbol RFU S10MillerEn 5 S10PulseType 4 S10Inv 3 2 S10EnvType 1 Access rights - r/w r/w r/w r/w 0 Table 223. TxSym10Mod bits Bit Symbol Description 7 RFU - 6 S10MillerEn If set, pulse modulation is applied according to modified miller code. Note: This bit shall be set only if S10PulseType is set to 1h. 5 to 4 S10PulseType Specifies which type of pulse modulation is selected: 0h - no pulse modulation 1h - pulse starts at beginning of bit 2h - pulse starts at beginning of second bit half 3h - pulse starts at beginning of third bit quarter 3 S10Inv If set. the output of Symbol0 and Symbol1 is inverted. 2 to 0 S10EnvType Specifies the type of envelope used for transmission of Symbol0 and Symbol1. The pseudo bit stream is logically combined with the selected envelope type. 0h - Direct output 1h - Manchester code 2h - Manchester code with subcarrier 3h - BPKSK 4h - RZ return zero, pulse of half bit length at beginning of second half of bit 5h - RZ return zero, pulse of half bit length at beginning of second half of bit 6h - RFU 7h - RFU OM9663 Product data sheet COMPANY PUBLIC All information provided in this document is subject to legal disclaimers. © NXP B.V. 2013. All rights reserved. Rev. 3.0 — 9 December 2013 111 of 137 OM9663 NXP Semiconductors High performance NFC reader solution 9.16.13 TxSym32Mod Table 224. TxSym32Mod register (address 57h) Bit 7 6 5 4 3 2 1 0 Symbol RFU S32MillerEn S32PulseType S32Inv S32EnvType Access rights - r/w r/w r/w r/w Table 225. TxSym32Mod bits Bit Symbol Description 7 RFU - 6 S32MillerEn If set, pulse modulation is applied according to modified miller code. Note: This bit shall be set only if S32PulseType is set to 1h. 5 to 4 S32PulseType Specifies which type of pulse modulation is selected: 0h - no pulse modulation 1h - pulse starts at beginning of bit 2h - pulse starts at beginning of second bit half 3h - pulse starts at beginning of third bit quarter 3 S32Inv If set. the output of Symbol2 and Symbol3 is inverted. 2 to 0 S32EnvType Specifies the type of envelope used for transmission of symbol 0 and symbol 1. The bit stream is logically combined with the selected envelope type. 0h - Direct output 1h - Manchester code 2h - Manchester code with subcarrier 3h - BPSK 4h - RZ return zero, pulse of half bit length at beginning of second half of bit) 5h - RZ return zero, pulse of half bit length at beginning of bit) 6h to 7h RFU 9.17 Receiver configuration 9.17.1 RxBitMod Table 226. RxBitMod (address 58h) Bit 7 6 5 4 3 2 1 0 Symbol RFU RFU RxStopOnInvPar RxStopOnLength RxMSBFirst RxStopBitEn RxParityType RFU Access rights - - r/w r/w r/w r/w r/w - OM9663 Product data sheet COMPANY PUBLIC All information provided in this document is subject to legal disclaimers. © NXP B.V. 2013. All rights reserved. Rev. 3.0 — 9 December 2013 112 of 137 OM9663 NXP Semiconductors High performance NFC reader solution Table 227. RxBitMod bits Bit Symbol Description 7 to 6 RFU - 5 RxStopOnInvPar If set to 1, inverse parity bit is a stop condition. 4 RxStopOnLength If set to 1, data reception stops when the number of received bytes reach the defined frame length. The value for the frame length is taken from the first data-byte received. 3 RxMSBFirst If set to 1, data bytes are interpreted MSB first for data reception, which means data is converted at the CLCoPro interface. If this bit is set to 0, data is interpreted LSB first. 2 RxStopBitEn If set, a stop-bit is expected and will be checked and extracted from data stream. Additionally on detection of a stop-bit a reset signal for the demodulator is generator to enable a re-synchronization of the demodulator. If the expected stop-bit is incorrect, a frame error flag is set and the reception is aborted. Note: A stop bit is always considered to be a logic 1 1 RxParityType Defines which type of the parity-bit is calculated: If cleared: Even parity If set: Odd parity 0 RFU - 9.17.2 RxEofSym Table 228. RxEofSym (address 59h) Bit 7 6 5 4 3 Symbol RxEOFSymbol Access rights r/w 2 1 0 Table 229. RxEOFSym bits Bit Symbol Description 7 to 0 RxEOF Symbol This value defines the pattern of the EOF symbol with a maximum length of 4 bit. Every tuple of 2 bits of the RxEOFSymbol encodes one bit of the EOF symbol. A 00 tuple closes the symbol. In this way symbols with less than 4 bits can be defined, starting with the bit0 and bit1. The leftmost active symbol pattern is processed first, which means the pattern is expected first. If the bit0 and bit1 are both zero, the EOF symbol is disabled. The following mapping is defined: 0h - no symbol bit 1h - zero value 2h - one value 3h - collision Example: 1Dh: Zero-Collision-Zero E8h: No symbol because two LSBits are zero OM9663 Product data sheet COMPANY PUBLIC All information provided in this document is subject to legal disclaimers. © NXP B.V. 2013. All rights reserved. Rev. 3.0 — 9 December 2013 113 of 137 OM9663 NXP Semiconductors High performance NFC reader solution 9.17.3 RxSyncValH Table 230. RxSyncValH register (address5Ah) Bit 7 6 5 4 3 Symbol RxSyncValH Access rights r/w 2 1 0 Table 231. RxSyncValH bits Bit Symbol Description 15 to 0 RxSyncValH Defines the high byte of the Start Of Frame (SOF) pattern, which must be in front of the receiving data. 9.17.4 RxSyncValL Table 232. RxSyncValL register (address 5Bh) Bit 7 6 5 4 3 Symbol RxSyncValL Access rights r/w 2 1 0 Table 233. RxSyncValL bits Bit Symbol Description 7 to 0 RxSyncValL Defines the low byte of the Start Of Frame (SOF) Pattern, which must be in front of the receiving data. 9.17.5 RxSyncMod Table 234. RxSyncMode register (address 5Ch) Bit 7 6 5 4 3 2 1 0 Symbol SyncLen SyncNegEdge LastSyncHalf SyncType Access rights r/w r/w r/w r/w Table 235. RxSyncMod bits Bit Symbol Description 7 to 4 SyncLen Defines how many Bits of registers RxSyncValH and RxSyncValL are valid. For ISO/IEC 14443B set to 0. 3 SyncNegEdge Is used for SOF with no correlation peak. The first negative edge of the correlation is used for defining the bit grid. 2 LastSyncHalf The last Bit of the Sync mode has only half of the length compared to all other bits. (ISO/IEC 18000-3 mode 3/ EPC Class-1HF). 1 to 0 SyncType 0: all 16 bits of SyncVal are interpreted as burst. 1: a nibble of bits is interpreted as one bit in following way: {data, coll} data = zero or one; coll = 1 means a collision on this bit. Note: if Coll = 1 the value of data is ignored. 2: the synchronisation is done at every start bit of each byte (type B) 3: RFU OM9663 Product data sheet COMPANY PUBLIC All information provided in this document is subject to legal disclaimers. © NXP B.V. 2013. All rights reserved. Rev. 3.0 — 9 December 2013 114 of 137 OM9663 NXP Semiconductors High performance NFC reader solution 9.17.6 RxMod Table 236. RxMod register (address 5Dh) Bit 7 6 5 4 3 2 1 0 Symbol RFU RFU PreFilter RectFilter SyncHigh CorrInv FSK BPSK Access rights - - r/w r/w r/w r/w r/w r/w Table 237. RxMod bits Bit Symbol Description 7 to 6 - RFU 5 PreFilter If set 4 samples are combined to one data. (average). 4 RectFilter If set, the ADC-values are changed to a more rectangular wave shape. 3 SyncHigh Defines if the bit grid is fixed at maximum (1) or at minimum (0) value of the correlation. 2 CorrInv Defines a logical for Manchester coding: 0: subcarrier / no subcarrier. 1 FSK If set to 1, the demodulation scheme is set to FSK. 0 BPSK If set to 1, the modulation scheme is BPSK. 9.17.7 RxCorr Table 238. RxCorr register (address 5Eh) Bit 7 Symbol Access rights 6 5 4 CorrFreq r/w CorrSpeed r/w r/w 3 2 1 0 CorrLen RFU r/w - r/w Table 239. RxCorr bits Bit Symbol Description 7, 6 CorrFreq 0h - 212 kHz 1h - 424 kHz 2h - 848 kHz 3h - 848 kHz 5, 4 CorrSpeed Defines the number of clocks used for one correlation. 0h - ISO/IEC 14443 1h - ICODE 53 kBd, FeliCa 424 kBd 2h - ICODE 26 kBd, FeliCa 212 kBd 3h - RFU 3 CorrLen Defines the length of the correlation data. (64 or 32 values). If set the lengths of the correlation data is 32 values. (ISO/IEC 18000-3 mode 3/ EPC Class-1HF, 2 Pulse Manchester 848 kHz subcarrier). 2 to 0 OM9663 Product data sheet COMPANY PUBLIC RFU - All information provided in this document is subject to legal disclaimers. © NXP B.V. 2013. All rights reserved. Rev. 3.0 — 9 December 2013 115 of 137 OM9663 NXP Semiconductors High performance NFC reader solution 9.17.8 FabCali Table 240. FabCali register (address 5Fh) Bit 7 6 5 4 3 Symbol FabCali Access rights r/w 2 1 0 Table 241. FabCali bits Bit Symbol 7 to 0 FabCali Description Fabrication calibration of the receiver. NOTE: do not change boot value. 9.18 Version register 9.18.1 Version Table 242. Version register (address 7Fh) Bit 7 6 5 4 3 2 1 Symbol Version SubVersion Access rights r r 0 Table 243. Version bits OM9663 Product data sheet COMPANY PUBLIC Bit Symbol Description 7 to 4 Version Includes the version of the OM9663 silicon. 3 to 0 SubVersion Includes the subversion of the OM9663 silicon. All information provided in this document is subject to legal disclaimers. © NXP B.V. 2013. All rights reserved. Rev. 3.0 — 9 December 2013 116 of 137 OM9663 NXP Semiconductors High performance NFC reader solution 10. Limiting values Table 244. Limiting values In accordance with the Absolute Maximum Rating System (IEC 60134). Symbol Parameter VDD supply voltage Conditions Min Max Unit 0.5 +5.5 V VDD(PVDD) PVDD supply voltage 0.5 +5.5 V VDD(TVDD) TVDD supply voltage 0.5 +5.5 V Vi(RXP) input voltage on pin RXP -0.5 +2.0 V Vi(RXN) input voltage on pin RXN 0.5 +2.0 V Ptot total power dissipation - 1125 mW VESD(HBM) electrostatic discharge voltage Human Body Model (HBM); 1500 , 100 pF; JESD22-A114-B per package - 2000 V VESD(CDM) electrostatic discharge voltage Charge Device Model (CDM); - 500 V Tj(max) maximum junction temperature - 150 °C 11. Recommended operating conditions Table 245. Operating conditions Symbol Parameter VDD supply voltage Conditions [1] Min Typ Max Unit 3 5 5.5 V VDD(TVDD) TVDD supply voltage 3 5 5.5 V VDD(PVDD) PVDD supply voltage 3 5 5.5 V Tamb ambient temperature 25 - +85 C [1] VDD(PVDD) must always be the same or lower than VDD. 12. Thermal characteristics Table 246. Thermal characteristics Symbol Parameter Rth(j-a) thermal resistance from junction to ambient Conditions Package Typ in still air with exposed pin soldered on a 4 layer JEDEC PCB HVQFN32 40 Unit K/W 13. Characteristics Table 247. Characteristics Symbol Parameter Conditions Min Typ Max Unit - 2 100 nA 0.5 - +0.3VDD(PVDD) V 0.7VDD(PVDD) - VDD(PVDD) + 0.5 V - - 0.3 Input characteristics I/O Pin Characteristics IF3-SDA in I2C configuration ILI input leakage current VIL LOW-level input voltage VIH HIGH-level input voltage VOL LOW-level output voltage OM9663 Product data sheet COMPANY PUBLIC output disabled IOL = 3 mA All information provided in this document is subject to legal disclaimers. V © NXP B.V. 2013. All rights reserved. Rev. 3.0 — 9 December 2013 117 of 137 OM9663 NXP Semiconductors High performance NFC reader solution Table 247. Characteristics …continued Symbol Parameter Conditions Min Typ Max Unit IOL LOW-level output current VOL = 0.4 V; Standard mode, Fast mode 4 - - mA VOL = 0.6 V; Standard mode, Fast mode 6 - - mA Standard mode, Fast mode, CL < 400 pF - - 250 ns Fast mode +; CL < 550 pF - - 120 ns tf(o) output fall time tSP pulse width of spikes that must be suppressed by the input filter 0 - 50 ns Ci input capacitance - 3.5 5 pF CL load capacitance Standard mode - - 400 pF Fast mode - - 550 pF Tamb = +55 °C 10 - - year EEPROM endurance under all operating 5 x 105 - - cycle (number of programming conditions - 1.8 - V tEER EEPROM data retention time NEEC cycles) Analog and digital supply AVDD,DVDD VDDA analog supply voltage VDDD digital supply voltage - 1.8 - V CL load capacitance AVDD 220 470 - nF CL load capacitance DVDD 220 470 - nF Current consumption Istb standby current Standby bit = 1 - 3 6 A IDD supply current modem on - 17 20 mA modem off - 0.45 0.5 mA - 100 200 mA - 50 500 nA 0.5 - 0.3VDD(PVDD) V IDD(TVDD) TVDD supply current I/O pin characteristics SIGIN, SIGOUT, CLKOUT, IFSEL0, IFSEL1, TCK, TMS, TDI, TDO, IRQ, IF0, IF1, IF2, SCL2, SDA2 ILI input leakage current VIL LOW-level input voltage VIH HIGH-level input voltage VOL LOW-level output voltage VOH Ci output disabled 0.7VDD(PVDD) - VDD(PVDD) + 0.5 V IOL = 4 mA, VDD(PVDD) = 5.0 V - - 0.4 V IOL = 4 mA, VDD(PVDD) = 3.3 V - - 0.4 V HIGH-level output voltage IOL = 4 mA, VDD(PVDD) = 5.0 V 4.6 - - V IOL = 4 mA, VDD(PVDD) = 3.3 V 2.9 - - V - 2.5 4.5 pF 50 72 120 K input capacitance Pull-up resistance for TCK, TMS, TDI, IF2 Rpu pull-up resistance OM9663 Product data sheet COMPANY PUBLIC All information provided in this document is subject to legal disclaimers. © NXP B.V. 2013. All rights reserved. Rev. 3.0 — 9 December 2013 118 of 137 OM9663 NXP Semiconductors High performance NFC reader solution Table 247. Characteristics …continued Symbol Parameter Conditions Min Typ Max Unit Pin characteristics AUX 1, AUX 2 Vo output voltage 0 - 1.8 V CL load capacitance - - 400 pF Pin characteristics RXP, RXN Vi input voltage 0 - 1.8 V Ci input capacitance 2 3.5 5 pF Vmod(pp) modulation voltage - 2.5 - mV - - 1.65 V Vmod(pp) = Vi(pp)(max)  Vi(pp) (min) Vpp signal on RXP, RXN Pins TX1 and TX2 Vo output voltage Vss(TVSS) - VDD(TVDD) V Ro output resistance - 1.5 -  - 8 40 nA Current consumption power-down current Ipd ambient temp = 25°C ambient temp = 85°C Istby standby current ILPCD LPCD sleep current IDD supply current ambient temp = 25°C - 200 400 nA [1] - 3 6 A [1] - 3 6 A - 17 20 mA 0.5 mA modem off; transceiver off IDD(PVDD) PVDD supply current IDD(TVDD) TVDD supply current no load on digital pin - 0.45 [2] - - 10 A [3][4][5] - 100 200 mA - 27.12 - MHz - 50 - % - 1 - V Clock frequency Pin CLKOUT fclk clock frequency clk clock duty cycle configured to 27.12 MHz Crystal oscillator Vo(p-p) peak-to-peak output voltage pin XTAL1 Vi input voltage pin XTAL1 0 - 1.8 V Ci input capacitance pin XTAL1 - 3 - pF Typical input requirements fxtal crystal frequency - 27.12 - MHz ESR equivalent series resistance - 50 100  CL load capacitance - 10 - pF Pxtal crystal power dissipation - 50 100 W [1] Ipd is the total current for all supplies. [2] IDD(PVDD) depends on the overall load at the digital pins. [3] IDD(TVDD) depends on VDD(TVDD) and the external circuit connected to pins TX1 and TX2. [4] During typical circuit operation, the overall current is below 100 mA. [5] Typical value using a complementary driver configuration and an antenna matched to 40  between pins TX1 and TX2 at 13.56 MHz. OM9663 Product data sheet COMPANY PUBLIC All information provided in this document is subject to legal disclaimers. © NXP B.V. 2013. All rights reserved. Rev. 3.0 — 9 December 2013 119 of 137 OM9663 NXP Semiconductors High performance NFC reader solution Vmod Vi(p-p)(max) Vi(p-p)(min) VMID 13.56 MHz carrier 0V 001aak012 Fig 34. Pin RX input voltage 13.1 Timing characteristics Table 248. SPI timing characteristics Symbol Parameter tSCKL Conditions Min Typ Max Unit SCK LOW time 50 - - ns tSCKH SCK HIGH time 50 - - ns th(SCKH-D) SCK HIGH to data input hold SCK to changing MOSI time 25 - - ns tsu(D-SCKH) data input to SCK HIGH set-up time changing MOSI to SCK 25 - - ns th(SCKL-Q) SCK LOW to data output hold time SCK to changing MISO - - 25 ns t(SCKL-NSSH) SCK LOW to NSS HIGH time 0 - - ns tNSSH NSS HIGH time 50 - - ns before communication Remark: To send more bytes in one data stream the NSS signal must be LOW during the send process. To send more than one data stream the NSS signal must be HIGH between each data stream. Table 249. I2C-bus timing in fast mode and fast mode plus Symbol Parameter OM9663 Product data sheet COMPANY PUBLIC Conditions Fast mode Fast mode Plus Unit Min Max Min Max 0 400 0 1000 kHz after this period, 600 the first clock pulse is generated - 260 - ns fSCL SCL clock frequency tHD;STA hold time (repeated) START condition tSU;STA set-up time for a repeated START condition 600 - 260 - ns tSU;STO set-up time for STOP condition 600 - 260 - ns tLOW LOW period of the SCL clock 1300 - 500 - ns tHIGH HIGH period of the SCL clock 600 - 260 - ns tHD;DAT data hold time 0 900 - 450 ns All information provided in this document is subject to legal disclaimers. © NXP B.V. 2013. All rights reserved. Rev. 3.0 — 9 December 2013 120 of 137 OM9663 NXP Semiconductors High performance NFC reader solution Table 249. I2C-bus timing in fast mode and fast mode plus …continued Symbol Parameter Conditions Fast mode Fast mode Plus Min Max Min Max 100 - - - Unit tSU;DAT data set-up time ns tr rise time SCL signal 20 300 - 120 ns tf fall time SCL signal 20 300 - 120 ns tr rise time SDA and SCL signals 20 300 - 120 ns tf fall time SDA and SCL signals 20 300 - 120 ns tBUF bus free time between a STOP and START condition 1.3 - 0.5 - s SDA tSU;DAT tf tSP tr tHD;STA tf tLOW tBUF SCL tr tHD;STA S tHIGH tHD;DAT tSU;STA tSU;STO Sr P S 001aaj635 Fig 35. Timing for fast and standard mode devices on the I2C-bus OM9663 Product data sheet COMPANY PUBLIC All information provided in this document is subject to legal disclaimers. © NXP B.V. 2013. All rights reserved. Rev. 3.0 — 9 December 2013 121 of 137 OM9663 NXP Semiconductors High performance NFC reader solution 14. Application information A typical application diagram using a complementary antenna connection to the OM9663 is shown in Figure 36. The antenna tuning and RF part matching is described in the application note Ref. 1 and Ref. 2. VDD PVDD TVDD 25 18 8 AVDD 9 13 14 PDOWN MICROPROCESSOR host interface 21 17 16 32 15 DVDD VMID TX1 CRXN R1 C vmid R2 C1 L0 Ra antenna READER IC 28-31 IRQ RXN C0 C2 C0 C2 Ra TVSS TX2 Lant L0 C1 14 7 12 33 VSS 19 RXP 20 XTAL1 XTAL2 R3 R4 CRXP 27.12 MHz 001aam269 Fig 36. Typical application antenna circuit diagram 14.1 Antenna design description The matching circuit for the antenna consists of an EMC low pass filter (L0 and C0), a matching circuitry (C1 and C2), and a receiving circuits (R1 = R3, R2 = R4, C3 = C5 and C4 = C6;), and the antenna itself. The receiving circuit component values needs to be designed for operation with the OM9663. A reuse of dedicated antenna designs done for other products without adaptation of component values will result in degraded performance. For a more detailed information about designing and tuning the antenna, please refer to the relevant application notes: • MICORE reader IC family; Directly Matched Antenna Design, Ref. 1 and • MIFARE (14443A) 13.56 MHz RFID Proximity Antennas, Ref. 2. 14.1.1 EMC low pass filter The MIFARE system operates at a frequency of 13.56 MHz. This frequency is derived from a quartz oscillator to clock the OM9663 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 OM9663 Product data sheet COMPANY PUBLIC All information provided in this document is subject to legal disclaimers. © NXP B.V. 2013. All rights reserved. Rev. 3.0 — 9 December 2013 122 of 137 OM9663 NXP Semiconductors High performance NFC reader solution 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. Remark: The PCB layout has a major influence on the overall performance of the filter. 14.1.2 Antenna matching 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 ISO/IEC 14443 communication scheme. Environmental influences have to be considered as well as common EMC design rules. For details refer to the NXP application notes. 14.1.3 Receiving circuit The internal receiving concept of the OM9663 makes use both side-bands of the sub-carrier load modulation of the card response via a differential receiving concept (RXP, RXN). 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-pins via R2 and R4. To provide a stable DC reference voltage capacitances C4, C6 has to be connected between VMID and ground. Refer to Figure 36 Considering the (AC) voltage limits at the Rx-pins the AC voltage divider of R1 + C3 and R2 as well as R3 + C5 and R4 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(= R3), R2 (= R4), and C3 (= C5) from the above mentioned application note, and adjust the voltage at the RX-pins by varying R1(= R3) within the given limits. Remark: R2 and R4 are AC-wise connected to ground (via C4 and C6). OM9663 Product data sheet COMPANY PUBLIC All information provided in this document is subject to legal disclaimers. © NXP B.V. 2013. All rights reserved. Rev. 3.0 — 9 December 2013 123 of 137 OM9663 NXP Semiconductors High performance NFC reader solution 14.1.4 Antenna coil 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. I1 1 8 L 1 = 2  I 1   ln  ------ – K N 1   D1 (4) • I1 - Length in cm 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) • L1 - Inductance in nH • 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 such as: • • • • • antenna construction (Type of PCB) thickness of conductor distance between the windings shielding layer metal or ferrite in the near environment Therefore a measurement of those parameters under real life conditions, or at least a rough measurement and a tuning procedure is highly recommended to guarantee a reasonable performance. For details refer to the above mentioned application notes. OM9663 Product data sheet COMPANY PUBLIC All information provided in this document is subject to legal disclaimers. © NXP B.V. 2013. All rights reserved. Rev. 3.0 — 9 December 2013 124 of 137 OM9663 NXP Semiconductors High performance NFC reader solution 15. Package outline HVQFN32: plastic thermal enhanced very thin quad flat package; no leads; 32 terminals; body 5 x 5 x 0.85 mm A B D SOT617-1 terminal 1 index area A A1 E c detail X C e1 e 1/2 e b 9 y y1 C v M C A B w M C 16 L 17 8 e e2 Eh 1/2 1 terminal 1 index area e 24 32 25 X Dh 0 2.5 5 mm scale DIMENSIONS (mm are the original dimensions) UNIT A(1) max. A1 b c D (1) Dh E (1) Eh e e1 e2 L v w y y1 mm 1 0.05 0.00 0.30 0.18 0.2 5.1 4.9 3.25 2.95 5.1 4.9 3.25 2.95 0.5 3.5 3.5 0.5 0.3 0.1 0.05 0.05 0.1 Note 1. Plastic or metal protrusions of 0.075 mm maximum per side are not included. REFERENCES OUTLINE VERSION IEC JEDEC JEITA SOT617-1 --- MO-220 --- EUROPEAN PROJECTION ISSUE DATE 01-08-08 02-10-18 Fig 37. Package outline SOT617-1 (HVQFN32) OM9663 Product data sheet COMPANY PUBLIC All information provided in this document is subject to legal disclaimers. © NXP B.V. 2013. All rights reserved. Rev. 3.0 — 9 December 2013 125 of 137 OM9663 NXP Semiconductors High performance NFC reader solution Detailed package information can be found at http://www.nxp.com/package/SOT617-1.html. 16. Handling information Moisture Sensitivity Level (MSL) evaluation has been performed according to SNW-FQ-225B rev.04/07/07 (JEDEC J-STD-020C). MSL for this package is level 2 which means 260 C convection reflow temperature. For MSL2: • Dry pack is required. • 1 year out-of-pack floor life at maximum ambient temperature 30 C/ 85 % RH. For MSL1: • No dry pack is required. • No out-of-pack floor live spec. required. 17. Packing information The straps around the package of stacked trays inside the piano-box have sufficient pre-tension to avoid loosening of the trays. strap 46 mm from corner tray ESD warning preprinted chamfer barcode label (permanent) PIN 1 barcode label (peel-off) chamfer QA seal PIN 1 Hyatt patent preprinted In the traystack (2 trays) only ONE tray type* allowed *one supplier and one revision number. printed piano box 001aaj740 Fig 38. Packing information 1 tray OM9663 Product data sheet COMPANY PUBLIC All information provided in this document is subject to legal disclaimers. © NXP B.V. 2013. All rights reserved. Rev. 3.0 — 9 December 2013 126 of 137 xxxxxxxxxxxxxxxxxxxxx xxxxxxxxxxxxxxxxxxxxxxxxxx xxxxxxx x x x xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx xxxxxxxxxxxxxxxxxxx xx xx xxxxx xxxxxxxxxxxxxxxxxxxxxxxxxxx xxxxxxxxxxxxxxxxxxx xxxxxx xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx xxxxxxxxxxxx x x xxxxxxxxxxxxxxxxxxxxx xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx xxxxx xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx xxxxxxxx xxxxxxxxxxxxxxxxxxxxxxxxx xxxxxxxxxxxxxxxxxxxx xxx NXP Semiconductors OM9663 Product data sheet COMPANY PUBLIC strap 46 mm from the corner PQ-label (permanent) bag dry-agent relative humidity indicator preprinted: recycling symbol moisture caution label ESD warning tray manufacturer bag info chamfer Rev. 3.0 — 9 December 2013 PQ-label (permanent) PIN 1 PLCC52 dry-pack ID preprinted chamfer strap PIN 1 QA seal chamfer printed plano box PIN 1 aaa-004952 Fig 39. Packing information 5 tray OM9663 © NXP B.V. 2013. All rights reserved. 127 of 137 High performance NFC reader solution All information provided in this document is subject to legal disclaimers. ESD warning preprinted xxxxxxxxxxxxxxxxxxxxx xxxxxxxxxxxxxxxxxxxxxxxxxx xxxxxxx x x x xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx xxxxxxxxxxxxxxxxxxx xx xx xxxxx xxxxxxxxxxxxxxxxxxxxxxxxxxx xxxxxxxxxxxxxxxxxxx xxxxxx xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx xxxxxxxxxxxx x x xxxxxxxxxxxxxxxxxxxxx xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx xxxxx xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx xxxxxxxx xxxxxxxxxxxxxxxxxxxxxxxxx xxxxxxxxxxxxxxxxxxxx xxx BB BA BA BD BD section BC-BC scale 4:1 BB A B C 0.50 3.00 2.50 1.55 3.32 1.10 (0.30) A B C end lock vacuum cell AJ AJ AR AR side lock AN AK AL AL section BA-BA scale 4:1 AK section AK-AK scale 5:1 AN section AN-AN scale 4:1 section AJ-AJ scale 2:1 section AL-AL scale 5:1 section AM-AM scale 4:1 section AR-AR scale 2:1 aaa-004949 OM9663 128 of 137 © NXP B.V. 2013. All rights reserved. Fig 40. Tray details AM High performance NFC reader solution detail AC scale 20:1 section BD-BD scale 4:1 AM 0.35 14.20±0.08+10°/S SQ. 1.20 12.80-5°/S SQ. 0.56 (14.40+5°/S SQ.) (1.45) 16.60±0.08+7°/S SQ. 13.85±0.08+12°/S SQ. (0.64) Rev. 3.0 — 9 December 2013 All information provided in this document is subject to legal disclaimers. BC 0.50 NXP Semiconductors OM9663 Product data sheet COMPANY PUBLIC BC xxxxxxxxxxxxxxxxxxxxx xxxxxxxxxxxxxxxxxxxxxxxxxx xxxxxxx x x x xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx xxxxxxxxxxxxxxxxxxx xx xx xxxxx xxxxxxxxxxxxxxxxxxxxxxxxxxx xxxxxxxxxxxxxxxxxxx xxxxxx xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx xxxxxxxxxxxx x x xxxxxxxxxxxxxxxxxxxxx xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx xxxxx xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx xxxxxxxx xxxxxxxxxxxxxxxxxxxxxxxxx xxxxxxxxxxxxxxxxxxxx xxx NXP Semiconductors OM9663 Product data sheet COMPANY PUBLIC ASSY REEL + LABELS tape (see: HOW TO SECURE) see: ASSY REEL + LABELS Ø 330x12/16/24/32 (hub 7’’) guard band label side embossed ESD logo tape (see: HOW TO SECURE) circular sprocket holes opposite the label side of reel printed plano-box cover tape embossed ESD logo Ø 330x16/24/32/44 (hub 4’’) Ø 330x44 (hub 6’’) carrier tape Rev. 3.0 — 9 December 2013 enlongated PIN1 has to be in quadrant 1 circular PIN1 PIN1 1 SO enlongated PLCC PIN1 PIN1 product orientation in carrier tape 2 3 4 BGA bare die QFP unreeling direction (HV)QFN (HV)SON (H)BCC product orientation ONLY for turned products with 12nc ending 128 PIN1 SO PIN1 QFP HOW TO SECURE LEADER END TO THE GUARD BAND, HOW TO SECURE GUARD BAND PIN1 1 2 PIN1 3 4 PIN1 for SOT765 BGA for SOT505-2 ending 125 bare die ending 125 (HV)QFN (HV)SON (H)BCC tapeslot label side trailer trailer : lenght of trailer shall be 160 mm min. and covered with cover tape leader : lenght of trailer shall be 400 mm min. and covered with cover tape circular sprocket hole side guard band leader QA seal tape (with pull tabs on both ends) preprinted ESD warning Fig 41. Packing information Reel guard band aaa-004950 OM9663 129 of 137 © NXP B.V. 2013. All rights reserved. PQ-label (permanent) dry-pack ID preprinted lape double-backed onto itself on both ends High performance NFC reader solution All information provided in this document is subject to legal disclaimers. Ø 180x12/16/24 OM9663 NXP Semiconductors High performance NFC reader solution 18. Abbreviations Table 250. Abbreviations Acronym OM9663 Product data sheet COMPANY PUBLIC Description ADC Analog-to-Digital Converter BPSK Binary Phase Shift Keying CRC Cyclic Redundancy Check CW Continuous Wave EGT Extra Guard Time EMC Electro Magnetic Compatibility EMD Electro Magnetic Disturbance EOF End Of Frame EPC Electronic Product Code ETU Elementary Time Unit GPIO General Purpose Input/Output HBM Human Body Model I2C Inter-Integrated Circuit LFO Low Frequency Oscillator LPCD Low-Power Card Detection LSB Least Significant Bit MISO Master In Slave Out MOSI Master Out Slave In MSB Most Significant Bit NRZ Not Return to Zero NSS Not Slave Select PCD Proximity Coupling Device PLL Phase-Locked Loop RZ Return To Zero RX Receiver SAM Secure Access Module SOF Start Of Frame SPI Serial Peripheral Interface SW Software TTimer Timing of the clk period TX Transmitter UART Universal Asynchronous Receiver Transmitter UID Unique IDentification VCO Voltage Controlled Oscillator All information provided in this document is subject to legal disclaimers. © NXP B.V. 2013. All rights reserved. Rev. 3.0 — 9 December 2013 130 of 137 OM9663 NXP Semiconductors High performance NFC reader solution 19. References OM9663 Product data sheet COMPANY PUBLIC [1] Application note — MFRC52x Reader IC Family Directly Matched Antenna Design [2] Application note — MIFARE (ISO/IEC 14443 A) 13.56 MHz RFID Proximity Antennas [3] BSDL File — Boundary scan description language file of the OM9663 All information provided in this document is subject to legal disclaimers. © NXP B.V. 2013. All rights reserved. Rev. 3.0 — 9 December 2013 131 of 137 OM9663 NXP Semiconductors High performance NFC reader solution 20. Revision history Table 251. Revision history Document ID Release date Data sheet status Change notice Supersedes OM9663 v.3.0 20131209 Product data sheet - - OM9663 Product data sheet COMPANY PUBLIC All information provided in this document is subject to legal disclaimers. © NXP B.V. 2013. All rights reserved. Rev. 3.0 — 9 December 2013 132 of 137 OM9663 NXP Semiconductors High performance NFC reader solution 21. Legal information 21.1 Data sheet status Document status[1][2] Product status[3] Definition Objective [short] data sheet Development This document contains data from the objective specification for product development. Preliminary [short] data sheet Qualification This document contains data from the preliminary specification. Product [short] data sheet Production This document contains the product specification. [1] Please consult the most recently issued document before initiating or completing a design. [2] The term ‘short data sheet’ is explained in section “Definitions”. [3] The product status of device(s) described in this document may have changed since this document was published and may differ in case of multiple devices. The latest product status information is available on the Internet at URL http://www.nxp.com. 21.2 Definitions Draft — The document is a draft version only. The content is still under internal review and subject to formal approval, which may result in modifications or additions. NXP Semiconductors does not give any representations or warranties as to the accuracy or completeness of information included herein and shall have no liability for the consequences of use of such information. Short data sheet — A short data sheet is an extract from a full data sheet with the same product type number(s) and title. A short data sheet is intended for quick reference only and should not be relied upon to contain detailed and full information. For detailed and full information see the relevant full data sheet, which is available on request via the local NXP Semiconductors sales office. In case of any inconsistency or conflict with the short data sheet, the full data sheet shall prevail. Product specification — The information and data provided in a Product data sheet shall define the specification of the product as agreed between NXP Semiconductors and its customer, unless NXP Semiconductors and customer have explicitly agreed otherwise in writing. In no event however, shall an agreement be valid in which the NXP Semiconductors product is deemed to offer functions and qualities beyond those described in the Product data sheet. 21.3 Disclaimers Limited warranty and liability — Information in this document is believed to be accurate and reliable. However, NXP Semiconductors does not give any representations or warranties, expressed or implied, as to the accuracy or completeness of such information and shall have no liability for the consequences of use of such information. NXP Semiconductors takes no responsibility for the content in this document if provided by an information source outside of NXP Semiconductors. In no event shall NXP Semiconductors be liable for any indirect, incidental, punitive, special or consequential damages (including - without limitation - lost profits, lost savings, business interruption, costs related to the removal or replacement of any products or rework charges) whether or not such damages are based on tort (including negligence), warranty, breach of contract or any other legal theory. Notwithstanding any damages that customer might incur for any reason whatsoever, NXP Semiconductors’ aggregate and cumulative liability towards customer for the products described herein shall be limited in accordance with the Terms and conditions of commercial sale of NXP Semiconductors. Right to make changes — NXP Semiconductors reserves the right to make changes to information published in this document, including without limitation specifications and product descriptions, at any time and without notice. This document supersedes and replaces all information supplied prior to the publication hereof. OM9663 Product data sheet COMPANY PUBLIC Suitability for use — NXP Semiconductors products are not designed, authorized or warranted to be suitable for use in life support, life-critical or safety-critical systems or equipment, nor in applications where failure or malfunction of an NXP Semiconductors product can reasonably be expected to result in personal injury, death or severe property or environmental damage. NXP Semiconductors and its suppliers accept no liability for inclusion and/or use of NXP Semiconductors products in such equipment or applications and therefore such inclusion and/or use is at the customer’s own risk. Applications — Applications that are described herein for any of these products are for illustrative purposes only. NXP Semiconductors makes no representation or warranty that such applications will be suitable for the specified use without further testing or modification. Customers are responsible for the design and operation of their applications and products using NXP Semiconductors products, and NXP Semiconductors accepts no liability for any assistance with applications or customer product design. It is customer’s sole responsibility to determine whether the NXP Semiconductors product is suitable and fit for the customer’s applications and products planned, as well as for the planned application and use of customer’s third party customer(s). Customers should provide appropriate design and operating safeguards to minimize the risks associated with their applications and products. NXP Semiconductors does not accept any liability related to any default, damage, costs or problem which is based on any weakness or default in the customer’s applications or products, or the application or use by customer’s third party customer(s). Customer is responsible for doing all necessary testing for the customer’s applications and products using NXP Semiconductors products in order to avoid a default of the applications and the products or of the application or use by customer’s third party customer(s). NXP does not accept any liability in this respect. Limiting values — Stress above one or more limiting values (as defined in the Absolute Maximum Ratings System of IEC 60134) will cause permanent damage to the device. Limiting values are stress ratings only and (proper) operation of the device at these or any other conditions above those given in the Recommended operating conditions section (if present) or the Characteristics sections of this document is not warranted. Constant or repeated exposure to limiting values will permanently and irreversibly affect the quality and reliability of the device. Terms and conditions of commercial sale — NXP Semiconductors products are sold subject to the general terms and conditions of commercial sale, as published at http://www.nxp.com/profile/terms, unless otherwise agreed in a valid written individual agreement. In case an individual agreement is concluded only the terms and conditions of the respective agreement shall apply. NXP Semiconductors hereby expressly objects to applying the customer’s general terms and conditions with regard to the purchase of NXP Semiconductors products by customer. No offer to sell or license — Nothing in this document may be interpreted or construed as an offer to sell products that is open for acceptance or the grant, conveyance or implication of any license under any copyrights, patents or other industrial or intellectual property rights. All information provided in this document is subject to legal disclaimers. © NXP B.V. 2013. All rights reserved. Rev. 3.0 — 9 December 2013 133 of 137 OM9663 NXP Semiconductors High performance NFC reader solution Quick reference data — The Quick reference data is an extract of the product data given in the Limiting values and Characteristics sections of this document, and as such is not complete, exhaustive or legally binding. Export control — This document as well as the item(s) described herein may be subject to export control regulations. Export might require a prior authorization from competent authorities. Non-automotive qualified products — Unless this data sheet expressly states that this specific NXP Semiconductors product is automotive qualified, the product is not suitable for automotive use. It is neither qualified nor tested in accordance with automotive testing or application requirements. NXP Semiconductors accepts no liability for inclusion and/or use of non-automotive qualified products in automotive equipment or applications. In the event that customer uses the product for design-in and use in automotive applications to automotive specifications and standards, customer (a) shall use the product without NXP Semiconductors’ warranty of the product for such automotive applications, use and specifications, and (b) whenever customer uses the product for automotive applications beyond NXP Semiconductors’ specifications such use shall be solely at customer’s own risk, and (c) customer fully indemnifies NXP Semiconductors for any liability, damages or failed product claims resulting from customer design and use of the product for automotive applications beyond NXP Semiconductors’ standard warranty and NXP Semiconductors’ product specifications. Translations — A non-English (translated) version of a document is for reference only. The English version shall prevail in case of any discrepancy between the translated and English versions. 21.4 Licenses Purchase of NXP ICs with ISO/IEC 14443 type B functionality This NXP Semiconductors IC is ISO/IEC 14443 Type B software enabled and is licensed under Innovatron’s Contactless Card patents license for ISO/IEC 14443 B. The license includes the right to use the IC in systems and/or end-user equipment. RATP/Innovatron Technology Purchase of NXP ICs with NFC technology Purchase of an NXP Semiconductors IC that complies with one of the Near Field Communication (NFC) standards ISO/IEC 18092 and ISO/IEC 21481 does not convey an implied license under any patent right infringed by implementation of any of those standards. 21.5 Trademarks Notice: All referenced brands, product names, service names and trademarks are the property of their respective owners. I2C-bus — logo is a trademark of NXP B.V. MIFARE — is a trademark of NXP B.V. MIFARE Ultralight — is a trademark of NXP B.V. DESFire — is a trademark of NXP B.V. MIFARE Plus — is a trademark of NXP B.V. ICODE and I-CODE — are trademarks of NXP B.V. 22. Contact information For more information, please visit: http://www.nxp.com For sales office addresses, please send an email to: salesaddresses@nxp.com OM9663 Product data sheet COMPANY PUBLIC All information provided in this document is subject to legal disclaimers. © NXP B.V. 2013. All rights reserved. Rev. 3.0 — 9 December 2013 134 of 137 OM9663 NXP Semiconductors High performance NFC reader solution 23. Contents 1 2 3 4 5 6 7 7.1 8 8.1 8.2 8.2.1 8.2.1.1 8.2.1.2 8.2.1.3 8.2.1.4 8.2.1.5 8.3 8.3.1 8.3.2 8.3.3 8.3.3.1 8.3.4 8.3.5 8.3.6 8.3.7 8.3.7.1 8.3.7.2 8.3.7.3 8.3.8 8.3.8.1 8.4 8.4.1 8.4.2 8.4.2.1 8.4.2.2 8.4.2.3 8.4.2.4 8.4.2.5 8.4.3 8.4.3.1 8.4.3.2 8.4.4 8.4.4.1 8.4.4.2 8.4.4.3 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 General description . . . . . . . . . . . . . . . . . . . . . . 1 Features and benefits . . . . . . . . . . . . . . . . . . . . 2 Quick reference data . . . . . . . . . . . . . . . . . . . . . 3 Ordering information . . . . . . . . . . . . . . . . . . . . . 3 Block diagram . . . . . . . . . . . . . . . . . . . . . . . . . . 4 Pinning information . . . . . . . . . . . . . . . . . . . . . . 4 Pin description . . . . . . . . . . . . . . . . . . . . . . . . . 5 Functional description . . . . . . . . . . . . . . . . . . . 6 Interrupt controller . . . . . . . . . . . . . . . . . . . . . . 7 Timer module . . . . . . . . . . . . . . . . . . . . . . . . . . 9 Timer modes. . . . . . . . . . . . . . . . . . . . . . . . . . 10 Time-Out- and Watch-Dog-Counter . . . . . . . . 10 Wake-up timer . . . . . . . . . . . . . . . . . . . . . . . . 10 Stop watch . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 Programmable one-shot timer . . . . . . . . . . . . 10 Periodical trigger. . . . . . . . . . . . . . . . . . . . . . . 10 Contactless interface unit . . . . . . . . . . . . . . . 11 ISO/IEC14443A/MIFARE functionality . . . . . . 11 ISO/IEC14443B functionality . . . . . . . . . . . . . 13 FeliCa functionality . . . . . . . . . . . . . . . . . . . . . 14 FeliCa framing and coding . . . . . . . . . . . . . . . 14 ISO/IEC15693 functionality . . . . . . . . . . . . . . 14 EPC-UID/UID-OTP functionality . . . . . . . . . . . 16 ISO/IEC 18000-3 mode 3/ EPC Class-1 HF functionality. . . . . . . . . . . . . . . . . . . . . . . . . . . 16 ISO/IEC 18092 mode . . . . . . . . . . . . . . . . . . . 16 Passive communication mode . . . . . . . . . . . . 17 ISO/IEC 18092 framing and coding . . . . . . . . 18 ISO/IEC 18092 protocol support. . . . . . . . . . . 18 EPC Class-1 HF and ICODE . . . . . . . . . . . . . 18 Data encoding ICODE . . . . . . . . . . . . . . . . . . 18 Host interfaces . . . . . . . . . . . . . . . . . . . . . . . . 18 Host interface configuration . . . . . . . . . . . . . . 18 SPI interface . . . . . . . . . . . . . . . . . . . . . . . . . . 19 General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 Read data . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 Write data . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 Address byte. . . . . . . . . . . . . . . . . . . . . . . . . . 20 Timing Specification SPI . . . . . . . . . . . . . . . . . 20 RS232 interface . . . . . . . . . . . . . . . . . . . . . . . 21 Selection of the transfer speeds . . . . . . . . . . . 21 Framing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 I2C-bus interface . . . . . . . . . . . . . . . . . . . . . . 24 General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24 I2C Data validity . . . . . . . . . . . . . . . . . . . . . . . 24 I2C START and STOP conditions . . . . . . . . . . 25 8.4.4.4 8.4.4.5 8.4.4.6 8.4.4.7 8.4.4.8 8.4.4.9 8.4.5 8.4.5.1 8.4.5.2 8.4.6 8.4.6.1 8.4.6.2 8.4.6.3 8.4.6.4 8.4.6.5 8.4.6.6 8.4.6.7 8.4.6.8 8.4.6.9 8.4.6.10 8.5 8.5.1 8.5.2 8.5.3 8.5.4 8.6 8.6.1 8.6.2 8.6.2.1 8.6.2.2 8.6.3 8.6.3.1 8.6.3.2 8.6.4 8.6.5 8.7 8.7.1 8.7.2 8.7.2.1 8.7.3 8.8 8.8.1 8.8.2 8.8.3 8.9 8.9.1 8.9.2 I2C byte format . . . . . . . . . . . . . . . . . . . . . . . . 25 I2C Acknowledge . . . . . . . . . . . . . . . . . . . . . . 26 I2C 7-bit addressing . . . . . . . . . . . . . . . . . . . . 26 I2C-register write access . . . . . . . . . . . . . . . . 27 I2C-register read access . . . . . . . . . . . . . . . . 27 I2CL-bus interface . . . . . . . . . . . . . . . . . . . . . 28 SAM interface I2C . . . . . . . . . . . . . . . . . . . . . 29 SAM functionality . . . . . . . . . . . . . . . . . . . . . . 29 SAM connection. . . . . . . . . . . . . . . . . . . . . . . 30 Boundary scan interface . . . . . . . . . . . . . . . . 30 Interface signals. . . . . . . . . . . . . . . . . . . . . . . 31 Test Clock (TCK) . . . . . . . . . . . . . . . . . . . . . . 31 Test Mode Select (TMS) . . . . . . . . . . . . . . . . 31 Test Data Input (TDI) . . . . . . . . . . . . . . . . . . . 31 Test Data Output (TDO) . . . . . . . . . . . . . . . . . 31 Data register . . . . . . . . . . . . . . . . . . . . . . . . . 32 Boundary scan cell. . . . . . . . . . . . . . . . . . . . . 32 Boundary scan path . . . . . . . . . . . . . . . . . . . . 32 Boundary Scan Description Language (BSDL) 33 Non-IEEE1149.1 commands . . . . . . . . . . . . . 34 Buffer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35 Accessing the FIFO buffer . . . . . . . . . . . . . . . 35 Controlling the FIFO buffer . . . . . . . . . . . . . . 35 Status Information about the FIFO buffer. . . . 35 Analog interface and contactless UART . . . . 37 General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37 TX transmitter . . . . . . . . . . . . . . . . . . . . . . . . 37 Overshoot protection . . . . . . . . . . . . . . . . . . . 39 Bit generator . . . . . . . . . . . . . . . . . . . . . . . . . 40 Receiver circuitry . . . . . . . . . . . . . . . . . . . . . . 40 General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40 Block diagram . . . . . . . . . . . . . . . . . . . . . . . . 41 Active antenna concept . . . . . . . . . . . . . . . . . 42 Symbol generator. . . . . . . . . . . . . . . . . . . . . . 45 Memory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45 Memory overview. . . . . . . . . . . . . . . . . . . . . . 45 EEPROM memory organization. . . . . . . . . . . 46 Product information and configuration Page 0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47 EEPROM initialization content LoadProtocol. 49 Clock generation . . . . . . . . . . . . . . . . . . . . . . 51 Crystal oscillator. . . . . . . . . . . . . . . . . . . . . . . 51 IntegerN PLL clock line . . . . . . . . . . . . . . . . . 51 Low Frequency Oscillator (LFO) . . . . . . . . . . 52 Power management. . . . . . . . . . . . . . . . . . . . 53 Supply concept . . . . . . . . . . . . . . . . . . . . . . . 53 Power reduction mode . . . . . . . . . . . . . . . . . . 53 continued >> OM9663 Product data sheet COMPANY PUBLIC All information provided in this document is subject to legal disclaimers. © NXP B.V. 2013. All rights reserved. Rev. 3.0 — 9 December 2013 135 of 137 OM9663 NXP Semiconductors High performance NFC reader solution 8.9.2.1 Power-down . . . . . . . . . . . . . . . . . . . . . . . . . . 8.9.2.2 Standby mode. . . . . . . . . . . . . . . . . . . . . . . . . 8.9.2.3 Modem off mode. . . . . . . . . . . . . . . . . . . . . . . 8.9.3 Low-Power Card Detection (LPCD) . . . . . . . . 8.9.4 Reset and start-up time . . . . . . . . . . . . . . . . . 8.10 Command set . . . . . . . . . . . . . . . . . . . . . . . . . 8.10.1 General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8.10.2 Command set overview . . . . . . . . . . . . . . . . . 8.10.3 Command functionality . . . . . . . . . . . . . . . . . . 8.10.3.1 Idle command . . . . . . . . . . . . . . . . . . . . . . . . . 8.10.3.2 LPCD command . . . . . . . . . . . . . . . . . . . . . . . 8.10.3.3 Load key command . . . . . . . . . . . . . . . . . . . . 8.10.3.4 MFAuthent command . . . . . . . . . . . . . . . . . . . 8.10.3.5 AckReq command . . . . . . . . . . . . . . . . . . . . . 8.10.3.6 Receive command . . . . . . . . . . . . . . . . . . . . . 8.10.3.7 Transmit command . . . . . . . . . . . . . . . . . . . . . 8.10.3.8 Transceive command . . . . . . . . . . . . . . . . . . . 8.10.3.9 WriteE2 command . . . . . . . . . . . . . . . . . . . . . 8.10.3.10 WriteE2PAGE command . . . . . . . . . . . . . . . . 8.10.3.11 ReadE2 command . . . . . . . . . . . . . . . . . . . . . 8.10.3.12 LoadReg command . . . . . . . . . . . . . . . . . . . . 8.10.3.13 LoadProtocol command . . . . . . . . . . . . . . . . . 8.10.3.14 LoadKeyE2 command . . . . . . . . . . . . . . . . . . 8.10.3.15 StoreKeyE2 command . . . . . . . . . . . . . . . . . . 8.10.3.16 GetRNR command . . . . . . . . . . . . . . . . . . . . . 8.10.3.17 SoftReset command . . . . . . . . . . . . . . . . . . . . 9 OM9663 registers . . . . . . . . . . . . . . . . . . . . . . . 9.1 Register bit behavior. . . . . . . . . . . . . . . . . . . . 9.2 Command configuration . . . . . . . . . . . . . . . . . 9.2.1 Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9.3 SAM configuration register . . . . . . . . . . . . . . . 9.3.1 HostCtrl. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9.4 FIFO configuration register . . . . . . . . . . . . . . . 9.4.1 FIFOControl . . . . . . . . . . . . . . . . . . . . . . . . . . 9.4.2 WaterLevel . . . . . . . . . . . . . . . . . . . . . . . . . . . 9.4.3 FIFOLength . . . . . . . . . . . . . . . . . . . . . . . . . . 9.4.4 FIFOData . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9.5 Interrupt configuration registers . . . . . . . . . . . 9.5.1 IRQ0 register . . . . . . . . . . . . . . . . . . . . . . . . . 9.5.2 IRQ1 register . . . . . . . . . . . . . . . . . . . . . . . . . 9.5.3 IRQ0En register . . . . . . . . . . . . . . . . . . . . . . . 9.5.4 IRQ1En . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9.6 Contactless interface configuration registers . 9.6.1 Error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9.6.2 Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9.6.3 RxBitCtrl . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9.6.4 RxColl . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9.7 Timer configuration registers . . . . . . . . . . . . . 9.7.1 TControl . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9.7.2 T0Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53 53 53 54 54 55 55 55 56 56 56 56 56 57 57 58 58 58 58 58 59 59 60 60 61 61 62 62 65 65 65 65 66 66 66 68 68 68 69 69 70 70 71 71 72 73 75 76 76 76 9.7.2.1 9.7.2.2 9.7.2.3 9.7.2.4 9.7.2.5 9.7.2.6 9.7.2.7 9.7.2.8 9.7.2.9 9.7.2.10 9.7.2.11 9.7.2.12 9.7.2.13 9.7.2.14 9.7.2.15 9.7.2.16 9.7.2.17 9.7.2.18 9.7.2.19 9.7.2.20 9.7.2.21 9.7.2.22 9.7.2.23 9.7.2.24 9.8 9.8.1 9.8.2 9.8.3 9.8.4 9.9 9.9.1 9.9.2 9.10 9.10.1 9.10.2 9.10.3 9.10.4 9.10.5 9.11 9.12 9.12.1 9.12.2 9.12.3 9.12.4 9.12.5 9.12.6 9.13 9.13.1 9.13.2 9.13.3 9.13.4 T0ReloadHi . . . . . . . . . . . . . . . . . . . . . . . . . . 77 T0ReloadLo . . . . . . . . . . . . . . . . . . . . . . . . . . 77 T0CounterValHi . . . . . . . . . . . . . . . . . . . . . . . 78 T0CounterValLo . . . . . . . . . . . . . . . . . . . . . . . 78 T1Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78 T1ReloadHi . . . . . . . . . . . . . . . . . . . . . . . . . . 79 T1ReloadLo . . . . . . . . . . . . . . . . . . . . . . . . . . 79 T1CounterValHi . . . . . . . . . . . . . . . . . . . . . . . 80 T1CounterValLo . . . . . . . . . . . . . . . . . . . . . . . 80 T2Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80 T2ReloadHi . . . . . . . . . . . . . . . . . . . . . . . . . . 81 T2ReloadLo . . . . . . . . . . . . . . . . . . . . . . . . . . 81 T2CounterValHi . . . . . . . . . . . . . . . . . . . . . . . 82 T2CounterValLoReg . . . . . . . . . . . . . . . . . . . 82 T3Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82 T3ReloadHi . . . . . . . . . . . . . . . . . . . . . . . . . . 83 T3ReloadLo . . . . . . . . . . . . . . . . . . . . . . . . . . 83 T3CounterValHi . . . . . . . . . . . . . . . . . . . . . . . 84 T3CounterValLo . . . . . . . . . . . . . . . . . . . . . . . 84 T4Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84 T4ReloadHi . . . . . . . . . . . . . . . . . . . . . . . . . . 85 T4ReloadLo . . . . . . . . . . . . . . . . . . . . . . . . . . 85 T4CounterValHi . . . . . . . . . . . . . . . . . . . . . . . 86 T4CounterValLo . . . . . . . . . . . . . . . . . . . . . . . 86 Transmitter configuration registers. . . . . . . . . 86 TxMode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86 TxAmp . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87 TxCon . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87 Txl . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88 CRC configuration registers. . . . . . . . . . . . . . 88 TxCrcPreset . . . . . . . . . . . . . . . . . . . . . . . . . . 88 RxCrcCon . . . . . . . . . . . . . . . . . . . . . . . . . . . 89 Transmitter configuration registers. . . . . . . . . 90 TxDataNum . . . . . . . . . . . . . . . . . . . . . . . . . . 90 TxDATAModWidth . . . . . . . . . . . . . . . . . . . . . 91 TxSym10BurstLen . . . . . . . . . . . . . . . . . . . . . 92 TxWaitCtrl . . . . . . . . . . . . . . . . . . . . . . . . . . . 92 TxWaitLo . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94 FrameCon . . . . . . . . . . . . . . . . . . . . . . . . . . . 94 Receiver configuration registers . . . . . . . . . . 95 RxSofD. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95 RxCtrl . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95 RxWait . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96 RxThreshold. . . . . . . . . . . . . . . . . . . . . . . . . . 96 Rcv. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97 RxAna . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97 Clock configuration . . . . . . . . . . . . . . . . . . . . 98 SerialSpeed . . . . . . . . . . . . . . . . . . . . . . . . . . 98 LFO_Trimm . . . . . . . . . . . . . . . . . . . . . . . . . . 99 PLL_Ctrl Register. . . . . . . . . . . . . . . . . . . . . 100 PLLDiv_Out . . . . . . . . . . . . . . . . . . . . . . . . . 100 continued >> OM9663 Product data sheet COMPANY PUBLIC All information provided in this document is subject to legal disclaimers. © NXP B.V. 2013. All rights reserved. Rev. 3.0 — 9 December 2013 136 of 137 OM9663 NXP Semiconductors High performance NFC reader solution 9.14 9.14.1 9.14.2 9.14.3 9.14.4 9.14.5 9.15 9.15.1 9.15.2 9.15.3 9.15.4 9.16 9.16.1 9.16.2 9.16.3 9.16.4 9.16.5 9.16.6 9.16.7 9.16.8 9.16.9 9.16.10 9.16.11 9.16.12 9.16.13 9.17 9.17.1 9.17.2 9.17.3 9.17.4 9.17.5 9.17.6 9.17.7 9.17.8 9.18 9.18.1 10 11 12 13 13.1 14 14.1 14.1.1 14.1.2 14.1.3 14.1.4 15 Low-power card detection configuration registers . . . . . . . . . . . . . . . . . . . . . . . . . . . . LPCD_QMin . . . . . . . . . . . . . . . . . . . . . . . . . LPCD_QMax . . . . . . . . . . . . . . . . . . . . . . . . LPCD_IMin . . . . . . . . . . . . . . . . . . . . . . . . . . LPCD_Result_I . . . . . . . . . . . . . . . . . . . . . . . LPCD_Result_Q . . . . . . . . . . . . . . . . . . . . . . Pin configuration . . . . . . . . . . . . . . . . . . . . . . PinEn . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PinOut. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PinIn . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SigOut. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Protocol configuration registers . . . . . . . . . . TxBitMod . . . . . . . . . . . . . . . . . . . . . . . . . . . TxDataCon . . . . . . . . . . . . . . . . . . . . . . . . . . TxDataMod . . . . . . . . . . . . . . . . . . . . . . . . . . TxSymFreq . . . . . . . . . . . . . . . . . . . . . . . . . . TxSym0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . TxSym . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TxSym2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . TxSym3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . TxSym10Len . . . . . . . . . . . . . . . . . . . . . . . . TxSym32Len . . . . . . . . . . . . . . . . . . . . . . . . TxSym10BurstCtrl . . . . . . . . . . . . . . . . . . . . TxSym10Mod Reg . . . . . . . . . . . . . . . . . . . . TxSym32Mod . . . . . . . . . . . . . . . . . . . . . . . . Receiver configuration . . . . . . . . . . . . . . . . . RxBitMod . . . . . . . . . . . . . . . . . . . . . . . . . . . RxEofSym. . . . . . . . . . . . . . . . . . . . . . . . . . . RxSyncValH . . . . . . . . . . . . . . . . . . . . . . . . . RxSyncValL . . . . . . . . . . . . . . . . . . . . . . . . . RxSyncMod . . . . . . . . . . . . . . . . . . . . . . . . . RxMod . . . . . . . . . . . . . . . . . . . . . . . . . . . . . RxCorr . . . . . . . . . . . . . . . . . . . . . . . . . . . . . FabCali . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Version register. . . . . . . . . . . . . . . . . . . . . . . Version . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Limiting values. . . . . . . . . . . . . . . . . . . . . . . . Recommended operating conditions. . . . . . Thermal characteristics . . . . . . . . . . . . . . . . Characteristics . . . . . . . . . . . . . . . . . . . . . . . . Timing characteristics . . . . . . . . . . . . . . . . . . Application information. . . . . . . . . . . . . . . . . Antenna design description . . . . . . . . . . . . . EMC low pass filter . . . . . . . . . . . . . . . . . . . . Antenna matching. . . . . . . . . . . . . . . . . . . . . Receiving circuit . . . . . . . . . . . . . . . . . . . . . . Antenna coil . . . . . . . . . . . . . . . . . . . . . . . . . Package outline . . . . . . . . . . . . . . . . . . . . . . . 101 101 102 102 102 103 103 103 104 104 104 105 105 106 106 107 108 109 109 109 110 110 110 111 112 112 112 113 114 114 114 115 115 116 116 116 117 117 117 117 120 122 122 122 123 123 124 125 16 17 18 19 20 21 21.1 21.2 21.3 21.4 21.5 22 23 Handling information . . . . . . . . . . . . . . . . . . Packing information . . . . . . . . . . . . . . . . . . . Abbreviations . . . . . . . . . . . . . . . . . . . . . . . . References. . . . . . . . . . . . . . . . . . . . . . . . . . . Revision history . . . . . . . . . . . . . . . . . . . . . . Legal information . . . . . . . . . . . . . . . . . . . . . Data sheet status . . . . . . . . . . . . . . . . . . . . . Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . Disclaimers . . . . . . . . . . . . . . . . . . . . . . . . . Licenses. . . . . . . . . . . . . . . . . . . . . . . . . . . . Trademarks . . . . . . . . . . . . . . . . . . . . . . . . . Contact information . . . . . . . . . . . . . . . . . . . Contents. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126 126 130 131 132 133 133 133 133 134 134 134 135 Please be aware that important notices concerning this document and the product(s) described herein, have been included in section ‘Legal information’. © NXP B.V. 2013. All rights reserved. For more information, please visit: http://www.nxp.com For sales office addresses, please send an email to: salesaddresses@nxp.com Date of release: 9 December 2013