Data Sheet

PN512_C1_SDS All information provided in this document is subject to legal disclaimers. © NXP B.V. 2012. All rights reserved.
Product short data sheet
COMPANY PUBLIC
Rev. 3.2 — 20 September 2012
120132 11 of 27
NXP Semiconductors
PN532/C1
Near Field Communication (NFC) controller
7.1.3.2 FeliCa Reader/Writer
The following diagram describes the communication at the physical level. Table 4
describes the physical parameters.
With appropriate firmware, the PN532 can handle the FeliCa protocol.
The FeliCa Framing and coding must comply with the following table:
To enable the FeliCa communication a 6-byte preamble (00h, 00h, 00h, 00h, 00h, 00h)
and 2-byte 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 80C51 has to send the LEN and data bytes to the
CIU. The Preamble and SYNC bytes are generated by the CIU automatically and must not
be written to the FIFO. The CIU performs internally the CRC calculation and adds the
result to the frame.
The starting value for the CRC Polynomial is 2 null bytes: (00h), (00h)
Example of frame:
Fig 5. FeliCa Reader/Writer communication diagram
Table 4. Communication overview for FeliCa Reader/Writer
Communication scheme FeliCa FeliCa higher baud rate
Baud rate 212 kbit/s 424 kbit/s
Bit length
PN532 to
PICC/Card
Modulation 8 - 30% ASK 8 - 30% ASK
Bit coding Manchester coding Manchester coding
PICC/Card to
PN532
Modulation >12% ASK >12% ASK
Bit coding Manchester coding Manchester coding
Table 5. FeliCa Framing and Coding
Preamble SYNC LEN n-Data CRC
00h 00h 00h 00h 00h 00h B2h 4Dh
Table 6. FeliCa framing and coding
Preamble SYNC LEN 2 Data Bytes CRC
00 00 00 00 00 00 B2 4D 03 AB CD 90 35
64
13.56MHz
--------------------------
4.72s
32
13.56MHz
--------------------------
2.36s