<?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 NFC Commuication architecture in NFC</title>
    <link>https://community.nxp.com/t5/NFC/NFC-Commuication-architecture/m-p/655890#M1790</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Does NXP utilize Xped's patented NFC software for the tap and go NFC aspects of your chip offering on ARM?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 27 Sep 2016 09:59:57 GMT</pubDate>
    <dc:creator>martinbirch</dc:creator>
    <dc:date>2016-09-27T09:59:57Z</dc:date>
    <item>
      <title>NFC Commuication architecture</title>
      <link>https://community.nxp.com/t5/NFC/NFC-Commuication-architecture/m-p/655890#M1790</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Does NXP utilize Xped's patented NFC software for the tap and go NFC aspects of your chip offering on ARM?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 27 Sep 2016 09:59:57 GMT</pubDate>
      <guid>https://community.nxp.com/t5/NFC/NFC-Commuication-architecture/m-p/655890#M1790</guid>
      <dc:creator>martinbirch</dc:creator>
      <dc:date>2016-09-27T09:59:57Z</dc:date>
    </item>
    <item>
      <title>Re: NFC Commuication architecture</title>
      <link>https://community.nxp.com/t5/NFC/NFC-Commuication-architecture/m-p/655891#M1791</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello Martin Birch,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Sorry, I did not fully understand the question.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;NXP's NFC offering includes frontend ICs, controller ICs and connected tags, mainly compliant with ISO-14443(A/B) but also to other ISO standards and NFC Forum specifications depending on the device.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;While NXP provides some software enablement tools (linux drivers, stacks, NFC Reader libraries, MIFARE SDK or now TapLinx, Android demo apps, etc), the choice of a particular application software depends on the customer.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards!&lt;/P&gt;&lt;P&gt;Jorge Gonzalez&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 20 Oct 2016 00:06:58 GMT</pubDate>
      <guid>https://community.nxp.com/t5/NFC/NFC-Commuication-architecture/m-p/655891#M1791</guid>
      <dc:creator>Jorge_Gonzalez</dc:creator>
      <dc:date>2016-10-20T00:06:58Z</dc:date>
    </item>
  </channel>
</rss>

