<?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: PN7160 devkit power(?) issue in Other NXP Products</title>
    <link>https://community.nxp.com/t5/Other-NXP-Products/PN7160-devkit-power-issue/m-p/1978007#M25991</link>
    <description>Disabling the TXLDO check indeed resolved the issue. Thanks alot!</description>
    <pubDate>Mon, 21 Oct 2024 08:54:16 GMT</pubDate>
    <dc:creator>kowalski_analysis</dc:creator>
    <dc:date>2024-10-21T08:54:16Z</dc:date>
    <item>
      <title>PN7160 devkit power(?) issue</title>
      <link>https://community.nxp.com/t5/Other-NXP-Products/PN7160-devkit-power-issue/m-p/1977168#M25973</link>
      <description>&lt;P&gt;I'm working with a PN7160 devkit, the &lt;STRONG&gt;OM27160A1HN&lt;/STRONG&gt; (I2C version), connected to a Karo QS93 which features an i.mx93 processor.&lt;/P&gt;&lt;P&gt;The issue I'm encountering has to do with the two voltage inputs of the devkit (screenshot from the devkit user manual):&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="kowalski_analysis_0-1729258832492.png" style="width: 400px;"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/305549i275F263D317459B7/image-size/medium?v=v2&amp;amp;px=400" role="button" title="kowalski_analysis_0-1729258832492.png" alt="kowalski_analysis_0-1729258832492.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;It can be seen that both &lt;STRONG&gt;VDD(PAD) &lt;/STRONG&gt;and &lt;STRONG&gt;VDD(UP)/VBAT&lt;/STRONG&gt; are supposed to work with a 3.3V input. But the issue I'm running into, is that the devkit can't detect a tag, when using this 3.3V input voltage. &lt;STRONG&gt;ONLY &lt;/STRONG&gt;when providing &lt;STRONG&gt;VDD(UP)/VBAT &lt;/STRONG&gt;with &lt;STRONG&gt;5V&lt;/STRONG&gt; from the Karo QS93, the devkit will actually detect the tag and can successfully read its data. When providing this pin with &lt;STRONG&gt;3.3V &lt;/STRONG&gt;the tag CAN NOT be detected.&lt;/P&gt;&lt;P&gt;Regarding the software: I use the &lt;STRONG&gt;libnfc-nci&lt;/STRONG&gt; library and the provided &lt;STRONG&gt;nfcDemoApp&lt;/STRONG&gt; to verify the devkit. Link to the library:&lt;/P&gt;&lt;P&gt;&lt;A href="https://github.com/NXPNFCLinux/linux_libnfc-nci" target="_blank"&gt;https://github.com/NXPNFCLinux/linux_libnfc-nci&lt;/A&gt;&lt;/P&gt;&lt;P&gt;I run the demoApp with the 'poll' argument, and the tag is only detected and read out successfully, when using &lt;STRONG&gt;5v &lt;/STRONG&gt;for &lt;STRONG&gt;VDD(UP)/VBAT&lt;/STRONG&gt;. With 3.3V, nothing happens, whatever I try. The demoAPP is just stuck on "waiting for tag" in that case.&lt;/P&gt;&lt;P&gt;I've read through all the related documentation and have not been able to find any remarks that address this issue. So for now I'm a bit stuck on this, any help would be greatly appreciated!&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 18 Oct 2024 14:00:32 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Other-NXP-Products/PN7160-devkit-power-issue/m-p/1977168#M25973</guid>
      <dc:creator>kowalski_analysis</dc:creator>
      <dc:date>2024-10-18T14:00:32Z</dc:date>
    </item>
    <item>
      <title>Re: PN7160 devkit power(?) issue</title>
      <link>https://community.nxp.com/t5/Other-NXP-Products/PN7160-devkit-power-issue/m-p/1977730#M25984</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/242206"&gt;@kowalski_analysis&lt;/a&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;There is a very similar issue described in AN13892.&amp;nbsp; &amp;nbsp;It could happen that PN7160 can not generate an RF field due to bad power supply on VUP/TVDD or a bad power configuration.&amp;nbsp; Typically happens once 3.3V as the VUP has been used.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;A href="https://www.nxp.com/docs/en/application-note/AN13892.pdf" target="_blank" rel="nofollow noopener noreferrer"&gt;https://www.nxp.com/docs/en/application-note/AN13892.pdf&lt;/A&gt;&amp;nbsp;-&amp;gt;&amp;nbsp;&lt;STRONG&gt;9 TXLDO check&amp;nbsp;&amp;nbsp;&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;Can you try to disable the TXLDO check?&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&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, 21 Oct 2024 04:35:46 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Other-NXP-Products/PN7160-devkit-power-issue/m-p/1977730#M25984</guid>
      <dc:creator>danielchen</dc:creator>
      <dc:date>2024-10-21T04:35:46Z</dc:date>
    </item>
    <item>
      <title>Re: PN7160 devkit power(?) issue</title>
      <link>https://community.nxp.com/t5/Other-NXP-Products/PN7160-devkit-power-issue/m-p/1978007#M25991</link>
      <description>Disabling the TXLDO check indeed resolved the issue. Thanks alot!</description>
      <pubDate>Mon, 21 Oct 2024 08:54:16 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Other-NXP-Products/PN7160-devkit-power-issue/m-p/1978007#M25991</guid>
      <dc:creator>kowalski_analysis</dc:creator>
      <dc:date>2024-10-21T08:54:16Z</dc:date>
    </item>
  </channel>
</rss>

