<?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 Re: How to kill a NTag I2c Plus (or stop it) in NFC</title>
    <link>https://community.nxp.com/t5/NFC/How-to-kill-a-NTag-I2c-Plus-or-stop-it/m-p/714141#M2740</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P style="color: #51626f; background-color: #ffffff; border: 0px;"&gt;Hello,&lt;/P&gt;&lt;P style="color: #51626f; background-color: #ffffff; border: 0px;"&gt;&lt;/P&gt;&lt;P style="color: #51626f; background-color: #ffffff; border: 0px;"&gt;Could you please answer to the following questions so that we can help you in a more accurate way?&lt;/P&gt;&lt;P style="color: #51626f; background-color: #ffffff; border: 0px;"&gt;&lt;/P&gt;&lt;P style="color: #51626f; background-color: #ffffff; border: 0px;"&gt;- What are the values you are&amp;nbsp;trying to write to NC_REG?&lt;/P&gt;&lt;P style="color: #51626f; background-color: #ffffff; border: 0px;"&gt;- Do you do a power cycle (reset), those configuration registers gets mirrored into session regs. and these new settings are valid?&lt;/P&gt;&lt;P style="color: #51626f; background-color: #ffffff; border: 0px;"&gt;- You are mentioning that you set writing access conditions for I2C side. What precisely did you set (which byte to what value)?&lt;/P&gt;&lt;P style="color: #51626f; background-color: #ffffff; border: 0px;"&gt;- Are you by accident overwriting Byte0 on Page0 where I2C address of the NTAG is?&lt;/P&gt;&lt;P style="color: #51626f; background-color: #ffffff; border: 0px;"&gt;&lt;/P&gt;&lt;P style="color: #51626f; background-color: #ffffff; border: 0px;"&gt;Regards,&lt;/P&gt;&lt;P style="color: #51626f; background-color: #ffffff; border: 0px;"&gt;Ivan.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 25 Sep 2017 17:06:29 GMT</pubDate>
    <dc:creator>IvanRuiz</dc:creator>
    <dc:date>2017-09-25T17:06:29Z</dc:date>
    <item>
      <title>How to kill a NTag I2c Plus (or stop it)</title>
      <link>https://community.nxp.com/t5/NFC/How-to-kill-a-NTag-I2c-Plus-or-stop-it/m-p/714140#M2739</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;I'm using a NT3H2111 (QFN package) and commuincate with it over the i2c interface and a busy bee efm8b2 microcontroller. The NT3H2111 is supplied with 3.3v, has 3kOhm pull ups on sda and scl and 0.1uF capaictor next to its vcc pin.&amp;nbsp;&lt;/P&gt;&lt;P&gt;At first I did only read 7 Bytes of the config register (address&amp;nbsp;0x3A) just for testing the busy bee smbus driver. That test reading was running for at least a week or two, while I was working on other stuff. Today I started to develop the communction between the uC and the ntag, so the manual stated&amp;nbsp; that a i2c read and write config registers always transfers 16bytes. So I changed that from my 7byte to 16 and added a write accees to the config register ( stetting some values in the NC_REG at the config address, remaining bytes are kept to their default values). And this kills my ntag. I killed now the fourth chip, after I read more than the 7bytes and/or start writing the config reg. The chip dies after 4 or 5 times doing that. Looking on the SDA and SCL line then, they both are pulled to gnd when the uC tries to start the communiction. I can still access the ntag with my Smartphone (ndef data), but erase or wirting the config regsiters does not work either after the i2c communictation starts failing.&lt;/P&gt;&lt;P&gt;I measured everything around the ntag on my pcb, there is defenetly no shortcut, and 3kOhm pull ups should be fine also. And the test reading was running for at least a week, like I already stated.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Has anyone faced a issue like that? I'm totally confused.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 01 Sep 2017 23:28:28 GMT</pubDate>
      <guid>https://community.nxp.com/t5/NFC/How-to-kill-a-NTag-I2c-Plus-or-stop-it/m-p/714140#M2739</guid>
      <dc:creator>kaibuechler</dc:creator>
      <dc:date>2017-09-01T23:28:28Z</dc:date>
    </item>
    <item>
      <title>Re: How to kill a NTag I2c Plus (or stop it)</title>
      <link>https://community.nxp.com/t5/NFC/How-to-kill-a-NTag-I2c-Plus-or-stop-it/m-p/714141#M2740</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P style="color: #51626f; background-color: #ffffff; border: 0px;"&gt;Hello,&lt;/P&gt;&lt;P style="color: #51626f; background-color: #ffffff; border: 0px;"&gt;&lt;/P&gt;&lt;P style="color: #51626f; background-color: #ffffff; border: 0px;"&gt;Could you please answer to the following questions so that we can help you in a more accurate way?&lt;/P&gt;&lt;P style="color: #51626f; background-color: #ffffff; border: 0px;"&gt;&lt;/P&gt;&lt;P style="color: #51626f; background-color: #ffffff; border: 0px;"&gt;- What are the values you are&amp;nbsp;trying to write to NC_REG?&lt;/P&gt;&lt;P style="color: #51626f; background-color: #ffffff; border: 0px;"&gt;- Do you do a power cycle (reset), those configuration registers gets mirrored into session regs. and these new settings are valid?&lt;/P&gt;&lt;P style="color: #51626f; background-color: #ffffff; border: 0px;"&gt;- You are mentioning that you set writing access conditions for I2C side. What precisely did you set (which byte to what value)?&lt;/P&gt;&lt;P style="color: #51626f; background-color: #ffffff; border: 0px;"&gt;- Are you by accident overwriting Byte0 on Page0 where I2C address of the NTAG is?&lt;/P&gt;&lt;P style="color: #51626f; background-color: #ffffff; border: 0px;"&gt;&lt;/P&gt;&lt;P style="color: #51626f; background-color: #ffffff; border: 0px;"&gt;Regards,&lt;/P&gt;&lt;P style="color: #51626f; background-color: #ffffff; border: 0px;"&gt;Ivan.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 25 Sep 2017 17:06:29 GMT</pubDate>
      <guid>https://community.nxp.com/t5/NFC/How-to-kill-a-NTag-I2c-Plus-or-stop-it/m-p/714141#M2740</guid>
      <dc:creator>IvanRuiz</dc:creator>
      <dc:date>2017-09-25T17:06:29Z</dc:date>
    </item>
  </channel>
</rss>

