<?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 timeout during data transfer in Other NXP Products</title>
    <link>https://community.nxp.com/t5/Other-NXP-Products/PN7150-timeout-during-data-transfer/m-p/1885941#M23097</link>
    <description>&lt;P&gt;Thanks,&amp;nbsp;&lt;SPAN&gt;Eduardo.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;From UM10936, PN7150 will keep in poll active state even it sending a CORE_INTERFACE_ERROR_NTF. I will wait here for a while and try to recieve further data from tag. Not sure if it is working, but let me try it first. &lt;LI-EMOJI id="lia_slightly-smiling-face" title=":slightly_smiling_face:"&gt;&lt;/LI-EMOJI&gt;&lt;/SPAN&gt;&lt;/P&gt;</description>
    <pubDate>Wed, 12 Jun 2024 08:06:21 GMT</pubDate>
    <dc:creator>jiamin_fan</dc:creator>
    <dc:date>2024-06-12T08:06:21Z</dc:date>
    <item>
      <title>PN7150 timeout during data transfer</title>
      <link>https://community.nxp.com/t5/Other-NXP-Products/PN7150-timeout-during-data-transfer/m-p/1881060#M22964</link>
      <description>&lt;P&gt;Hello NXP community. I am using PN7150 on a NFC reader to talk with nRF52 NFC device.&lt;/P&gt;&lt;P&gt;now PN7150 has connected with nRF52. But when nRF52 receiving a custom command, it will go into an interrput which cause NFC peripheral stopped for 10~300ms&amp;nbsp;(maybe longer).&lt;/P&gt;&lt;P&gt;According to the state machine drawing in UM10936, once PN7150 discover a tag, it goes into RFST_POLL_ACTIVE state. When PN7150 has detected a timeout or an unrecoverable protocol error during the RF communication with the PICC, it will autonomously come back to RFST_DISCOVERY state.&lt;/P&gt;&lt;P&gt;So I think PN7150 must have a periodical device present check or timeout check in RFST_POLL_ACTIVE state.&lt;/P&gt;&lt;P&gt;Is there anyway to change the timeout setting or retry setting in PN7150 so that it will not come back to RFST_DISCOVERY even when the tag stop working for a while.&lt;/P&gt;</description>
      <pubDate>Wed, 05 Jun 2024 01:39:49 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Other-NXP-Products/PN7150-timeout-during-data-transfer/m-p/1881060#M22964</guid>
      <dc:creator>jiamin_fan</dc:creator>
      <dc:date>2024-06-05T01:39:49Z</dc:date>
    </item>
    <item>
      <title>Re: PN7150 timeout during data transfer</title>
      <link>https://community.nxp.com/t5/Other-NXP-Products/PN7150-timeout-during-data-transfer/m-p/1883044#M23005</link>
      <description>&lt;P&gt;Hello&amp;nbsp;&lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/234556"&gt;@jiamin_fan&lt;/a&gt;&lt;/P&gt;
&lt;P&gt;Hope you are doing well.&lt;/P&gt;
&lt;P&gt;Please, consider that &lt;A href="https://www.nxp.com/products/rfid-nfc/nfc-hf/nfc-readers/high-performance-nfc-controller-with-integrated-firmware-for-smart-devices:PN7150" target="_blank"&gt;PN7150&lt;/A&gt; is Not Recommended for New Designs; we recommend using&amp;nbsp;&lt;A href="https://www.nxp.com/products/rfid-nfc/nfc-hf/nfc-readers/nfc-plug-and-play-controller-with-integrated-firmware-and-nci-interface:PN7160" target="_blank"&gt;PN7160&lt;/A&gt; instead. Also, our support scope is limited to the usage of our recommended &lt;A href="https://www.nxp.com/design/design-center/development-boards-and-designs/nfc-reader-library-software-support-for-nfc-frontend-solutions:NFC-READER-LIBRARY" target="_blank"&gt;NFC Reader Library&lt;/A&gt; or specific &lt;A href="https://www.nxp.com/docs/en/application-note/AN11990.pdf" target="_blank"&gt;NXP-NCI MCUXpresso &lt;/A&gt;example and&amp;nbsp;supported MCUs from our portfolio.&lt;/P&gt;
&lt;P&gt;In case the RF link with the PICC is broken, the regular way to behave according to NCI is that the PN7150 will detect a timeout or an unrecoverable protocol error and send then a CORE_INTERFACE_ERROR_NTF with the appropriate status. It is then up to the DH to stop the RF Discovery with RF_DEACTIVATE_CMD(IDLE) and to restart the RF Discovery with RF_DISCOVER_CMD.&lt;/P&gt;
&lt;P&gt;As an alternative to comply with EMVCo requirements, the autonomous transition from RFST_POLL_ACTIVE to RFST_DISCOVERY can be triggered by the sending of the RF_DEACTIVATE_NTF(Discovery, Link Loss).&lt;/P&gt;
&lt;P&gt;You can find the possible states and conditions/events that trigger the transitions between states In &lt;A href="https://www.nxp.com/docs/en/user-guide/UM10936.pdf" target="_blank"&gt;UM10936&lt;/A&gt;, Section 9.1.&lt;/P&gt;
&lt;P&gt;Regards,&lt;BR /&gt;Eduardo.&lt;/P&gt;</description>
      <pubDate>Thu, 06 Jun 2024 20:54:31 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Other-NXP-Products/PN7150-timeout-during-data-transfer/m-p/1883044#M23005</guid>
      <dc:creator>EduardoZamora</dc:creator>
      <dc:date>2024-06-06T20:54:31Z</dc:date>
    </item>
    <item>
      <title>Re: PN7150 timeout during data transfer</title>
      <link>https://community.nxp.com/t5/Other-NXP-Products/PN7150-timeout-during-data-transfer/m-p/1885941#M23097</link>
      <description>&lt;P&gt;Thanks,&amp;nbsp;&lt;SPAN&gt;Eduardo.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;From UM10936, PN7150 will keep in poll active state even it sending a CORE_INTERFACE_ERROR_NTF. I will wait here for a while and try to recieve further data from tag. Not sure if it is working, but let me try it first. &lt;LI-EMOJI id="lia_slightly-smiling-face" title=":slightly_smiling_face:"&gt;&lt;/LI-EMOJI&gt;&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 12 Jun 2024 08:06:21 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Other-NXP-Products/PN7150-timeout-during-data-transfer/m-p/1885941#M23097</guid>
      <dc:creator>jiamin_fan</dc:creator>
      <dc:date>2024-06-12T08:06:21Z</dc:date>
    </item>
  </channel>
</rss>

