<?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: Using SAM on CLRC663 for secure NFC communication in Other NXP Products</title>
    <link>https://community.nxp.com/t5/Other-NXP-Products/Using-SAM-on-CLRC663-for-secure-NFC-communication/m-p/1478812#M14437</link>
    <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/201920"&gt;@mikemov&lt;/a&gt;&amp;nbsp;:&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;RC663 SAM is secured under NDA (Non Disclosure Agreement), this means all the information, support and tools should be done through secured communication channels and only to customers with active NDA.&amp;nbsp; I would suggest you create a ticket for this.&amp;nbsp; Thanks.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Regards&lt;/P&gt;
&lt;P&gt;Daniel&lt;/P&gt;</description>
    <pubDate>Thu, 23 Jun 2022 07:23:20 GMT</pubDate>
    <dc:creator>danielchen</dc:creator>
    <dc:date>2022-06-23T07:23:20Z</dc:date>
    <item>
      <title>Using SAM on CLRC663 for secure NFC communication</title>
      <link>https://community.nxp.com/t5/Other-NXP-Products/Using-SAM-on-CLRC663-for-secure-NFC-communication/m-p/1470197#M14270</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;I am considering using CLRC663 for reader/writer applications and wanted to know how the SAM module can be used to protect NFC communication. Namely I wanted to know the following:&lt;/P&gt;&lt;P&gt;1) How are encryption keys distributed? Is a license required for this? If so, where can I find more information about this?&lt;/P&gt;&lt;P&gt;2) How are these secret keys loaded into SAM?&lt;/P&gt;&lt;P&gt;3) Does SAM require its own I2C interface (separate from the host I2C/control interface)&amp;nbsp;&amp;nbsp;&lt;/P&gt;&lt;P&gt;4) Can SAM secret keys be read via its I2C interface? If so, how can this be protected? Is there a data direction flow control?&lt;/P&gt;&lt;P&gt;Thank you!&lt;/P&gt;</description>
      <pubDate>Tue, 07 Jun 2022 22:38:21 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Other-NXP-Products/Using-SAM-on-CLRC663-for-secure-NFC-communication/m-p/1470197#M14270</guid>
      <dc:creator>mikemov</dc:creator>
      <dc:date>2022-06-07T22:38:21Z</dc:date>
    </item>
    <item>
      <title>Re: Using SAM on CLRC663 for secure NFC communication</title>
      <link>https://community.nxp.com/t5/Other-NXP-Products/Using-SAM-on-CLRC663-for-secure-NFC-communication/m-p/1478812#M14437</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/201920"&gt;@mikemov&lt;/a&gt;&amp;nbsp;:&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;RC663 SAM is secured under NDA (Non Disclosure Agreement), this means all the information, support and tools should be done through secured communication channels and only to customers with active NDA.&amp;nbsp; I would suggest you create a ticket for this.&amp;nbsp; Thanks.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Regards&lt;/P&gt;
&lt;P&gt;Daniel&lt;/P&gt;</description>
      <pubDate>Thu, 23 Jun 2022 07:23:20 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Other-NXP-Products/Using-SAM-on-CLRC663-for-secure-NFC-communication/m-p/1478812#M14437</guid>
      <dc:creator>danielchen</dc:creator>
      <dc:date>2022-06-23T07:23:20Z</dc:date>
    </item>
  </channel>
</rss>

