- Product Overview
- Features
- Applications
- Antenna Design Guide
- NFC antenna design Web-tool
- Evaluation board
- FAQs
Product Overview
We are one of the leading NFC Tag LSIs (also known as NFC Tag ICs) maker in the world. Our NFC Tag LSI is a contactless IC tag supporting
Near Field Communication (NFC) technology, where NFC devices like smartphones can communicate with the tag to read/write data .
Embedding this NFC LSI in various equipment enables radio communication between the equipment and NFC devices.
In addition, with built-in memory for data retention, this NFC interface LSI can be used as an individual wireless IC tag.
NFC tag IC works with the power supplied wirelessly from NFC devices, and enables radio communication to NFC devices even while equipment
with this LSI are turned off.
Using this LSI as an individual contactless IC tag enables the system to be configured without power supply.
Features
- Built-in 4-Kbit FeRAM non-volatile memory with fast write and low power consumption.
- RF interface compliant with JIS X 6319-4 (FeliCa) and ISO/IEC 14443 Type A/B of the 13.56-MHz contactless IC card standards.
- Serial interface: Selectable from UART, I²C and Synchronous serial (except MN63Y1212).
| Parts MN63Y1 MN63Y12 |
NFC Spec. | Host Interface | Security Function* |
|||||
|---|---|---|---|---|---|---|---|---|
| Type3 NFC-F |
Type4B NFC-B |
Type4A NFC-A |
UART (to 38.4 kbps) |
I²C (to 100 kbps) |
I²C (to 400 kbps) |
Synchronous serial (to 1 Mbps) |
||
| MN63Y1210A | ||||||||
| MN63Y1212 | ||||||||
| MN63Y1213 | ||||||||
| MN63Y1214 | ||||||||
| MN63Y1221 | ||||||||
Security Function * : A=AES Encryption, P=Password Protection
Battery-off mode (powered by field) at RF communication.
Without power supply from the host, NFC LSI can work with power supply from reader/writer.
(1) Operation of the NFC wireless tag:
- Even when the host power is OFF, FeRAM is still accessible.
(2) Drive of the host:
- Even when the host power is OFF, IRQ signal is still available as output.
- IRQ signal to output condition:
- When the LSI has received the tunnel communication mode command
- When the LSI has detected a carrier
Three communication modes
Three communication modes of RF, serial, and tunnel (Tunnel mode allows communications between reader/writer and host CPU via this LSI.)
(1) RF communication mode: Access from NFC devices (smartphones, etc.) to FeRAM
Example: The data measured by health-care equipment is transferred to smartphones just by holding them over the equipment.
(2) Serial communication mode: Access from host to FeRAM
Example: The data measured by health-care equipment is written to FeRAM of NFC tags.
(3) Tunnel communication mode: interactive communication is allowed between reader/writer (NFC devices) and
the host CPU via this LSI.
Example: Updated information of equipment is transferred via smartphones.
Handover function
Handover function which enables faster communications like Bluetooth or Wi-Fi by pairing devices with NFC.
Applications
NFC tag is widely used in communication industry in the recent years. Our NFC tags IC can be used for communication between NFC devices and home appliances.
In the case of appliance embedded with NFC tag, the recipes collected from internet can be transmitted to home appliances with built-in NFC (rice cookers, etc) via NFC devices such as mobile phones. With the simple touch and transmit features, the rice cooker or microwave oven cooks according to the recipe. With this implementation, it will bring convenience in our daily life.
In case of appliance embedded NFC tag usages,
Antenna Design Guide
Get "Antenna Design Guide" here
Support for antenna design and the estimation of maximum communication distance for NFC tag
The NFC Design Navigator supports antenna design and the estimation of maximum communication distance for NFC tag.
Click here to use the NFC Design Navigator or see the associated tutorial and design guide.
Video of operation for NFC Design Navigator
*Clicking opens new window for viewing video.
The NFC Design Navigator allows you to:
- Add document for measurement and the tuning methods of resonance frequency.
- Design a rectangle antenna with desired size and simulate its communication distance and other parameters.
- Confirm the recommended values of communication distance and resonance capacitance by adjusting antenna conditions with a slider.
- Confirm the effect on communication distance due to the difference in position or angle between NFC tag antenna and Reader/Writer antenna.
- Confirm the intensity distribution of the magnetic field radiated from the Reader/Writer antenna.
- Design the optimal antenna automatically.
- Create the printed-circuit board Gerber data for antenna and LSI peripheral circuit.
- The communication distance dependence for the antenna parameters can be calculated.
Before using the NFC Design Navigator
- The recommended browsers for this tool are Firefox, Safari, Chrome, or IE (9 or later), with which you can use all functions of this tool.
- For more information, see the associated tutorial or design guide.
Evaluation board
Evaluation boards implementing NFC tag IC, antenna, and the interface to microcontroller are provided.
- Allows you to evaluate the communication status between NFC tag and NFC Reader/Writer (smartphone).
- Software for Android Reader/Writer is also provided.
- Using the serial interface also allows communication data to be transferred to the host microcontroller (MCU).
 |
 |
|
 |
|
|
 |
|
|
 |
|
|
 |
