<?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>topic NTAG I2C Plus giving NACK over i2c  in NFC</title>
    <link>https://community.nxp.com/t5/NFC/NTAG-I2C-Plus-giving-NACK-over-i2c/m-p/711643#M2715</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I am working on &amp;nbsp;NTAG I2C. plus 2k version&lt;/P&gt;&lt;P&gt;I &amp;nbsp;Could read/ write to the NFC chip through the host microcontroller and a NFC device.&lt;/P&gt;&lt;P&gt;Now all of sudden the I can neither read nor write into the NFC chip through I2C from the host MCU, but I can read/ write NDEF mesages through my mobile phone (NFC device). I can also read registers using the NXP Android app.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I check the I2C pin, everything is correct.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Can someone please tell me whats going on here?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 30 Aug 2017 10:21:23 GMT</pubDate>
    <dc:creator>tarunpanchal</dc:creator>
    <dc:date>2017-08-30T10:21:23Z</dc:date>
    <item>
      <title>NTAG I2C Plus giving NACK over i2c</title>
      <link>https://community.nxp.com/t5/NFC/NTAG-I2C-Plus-giving-NACK-over-i2c/m-p/711643#M2715</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I am working on &amp;nbsp;NTAG I2C. plus 2k version&lt;/P&gt;&lt;P&gt;I &amp;nbsp;Could read/ write to the NFC chip through the host microcontroller and a NFC device.&lt;/P&gt;&lt;P&gt;Now all of sudden the I can neither read nor write into the NFC chip through I2C from the host MCU, but I can read/ write NDEF mesages through my mobile phone (NFC device). I can also read registers using the NXP Android app.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I check the I2C pin, everything is correct.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Can someone please tell me whats going on here?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 30 Aug 2017 10:21:23 GMT</pubDate>
      <guid>https://community.nxp.com/t5/NFC/NTAG-I2C-Plus-giving-NACK-over-i2c/m-p/711643#M2715</guid>
      <dc:creator>tarunpanchal</dc:creator>
      <dc:date>2017-08-30T10:21:23Z</dc:date>
    </item>
    <item>
      <title>Re: NTAG I2C Plus giving NACK over i2c</title>
      <link>https://community.nxp.com/t5/NFC/NTAG-I2C-Plus-giving-NACK-over-i2c/m-p/711644#M2716</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hey,&amp;nbsp;&lt;/P&gt;&lt;P&gt;I'm having the exact same problem! I already killed 4 of these tags in a row. Reading worked fine for a few weeks (I was developing other stuff meanwhile but a reading of the config Register after every reset was implemented), than I started to write to the tag (over I2C) and the chip died after a few resets. With the Android app you can still connect, but writing to the config register stopped working in most of the cases.&lt;/P&gt;&lt;P&gt;What I did so far:&lt;/P&gt;&lt;P&gt;I checked the i2c bus with my scope - looks good, no noise, no Spikes.&lt;/P&gt;&lt;P&gt;I checked the supply voltag, steady at 3.3V with Vpp of 30mV&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;May I ask which mcu you are using? For me it is a EFM8B2.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 04 Sep 2017 17:48:10 GMT</pubDate>
      <guid>https://community.nxp.com/t5/NFC/NTAG-I2C-Plus-giving-NACK-over-i2c/m-p/711644#M2716</guid>
      <dc:creator>kaibuechler</dc:creator>
      <dc:date>2017-09-04T17:48:10Z</dc:date>
    </item>
    <item>
      <title>Re: NTAG I2C Plus giving NACK over i2c</title>
      <link>https://community.nxp.com/t5/NFC/NTAG-I2C-Plus-giving-NACK-over-i2c/m-p/711645#M2717</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Can the I2C host access the register in the tag? for example, the session register.&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;Have a great day,&lt;BR /&gt;Kan&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;-----------------------------------------------------------------------------------------------------------------------&lt;BR /&gt;Note: If this post answers your question, please click the Correct Answer button. Thank you!&lt;BR /&gt;-----------------------------------------------------------------------------------------------------------------------&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 06 Sep 2017 07:32:31 GMT</pubDate>
      <guid>https://community.nxp.com/t5/NFC/NTAG-I2C-Plus-giving-NACK-over-i2c/m-p/711645#M2717</guid>
      <dc:creator>Kan_Li</dc:creator>
      <dc:date>2017-09-06T07:32:31Z</dc:date>
    </item>
    <item>
      <title>Re: NTAG I2C Plus giving NACK over i2c</title>
      <link>https://community.nxp.com/t5/NFC/NTAG-I2C-Plus-giving-NACK-over-i2c/m-p/711646#M2718</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;no I cannot access seassion or config registers. I'm geting a NACK after sending the NTAG address and a 0 for writing.&lt;/P&gt;&lt;P&gt;I can read the seassion and config registers over nfc, but writing the config registers fails (with the nxp nfc demo app).&lt;/P&gt;&lt;P&gt;Like I've said before, a new chip works for a while, but they'll&amp;nbsp; start to act weird sooner or later (all 4 chips usesd are from the same reel).&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="NewFile1.png"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/28732iB7EAECB96A0F7AAF/image-size/large?v=v2&amp;amp;px=999" role="button" title="NewFile1.png" alt="NewFile1.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 10 Sep 2017 15:46:17 GMT</pubDate>
      <guid>https://community.nxp.com/t5/NFC/NTAG-I2C-Plus-giving-NACK-over-i2c/m-p/711646#M2718</guid>
      <dc:creator>kaibuechler</dc:creator>
      <dc:date>2017-09-10T15:46:17Z</dc:date>
    </item>
    <item>
      <title>Re: NTAG I2C Plus giving NACK over i2c</title>
      <link>https://community.nxp.com/t5/NFC/NTAG-I2C-Plus-giving-NACK-over-i2c/m-p/711647#M2719</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I think I found the Problem. It seems like the reset button of the ntag demo app is Setting the slave address of the tag to 0.&amp;nbsp;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 10 Sep 2017 16:23:18 GMT</pubDate>
      <guid>https://community.nxp.com/t5/NFC/NTAG-I2C-Plus-giving-NACK-over-i2c/m-p/711647#M2719</guid>
      <dc:creator>kaibuechler</dc:creator>
      <dc:date>2017-09-10T16:23:18Z</dc:date>
    </item>
  </channel>
</rss>

