<?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: SmartMX3 Contactless Identification procédure in Smart Cards and Secure Element</title>
    <link>https://community.nxp.com/t5/Smart-Cards-and-Secure-Element/SmartMX3-Contactless-Identification-proc%C3%A9dure/m-p/1954311#M167</link>
    <description>I misread AN10833.&lt;BR /&gt;GetVersion gives all the information I need in the hardware type byte !</description>
    <pubDate>Fri, 13 Sep 2024 13:24:06 GMT</pubDate>
    <dc:creator>frederic_surleau</dc:creator>
    <dc:date>2024-09-13T13:24:06Z</dc:date>
    <item>
      <title>SmartMX3 Contactless Identification procédure</title>
      <link>https://community.nxp.com/t5/Smart-Cards-and-Secure-Element/SmartMX3-Contactless-Identification-proc%C3%A9dure/m-p/1574869#M13</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;SAK of SmartMX3 is 0x28.&lt;/P&gt;&lt;P&gt;If I follow AN10833, I find "SmartMX with MIFARE Classic 1 K", not SmartMX 3...&lt;/P&gt;&lt;P&gt;It is true, that SmartMX3 if capable of emulating MIFARE Classic, but it can do more than that.&lt;/P&gt;&lt;P&gt;Is there an official way to differenciate SmartMX and SmartMX 3 ?&lt;/P&gt;&lt;P&gt;Personnaly, I use GetVersion in L4, but doing that, I find A Mifare DESFire with unknown version...&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Fred.&lt;/P&gt;</description>
      <pubDate>Tue, 27 Dec 2022 09:13:22 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Smart-Cards-and-Secure-Element/SmartMX3-Contactless-Identification-proc%C3%A9dure/m-p/1574869#M13</guid>
      <dc:creator>frederic_surleau</dc:creator>
      <dc:date>2022-12-27T09:13:22Z</dc:date>
    </item>
    <item>
      <title>Re: SmartMX3 Contactless Identification procédure</title>
      <link>https://community.nxp.com/t5/Smart-Cards-and-Secure-Element/SmartMX3-Contactless-Identification-proc%C3%A9dure/m-p/1575334#M14</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/119431"&gt;@frederic_surleau&lt;/a&gt;&amp;nbsp;,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Is&amp;nbsp;SmartMX and SMX3 with JCOP? If this is the case, you may use a JCOP command to readout information about the platform.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Have a great day,&lt;BR /&gt;Kan&lt;/P&gt;
