<?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>S32K中的主题 Re: S32K312 Wake UP</title>
    <link>https://community.nxp.com/t5/S32K/S32K312-Wake-UP/m-p/2142906#M51440</link>
    <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/252804"&gt;@ZZZZZJH&lt;/a&gt;&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;Is the wake-up method configured through the GPIO input pin and the WKPU pin the same?&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;I'm not sure I understand this question but let me try to clear it up. The WKPU instance shares functionality with the other pins, using a MUX. This means that any GPIO pin can be used as wake up source as long as it has a WKPU interrupt assigned (check S32K_IOMUX.xlsx file attached to S32K3 reference manual for full pinout confirmation).&lt;/P&gt;
&lt;P&gt;You can find a GPIO WKPU routine for the S32K312 in both LLD and HLD in this community post:&amp;nbsp;&lt;A href="https://community.nxp.com/t5/S32K-Knowledge-Base/RTD400-amp-500-MCAL-amp-IP-S32K3-Low-Power-Management-AN-and/ta-p/1993152" target="_blank"&gt;[RTD400 &amp;amp; 500 MCAL &amp;amp; IP] S32K3 Low Power Management AN and demos - NXP Community&lt;/A&gt;.&lt;/P&gt;
&lt;P&gt;They are based in RTD 5.0.0 &amp;amp; S32DS 3.5/3.6. Hope this helps.&lt;/P&gt;
&lt;P&gt;Best regards,&lt;BR /&gt;Julián&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Tue, 29 Jul 2025 18:39:03 GMT</pubDate>
    <dc:creator>Julián_AragónM</dc:creator>
    <dc:date>2025-07-29T18:39:03Z</dc:date>
    <item>
      <title>S32K312 Wake UP</title>
      <link>https://community.nxp.com/t5/S32K/S32K312-Wake-UP/m-p/2141698#M51382</link>
      <description>&lt;P&gt;Hello, supporters of NXP. I would like to inquire whether the S32K312 can achieve low-power wake-up through the S32DS configuration of LLD. Is the wake-up method configured through the GPIO input pin and the WKPU pin the same? Is there any routine provided for the wake-up method configured through the WKPU pin? Thank you.&lt;/P&gt;</description>
      <pubDate>Mon, 28 Jul 2025 10:38:52 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32K/S32K312-Wake-UP/m-p/2141698#M51382</guid>
      <dc:creator>ZZZZZJH</dc:creator>
      <dc:date>2025-07-28T10:38:52Z</dc:date>
    </item>
    <item>
      <title>Re: S32K312 Wake UP</title>
      <link>https://community.nxp.com/t5/S32K/S32K312-Wake-UP/m-p/2142906#M51440</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/252804"&gt;@ZZZZZJH&lt;/a&gt;&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;Is the wake-up method configured through the GPIO input pin and the WKPU pin the same?&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;I'm not sure I understand this question but let me try to clear it up. The WKPU instance shares functionality with the other pins, using a MUX. This means that any GPIO pin can be used as wake up source as long as it has a WKPU interrupt assigned (check S32K_IOMUX.xlsx file attached to S32K3 reference manual for full pinout confirmation).&lt;/P&gt;
&lt;P&gt;You can find a GPIO WKPU routine for the S32K312 in both LLD and HLD in this community post:&amp;nbsp;&lt;A href="https://community.nxp.com/t5/S32K-Knowledge-Base/RTD400-amp-500-MCAL-amp-IP-S32K3-Low-Power-Management-AN-and/ta-p/1993152" target="_blank"&gt;[RTD400 &amp;amp; 500 MCAL &amp;amp; IP] S32K3 Low Power Management AN and demos - NXP Community&lt;/A&gt;.&lt;/P&gt;
&lt;P&gt;They are based in RTD 5.0.0 &amp;amp; S32DS 3.5/3.6. Hope this helps.&lt;/P&gt;
&lt;P&gt;Best regards,&lt;BR /&gt;Julián&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 29 Jul 2025 18:39:03 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32K/S32K312-Wake-UP/m-p/2142906#M51440</guid>
      <dc:creator>Julián_AragónM</dc:creator>
      <dc:date>2025-07-29T18:39:03Z</dc:date>
    </item>
  </channel>
</rss>

