<?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 pn5180 timeout interrupt after receiving data in Wireless MCU</title>
    <link>https://community.nxp.com/t5/Wireless-MCU/pn5180-timeout-interrupt-after-receiving-data/m-p/1522061#M13693</link>
    <description>&lt;P&gt;when we use this device and we receive data, we receive and handle the interrupt for the received data. then we get a timeout interrupt as if the data didn't transfer. can someone explain this from NXP.&amp;nbsp;&lt;/P&gt;&lt;P&gt;is this normal behaviour or does this signify a bigger issue.&amp;nbsp;&lt;/P&gt;&lt;P&gt;does the timeout interrupt mean that that data is suspect??&lt;/P&gt;&lt;P&gt;also what data chunks can i reasonably expect to transfer using this process ?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;also do we need to reset between every transfer, i assume not.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;thanks in advance Sean &lt;LI-EMOJI id="lia_slightly-smiling-face" title=":slightly_smiling_face:"&gt;&lt;/LI-EMOJI&gt;&lt;/P&gt;&lt;P&gt;64&lt;BR /&gt;T = 3&lt;BR /&gt;NFC Driver: configue TX CRC state&lt;BR /&gt;T = 64&lt;BR /&gt;T = 3&lt;BR /&gt;NFC Driver: configue RX CRC state&lt;BR /&gt;T = 64&lt;BR /&gt;T = 3&lt;BR /&gt;NFC Driver: configue Complete state&lt;BR /&gt;NFC Driver: Trans Write state&lt;BR /&gt;T = 64&lt;BR /&gt;T = 2&lt;BR /&gt;T = 1&lt;BR /&gt;NFC Driver: comms comp Trans state&lt;BR /&gt;NFC Driver: Trans Send state&lt;BR /&gt;T = 4&lt;BR /&gt;T = 2&lt;BR /&gt;T = 1&lt;BR /&gt;T = 3&lt;BR /&gt;T = 2&lt;BR /&gt;T = 1&lt;BR /&gt;NFC Driver: IRQ callback flags = 1&lt;BR /&gt;NFC Driver: Trans Read status state&lt;BR /&gt;T = 64&lt;BR /&gt;T = 3&lt;BR /&gt;T = 3&lt;BR /&gt;NFC Driver: comms comp Trans state&lt;BR /&gt;NFC Driver: Read Rx error return = 11&lt;BR /&gt;NFC Driver: Trans Read data state&lt;BR /&gt;T = 64&lt;BR /&gt;T = 3&lt;BR /&gt;T = 3&lt;BR /&gt;NFC Driver: comms comp Trans state&lt;BR /&gt;NFC Driver: Trans Return data state&lt;BR /&gt;NFC 1231&lt;/P&gt;&lt;P&gt;T = 64&lt;BR /&gt;T = 2&lt;BR /&gt;T = 1&lt;BR /&gt;T = 4&lt;BR /&gt;T = 2&lt;BR /&gt;T = 1&lt;BR /&gt;T = 3&lt;BR /&gt;T = 3&lt;BR /&gt;NFC Driver: IRQ callback flags = 4&lt;BR /&gt;NFC Driver: IRQ Reset state&lt;BR /&gt;NFC Driver: configue IRQ state&lt;BR /&gt;T = 64&lt;BR /&gt;T = 3&lt;BR /&gt;NFC Driver: configue Load Protocol state&lt;BR /&gt;T = 64&lt;BR /&gt;T = 2&lt;BR /&gt;T = 1&lt;BR /&gt;NFC Driver: configue Timer state&lt;BR /&gt;T = 64&lt;BR /&gt;T = 3&lt;BR /&gt;NFC Driver: configue TX CRC state&lt;BR /&gt;T = 64&lt;BR /&gt;T = 3&lt;BR /&gt;NFC Driver: configue RX CRC state&lt;BR /&gt;T = 64&lt;BR /&gt;T = 3&lt;BR /&gt;NFC Driver: configue Complete state&lt;BR /&gt;NFC Driver: Trans Write state&lt;BR /&gt;T = 64&lt;BR /&gt;T = 2&lt;BR /&gt;T = 1&lt;BR /&gt;NFC Driver: comms comp Trans state&lt;BR /&gt;NFC Driver: Trans Send state&lt;BR /&gt;T = 4&lt;BR /&gt;T = 2&lt;BR /&gt;T = 1&lt;BR /&gt;T = 3&lt;BR /&gt;T = 3&lt;BR /&gt;NFC Driver: IRQ callback flags = 1&lt;BR /&gt;NFC Driver: Trans Read status state&lt;BR /&gt;T = 64&lt;BR /&gt;T = 3&lt;BR /&gt;T = 3&lt;BR /&gt;NFC Driver: comms comp Trans state&lt;BR /&gt;NFC Driver: Read Rx error return = 11&lt;BR /&gt;NFC Driver: Trans Read data state&lt;BR /&gt;T = 64&lt;BR /&gt;T = 3&lt;BR /&gt;T = 3&lt;BR /&gt;NFC Driver: comms comp Trans state&lt;BR /&gt;NFC Driver: Trans Return data state&lt;BR /&gt;NFC 1239&lt;/P&gt;&lt;P&gt;T = 4&lt;BR /&gt;T = 3&lt;BR /&gt;T = 3&lt;BR /&gt;T = 3&lt;BR /&gt;NFC Driver: IRQ callback flags = 2048&lt;BR /&gt;NFC Driver: timeoNFC Driver: Trans Timeout Timeout sta state&lt;BR /&gt;T = 4&lt;BR /&gt;T = 3&lt;BR /&gt;T = 3&lt;BR /&gt;T = 3&lt;BR /&gt;NFC Driver: IRQ callback flags = 2048&lt;BR /&gt;NFC Driver: timeoNFC Driver: Trans Timeout Timeout sta state&lt;BR /&gt;T = 64&lt;BR /&gt;T = 4&lt;/P&gt;</description>
    <pubDate>Wed, 14 Sep 2022 15:14:05 GMT</pubDate>
    <dc:creator>Splatspeed</dc:creator>
    <dc:date>2022-09-14T15:14:05Z</dc:date>
    <item>
      <title>pn5180 timeout interrupt after receiving data</title>
      <link>https://community.nxp.com/t5/Wireless-MCU/pn5180-timeout-interrupt-after-receiving-data/m-p/1522061#M13693</link>
      <description>&lt;P&gt;when we use this device and we receive data, we receive and handle the interrupt for the received data. then we get a timeout interrupt as if the data didn't transfer. can someone explain this from NXP.&amp;nbsp;&lt;/P&gt;&lt;P&gt;is this normal behaviour or does this signify a bigger issue.&amp;nbsp;&lt;/P&gt;&lt;P&gt;does the timeout interrupt mean that that data is suspect??&lt;/P&gt;&lt;P&gt;also what data chunks can i reasonably expect to transfer using this process ?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;also do we need to reset between every transfer, i assume not.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;thanks in advance Sean &lt;LI-EMOJI id="lia_slightly-smiling-face" title=":slightly_smiling_face:"&gt;&lt;/LI-EMOJI&gt;&lt;/P&gt;&lt;P&gt;64&lt;BR /&gt;T = 3&lt;BR /&gt;NFC Driver: configue TX CRC state&lt;BR /&gt;T = 64&lt;BR /&gt;T = 3&lt;BR /&gt;NFC Driver: configue RX CRC state&lt;BR /&gt;T = 64&lt;BR /&gt;T = 3&lt;BR /&gt;NFC Driver: configue Complete state&lt;BR /&gt;NFC Driver: Trans Write state&lt;BR /&gt;T = 64&lt;BR /&gt;T = 2&lt;BR /&gt;T = 1&lt;BR /&gt;NFC Driver: comms comp Trans state&lt;BR /&gt;NFC Driver: Trans Send state&lt;BR /&gt;T = 4&lt;BR /&gt;T = 2&lt;BR /&gt;T = 1&lt;BR /&gt;T = 3&lt;BR /&gt;T = 2&lt;BR /&gt;T = 1&lt;BR /&gt;NFC Driver: IRQ callback flags = 1&lt;BR /&gt;NFC Driver: Trans Read status state&lt;BR /&gt;T = 64&lt;BR /&gt;T = 3&lt;BR /&gt;T = 3&lt;BR /&gt;NFC Driver: comms comp Trans state&lt;BR /&gt;NFC Driver: Read Rx error return = 11&lt;BR /&gt;NFC Driver: Trans Read data state&lt;BR /&gt;T = 64&lt;BR /&gt;T = 3&lt;BR /&gt;T = 3&lt;BR /&gt;NFC Driver: comms comp Trans state&lt;BR /&gt;NFC Driver: Trans Return data state&lt;BR /&gt;NFC 1231&lt;/P&gt;&lt;P&gt;T = 64&lt;BR /&gt;T = 2&lt;BR /&gt;T = 1&lt;BR /&gt;T = 4&lt;BR /&gt;T = 2&lt;BR /&gt;T = 1&lt;BR /&gt;T = 3&lt;BR /&gt;T = 3&lt;BR /&gt;NFC Driver: IRQ callback flags = 4&lt;BR /&gt;NFC Driver: IRQ Reset state&lt;BR /&gt;NFC Driver: configue IRQ state&lt;BR /&gt;T = 64&lt;BR /&gt;T = 3&lt;BR /&gt;NFC Driver: configue Load Protocol state&lt;BR /&gt;T = 64&lt;BR /&gt;T = 2&lt;BR /&gt;T = 1&lt;BR /&gt;NFC Driver: configue Timer state&lt;BR /&gt;T = 64&lt;BR /&gt;T = 3&lt;BR /&gt;NFC Driver: configue TX CRC state&lt;BR /&gt;T = 64&lt;BR /&gt;T = 3&lt;BR /&gt;NFC Driver: configue RX CRC state&lt;BR /&gt;T = 64&lt;BR /&gt;T = 3&lt;BR /&gt;NFC Driver: configue Complete state&lt;BR /&gt;NFC Driver: Trans Write state&lt;BR /&gt;T = 64&lt;BR /&gt;T = 2&lt;BR /&gt;T = 1&lt;BR /&gt;NFC Driver: comms comp Trans state&lt;BR /&gt;NFC Driver: Trans Send state&lt;BR /&gt;T = 4&lt;BR /&gt;T = 2&lt;BR /&gt;T = 1&lt;BR /&gt;T = 3&lt;BR /&gt;T = 3&lt;BR /&gt;NFC Driver: IRQ callback flags = 1&lt;BR /&gt;NFC Driver: Trans Read status state&lt;BR /&gt;T = 64&lt;BR /&gt;T = 3&lt;BR /&gt;T = 3&lt;BR /&gt;NFC Driver: comms comp Trans state&lt;BR /&gt;NFC Driver: Read Rx error return = 11&lt;BR /&gt;NFC Driver: Trans Read data state&lt;BR /&gt;T = 64&lt;BR /&gt;T = 3&lt;BR /&gt;T = 3&lt;BR /&gt;NFC Driver: comms comp Trans state&lt;BR /&gt;NFC Driver: Trans Return data state&lt;BR /&gt;NFC 1239&lt;/P&gt;&lt;P&gt;T = 4&lt;BR /&gt;T = 3&lt;BR /&gt;T = 3&lt;BR /&gt;T = 3&lt;BR /&gt;NFC Driver: IRQ callback flags = 2048&lt;BR /&gt;NFC Driver: timeoNFC Driver: Trans Timeout Timeout sta state&lt;BR /&gt;T = 4&lt;BR /&gt;T = 3&lt;BR /&gt;T = 3&lt;BR /&gt;T = 3&lt;BR /&gt;NFC Driver: IRQ callback flags = 2048&lt;BR /&gt;NFC Driver: timeoNFC Driver: Trans Timeout Timeout sta state&lt;BR /&gt;T = 64&lt;BR /&gt;T = 4&lt;/P&gt;</description>
      <pubDate>Wed, 14 Sep 2022 15:14:05 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Wireless-MCU/pn5180-timeout-interrupt-after-receiving-data/m-p/1522061#M13693</guid>
      <dc:creator>Splatspeed</dc:creator>
      <dc:date>2022-09-14T15:14:05Z</dc:date>
    </item>
    <item>
      <title>Re: pn5180 timeout interrupt after receiving data</title>
      <link>https://community.nxp.com/t5/Wireless-MCU/pn5180-timeout-interrupt-after-receiving-data/m-p/1522649#M13701</link>
      <description>&lt;P&gt;Hello&amp;nbsp;&lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/206177"&gt;@Splatspeed&lt;/a&gt;&amp;nbsp;,&lt;/P&gt;
&lt;P&gt;For PN5180, the Timers are used to measure certain intervals between certain configurable events of the receiver, transmitter and other RF-events.&amp;nbsp;You can configure it according to your application. If you don't want to use it, it can be disabled or overload its counter to prevent overflowing, and then generating an timeout interrupt event. For more details, you can refer to the datasheet.&lt;/P&gt;
&lt;P&gt;Hope my reply can help you.&lt;/P&gt;
&lt;P&gt;Best Regards,&lt;/P&gt;
&lt;P&gt;Thanks,&lt;/P&gt;
&lt;P&gt;kelly&lt;/P&gt;</description>
      <pubDate>Thu, 15 Sep 2022 07:17:01 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Wireless-MCU/pn5180-timeout-interrupt-after-receiving-data/m-p/1522649#M13701</guid>
      <dc:creator>KaiLi</dc:creator>
      <dc:date>2022-09-15T07:17:01Z</dc:date>
    </item>
  </channel>
</rss>

