<?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: Problems doing updateBinary in NFC</title>
    <link>https://community.nxp.com/t5/NFC/Problems-doing-updateBinary/m-p/828143#M4365</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Harry,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks for your email!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;It was explained to me that the f2 2  was in truth a WTX.  I had been looking at the ST25TA64k doc(where the table was labelled S-Block detailed format), but in the corresponding table in the ST25TA2k doc, the table is labelled PCB field of the S-Block format) so that makes sense.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Now (with a different card) I am writing an 8 byte message successfully at offset 4 but when I try a longer 16 byte message I get no ACK/NAK.   I’m suspicious that I need to zero the NDEF but when I tried overwriting the two bytes at offset 0, I once again got the no ACK/NAK.  But when I changed my offset back to 4 (where I had been writing the 8 bytes successfully) I was once again able to write the 8 bytes.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I would be grateful for any guidance!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks again,&lt;/P&gt;&lt;P&gt;Larry&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 20 Nov 2018 20:52:35 GMT</pubDate>
    <dc:creator>larryansell</dc:creator>
    <dc:date>2018-11-20T20:52:35Z</dc:date>
    <item>
      <title>Problems doing updateBinary</title>
      <link>https://community.nxp.com/t5/NFC/Problems-doing-updateBinary/m-p/828139#M4361</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Problem doing updateBinary on ST25TA 8K.&amp;nbsp; I have been able to write using updateBinary only several times.&amp;nbsp; &amp;nbsp;Most often I get a strange set of bytes.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;For example:&lt;/P&gt;&lt;P&gt;I send 16 bytes using the NDEF updateBinary command after the NDEF Select file&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;0x2 0x0 0xd6 0x0 0x4 0x10 0x54, 0x77 0x61 0x73 0x62 0x72 0x69 0x6c 0x6c 0x69, 0x67 0x61 0x6e 0x64 0x74 0x68&amp;nbsp;&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;and I get back&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;0xf2,0x2,&amp;nbsp;&amp;nbsp;&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Which almost fits as a WTX but the bits 7 and 6 are not set.&amp;nbsp; So it's almost like a deselect?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Sometimes I get no response from the card.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Any insight into this would be greatly appreciated.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Larry&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 13 Nov 2018 00:10:41 GMT</pubDate>
      <guid>https://community.nxp.com/t5/NFC/Problems-doing-updateBinary/m-p/828139#M4361</guid>
      <dc:creator>larryansell</dc:creator>
      <dc:date>2018-11-13T00:10:41Z</dc:date>
    </item>
    <item>
      <title>Re: Problems doing updateBinary</title>
      <link>https://community.nxp.com/t5/NFC/Problems-doing-updateBinary/m-p/828140#M4362</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello,&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Could you please let me know which reader or frontend are you using?&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&amp;nbsp;&lt;BR /&gt;Estepahania&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 15 Nov 2018 20:59:27 GMT</pubDate>
      <guid>https://community.nxp.com/t5/NFC/Problems-doing-updateBinary/m-p/828140#M4362</guid>
      <dc:creator>stephanie_m</dc:creator>
      <dc:date>2018-11-15T20:59:27Z</dc:date>
    </item>
    <item>
      <title>Re: Problems doing updateBinary</title>
      <link>https://community.nxp.com/t5/NFC/Problems-doing-updateBinary/m-p/828141#M4363</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Estepahania,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I’m using a pn5180, with code modelled on the nxp reader lib.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Larry&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 15 Nov 2018 21:12:58 GMT</pubDate>
      <guid>https://community.nxp.com/t5/NFC/Problems-doing-updateBinary/m-p/828141#M4363</guid>
      <dc:creator>larryansell</dc:creator>
      <dc:date>2018-11-15T21:12:58Z</dc:date>
    </item>
    <item>
      <title>Re: Problems doing updateBinary</title>
      <link>https://community.nxp.com/t5/NFC/Problems-doing-updateBinary/m-p/828142#M4364</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Can you please explain it a bit? I mean&amp;nbsp;what's exactly you are facing and all such stuffs, so that I can guide you. Thanks and Regards, Harry Bellen.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 17 Nov 2018 10:25:26 GMT</pubDate>
      <guid>https://community.nxp.com/t5/NFC/Problems-doing-updateBinary/m-p/828142#M4364</guid>
      <dc:creator>harrybellen11</dc:creator>
      <dc:date>2018-11-17T10:25:26Z</dc:date>
    </item>
    <item>
      <title>Re: Problems doing updateBinary</title>
      <link>https://community.nxp.com/t5/NFC/Problems-doing-updateBinary/m-p/828143#M4365</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Harry,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks for your email!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;It was explained to me that the f2 2  was in truth a WTX.  I had been looking at the ST25TA64k doc(where the table was labelled S-Block detailed format), but in the corresponding table in the ST25TA2k doc, the table is labelled PCB field of the S-Block format) so that makes sense.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Now (with a different card) I am writing an 8 byte message successfully at offset 4 but when I try a longer 16 byte message I get no ACK/NAK.   I’m suspicious that I need to zero the NDEF but when I tried overwriting the two bytes at offset 0, I once again got the no ACK/NAK.  But when I changed my offset back to 4 (where I had been writing the 8 bytes successfully) I was once again able to write the 8 bytes.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I would be grateful for any guidance!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks again,&lt;/P&gt;&lt;P&gt;Larry&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 20 Nov 2018 20:52:35 GMT</pubDate>
      <guid>https://community.nxp.com/t5/NFC/Problems-doing-updateBinary/m-p/828143#M4365</guid>
      <dc:creator>larryansell</dc:creator>
      <dc:date>2018-11-20T20:52:35Z</dc:date>
    </item>
  </channel>
</rss>

