<?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>i.MX ProcessorsのトピックRe: issue in reading input signals</title>
    <link>https://community.nxp.com/t5/i-MX-Processors/issue-in-reading-input-signals/m-p/1710113#M211307</link>
    <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/215734"&gt;@rudi_cyber&lt;/a&gt;,&lt;/P&gt;
&lt;P&gt;Of course. Share your IOMUX configurations and I can take a look into them.&lt;/P&gt;
&lt;P&gt;BR,&lt;BR /&gt;Edwin.&lt;/P&gt;</description>
    <pubDate>Wed, 23 Aug 2023 20:28:05 GMT</pubDate>
    <dc:creator>EdwinHz</dc:creator>
    <dc:date>2023-08-23T20:28:05Z</dc:date>
    <item>
      <title>issue in reading input signals</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/issue-in-reading-input-signals/m-p/1704477#M210760</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;We are using the MIMXRT1051CVL5B in our design.&lt;/P&gt;&lt;P&gt;We are encountering an issue with the p4, N4 and D6 pins.&lt;/P&gt;&lt;P&gt;We have configured those signals as input, and the MCU read always the same value, regardless of the real HW input.&lt;/P&gt;&lt;P&gt;P4- always read '1'&lt;/P&gt;&lt;P&gt;N4- always read '0'&lt;/P&gt;&lt;P&gt;D6- always read '1'&lt;/P&gt;&lt;P&gt;Could you please assist us in understanding why this issue is occurring?&lt;/P&gt;</description>
      <pubDate>Mon, 14 Aug 2023 18:17:19 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/issue-in-reading-input-signals/m-p/1704477#M210760</guid>
      <dc:creator>sapirbuz</dc:creator>
      <dc:date>2023-08-14T18:17:19Z</dc:date>
    </item>
    <item>
      <title>Re: issue in reading input signals</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/issue-in-reading-input-signals/m-p/1705206#M210844</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/200625"&gt;@sapirbuz&lt;/a&gt;,&lt;/P&gt;
&lt;P&gt;Could you please provide more details about how you are configuring the pins, and how the hardware connection to these are being done? There is currently not enough information to clearly see if this is a hw or sw related issue.&lt;/P&gt;
&lt;P&gt;BR,&lt;BR /&gt;Edwin.&lt;/P&gt;</description>
      <pubDate>Tue, 15 Aug 2023 20:48:16 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/issue-in-reading-input-signals/m-p/1705206#M210844</guid>
      <dc:creator>EdwinHz</dc:creator>
      <dc:date>2023-08-15T20:48:16Z</dc:date>
    </item>
    <item>
      <title>Re: issue in reading input signals</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/issue-in-reading-input-signals/m-p/1705846#M210920</link>
      <description>&lt;P&gt;&lt;STRONG&gt;The pins are connected to TP, and we use an external power regulator to externally inject the required voltage through the TP (0V or 1.8V).&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;NVCC_SD=1.8V&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;It works the same way on our board and on the NXP EVKB (attached the schematics).&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;The configuration: Input, no pull up/down, no keeper &lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="sapirbuz_0-1692195729755.png" style="width: 400px;"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/236702iEC6DE238FCBC4EDE/image-size/medium?v=v2&amp;amp;px=400" role="button" title="sapirbuz_0-1692195729755.png" alt="sapirbuz_0-1692195729755.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 16 Aug 2023 14:23:53 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/issue-in-reading-input-signals/m-p/1705846#M210920</guid>
      <dc:creator>sapirbuz</dc:creator>
      <dc:date>2023-08-16T14:23:53Z</dc:date>
    </item>
    <item>
      <title>Re: issue in reading input signals</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/issue-in-reading-input-signals/m-p/1708549#M211178</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/200625"&gt;@sapirbuz&lt;/a&gt;,&lt;/P&gt;
&lt;P&gt;Did you previously supply these pins in a manner that could cause damage to the pads? From your hw and sw description, there isn't anything in particular that stands out as the issue.&lt;/P&gt;
&lt;P&gt;BR,&lt;BR /&gt;Edwin.&lt;/P&gt;</description>
      <pubDate>Mon, 21 Aug 2023 19:45:41 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/issue-in-reading-input-signals/m-p/1708549#M211178</guid>
      <dc:creator>EdwinHz</dc:creator>
      <dc:date>2023-08-21T19:45:41Z</dc:date>
    </item>
    <item>
      <title>Re: issue in reading input signals</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/issue-in-reading-input-signals/m-p/1708703#M211189</link>
      <description>&lt;P&gt;how about the iomux? could you please confirm the routing is correct.&lt;/P&gt;</description>
      <pubDate>Tue, 22 Aug 2023 03:46:30 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/issue-in-reading-input-signals/m-p/1708703#M211189</guid>
      <dc:creator>rudi_cyber</dc:creator>
      <dc:date>2023-08-22T03:46:30Z</dc:date>
    </item>
    <item>
      <title>Re: issue in reading input signals</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/issue-in-reading-input-signals/m-p/1710113#M211307</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/215734"&gt;@rudi_cyber&lt;/a&gt;,&lt;/P&gt;
&lt;P&gt;Of course. Share your IOMUX configurations and I can take a look into them.&lt;/P&gt;
&lt;P&gt;BR,&lt;BR /&gt;Edwin.&lt;/P&gt;</description>
      <pubDate>Wed, 23 Aug 2023 20:28:05 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/issue-in-reading-input-signals/m-p/1710113#M211307</guid>
      <dc:creator>EdwinHz</dc:creator>
      <dc:date>2023-08-23T20:28:05Z</dc:date>
    </item>
    <item>
      <title>Re: issue in reading input signals</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/issue-in-reading-input-signals/m-p/1711033#M211412</link>
      <description>&lt;P&gt;I just suggest to double confirm the iomux. Because the sdk default is following.&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="1.png" style="width: 687px;"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/237965iDE3F1E6B8E1C2E82/image-size/large?v=v2&amp;amp;px=999" role="button" title="1.png" alt="1.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 24 Aug 2023 23:20:00 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/issue-in-reading-input-signals/m-p/1711033#M211412</guid>
      <dc:creator>rudi_cyber</dc:creator>
      <dc:date>2023-08-24T23:20:00Z</dc:date>
    </item>
    <item>
      <title>Re: issue in reading input signals</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/issue-in-reading-input-signals/m-p/1712616#M211601</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/215734"&gt;@rudi_cyber&lt;/a&gt;,&lt;/P&gt;&lt;P&gt;Thanks for sharing the default IOMUX. I presume this is not the muxing you use for your application, however, since you are setting them up as inputs. At what point of your application are you setting these as inputs and how are you doing so?&lt;/P&gt;&lt;P&gt;BR,&lt;BR /&gt;Edwin.&lt;/P&gt;</description>
      <pubDate>Mon, 28 Aug 2023 20:53:43 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/issue-in-reading-input-signals/m-p/1712616#M211601</guid>
      <dc:creator>EdwinHz</dc:creator>
      <dc:date>2023-08-28T20:53:43Z</dc:date>
    </item>
  </channel>
</rss>