&lt;P&gt;&lt;BR /&gt;-------------------------------------------------------------------------------&lt;BR /&gt;Note:&lt;BR /&gt;- If this post answers your question, please click the "Mark Correct" button. Thank you!&lt;BR /&gt;- We are following threads for 7 weeks after the last post, later replies are ignored&lt;BR /&gt;Please open a new thread and refer to the closed one, if you have a related question at a later point in time.&lt;BR /&gt;-------------------------------------------------------------------------------&lt;/P&gt;</description>
      <pubDate>Thu, 29 Dec 2022 01:30:46 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Smart-Cards-and-Secure-Element/SmartMX3-Contactless-Identification-proc%C3%A9dure/m-p/1575334#M14</guid>
      <dc:creator>Kan_Li</dc:creator>
      <dc:date>2022-12-29T01:30:46Z</dc:date>
    </item>
    <item>
      <title>Re: SmartMX3 Contactless Identification procédure</title>
      <link>https://community.nxp.com/t5/Smart-Cards-and-Secure-Element/SmartMX3-Contactless-Identification-proc%C3%A9dure/m-p/1578578#M15</link>
      <description>&lt;P&gt;HI,&lt;/P&gt;&lt;P&gt;The reader is supposed to detect the type or capabilities of card : Mifare and/or Desfire because the users have all sorts of cards.&lt;/P&gt;&lt;P&gt;If the reader must know the type of card presented, what is the purpose of AN10833 "MIFARE type identification procedure" ?&lt;/P&gt;&lt;P&gt;Regards.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 06 Jan 2023 12:56:03 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Smart-Cards-and-Secure-Element/SmartMX3-Contactless-Identification-proc%C3%A9dure/m-p/1578578#M15</guid>
      <dc:creator>frederic_surleau</dc:creator>
      <dc:date>2023-01-06T12:56:03Z</dc:date>
    </item>
    <item>
      <title>Re: SmartMX3 Contactless Identification procédure</title>
      <link>https://community.nxp.com/t5/Smart-Cards-and-Secure-Element/SmartMX3-Contactless-Identification-proc%C3%A9dure/m-p/1579115#M16</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/119431"&gt;@frederic_surleau&lt;/a&gt;&amp;nbsp;,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;&amp;nbsp;AN10833 is used for Mifare type identification, and it can also be used to distinguish SmartMX family from Mifare, but if you want to further identify if it is a SmartMX3, you have to use the JCOP command.&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Hope that makes sense,&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Have a great day,&lt;BR /&gt;Kan&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;-------------------------------------------------------------------------------&lt;BR /&gt;Note:&lt;BR /&gt;- If this post answers your question, please click the "Mark Correct" button. Thank you!&lt;BR /&gt;- We are following threads for 7 weeks after the last post, later replies are ignored&lt;BR /&gt;Please open a new thread and refer to the closed one, if you have a related question at a later point in time.&lt;BR /&gt;-------------------------------------------------------------------------------&lt;/P&gt;</description>
      <pubDate>Mon, 09 Jan 2023 08:34:47 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Smart-Cards-and-Secure-Element/SmartMX3-Contactless-Identification-proc%C3%A9dure/m-p/1579115#M16</guid>
      <dc:creator>Kan_Li</dc:creator>
      <dc:date>2023-01-09T08:34:47Z</dc:date>
    </item>
    <item>
      <title>Re: SmartMX3 Contactless Identification procédure</title>
      <link>https://community.nxp.com/t5/Smart-Cards-and-Secure-Element/SmartMX3-Contactless-Identification-proc%C3%A9dure/m-p/1954142#M166</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;Our card reader is used to read Mifare classic and Mifare DESFire cards.&lt;/P&gt;&lt;P&gt;Some customers have both DESFire cards and P71D600 JCOP4.5 with DESFire emulation.&lt;/P&gt;&lt;P&gt;I need to be able to recognise the card to adjust timings.&lt;/P&gt;&lt;P&gt;With "'&lt;SPAN&gt;SmartMX3 P71D320 JCOP4" I can read Historical byte to distiguish real DESFire and P71D320, but not with P71D600.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;The only thing I can see is a "strange" hardware version" : 0x43.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;How can i detect P71D600 emulating a DESFire without entering the "JCOP world" I don't need ?&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Regards,&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Fred.&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 13 Sep 2024 09:14:56 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Smart-Cards-and-Secure-Element/SmartMX3-Contactless-Identification-proc%C3%A9dure/m-p/1954142#M166</guid>
      <dc:creator>frederic_surleau</dc:creator>
      <dc:date>2024-09-13T09:14:56Z</dc:date>
    </item>
    <item>
      <title>Re: SmartMX3 Contactless Identification procédure</title>
      <link>https://community.nxp.com/t5/Smart-Cards-and-Secure-Element/SmartMX3-Contactless-Identification-proc%C3%A9dure/m-p/1954311#M167</link>
      <description>I misread AN10833.&lt;BR /&gt;GetVersion gives all the information I need in the hardware type byte !</description>
      <pubDate>Fri, 13 Sep 2024 13:24:06 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Smart-Cards-and-Secure-Element/SmartMX3-Contactless-Identification-proc%C3%A9dure/m-p/1954311#M167</guid>
      <dc:creator>frederic_surleau</dc:creator>
      <dc:date>2024-09-13T13:24:06Z</dc:date>
    </item>
  </channel>
</rss>

