<?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のトピックInitialize Capability Container using i2c</title>
    <link>https://community.nxp.com/t5/NFC/Initialize-Capability-Container-using-i2c/m-p/807573#M4064</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I am attempting to initial the capability container on a NT3H2111 using I2C.&lt;/P&gt;&lt;P&gt;My first attempt was to read the existing data in pages 0 to 3 and set &lt;BR /&gt;page 3 to 0xE1 0X10 0x6D 0x00.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Following the write I an no longer able&amp;nbsp;to read or write using i2c.&lt;/P&gt;&lt;P&gt;Later I noticed a not in the specification:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;"The byte 0 of block 0 is always read as 04h. Writing to this byte modifies the l2C address."&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;What does this mean? Do I have to set byte 0 to 0x55 so the ics address stays at 0x55 ?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 17 Dec 2018 20:45:28 GMT</pubDate>
    <dc:creator>dcorb</dc:creator>
    <dc:date>2018-12-17T20:45:28Z</dc:date>
    <item>
      <title>Initialize Capability Container using i2c</title>
      <link>https://community.nxp.com/t5/NFC/Initialize-Capability-Container-using-i2c/m-p/807573#M4064</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I am attempting to initial the capability container on a NT3H2111 using I2C.&lt;/P&gt;&lt;P&gt;My first attempt was to read the existing data in pages 0 to 3 and set &lt;BR /&gt;page 3 to 0xE1 0X10 0x6D 0x00.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Following the write I an no longer able&amp;nbsp;to read or write using i2c.&lt;/P&gt;&lt;P&gt;Later I noticed a not in the specification:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;"The byte 0 of block 0 is always read as 04h. Writing to this byte modifies the l2C address."&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;What does this mean? Do I have to set byte 0 to 0x55 so the ics address stays at 0x55 ?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 17 Dec 2018 20:45:28 GMT</pubDate>
      <guid>https://community.nxp.com/t5/NFC/Initialize-Capability-Container-using-i2c/m-p/807573#M4064</guid>
      <dc:creator>dcorb</dc:creator>
      <dc:date>2018-12-17T20:45:28Z</dc:date>
    </item>
    <item>
      <title>Re: Initialize Capability Container using i2c</title>
      <link>https://community.nxp.com/t5/NFC/Initialize-Capability-Container-using-i2c/m-p/807574#M4065</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;A little more info:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I wrote the first sixteen bytes as follows. 0x55 in byte 0.&lt;/P&gt;&lt;P&gt;i2c_util /dev/i2c-0 0x55 w 0x0 16 55 92 5e 6a 09 4f 80 00 44 00 00 00 e1 10 6d 00&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Following the write the i2c address of the device changed to 0x1b&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;-bash-4.4# i2c_util /dev/i2c-0 0x1b r 0x0 16&lt;BR /&gt;0x1b[0x0000]: 04 92 5e 6a 09 4f 80 00 44 00 00 00 00 0a 06 00&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The last four bytes do not match what I wrote.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 18 Dec 2018 22:32:01 GMT</pubDate>
      <guid>https://community.nxp.com/t5/NFC/Initialize-Capability-Container-using-i2c/m-p/807574#M4065</guid>
      <dc:creator>dcorb</dc:creator>
      <dc:date>2018-12-18T22:32:01Z</dc:date>
    </item>
    <item>
      <title>Re: Initialize Capability Container using i2c</title>
      <link>https://community.nxp.com/t5/NFC/Initialize-Capability-Container-using-i2c/m-p/807575#M4066</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;If you suspect the I2C address has been modified, you may try the peek and poke application, it can scan all the possible address and find the right one.&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="pastedImage_1.png"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/70749i473B95803EED6DC8/image-size/large?v=v2&amp;amp;px=999" role="button" title="pastedImage_1.png" alt="pastedImage_1.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;This window app can be downloaded from &lt;A class="link-titled" href="https://www.nxp.com/downloads/en/apps/SW3652.zip" title="https://www.nxp.com/downloads/en/apps/SW3652.zip"&gt;https://www.nxp.com/downloads/en/apps/SW3652.zip&lt;/A&gt; , please also note the MCU connected with Ntag I2C should be programmed with the following firmware:&lt;A class="link-titled" href="https://www.nxp.com/downloads/en/snippets-boot-code-headers-monitors/SW3647.zip" title="https://www.nxp.com/downloads/en/snippets-boot-code-headers-monitors/SW3647.zip"&gt;https://www.nxp.com/downloads/en/snippets-boot-code-headers-monitors/SW3647.zip&lt;/A&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope that helps,&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>Mon, 24 Dec 2018 07:21:19 GMT</pubDate>
      <guid>https://community.nxp.com/t5/NFC/Initialize-Capability-Container-using-i2c/m-p/807575#M4066</guid>
      <dc:creator>Kan_Li</dc:creator>
      <dc:date>2018-12-24T07:21:19Z</dc:date>
    </item>
    <item>
      <title>Re: Initialize Capability Container using i2c</title>
      <link>https://community.nxp.com/t5/NFC/Initialize-Capability-Container-using-i2c/m-p/807576#M4067</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I am not working with the NXP developer board. The NFC chip I am programming is in our product. I can use the&amp;nbsp;i2cdetect utility to scan the i2c addresses.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;When I wrote 0xAA to byte 0 the chip does not appear in the scan anymore.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 02 Jan 2019 15:41:43 GMT</pubDate>
      <guid>https://community.nxp.com/t5/NFC/Initialize-Capability-Container-using-i2c/m-p/807576#M4067</guid>
      <dc:creator>dcorb</dc:creator>
      <dc:date>2019-01-02T15:41:43Z</dc:date>
    </item>
  </channel>
</rss>

