<?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 NTAG424 Personalization Example Shows Incorrect Data in NFC</title>
    <link>https://community.nxp.com/t5/NFC/NTAG424-Personalization-Example-Shows-Incorrect-Data/m-p/1706397#M10651</link>
    <description>&lt;P&gt;The NTAG 424 DNA personalization examples (AN12196) for Get File Settings (section 6.4) and Change NDEF File Settings (section 6.9) do NOT match the specifications listed by the NTAG 424 DNA Product Sheet (NT4H2421Gx and&amp;nbsp;NT4H2421Tx).&lt;BR /&gt;&lt;BR /&gt;The first mismatch is around AccessRights. In the personalization examples (see section 6.4 and 6.9), the hex value "00E0" is used to reference the following AccessRights:&lt;BR /&gt;- FileAR.ReadWrite = 0&lt;BR /&gt;- FileAR.Change = 0&lt;BR /&gt;- FileAR.Read = E&lt;BR /&gt;- FileAR.Write = 0&lt;BR /&gt;&lt;BR /&gt;However, in the actual product spec, in section 8.2.3.3, it is specified that:&lt;BR /&gt;- FileAR.Read = Bit index 15..12&lt;BR /&gt;- FileAR.Write = Bit Index 11..8&lt;BR /&gt;- FileAR.ReadWrite = Bit Index 7..4&lt;BR /&gt;- FileAR.Change = bit Index 3..0&lt;BR /&gt;&lt;BR /&gt;Thus, based on the product guidelines, "00E0" should in fact represent the following AccessRights:&lt;BR /&gt;- FileAr.Read = 0&lt;BR /&gt;- FileAr.Write = 0&lt;BR /&gt;- FileAr.ReadWrite = E&lt;BR /&gt;- FileAr.Write = 0&lt;BR /&gt;&lt;BR /&gt;It is thus not clear whether the product guidelines are incorrect, or if the personalization document is incorrect.&lt;BR /&gt;&lt;BR /&gt;A similar mismatch presents itself in the SDMAccessRights, where in the personalization example the hex value "F121" is used to reference the following SDMAccessRights:&lt;BR /&gt;- RFU = F&lt;BR /&gt;- FileAR.SDMCtrRet = 1&lt;BR /&gt;- FileAR.SDMMetaRead = 2&lt;BR /&gt;- FileAr.SDMFileRead = 1&lt;BR /&gt;&lt;BR /&gt;However, in the actual product spec, under section 10.7.1 Table 69, it is specified that:&lt;BR /&gt;- FileAR.SDMMetaRead = Bit Index 15..12&lt;BR /&gt;- FileAR.SDMFileRead = Bit Index 11..8&lt;BR /&gt;- RFU = Bit Index 7..4&lt;BR /&gt;- FileAR.SDMCtrRet = Bit Index 3..0&lt;BR /&gt;&lt;BR /&gt;Thus, based on the product guidelines, "F121" should in fact represent the following SDMAccessRights:&lt;BR /&gt;- FileAR.SDMMetaRead = F&lt;BR /&gt;- FileAR.SDMFileRead = 1&lt;BR /&gt;- RFU = 2&lt;BR /&gt;- FileAR.SDMCtrRet = 1&lt;BR /&gt;&lt;BR /&gt;This is of course incorrect since the RFU bit may not be 2. But yet again, we cannot determine whether it is the personalization example that presented incorrect data or the product spec itself.&lt;BR /&gt;&lt;BR /&gt;Could someone please help clarify which document is in fact correct?&lt;/P&gt;</description>
    <pubDate>Thu, 17 Aug 2023 08:03:02 GMT</pubDate>
    <dc:creator>fwabbin</dc:creator>
    <dc:date>2023-08-17T08:03:02Z</dc:date>
    <item>
      <title>NTAG424 Personalization Example Shows Incorrect Data</title>
      <link>https://community.nxp.com/t5/NFC/NTAG424-Personalization-Example-Shows-Incorrect-Data/m-p/1706397#M10651</link>
      <description>&lt;P&gt;The NTAG 424 DNA personalization examples (AN12196) for Get File Settings (section 6.4) and Change NDEF File Settings (section 6.9) do NOT match the specifications listed by the NTAG 424 DNA Product Sheet (NT4H2421Gx and&amp;nbsp;NT4H2421Tx).&lt;BR /&gt;&lt;BR /&gt;The first mismatch is around AccessRights. In the personalization examples (see section 6.4 and 6.9), the hex value "00E0" is used to reference the following AccessRights:&lt;BR /&gt;- FileAR.ReadWrite = 0&lt;BR /&gt;- FileAR.Change = 0&lt;BR /&gt;- FileAR.Read = E&lt;BR /&gt;- FileAR.Write = 0&lt;BR /&gt;&lt;BR /&gt;However, in the actual product spec, in section 8.2.3.3, it is specified that:&lt;BR /&gt;- FileAR.Read = Bit index 15..12&lt;BR /&gt;- FileAR.Write = Bit Index 11..8&lt;BR /&gt;- FileAR.ReadWrite = Bit Index 7..4&lt;BR /&gt;- FileAR.Change = bit Index 3..0&lt;BR /&gt;&lt;BR /&gt;Thus, based on the product guidelines, "00E0" should in fact represent the following AccessRights:&lt;BR /&gt;- FileAr.Read = 0&lt;BR /&gt;- FileAr.Write = 0&lt;BR /&gt;- FileAr.ReadWrite = E&lt;BR /&gt;- FileAr.Write = 0&lt;BR /&gt;&lt;BR /&gt;It is thus not clear whether the product guidelines are incorrect, or if the personalization document is incorrect.&lt;BR /&gt;&lt;BR /&gt;A similar mismatch presents itself in the SDMAccessRights, where in the personalization example the hex value "F121" is used to reference the following SDMAccessRights:&lt;BR /&gt;- RFU = F&lt;BR /&gt;- FileAR.SDMCtrRet = 1&lt;BR /&gt;- FileAR.SDMMetaRead = 2&lt;BR /&gt;- FileAr.SDMFileRead = 1&lt;BR /&gt;&lt;BR /&gt;However, in the actual product spec, under section 10.7.1 Table 69, it is specified that:&lt;BR /&gt;- FileAR.SDMMetaRead = Bit Index 15..12&lt;BR /&gt;- FileAR.SDMFileRead = Bit Index 11..8&lt;BR /&gt;- RFU = Bit Index 7..4&lt;BR /&gt;- FileAR.SDMCtrRet = Bit Index 3..0&lt;BR /&gt;&lt;BR /&gt;Thus, based on the product guidelines, "F121" should in fact represent the following SDMAccessRights:&lt;BR /&gt;- FileAR.SDMMetaRead = F&lt;BR /&gt;- FileAR.SDMFileRead = 1&lt;BR /&gt;- RFU = 2&lt;BR /&gt;- FileAR.SDMCtrRet = 1&lt;BR /&gt;&lt;BR /&gt;This is of course incorrect since the RFU bit may not be 2. But yet again, we cannot determine whether it is the personalization example that presented incorrect data or the product spec itself.&lt;BR /&gt;&lt;BR /&gt;Could someone please help clarify which document is in fact correct?&lt;/P&gt;</description>
      <pubDate>Thu, 17 Aug 2023 08:03:02 GMT</pubDate>
      <guid>https://community.nxp.com/t5/NFC/NTAG424-Personalization-Example-Shows-Incorrect-Data/m-p/1706397#M10651</guid>
      <dc:creator>fwabbin</dc:creator>
      <dc:date>2023-08-17T08:03:02Z</dc:date>
    </item>
    <item>
      <title>Re: NTAG424 Personalization Example Shows Incorrect Data</title>
      <link>https://community.nxp.com/t5/NFC/NTAG424-Personalization-Example-Shows-Incorrect-Data/m-p/1709074#M10660</link>
      <description>&lt;P&gt;Hello&amp;nbsp;&lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/221804"&gt;@fwabbin&lt;/a&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thanks for contacting us and interested the NXP products.&lt;/P&gt;
&lt;P&gt;Please refer to section 6 of AN12196, personalization&amp;nbsp;examples are tested and available.&lt;/P&gt;
&lt;P&gt;BR&lt;/P&gt;
&lt;P&gt;kelly&lt;/P&gt;</description>
      <pubDate>Tue, 22 Aug 2023 11:37:37 GMT</pubDate>
      <guid>https://community.nxp.com/t5/NFC/NTAG424-Personalization-Example-Shows-Incorrect-Data/m-p/1709074#M10660</guid>
      <dc:creator>KaiLi</dc:creator>
      <dc:date>2023-08-22T11:37:37Z</dc:date>
    </item>
  </channel>
</rss>

