<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>NFCのトピックRe: NFC Write to NT3H2111</title>
    <link>https://community.nxp.com/t5/NFC/NFC-Write-to-NT3H2111/m-p/1350430#M8898</link>
    <description>&lt;P&gt;Dear Hitesh,&lt;/P&gt;
&lt;P&gt;Please check&amp;nbsp;3.2.4 "Why is it not possible to write a NDEF message with TagWriter?" in&amp;nbsp;&lt;A title="NTAG I²C plus - FAQs" href="https://www.nxp.com/docs/en/engineering-bulletin/TN00042.pdf" target="_blank" rel="noopener"&gt;NTAG I²C plus - FAQs&lt;/A&gt;.&lt;/P&gt;
&lt;P&gt;In general:&lt;/P&gt;
&lt;P&gt;1.) Applications shall use FD pin (interrupt) functionalities - to determine presence of NFC field. µC is notified when NFC field comes in and shall immediately stop any access to NTAG's I²C EEPROM access.&lt;/P&gt;
&lt;P&gt;2.) Access from I²C side shall always check for RF_LOCKED to be 0b before accessing (Read/Write) NTAG's EEPROM.&lt;/P&gt;
&lt;P&gt;3.) Access to EEPROM from I²C shall be as fast as possible and shall happen less frequent (e.g. every 1s)&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Best regards,&lt;/P&gt;
&lt;P&gt;uksac&lt;/P&gt;</description>
    <pubDate>Tue, 05 Oct 2021 07:50:33 GMT</pubDate>
    <dc:creator>ukcas</dc:creator>
    <dc:date>2021-10-05T07:50:33Z</dc:date>
    <item>
      <title>NFC Write to NT3H2111</title>
      <link>https://community.nxp.com/t5/NFC/NFC-Write-to-NT3H2111/m-p/1208886#M8884</link>
      <description>&lt;P&gt;I am using NT3H2211-2k with an esp 8266&amp;nbsp;&lt;BR /&gt;i am able to read and write using I2c and i can ensure the data is actually committed using NXP TagInfo /TagWriter but i cant write using NFC and as mentioned in Datasheet (AN12364),to avoid Conflict i have powered down the I2C master ,Still no cigar i have tried multiple apps and have got no positive response&lt;/P&gt;</description>
      <pubDate>Fri, 08 Jan 2021 10:21:39 GMT</pubDate>
      <guid>https://community.nxp.com/t5/NFC/NFC-Write-to-NT3H2111/m-p/1208886#M8884</guid>
      <dc:creator>hitesh_jetwani</dc:creator>
      <dc:date>2021-01-08T10:21:39Z</dc:date>
    </item>
    <item>
      <title>Re: NFC Write to NT3H2111</title>
      <link>https://community.nxp.com/t5/NFC/NFC-Write-to-NT3H2111/m-p/1350430#M8898</link>
      <description>&lt;P&gt;Dear Hitesh,&lt;/P&gt;
&lt;P&gt;Please check&amp;nbsp;3.2.4 "Why is it not possible to write a NDEF message with TagWriter?" in&amp;nbsp;&lt;A title="NTAG I²C plus - FAQs" href="https://www.nxp.com/docs/en/engineering-bulletin/TN00042.pdf" target="_blank" rel="noopener"&gt;NTAG I²C plus - FAQs&lt;/A&gt;.&lt;/P&gt;
&lt;P&gt;In general:&lt;/P&gt;
&lt;P&gt;1.) Applications shall use FD pin (interrupt) functionalities - to determine presence of NFC field. µC is notified when NFC field comes in and shall immediately stop any access to NTAG's I²C EEPROM access.&lt;/P&gt;
&lt;P&gt;2.) Access from I²C side shall always check for RF_LOCKED to be 0b before accessing (Read/Write) NTAG's EEPROM.&lt;/P&gt;
&lt;P&gt;3.) Access to EEPROM from I²C shall be as fast as possible and shall happen less frequent (e.g. every 1s)&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Best regards,&lt;/P&gt;
&lt;P&gt;uksac&lt;/P&gt;</description>
      <pubDate>Tue, 05 Oct 2021 07:50:33 GMT</pubDate>
      <guid>https://community.nxp.com/t5/NFC/NFC-Write-to-NT3H2111/m-p/1350430#M8898</guid>
      <dc:creator>ukcas</dc:creator>
      <dc:date>2021-10-05T07:50:33Z</dc:date>
    </item>
  </channel>
</rss>

