<?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: [PN7150] Why is the CORE_INIT_RSP payload 25 bytes long? in NFC</title>
    <link>https://community.nxp.com/t5/NFC/PN7150-Why-is-the-CORE-INIT-RSP-payload-25-bytes-long/m-p/1525269#M9686</link>
    <description>&lt;P&gt;It is possible, and it is not something critical, since in the example that I'm taking as a reference, it is only verified that the first byte is equal to 0x40 and the second is equal to 0x01, with these two values it is assumed that everything is fine and continue to the next step.&lt;/P&gt;&lt;P&gt;Thank you very much for answering.&lt;/P&gt;</description>
    <pubDate>Tue, 20 Sep 2022 20:57:36 GMT</pubDate>
    <dc:creator>dominusdrr</dc:creator>
    <dc:date>2022-09-20T20:57:36Z</dc:date>
    <item>
      <title>[PN7150] Why is the CORE_INIT_RSP payload 25 bytes long?</title>
      <link>https://community.nxp.com/t5/NFC/PN7150-Why-is-the-CORE-INIT-RSP-payload-25-bytes-long/m-p/1515820#M9642</link>
      <description>&lt;P&gt;Hi.&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;I'm writing my own routines to manage the PN7150.&lt;/P&gt;&lt;P&gt;I have successfully managed to send the CORE_RESET_CMD command and get its correct response.&lt;/P&gt;&lt;P&gt;The next step has been to send the CORE_INIT_CMD command:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="dominusdrr_0-1662066702699.png" style="width: 400px;"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/192197i25FF45D281D89CC8/image-size/medium?v=v2&amp;amp;px=400" role="button" title="dominusdrr_0-1662066702699.png" alt="dominusdrr_0-1662066702699.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;And when reading the response, the third byte (not counting the initial I2C control byte) which is the payload length is equal to 25 (0x19).&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="dominusdrr_1-1662066903814.png" style="width: 400px;"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/192202iC1742A0C83BB6E68/image-size/medium?v=v2&amp;amp;px=400" role="button" title="dominusdrr_1-1662066903814.png" alt="dominusdrr_1-1662066903814.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;But according to the NCI specification it would only be 18 bytes:&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="dominusdrr_2-1662067358665.png" style="width: 400px;"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/192205i188E58A1193606C2/image-size/medium?v=v2&amp;amp;px=400" role="button" title="dominusdrr_2-1662067358665.png" alt="dominusdrr_2-1662067358665.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Is it an error or am I confused?&lt;BR /&gt;&lt;BR /&gt;Regards&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 01 Sep 2022 21:25:05 GMT</pubDate>
      <guid>https://community.nxp.com/t5/NFC/PN7150-Why-is-the-CORE-INIT-RSP-payload-25-bytes-long/m-p/1515820#M9642</guid>
      <dc:creator>dominusdrr</dc:creator>
      <dc:date>2022-09-01T21:25:05Z</dc:date>
    </item>
    <item>
      <title>Re: [PN7150] Why is the CORE_INIT_RSP payload 25 bytes long?</title>
      <link>https://community.nxp.com/t5/NFC/PN7150-Why-is-the-CORE-INIT-RSP-payload-25-bytes-long/m-p/1523945#M9678</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/156216"&gt;@dominusdrr&lt;/a&gt;&amp;nbsp;:&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;There is a field called &lt;STRONG&gt;number of supported interfaces&lt;/STRONG&gt;.&amp;nbsp; we are giving number of interfaces,&amp;nbsp; the length is depends on N.&amp;nbsp; Maybe that is the reason why there is bigger amount of data.&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="danielchen_0-1663557529385.png" style="width: 400px;"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/194037i1F8E0E1807520E85/image-size/medium?v=v2&amp;amp;px=400" role="button" title="danielchen_0-1663557529385.png" alt="danielchen_0-1663557529385.png" /&gt;&lt;/span&gt;&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>Mon, 19 Sep 2022 03:21:02 GMT</pubDate>
      <guid>https://community.nxp.com/t5/NFC/PN7150-Why-is-the-CORE-INIT-RSP-payload-25-bytes-long/m-p/1523945#M9678</guid>
      <dc:creator>danielchen</dc:creator>
      <dc:date>2022-09-19T03:21:02Z</dc:date>
    </item>
    <item>
      <title>Re: [PN7150] Why is the CORE_INIT_RSP payload 25 bytes long?</title>
      <link>https://community.nxp.com/t5/NFC/PN7150-Why-is-the-CORE-INIT-RSP-payload-25-bytes-long/m-p/1525269#M9686</link>
      <description>&lt;P&gt;It is possible, and it is not something critical, since in the example that I'm taking as a reference, it is only verified that the first byte is equal to 0x40 and the second is equal to 0x01, with these two values it is assumed that everything is fine and continue to the next step.&lt;/P&gt;&lt;P&gt;Thank you very much for answering.&lt;/P&gt;</description>
      <pubDate>Tue, 20 Sep 2022 20:57:36 GMT</pubDate>
      <guid>https://community.nxp.com/t5/NFC/PN7150-Why-is-the-CORE-INIT-RSP-payload-25-bytes-long/m-p/1525269#M9686</guid>
      <dc:creator>dominusdrr</dc:creator>
      <dc:date>2022-09-20T20:57:36Z</dc:date>
    </item>
  </channel>
</rss>