|
Programs
| Application Software for Android | Download |
| Tag Dump Tool for Windows | Download |
* User registration is required for program download.
FAQ for NFC tag LSIs
Hardware
- Q1.Does the FeRAM data retention target period start from the last access (Read/Write)?
- Q2.What is the definition of the guarantee on 10-year data retention for FeRAM (physical or after refresh operation)?
- Q3.What is the biggest factor of data destruction in FeRAM?
- Q4.Does the term "10-year data retention for FeRAM" mean the retention period after 100 million cycle rewriting?
- Q5.Is it possible to connect the host MCU's PIO to VDDD or VDDA?
- Q6.Does current leak from IC's power supply pins during power-by-field operation (power OFF)?(I am concerned about malfunction due to the charge of leakage current when power supplies are connected to another circuit even though they are shut off.)
- Q7.Why are the host interface and interrupt signals pulled up to different power supplies?
- Q8.What is the maximum allowable value of the pull-up resistors connected to IRQ3V/5V (Pins 14 and 15)? To reduce power consumption, I want to use a large value as much as possible.
- Q9.There are 3 NC pins (Pins 5, 8, and 13). May I connect them to VSS? Or, should I leave them open?
- Q10.Is it possible to change the level of load modulation?
- Q11.Where does the output current flow to?
- Q12.What is the definition of consumption current?
- Q13.What function does the shunt circuit have?
- Q14.How much heat is generated by the current flowing due to the shunt circuit operation?
- Q15.Is it possible to switch the memory (user area) between read/write and read-only?
- Q16.Is it possible to switch the memory (system area) between read/write and read-only?
- Q17.Is it possible to enable communication limited to a certain group by using a key?
- Q18.Plaintext is used for serial interface communication. Is it possible to raise the secure level by writing the data encrypted by host?
- Q19.There is a setting that an interrupt is output to NIRQ when writing is completed. When is the interrupt output actually?
- Q20.Let me know the initial value and its meaning of each parameter for system area.
- Q21.Is the tunnel mode relevant to the NFC standard?
- Q22.Are there any precautions in using the tunnel mode?
- Q23.When a reader/writer writes data to NFC tag in RF communication mode, how do the reader/writer and the NFC tag confirm the write completion timing and the writing result (success/failure)?
- Q24.TypeB has 2 types of communication rates (106 kbps and 212 kbps）.How are they selectively used?
- Q25.Felica has 2 types of communication rates (212 kbps and 424 kbps). How are they selectively used?
- Q26.Is the command issued by reader/writer to require RF communication in tunnel mode specified by NFC Forum?
- Q27.In the table "Operation during Exclusive Control" (Table 7-1 for MN63Y1210 or Table 8-1 for MN63Y1208), what is the following modes enclosed in parentheses?RF communication mode in RF communication mode,serial communication mode in serial communication mode, etc.
- Q28.What does NFC tag do if no response is made for a certain period for tunnel mode interrupt?
- Q29.When accessing multiple NFC tags, is it possible to specify the NFC tag to be accessed by reader/writer?
- Q30.When accessing multiple NFC tags, don't they interfere with each other?
- Q31.When the serial communication mode and RF communication mode are executed simultaneously, which is the priority one?
- Q32.Is it possible to confirm the control from RF in RF communication mode?
- Q33.In REQB/WUPB of ISO/IEC14443 TypeB Specification, the "Remarks" of "Command message" - "Data field" - "PARAM" says that "Recognizes the number N of Slots is 1 (always responds with ATQB) even when bits 2-0 are set to any of the values (including PFU)."To confirm anti-collision, is it possible to make the NFC tag operate in accordance with the setting of bits 2-0?
- Q34.When the power supply of host controller is disconnected in the access during tunnel mode, can the NFC-enabled device detect the state?
- Q35.Can everyone read the data (ID information, etc.) that the host stores in FeRAM system area through serial interface, or is there a restriction not to do so?
- Q36.To change the state of the system area to Read/Write after setting it to Read-only (with SL [flag data] set to MODE1 or MODE2), do I have to issue an INIT command through serial interface?
- Q37.Is it possible to wake up the host with magnetic field?
- Q38.Can data transfer be performed only when the power is applied to the system?
- Q39.When reading the status information of RFID from the host with STATUS command, does a serial communication interrupt occur before RFID sends a response to the command to the host?
- Q40.Is there a limitation to the capacity of the host's virtual memory space in tunnel mode?
- Q41.Is it guaranteed that the initial value for the system area for NFC tag are fixed?
- Q42.Is it possible to turn ON the power supply for tag from OFF through communication from reader/writer?
- Q43.When does the host microcontroller use the IRQ pins (MN63Y1210: IRQ3V or IRQ5V, MN63Y1208: NIRQ)?
FAQ
Q1.
Does the FeRAM data retention target period start from the last access (Read/Write)?
A1.
FeRAM is re-written even in reading. So, the FeRAM data retention target period starts from Read/Write operation.
Q2.
What is the definition of the guarantee on 10-year data retention for FeRAM (physical or after refresh operation)?
A2.
It is guaranteed after refresh operation.
FeRAM is re-written even in reading due to its destructive readout.
Therefore, a read access triggers the start of data retention target period.
FeRAM is re-written even in reading due to its destructive readout.
Therefore, a read access triggers the start of data retention target period.
Q3.
What is the biggest factor of data destruction in FeRAM?
A3.
There is no other factor but retention.
Q4.
Does the term "10-year data retention for FeRAM" mean the retention period after 100 million cycle rewriting?
A4.
The 10-year data retention for FeRAM includes the period of data re-writing and retention, for which 100-million cycle rewriting is guaranteed.
Q5.
Is it possible to connect the host MCU's PIO to VDDD or VDDA?
A5.
Connect VDDD and VDDA pins to VSS through a capacitor.
Note that a current load to these pins may cause deterioration of communication performance.
Note that a current load to these pins may cause deterioration of communication performance.
Q6.
Does current leak from IC's power supply pins during power-by-field operation (power OFF)?
(I am concerned about malfunction due to the charge of leakage current when power supplies are connected to another circuit even though they are shut off.)
(I am concerned about malfunction due to the charge of leakage current when power supplies are connected to another circuit even though they are shut off.)
A6.
When the external power supply pin (VDDEX) of NFC tag is shut off, no leakage current flows from power supply pin to another circuit.
Q7.
Why are the host interface and interrupt signals pulled up to different power supplies?
A7.
This is an example of the functions to reduce power consumption.
The host interface signal does not always need to be pulled up, but the interrupt signal is always to be pulled up to inform the interrupt to the host, regardless of the host interface operation.
The host interface signal does not always need to be pulled up, but the interrupt signal is always to be pulled up to inform the interrupt to the host, regardless of the host interface operation.
Q8.
What is the maximum allowable value of the pull-up resistors connected to IRQ3V/5V (Pins 14 and 15)? To reduce power consumption, I want to use a large value as much as possible.
A8.
Since the maximum leakage current values for those pins are up to 10 mA in the product standards, the values of the pull-up resistors need to be specified so that the voltage drop across the resistors due to the leakage current does not affect the host's high level detection. (If the resistor value is 100 kΩ, the voltage drop is 1 V.) Therefore, the maximum allowable value is up to around 10 kΩ with margin included.
In addition, the clock-synchronous mode informs the host of the timing to start response by using IRQ. So, if the resistor value is large, the time constant (RC) becomes large and IRQ takes time to return from Low to High level after response, thus causing a time delay to the subsequent command input. The value should be set according to the specifications of your system.
In addition, the clock-synchronous mode informs the host of the timing to start response by using IRQ. So, if the resistor value is large, the time constant (RC) becomes large and IRQ takes time to return from Low to High level after response, thus causing a time delay to the subsequent command input. The value should be set according to the specifications of your system.
Q9.
There are 3 NC pins (Pins 5, 8, and 13). May I connect them to VSS? Or, should I leave them open?
A9.
NC pins are usually left open. But, you can also connect them to GND.
Q10.
Is it possible to change the level of load modulation?
A10.
Our NFC tags have no function to change the level of load modulation.
Q11.
Where does the output current flow to?
A11.
It is the current output from pins of the ICs by the power generated through antenna from the magnetic field or the power applied externally.
The upper limit of 3.6 V for the analog power supply in the ferromagnetic field may cause the output current to increase.
The upper limit of 3.6 V for the analog power supply in the ferromagnetic field may cause the output current to increase.
Q12.
What is the definition of consumption current?
A12.
The consumption current refers to a current flowing when a voltage is applied to the external power supply pin. If the applied voltage is 3.3 V, its value is 310 mA (typ.). The value includes the leakage currents of each pin, however, they are negligible compared to the consumption current.
Q13.
What function does the shunt circuit have?
A13.
Under a strong magnetic field, it suppresses an excessive increase of the power supply voltage, VDDA.
Q14.
How much heat is generated by the current flowing due to the shunt circuit operation?
A14.
For both MN63Y1210 and MN63Y1208, the temperature of the package (unmounted) increases by about 5 to 7 degrees.
With the package mounted on the substrate, it usually increases by about 3 to 4 degrees.
With the package mounted on the substrate, it usually increases by about 3 to 4 degrees.
Q15.
Is it possible to switch the memory (user area) between read/write and read-only?
A15.
Yes, it is possible.
For the memory (user area), you can select Read/Write or Read-only for memory access commands by block, in each mode of RF communication and serial communication.
The parameters for RF communication and serial communication modes are "RORF" and "ROSI," respectively.
To enable these parameters, the system area must be activated. See the Administrator's Manual.
For the memory (user area), you can select Read/Write or Read-only for memory access commands by block, in each mode of RF communication and serial communication.
The parameters for RF communication and serial communication modes are "RORF" and "ROSI," respectively.
To enable these parameters, the system area must be activated. See the Administrator's Manual.
Q16.
Is it possible to switch the memory (system area) between read/write and read-only?
A16.
Yes, it is possible.
You can lock the memory (system area) in two stages (MODE1 and MODE2) for the default setting (MODE0: Read/Write enabled for all areas) by using the parameter (SL).
To enable these parameters, the system area must be activated. See the Administrator's Manual.
You can lock the memory (system area) in two stages (MODE1 and MODE2) for the default setting (MODE0: Read/Write enabled for all areas) by using the parameter (SL).
To enable these parameters, the system area must be activated. See the Administrator's Manual.
Q17.
Is it possible to enable communication limited to a certain group by using a key?
A17.
Of the two keys (private key and family key), family key enables it.
It is enabled by building a system that allows a desired operation only for the smartphone having a given family key while a family shares the family key.
It is enabled by building a system that allows a desired operation only for the smartphone having a given family key while a family shares the family key.
Q18.
Plaintext is used for serial interface communication. Is it possible to raise the secure level by writing the data encrypted by host?
A18.
It is possible to write the data encrypted by host to user area.
However, it is not a special function to raise the secure level but just a writing without distinguishing between plaintext or encrypted data.
However, it is not a special function to raise the secure level but just a writing without distinguishing between plaintext or encrypted data.
Q19.
There is a setting that an interrupt is output to NIRQ when writing is completed.
When is the interrupt output actually?
When is the interrupt output actually?
A19.
An interrupt is output when a writing to FeRAM is completed.
For example, if the write length is 16 bytes, an interrupt is generated when the 16-byte write is completed, before a response is sent to reader/writer.
For example, if the write length is 16 bytes, an interrupt is generated when the 16-byte write is completed, before a response is sent to reader/writer.
Q20.
Let me know the initial value and its meaning of each parameter for system area.
A20.
→RORF, ROSI, SECURITY, HW (UARTSP, etc.), and TNPRM are set to the generally assumed values.
SC, IDM, PMM, AFI, and FWI are parameters specified in the communication standard.
SC, IDM, PMM, AFI, and FWI are parameters specified in the communication standard.
| Parameter | Default | Description |
|---|---|---|
| SC | 0xAAFF | For JISX6319-4 standard, the first 1 byte is fixed to 0xAA. The subsequent 0xFF means that the field of card (tag) does not matter. |
| IDM | 0x02FE000000000000 | An identifier for card. For JISX6319-4 standard, the first 2 bytes are fixed to 0x02FE. All of the subsequent 0s have no special meanings. For ISO/IEC14443, 0x00000000 is set, but that setting has no special meanings. |
| PMM | 0xFFFF | For JISX6319-4, specifies the maximum wait time for READ/WRITE command. (The time is informed to reader/writer with REQ response.) |
| AFI | 0x00 | For ISO/IEC14443, controls the response to the REQB command. The value means that the field of card (tag) does not matter. |
| FWI | 0xE0 | For ISO/IEC14443 standard, specifies the maximum wait time for the response to SELECT/READ/WRITE commands. The wait time is informed to reader/writer with ATQB. 0xE(14) is the maximum value on the standard. |
Q21.
Is the tunnel mode relevant to the NFC standard?
A21.
The tunnel mode is our own method and not relevant to the NFC standard.
If reader/writer is compatible with TypeB or TypeF, thus allowing RF communication with the NFC tag, the tunnel communication is enabled.
If reader/writer is compatible with TypeB or TypeF, thus allowing RF communication with the NFC tag, the tunnel communication is enabled.
Q22.
Are there any precautions in using the tunnel mode?
A22.
You should set the communication time between NFC tag and host to within the communication response time or the maximum wait time.
Q23.
When a reader/writer writes data to NFC tag in RF communication mode, how do the reader/writer and the NFC tag confirm the write completion timing and the writing result (success/failure)?
A23.
The reader/writer confirms the timing and result based on the response (writing completed) from NFC tag. Whether the writing has succeeded or failed is reflected to the status word of the response. If the writing fails due to the lack of power supply, no response is sent. Therefore, the reader/writer determines as "over the time limit," and the NFC tag makes its own decisions using WRITE command.
Q24.
TypeB has 2 types of communication rates (106 kbps and 212 kbps）.
How are they selectively used?
How are they selectively used?
A24.
The rate is determined through the communication between the reader/writer and NFC tag. Please see the "State Transition Diagram" of the Section 4.3.6 in the user's manual.
The communication rate is determined in the transition from IDLE to PROTOCOL state in the state transition diagram. The rate is fixed to 106 kbps in this process.
Based on the communication rate when the target NFC tag sends a response (transition to READY state) to ATQB during IDLE state, the reader/writer selects the communication rate (106 kbps or 212 kbps) and performs communications (READ, WRITE, etc.) with the rate determined by the response to the ATTRIB command.
The communication rate is determined in the transition from IDLE to PROTOCOL state in the state transition diagram. The rate is fixed to 106 kbps in this process.
Based on the communication rate when the target NFC tag sends a response (transition to READY state) to ATQB during IDLE state, the reader/writer selects the communication rate (106 kbps or 212 kbps) and performs communications (READ, WRITE, etc.) with the rate determined by the response to the ATTRIB command.
Q25.
Felica has 2 types of communication rates (212 kbps and 424 kbps). How are they selectively used?
A25.
The reader/writer selects 212 kbps or 424 kbps for Felica.
NFC tag sends a response at the same communication rate as that of the commands (READ, WRITE, or REQ) the reader/writer sends.
NFC tag sends a response at the same communication rate as that of the commands (READ, WRITE, or REQ) the reader/writer sends.
Q26.
Is the command issued by reader/writer to require RF communication in tunnel mode specified by NFC Forum?
A26.
The command type is not our own one.
Depending on the specified address, the mode changes to tunnel mode or serial communication mode.
Depending on the specified address, the mode changes to tunnel mode or serial communication mode.
Q27.
In the table "Operation during Exclusive Control" (Table 7-1 for MN63Y1210 or Table 8-1 for MN63Y1208), what is the following modes enclosed in parentheses?
RF communication mode in RF communication mode,serial communication mode in serial communication mode, etc.
RF communication mode in RF communication mode,serial communication mode in serial communication mode, etc.
A27.
The "RF communication mode in RF communication mode" is the state in which, while RF command is being processed (e.g., read/write from/to FeRAM or tunnel processing), another RF command is sent.
The "Serial communication mode in serial communication mode" is the state in which, while serial command is being processed (e.g., read/write from/to FeRAM), another serial command is sent.
The "Serial communication mode in serial communication mode" is the state in which, while serial command is being processed (e.g., read/write from/to FeRAM), another serial command is sent.
Q28.
What does NFC tag do if no response is made for a certain period for tunnel mode interrupt?
A28.
A timeout occurs and the tag returns an error to the reader/writer.
Then, it is enabled to receive a command at the host.
Then, it is enabled to receive a command at the host.
Q29.
When accessing multiple NFC tags, is it possible to specify the NFC tag to be accessed by reader/writer?
A29.
It is NOT possible to specify and detect a card from an application software because the software for smartphone can access only the card detected by OS.
Q30.
When accessing multiple NFC tags, don't they interfere with each other?
A30.
This NFC tag is designed to be used by itself.
Therefore, when multiple NFC tags are used, a reader/writer cannot distinguish each tag, resulting in an error at the reader/writer.
Since both TypeB and TypeF have anti-collision operation to pick out a tag from multiple tags, the NFC tag needs to send a response/non-response stochastically or to respond to the time slot. There is no problem in the standard even if the tag does not support anti-collision.
This NFC tag always responds to the anti-collision command or responds only to the head of time slot. Therefore, for multiple NFC tags, a reader/writer generates an error because it cannot distinguish each tag.
Therefore, when multiple NFC tags are used, a reader/writer cannot distinguish each tag, resulting in an error at the reader/writer.
Since both TypeB and TypeF have anti-collision operation to pick out a tag from multiple tags, the NFC tag needs to send a response/non-response stochastically or to respond to the time slot. There is no problem in the standard even if the tag does not support anti-collision.
This NFC tag always responds to the anti-collision command or responds only to the head of time slot. Therefore, for multiple NFC tags, a reader/writer generates an error because it cannot distinguish each tag.
Q31.
When the serial communication mode and RF communication mode are executed simultaneously, which is the priority one?
A31.
The communication established earlier takes priority due to exclusive control.
Q32.
Is it possible to confirm the control from RF in RF communication mode?
A32.
It can be confirmed by specifying the condition of generating an interrupt to NIRQ pin through IRQSEL setting. (For details, see the description about IRQSEL in Section 3.3.1, "Parameter Specifications" in the user's manual.)
MN63Y1210 does not have this function in RF communication mode, but in tunnel mode, it can perform the equivalent function.
MN63Y1210 does not have this function in RF communication mode, but in tunnel mode, it can perform the equivalent function.
Q33.
In REQB/WUPB of ISO/IEC14443 TypeB Specification, the "Remarks" of "Command message" - "Data field" - "PARAM" says that "Recognizes the number N of Slots is 1 (always responds with ATQB) even when bits 2-0 are set to any of the values (including PFU)."
To confirm anti-collision, is it possible to make the NFC tag operate in accordance with the setting of bits 2-0?
To confirm anti-collision, is it possible to make the NFC tag operate in accordance with the setting of bits 2-0?
A33.
It is NOT possible to make the tag operate in accordance with the setting of bits 2-0.
As described in the user's manual, this NFC tag always operates under the condition of "the number of slots = 1" regardless of the setting of bits 2-0.
In this operation, the tag must communicate with the reader/writer on a one-to-one basis.
In RF interface standards to which this NFC tag conforms, the communication distance is around 10 cm. We assume that multiple tags are not actually used within the range.
Therefore, no measures for anti-collision are not supported.
As described in the user's manual, this NFC tag always operates under the condition of "the number of slots = 1" regardless of the setting of bits 2-0.
In this operation, the tag must communicate with the reader/writer on a one-to-one basis.
In RF interface standards to which this NFC tag conforms, the communication distance is around 10 cm. We assume that multiple tags are not actually used within the range.
Therefore, no measures for anti-collision are not supported.
Q34.
When the power supply of host controller is disconnected in the access during tunnel mode, can the NFC-enabled device detect the state?
A34.
It is possible to detect the state using the response code to reader/writer. If the power supply of host controller is disconnected, the host does not return a response to the tag and the state is determined as the "No response from the host" of Tunnel mode error. Therefore, TypeF (JISX6319-4) and TypeB (ISO/IEC14443 TypeB) send back the status flag of xFF50 and the status word of x5000, respectively, to the reader/writer.
Q35.
Can everyone read the data (ID information, etc.) that the host stores in FeRAM system area through serial interface, or is there a restriction not to do so?
A35.
Everyone can read the data; no mechanism restricting the readout exists.
Q36.
To change the state of the system area to Read/Write after setting it to Read-only (with SL [flag data] set to MODE1 or MODE2), do I have to issue an INIT command through serial interface?
A36.
Yes, that's right!
Q37.
Is it possible to wake up the host with magnetic field?
A37.
For MN63Y1208, it is possible to generate an interrupt by detecting magnetic field.
Q38.
Can data transfer be performed only when the power is applied to the system?
A38.
For data transfer between a reader/writer and the host, both the host and NFC tag need to be powered.
To do so, apply a voltage to the power supply pin of NFC tag (MN63Y1210: VDD2, MN63Y1208: VDDEX).
For data transfer between a reader/writer and an NFC tag, the NFC tag operates with the magnetic field from a reader/writer, with no power applied. Therefore, you cannot stop the data transfer.
To do so, apply a voltage to the power supply pin of NFC tag (MN63Y1210: VDD2, MN63Y1208: VDDEX).
For data transfer between a reader/writer and an NFC tag, the NFC tag operates with the magnetic field from a reader/writer, with no power applied. Therefore, you cannot stop the data transfer.
Q39.
When reading the status information of RFID from the host with STATUS command, does a serial communication interrupt occur before RFID sends a response to the command to the host?
A39.
The issue of STATUS command generates no interrupt.
However, note that the NIRQ waveform changes from low to high when an interrupt source is generated before STATUS command is issued.
However, note that the NIRQ waveform changes from low to high when an interrupt source is generated before STATUS command is issued.
Q40.
Is there a limitation to the capacity of the host's virtual memory space in tunnel mode?
A40.
It is up to 4 Kbytes.
Q41.
Is it guaranteed that the initial value for the system area for NFC tag are fixed?
A41.
When you purchase the IC, the initial value for FeRAM, including system area, are indeterminate.
Therefore, the initial value is not guaranteed.
Therefore, the initial value is not guaranteed.
Q42.
Is it possible to turn ON the power supply for tag from OFF through communication from reader/writer?
A42.
It is possible to turn ON the power supply by sending a tunnel mode command from the reader/writer and thereby generating an interrupt request (IRQ) to the host from a tag.
Q43.
When does the host microcontroller use the IRQ pins (MN63Y1210: IRQ3V or IRQ5V, MN63Y1208: NIRQ)?
A43.
The host microcontroller uses the IRQ pins when using them as a trigger to apply VDD2 or send a QUERY command while in tunnel mode.
Software
- Q1.I got the following message, when trying to access the antenna evaluation board with a tag setting application software* for smartphone. What is the cause of this message? (* can be provided by us)
Error message: 「This device may not be MN63Yxxxx」 - Q2.When simultaneously accessed from both the reader/writer side (RF communication) and the equipment side (serial communication), which is the priority one? Is it necessary to make arrangement at the equipment side?
- Q3.Is it possible to change the communication protocol?
- Q4.It seems that the logic of TX waveform in tunnel mode is "Start bit = low, Stop bit = high."
Is the logic applicable to serial communication mode? - Q5.Is TypeB inferior to TypeA in communication performance?
- Q6.Is there any relationship between tunnel mode and NFC Forum specification? A tunnel mode command is issued when sending a startup pulse to the host. Is the command your own one or a one specified by NFC forum?
- Q7.When the system area is set to Read Only, how do I change it to Read/Write state?
- Q8.How do you execute the pairing in Bluetooth?
- Q9.Is NFC tag compatible with NDEF?
- Q10.Is it possible to enable NDEF for both TypeB and TypeF?
- Q11.What stage spends time for Bluetooth pairing?
- Q12.Is Handover for Wifi or Bluetooth specified?
- Q13.Are there any restrictions for reader/writer to communicate with NFC tag?
- Q14.What is the difference between SPI and the clock synchronous serial interface?
- Q15.MWhy the UART transfer rate of MN63Y1210 is 38.4 Kbps (max.)? It could have been much faster.
- Q16.When transferring image data with NFC, what is the actual rate?
- Q17.What is the procedure for paring?
- Q18.When the host's power supply is cut off in tunnel mode, can the NFC device detect it?
- Q19.In serial interface mode, is it possible for the tag ICs to be switched between master and slave?
- Q20.How does software relate to the NFC authentication?
- Q21.Is it possible to wake up the host even when the power of smartphone is off?
- Q22.Can the NFC tag be used as a reader/writer?
- Q23.With the NFC tag evaluation set (BTPB-101B and MN63Y1210 evaluation board), is it possible to turn on the tunnel mode forcibly?
- Q24.When making communication between host CPU and Tag LSI, what tools are required for a development environment?
- Q25.When making only RF communication, what tools are required for development environment ?
FAQ
Q1.
I got the following message, when trying to access the antenna evaluation board with a tag setting application software* for smartphone. What is the cause of this message? (* can be provided by us)
Error message: 「This device may not be MN63Yxxxx」
Error message: 「This device may not be MN63Yxxxx」
A1.
That message indicates that the system area has not been initialized.
Initialize the system area with the tag setting application software.
Initialize the system area with the tag setting application software.
Q2.
When simultaneously accessed from both the reader/writer side (RF communication) and the equipment side (serial communication), which is the priority one? Is it necessary to make arrangement at the equipment side?
A2.
The communication established earlier takes priority because of exclusive control.
For example, when performing a serial communication from equipment side during RF communication, the NFC tag sends back a response indicating busy status. So, the equipment side needs to perform a serial communication again.
For example, when performing a serial communication from equipment side during RF communication, the NFC tag sends back a response indicating busy status. So, the equipment side needs to perform a serial communication again.
Q3.
Is it possible to change the communication protocol?
A3.
The communication protocol corresponds to TypeB (ISO/IEC 14443 TypeB) and TypeF (JIS X6319-4). It is also possible to fix the protocol to either type.
Q4.
It seems that the logic of TX waveform in tunnel mode is "Start bit = low, Stop bit = high."
Is the logic applicable to serial communication mode?
Is the logic applicable to serial communication mode?
A4.
The logic in serial communication mode is the same as that in tunnel mode.
Q5.
Is TypeB inferior to TypeA in communication performance?
A5.
TypeB is commonly used for highly-functional IC card with built-in microcontroller, such as license, basic resident register, etc. TypeA is often used for small tag without built-in microcontroller. The communication distance is related to IC's power consumption. Therefore, small tag with low consumption has longer communication distance. From the above background, we are afraid that TypeB is considered inferior. However, our NFC tag without built-in microcontroller includes non-volatile memory, FeRAM with low power consumption, to reduce tag's power consumption, therefore enabling good communication performance for TypeB.
Q6.
Is there any relationship between tunnel mode and NFC Forum specification? A tunnel mode command is issued when sending a startup pulse to the host. Is the command your own one or a one specified by NFC forum?
A6.
We use the commands conforming to NFC Forum, achieving our own tunnel mode communication.
Q7.
When the system area is set to Read Only, how do I change it to Read/Write state?
A7.
You need to reset with the INIT command from host.
Q8.
How do you execute the pairing in Bluetooth?
A8.
Let us explain our demonstration environment as an example.
The driver in Windows or Android OS processes the pairing automatically. When it sends the Bluetooth MAC address of smartphone to a personal computer (PC) through NFC tag, the PC issues a connection request to the corresponding MAC address. At that time, the smartphone has been set to a reception wait state with bluetooth, and executes the pairing and starts communication when receiving the request from the PC.
The driver in Windows or Android OS processes the pairing automatically. When it sends the Bluetooth MAC address of smartphone to a personal computer (PC) through NFC tag, the PC issues a connection request to the corresponding MAC address. At that time, the smartphone has been set to a reception wait state with bluetooth, and executes the pairing and starts communication when receiving the request from the PC.
Q9.
Is NFC tag compatible with NDEF?
A9.
Yes, NFC tag is compatible with NDEF.
(Please see the specifications of each product to check whether it is NDEF compatible or not.)
MN63Y1208 is available for both TypeB and TypeF, while MN63Y1210A is available for TypeF only.
(Please see the specifications of each product to check whether it is NDEF compatible or not.)
MN63Y1208 is available for both TypeB and TypeF, while MN63Y1210A is available for TypeF only.
Q10.
Is it possible to enable NDEF for both TypeB and TypeF?
A10.
Yes, it is possible for NDEF-compatible product.
(Please see the specifications of each product to check whether it is NDEF compatible or not.)
To use tags as Type3 (TypeF), you should set the following as control information.
Attribute Information Block (Address: 0x0000 to 0x000F)
System Code (Address: 0x01E0 to 0x01E1)
To use tags as Type4B (TypeB), you should set the following as control information.
CC file (Address: 0x0180 to 0x018E)
NLEN (Address: 0x000C to 0x000D)
As an area to specify NDEF message size, the addresses of 0x000C-0x000D are used for both Type3 and Type4B Tags.
(Please see the specifications of each product to check whether it is NDEF compatible or not.)
To use tags as Type3 (TypeF), you should set the following as control information.
Attribute Information Block (Address: 0x0000 to 0x000F)
System Code (Address: 0x01E0 to 0x01E1)
To use tags as Type4B (TypeB), you should set the following as control information.
CC file (Address: 0x0180 to 0x018E)
NLEN (Address: 0x000C to 0x000D)
As an area to specify NDEF message size, the addresses of 0x000C-0x000D are used for both Type3 and Type4B Tags.
Q11.
What stage spends time for Bluetooth pairing?
A11.
Let us explain our demonstration environment as an example.
A personal computer (PC) starts Bluetooth connection with smartphone based on the MAC address sent from smartphone.
It spends time for Bluethooth connection with Windows.
(The application software on PC just calls the "connect" function for Bluetooth.)
A personal computer (PC) starts Bluetooth connection with smartphone based on the MAC address sent from smartphone.
It spends time for Bluethooth connection with Windows.
(The application software on PC just calls the "connect" function for Bluetooth.)
Q12.
Is Handover for Wifi or Bluetooth specified?
A12.
Handover is specified by NFC Forum.
For Bluetooth, the concrete specification is published: Bluetooth Secure Simple Pairing Using NFCFor WiFi, it is under consideration in NFC Forum.
For Bluetooth, the concrete specification is published: Bluetooth Secure Simple Pairing Using NFCFor WiFi, it is under consideration in NFC Forum.
Q13.
Are there any restrictions for reader/writer to communicate with NFC tag?
A13.
Use a reader/writer compatible with TypeB (ISO/IEC 14443 TypeB) or TypeF (JIS X6319-4) to enable communication with our NFC tags.
Q14.
What is the difference between SPI and the clock synchronous serial interface?
A14.
The clock synchronous serial interface we use differs from SPI in terms of pin count and options. However, it can perform the same serial communication as SPI.
Q15.
Why the UART transfer rate of MN63Y1210 is 38.4 Kbps (max.)? It could have been much faster.
A15.
The UART is intended to be used for home appliances. Therefore, we have determined that the rate from 9600 bps to 38.4 Kbps is enough for low-end home appliance microcontrollers. And the rate is lower than that of clock synchronous communication due to the enhanced noise suppression on signal line for home appliances.
Q16.
When transferring image data with NFC, what is the actual rate?
A16.
When data of 256 Kbytes are transferred with NFC, the rates are as follows:
Clock synchronous serial: 1 Mbps
TypeB: 42 seconds (50 Kbps)
TypeF: 28 seconds (76 Kbps)
* Samsung Nexus10 is used.
Clock synchronous serial: 1 Mbps
TypeB: 42 seconds (50 Kbps)
TypeF: 28 seconds (76 Kbps)
* Samsung Nexus10 is used.
Q17.
What is the procedure for paring?
A17.
Let us explain our demonstration environment as an example.
The pairing is executed as follows:
(1) MAC address is sent from smartphone to tag (microcontroller).
(2) Smartphone is set to a Bluetooth connection wait state.
(3) The tag (microcontroller) informs a personal computer (PC) of the MAC address.
(4) The PC issues a connection request to the MAC address by using the RFCOMM protocol.
(5) The connection is executed at OS level.
The pairing is executed as follows:
(1) MAC address is sent from smartphone to tag (microcontroller).
(2) Smartphone is set to a Bluetooth connection wait state.
(3) The tag (microcontroller) informs a personal computer (PC) of the MAC address.
(4) The PC issues a connection request to the MAC address by using the RFCOMM protocol.
(5) The connection is executed at OS level.
Q18.
When the host's power supply is cut off in tunnel mode, can the NFC device detect it?
A18.
The device can detect it with a response code. When the power supply of host controller is cut off, no response is returned to tag from host, so the state is considered as the "No response from Host" of tunnel mode error. Therefore, TypeF and TypeB return "Status flag = xFF50" and "Status word = x5000", respectively, to the NFC device.
Q19.
In serial interface mode, is it possible for the tag ICs to be switched between master and slave?
A19.
No, slave-only for both MN63Y1208 and MN63Y1210.
Q20.
How does software relate to the NFC authentication?
A20.
Smartphone (NFC controller) accesses NFC tag as the master. No software is required when smartphone reads/writes data from/to FeRAM of NFC tag. While in tunnel mode in which smartphone issues read/write requests to microcontroller through NFC tag, a tunnel request from smartphone causes an interrupt from NFC tag, triggering the processing to exchange pre-set commands between microcontroller software and NFC tag.
Q21.
Is it possible to wake up the host even when the power of smartphone is off?
A21.
No, it is impossible because generation of magnetic field is prevented when the power of smartphone is off.
Q22.
Can the NFC tag be used as a reader/writer?
A22.
No, it cannot. The NFC tag is a passive tag for reception only.
Q23.
With the NFC tag evaluation set (BTPB-101B and MN63Y1210 evaluation board), is it possible to turn on the tunnel mode forcibly?
A23.
It is possible. Whether tunnel communication or RF communication depends on the address to be specified. You should send a command with the address for tunnel communication fixed.
Q24.
When making communication between host CPU and Tag LSI, what tools are required for a development environment?
A24.
[Host CPU]
● Host CPU board (microcomputer board)
● Host CPU control software development tool (compiler, debugger, and so on)
● Host CPU control software (sample)
When connecting Host CPU to notebook personal computer [PC]:
● Notebook PC
● Control software for notebook PC
[NFC-enabled smartphone]
● NFC-enabled smartphone
● Android development environment (desktop PC and Android SDK [free])
● Application for smartphone (sample)
● Host CPU board (microcomputer board)
● Host CPU control software development tool (compiler, debugger, and so on)
● Host CPU control software (sample)
When connecting Host CPU to notebook personal computer [PC]:
● Notebook PC
● Control software for notebook PC
[NFC-enabled smartphone]
● NFC-enabled smartphone
● Android development environment (desktop PC and Android SDK [free])
● Application for smartphone (sample)
Q25.
When making only RF communication, what tools are required for development environment ?
A25.
● NFC-enabled smartphone
● Android developing environment (desktop PC and Android SDK [free])
● Application for smartphone (sample)
● Android developing environment (desktop PC and Android SDK [free])
● Application for smartphone (sample)
RF/Analog
- Q1.Is there some way to design an antenna without using Printed Circuit Board (PCB)?
- Q2.How do I determine the shape of antenna?
- Q3.How do I get the capacitor value for resonance frequency adjustment?
- Q4.Is it possible to measure the inductance of antenna without using expensive equipments, such as impedance analyzer?
- Q5.How do I measure the resonance frequency?
- Q6.Do you have any documents on how to design an antenna?
- Q7.Are the simulation results of communication distance of the NFC antenna design tool on your website guaranteed?
- Q8.Do you have any comparison data between the communication distance simulation result of the NFC antenna design tool on your website and the actually measured value.
- Q9.How can I use the full-featured version of NFC Design Navi on your website with Internet Explorer?
FAQ
Q1.
Is there some way to design an antenna without using Printed Circuit Board (PCB)?
A1.
You can use a coiled copper wire or Flexible Printed Circuits (FPC). Copper-wire antenna is often used when examining the antenna design (size, the number of turns, etc.) before making PCB. It is sometimes used in mass production. FPC is generally used in mass production.
Q2.
How do I determine the shape of antenna?
A2.
The antenna for tag should be designed with the following parameters: size, pattern width, spacing, thickness, number of turns of coil, input impedance to the IC, specifications of the reader antenna, and power supply to the antenna.
We have provided the antenna design tool (NFC Design Navigator) on our website to allow you to easily examine various antenna designs.
<NFC Design Navigator>
NFC Design Navigator
(The recommended browser is "Chrome.")
<NFC Design Navigator>
NFC Design Navigator
(The recommended browser is "Chrome.")
Q3.
How do I get the capacitor value for resonance frequency adjustment?
A3.
For more information, please see the "Adjustment of resonance frequency" in the antenna design guide for NFC Tag.
The antenna design guide for NFC
The antenna design guide for NFC
Q4.
Is it possible to measure the inductance of antenna without using expensive equipments, such as impedance analyzer?
A4.
Yes, you can use a dip meter or LCR meter, or can calculate with the NFC Design Navigator.
Q5.
How do I measure the resonance frequency?
A5.
For more information, please see the "Method for measurement of the resonance frequency" in the antenna design guide for NFC Tag.
The antenna design guide for NFC
The antenna design guide for NFC
Q6.
Do you have any documents on how to design an antenna?
A6.
The antenna design guide for NFC Tag is being published at the URL:
The antenna design guide for NFC
The antenna design guide for NFC
Q7.
Are the simulation results of communication distance of the NFC antenna design tool on your website guaranteed?
A7.
No. The results are not intended to guarantee operations, such as communication distance.
Please click the "Mag.Field" tag on the upper right of the NFC Design Navigator on our website to confirm the following note:
[Magnetic field strength and communication distance *)]
* Note: Example of our LSI, Characteristics is not guarantee on any condition
Please click the "Mag.Field" tag on the upper right of the NFC Design Navigator on our website to confirm the following note:
[Magnetic field strength and communication distance *)]
* Note: Example of our LSI, Characteristics is not guarantee on any condition
Q8.
Do you have any comparison data between the communication distance simulation result of the NFC antenna design tool on your website and the actually measured value.
A8.
Yes. You can see the comparison results for 11 types of tag antennas on the "Comparison of distance measurement and calculation tools" of the antenna design guide for NFC Tag.
Q9.
How can I use the full-featured version of NFC Design Navi on your website with Internet Explorer?
A9.
Use IE9 or later version. Firefox and Safari are also available.
Other
- Q1.What is the procedure to use NFC logo (N-mark) for instruction manual, packing case, and so on?
- Q2.Do I have to put NFC logo (N-mark) on packing case or instruction manual?
- Q3.Is the system (equipment) with built-in NFC tag subject to the radio law in each country?
Japan: Radio Act
US: FCC (Not EMC, but Wireless communications part)
EU: R&TTE Directive - Q4.Is it possible to provide a certificate showing that tag is not subject to Radio law?
- Q5.Is it necessary to register a unique ID (maker code, etc.) to NFC Forum?
- Q6.Is it possible to restrict the access from reader/writer to internal data ?
- Q7.Could you tell me the readers or smartphones with which you have confirmed reading of tag data?
- Q8.Is there any charge to get N-Mark?
- Q9.How does a smartphone and an NFC tag work when a CRC error occurs during RF communication?
- Q10.What is NFC Forum Certificate?
- Q11.I want to know product No. and name of each evaluation board.
- Q12.What is the package type?
- Q13.Do you have NFC tag ICs supporting TypeA?
- Q14.Can you provide the source code on evaluation board?
- Q15.Where are the tests specified by NFC Forum executed?
FAQ
Q1.
What is the procedure to use NFC logo (N-mark) for instruction manual, packing case, and so on?
A1.
http://www.nfc-forum.org/resources/N-Mark/
You can use the logo if you confirm the contents described on the following website and sign the "License Agreement" linked to the website to declare that you follow NFC Forum specifications.
You can use the logo if you confirm the contents described on the following website and sign the "License Agreement" linked to the website to declare that you follow NFC Forum specifications.
Q2.
Do I have to put NFC logo (N-mark) on packing case or instruction manual?
A2.
You are not obliged to put it on as of year 2013.
For more information, see the URL: http://www.nfc-forum.org/resources/N-Mark/.
For more information, see the URL: http://www.nfc-forum.org/resources/N-Mark/.
Q3.
Is the system (equipment) with built-in NFC tag subject to the radio law in each country?
Japan: Radio Act
US: FCC (Not EMC, but Wireless communications part)
EU: R&TTE Directive
Japan: Radio Act
US: FCC (Not EMC, but Wireless communications part)
EU: R&TTE Directive
A3.
Tag itself, which does not emit radio waves, is not subject to Radio Act and FCC, but to R&TTE.
For the application of R&TTE, you have to submit a declaration of conformity.
Q4.
Is it possible to provide a certificate showing that tag is not subject to Radio law?
A4.
Sorry. We cannot provide certificates.
Q5.
Is it necessary to register a unique ID (maker code, etc.) to NFC Forum?
A5.
There is no system to register a maker code or other IDs in NFC Forum.
Q6.
Is it possible to restrict the access from reader/writer to internal data ?
A6.
Yes. The access can be limited only to encrypted communication, from the reader/writer.
Q7.
Could you tell me the readers or smartphones with which you have confirmed reading of tag data?
A7.
NFC-enabled devices are being updated daily. For more information, please contact us.
Q8.
Is there any charge to get N-Mark?
A8.
It is free as of 2013.
For more information, see the rule at the URL. http://www.nfc-forum.org/resources/N-Mark/
For more information, see the rule at the URL. http://www.nfc-forum.org/resources/N-Mark/
Q9.
How does a smartphone and an NFC tag work when a CRC error occurs during RF communication?
A9.
Tag sends back no response when a CRC error occurs during RF communication .
Q10.
What is NFC Forum Certificate?
A10.
It is a mark that is allowed to use for the equipments which meet the specifications NFC Forum requires.
Q11.
I want to know product No. and name of each evaluation board.
A11.
Evaluation boards are different for each Product.
Please contact us after specifying the Part No.
Please contact us after specifying the Part No.
Q12.
What is the package type?
A12.
Package type is different for each product.
Please contact us after specifying the Part No.
Please contact us after specifying the Part No.
Q13.
Do you have NFC tag ICs supporting TypeA?
A13.
We don't provide the NFC tag ICs supporting TypeA (As of year 2013).
However, a reader/writer specified by NFC Forum includes not only TypeA but also TypeB and FeliCa. So, if a tag supports any one of them, communication is available.
However, a reader/writer specified by NFC Forum includes not only TypeA but also TypeB and FeliCa. So, if a tag supports any one of them, communication is available.
Q14.
Can you provide the source code on evaluation board?
A14.
It can be provided after signing the NDA with us.
Q15.
Where are the tests specified by NFC Forum executed?
A15.
The tests are executed at Test Labs listed in the following site.
http://www.nfc-forum.org/certification/certification-testing/labs-and-test-tools/authorized-test-labs/
http://www.nfc-forum.org/certification/certification-testing/labs-and-test-tools/authorized-test-labs/