| 1 |
============================================================================ |
| 2 |
Kernel driver for the NXP Semiconductors PN544 Near Field Communication chip |
| 3 |
============================================================================ |
| 4 |
|
| 5 |
|
| 6 |
General |
| 7 |
------- |
| 8 |
|
| 9 |
The PN544 is an integrated transmission module for contactless |
| 10 |
communication. The driver goes under drives/nfc/ and is compiled as a |
| 11 |
module named "pn544". |
| 12 |
|
| 13 |
Host Interfaces: I2C, SPI and HSU, this driver supports currently only I2C. |
| 14 |
|
| 15 |
Protocols |
| 16 |
--------- |
| 17 |
|
| 18 |
In the normal (HCI) mode and in the firmware update mode read and |
| 19 |
write functions behave a bit differently because the message formats |
| 20 |
or the protocols are different. |
| 21 |
|
| 22 |
In the normal (HCI) mode the protocol used is derived from the ETSI |
| 23 |
HCI specification. The firmware is updated using a specific protocol, |
| 24 |
which is different from HCI. |
| 25 |
|
| 26 |
HCI messages consist of an eight bit header and the message body. The |
| 27 |
header contains the message length. Maximum size for an HCI message is |
| 28 |
33. In HCI mode sent messages are tested for a correct |
| 29 |
checksum. Firmware update messages have the length in the second (MSB) |
| 30 |
and third (LSB) bytes of the message. The maximum FW message length is |
| 31 |
1024 bytes. |
| 32 |
|
| 33 |
For the ETSI HCI specification see |
| 34 |
http://www.etsi.org/WebSite/Technologies/ProtocolSpecification.aspx |