<?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: [SOLVED] PN7120: ICODE SLIX2 Read Single Block doesn't respond in NFC</title>
    <link>https://community.nxp.com/t5/NFC/SOLVED-PN7120-ICODE-SLIX2-Read-Single-Block-doesn-t-respond/m-p/775539#M3733</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Steve,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I am struggling with the same issue.&lt;/P&gt;&lt;P&gt;When sending a read single block( '00 00 03 02 20 05') or mutiple block read in no addressed (and also in addressed mode) without sending any CRC, I keep receiving the '60 06 03 01 00 01' as response.&amp;nbsp;&lt;/P&gt;&lt;P&gt;Would&amp;nbsp;somebody eventually have a log of the i2c exchanges.&lt;/P&gt;&lt;P&gt;It would surely help.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Marc&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Sun, 20 Oct 2019 07:21:19 GMT</pubDate>
    <dc:creator>marcvandegaar</dc:creator>
    <dc:date>2019-10-20T07:21:19Z</dc:date>
    <item>
      <title>[SOLVED] PN7120: ICODE SLIX2 Read Single Block doesn't respond</title>
      <link>https://community.nxp.com/t5/NFC/SOLVED-PN7120-ICODE-SLIX2-Read-Single-Block-doesn-t-respond/m-p/775537#M3731</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I'm trying to read/write ICODE SLIX2 ICs (SL2S2602) using a PN7120, which is connected to a PIC32MX microcontroller without an RTOS. Due to the timing constraints of the I2C bus (can only read/write within a very small window), I need to write my own code to communicate with the PN7120. I get to the point where&amp;nbsp;RF_INTF_ACTIVATED_NTF is returned (including UID). I then send a "single block read" command, which gets&amp;nbsp;a&amp;nbsp;CORE_CONN_CREDITS_NTF response, but never gets a response to the single block read. At first I thought maybe the CRC in the single block read command was incorrect, but I&amp;nbsp;verified my code generates the exact same CRC as the example at the end of the ISO/IEC FCD 15693-3 document.&lt;/P&gt;&lt;P&gt;Here's the complete transaction log I exported from an I2C protocol analyzer (TotalPhase Beagle).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: 'courier new', courier, monospace;"&gt;&lt;SPAN&gt;CORE_RESET_CMD&lt;/SPAN&gt;: 20 00 01 01&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;&amp;nbsp;&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN style="font-family: 'courier new', courier, monospace;"&gt;&lt;SPAN&gt;CORE_RESET_RSP&lt;/SPAN&gt;: 40 00 03 00 10 01*&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;&lt;SPAN style="font-family: 'courier new', courier, monospace;"&gt;CORE_INIT_CMD: 20 01 00&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN style="font-family: 'courier new', courier, monospace;"&gt;CORE_INIT_RSP: 40 01 17 00 03 0E 03 00 06 00 01 02 03 81 82 02 C8 00 FF 02 00 04 05 08 02 02*&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;&lt;SPAN style="font-family: 'courier new', courier, monospace;"&gt;RF_DISCOVER_MAP_CMD: 21 00 16 07 04 02 02 05 03 03 01 01 01 02 01 01 03 01 01 04 01 02 80 01 80&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN style="font-family: 'courier new', courier, monospace;"&gt;RF_DISCOVER_MAP_RSP: 41 00 01 00*&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;&lt;SPAN style="font-family: 'courier new', courier, monospace;"&gt;RF_DISCOVER_CMD: 21 03 15 0A 00 01 02 01 01 01 06 01 05 01 80 01 81 01 82 01 83 01 85 01&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN style="font-family: 'courier new', courier, monospace;"&gt;RF_DISCOVER_RSP: 41 03 01 00*&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN style="font-family: 'courier new', courier, monospace;"&gt;RF_INTF_ACTIVATED_NTF: 61 05 15 01 01 06 06 FF 01 0A 00 00 8C 70 D6 00 08 01 04 E0 06 80 80 00*&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;&lt;SPAN style="font-family: 'courier new', courier, monospace;"&gt;&lt;SPAN&gt;read single block&lt;/SPAN&gt;: 00 00 0D 20 20 8C 70 D6 00 08 01 04 E0 00 16 2D&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN style="font-family: 'courier new', courier, monospace;"&gt;CORE_CONN_CREDITS_NTF: 60 06 03 01 00 01*&lt;/SPAN&gt;&lt;BR /&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;It never gives a response to the read single block as all following reads on the I2C bus get NAK'ed. Am I missing something? I can't find any complete examples anywhere showing the I2C traffic while attempting to "read single block" on an&amp;nbsp;ICODE SLIX2.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 31 Jan 2018 21:38:59 GMT</pubDate>
      <guid>https://community.nxp.com/t5/NFC/SOLVED-PN7120-ICODE-SLIX2-Read-Single-Block-doesn-t-respond/m-p/775537#M3731</guid>
      <dc:creator>steverap</dc:creator>
      <dc:date>2018-01-31T21:38:59Z</dc:date>
    </item>
    <item>
      <title>Re: PN7120: ICODE SLIX2 Read Single Block doesn't respond</title>
      <link>https://community.nxp.com/t5/NFC/SOLVED-PN7120-ICODE-SLIX2-Read-Single-Block-doesn-t-respond/m-p/775538#M3732</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I finally got this to work. I could not find one document or detailed example that explained the process necessary&amp;nbsp;to read a block of memory from an ICODE SLIX2 using a PN7120.&amp;nbsp;I&amp;nbsp;had to read through&amp;nbsp;five different documents to try to figure this out.&lt;/P&gt;&lt;UL style="padding: 0px 0px 0px 30px;"&gt;&lt;LI style="margin: 0.2em 0px;"&gt;&lt;SPAN&gt;NFC Controller Interface (NCI) Technical Specification&lt;/SPAN&gt;&lt;/LI&gt;&lt;LI style="margin: 0.2em 0px;"&gt;&lt;SPAN&gt;PN7120 datasheet&lt;/SPAN&gt;&lt;/LI&gt;&lt;LI style="margin: 0.2em 0px;"&gt;&lt;SPAN&gt;PN7120 user manual&lt;/SPAN&gt;&lt;/LI&gt;&lt;LI style="margin: 0.2em 0px;"&gt;ICODE SLIX2 datasheet&lt;/LI&gt;&lt;LI style="margin: 0.2em 0px;"&gt;ISO 15693 spec&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;I could communicate with the PN7120 just fine, but was unable to read any memory on the ICODE SLIX2. The "&lt;SPAN&gt;Read Single Block&lt;/SPAN&gt;" command never got a response.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I had asked NXP tech support to provide me a I2C bus scan of I2C traffic to the PN7120 while executing a "&lt;SPAN&gt;Read Single Block&lt;/SPAN&gt;". They said they&amp;nbsp;were unable to do that. So we purchased a OM5577 and an UDOO Neo board, loaded Android, and ran the NXP Android app to read an ICODE SLIX2 while monitoring the I2C bus with a TotalPhase Beagle I2C analyzer. Turns out I was doing everything correct, except for one thing:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;The data packets sent over the I2C bus do NOT&amp;nbsp;include CRC!&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The documentation is somewhat misleading. The NCI Tech spec has little information on data packets. It does talk about CRC on data packets, but since I wasn't familiar with their terminology, it wasn't clear to me that the CRC is only used at the RF level. Since the ICODE SLIX2 uses ISO 15693, I looked at that document to see how to issue a "Read Single Block". For each command, that document shows CRC at the end of each command and response. So I (wrongly) assumed it was needed, and added CRC to all my commands. And those data packet commands never got a response, even an error response.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;And I doubt the tech support people have ever wrote code to communicate with this chip. Otherwise,&amp;nbsp;when I asked them for a CRC example&amp;nbsp;(I thought maybe my CRC generation wasn't correct), they should have replied, "You don't need CRC as it is only used at the RF level."&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I'm hoping this post will keep others from making the same mistake I did....&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 01 Mar 2018 19:44:08 GMT</pubDate>
      <guid>https://community.nxp.com/t5/NFC/SOLVED-PN7120-ICODE-SLIX2-Read-Single-Block-doesn-t-respond/m-p/775538#M3732</guid>
      <dc:creator>steverap</dc:creator>
      <dc:date>2018-03-01T19:44:08Z</dc:date>
    </item>
    <item>
      <title>Re: [SOLVED] PN7120: ICODE SLIX2 Read Single Block doesn't respond</title>
      <link>https://community.nxp.com/t5/NFC/SOLVED-PN7120-ICODE-SLIX2-Read-Single-Block-doesn-t-respond/m-p/775539#M3733</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Steve,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I am struggling with the same issue.&lt;/P&gt;&lt;P&gt;When sending a read single block( '00 00 03 02 20 05') or mutiple block read in no addressed (and also in addressed mode) without sending any CRC, I keep receiving the '60 06 03 01 00 01' as response.&amp;nbsp;&lt;/P&gt;&lt;P&gt;Would&amp;nbsp;somebody eventually have a log of the i2c exchanges.&lt;/P&gt;&lt;P&gt;It would surely help.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Marc&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 20 Oct 2019 07:21:19 GMT</pubDate>
      <guid>https://community.nxp.com/t5/NFC/SOLVED-PN7120-ICODE-SLIX2-Read-Single-Block-doesn-t-respond/m-p/775539#M3733</guid>
      <dc:creator>marcvandegaar</dc:creator>
      <dc:date>2019-10-20T07:21:19Z</dc:date>
    </item>
  </channel>
</rss>

