<?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: LPIT Interrupt is not working after VLPS to RUN  mode transition in S32 SDK</title>
    <link>https://community.nxp.com/t5/S32-SDK/LPIT-Interrupt-is-not-working-after-VLPS-to-RUN-mode-transition/m-p/1630577#M3030</link>
    <description>&lt;P&gt;The issue will be fixed in the next revision.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thank you,&lt;/P&gt;&lt;P&gt;BR, Daniel&lt;/P&gt;</description>
    <pubDate>Mon, 10 Apr 2023 14:25:43 GMT</pubDate>
    <dc:creator>danielmartynek</dc:creator>
    <dc:date>2023-04-10T14:25:43Z</dc:date>
    <item>
      <title>LPIT Interrupt is not working after VLPS to RUN  mode transition</title>
      <link>https://community.nxp.com/t5/S32-SDK/LPIT-Interrupt-is-not-working-after-VLPS-to-RUN-mode-transition/m-p/1620682#M2976</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;I'm using S32K148 MCU and RTD as MCAL. In my current project the MCU goes to VLPS mode and every 60ms wakes up using LPTMR interrupt. LPTMR uses LPO 1K as clock source. While waking up, a piece of code executes and MCU goes to VLPS again. This scenario repeats 5 times and then MCU stays in RUN mode till the end. At this time the clock is reinitialized and LPIT is started to generate periodic interrupts.&lt;/P&gt;&lt;P&gt;The problem is that LPIT ISR never executes in this case. I checked MCU registers and realized that LPIT interrupt stays pending and the routine doesn't execute.&lt;/P&gt;&lt;P&gt;LPIT uses SIRC as clock source.&lt;BR /&gt;&lt;SPAN&gt;I also tried initializing LPIT after the last wakeup when MCU doesn't go to VLPS mode anymore. but the same thing happened.&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 23 Mar 2023 08:41:11 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32-SDK/LPIT-Interrupt-is-not-working-after-VLPS-to-RUN-mode-transition/m-p/1620682#M2976</guid>
      <dc:creator>ab1995</dc:creator>
      <dc:date>2023-03-23T08:41:11Z</dc:date>
    </item>
    <item>
      <title>Re: LPIT Interrupt is not working after VLPS to RUN  mode transition</title>
      <link>https://community.nxp.com/t5/S32-SDK/LPIT-Interrupt-is-not-working-after-VLPS-to-RUN-mode-transition/m-p/1621043#M2979</link>
      <description>&lt;P&gt;Hello &lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/214613"&gt;@ab1995&lt;/a&gt;,&lt;/P&gt;
&lt;P&gt;Where do you see the LPIT interrupt pending?&lt;/P&gt;
&lt;P&gt;In the NVIC_ISPRn register or in the LPIT_MSR register.&lt;/P&gt;
&lt;P&gt;If it is pending in NVIC_ISPRn, is the interrupt enabled in NVIC_ISERn?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;BR, Daniel&lt;/P&gt;</description>
      <pubDate>Thu, 23 Mar 2023 15:40:34 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32-SDK/LPIT-Interrupt-is-not-working-after-VLPS-to-RUN-mode-transition/m-p/1621043#M2979</guid>
      <dc:creator>danielmartynek</dc:creator>
      <dc:date>2023-03-23T15:40:34Z</dc:date>
    </item>
    <item>
      <title>Re: LPIT Interrupt is not working after VLPS to RUN  mode transition</title>
      <link>https://community.nxp.com/t5/S32-SDK/LPIT-Interrupt-is-not-working-after-VLPS-to-RUN-mode-transition/m-p/1621966#M2984</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/160001"&gt;@danielmartynek&lt;/a&gt;&amp;nbsp;,&lt;/P&gt;&lt;P&gt;thank you for your quick response.&lt;/P&gt;&lt;P&gt;I see that interrupt is pending in NVIC_ISPRn register. Also it is enabled.&lt;/P&gt;&lt;P&gt;If I don’t switch between modes, I can get LPIT interrupt with the current configuration.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Sat, 25 Mar 2023 06:11:41 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32-SDK/LPIT-Interrupt-is-not-working-after-VLPS-to-RUN-mode-transition/m-p/1621966#M2984</guid>
      <dc:creator>ab1995</dc:creator>
      <dc:date>2023-03-25T06:11:41Z</dc:date>
    </item>
    <item>
      <title>Re: LPIT Interrupt is not working after VLPS to RUN  mode transition</title>
      <link>https://community.nxp.com/t5/S32-SDK/LPIT-Interrupt-is-not-working-after-VLPS-to-RUN-mode-transition/m-p/1622406#M2986</link>
      <description>&lt;P&gt;Hi &lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/214613"&gt;@ab1995&lt;/a&gt;,&lt;/P&gt;
&lt;P&gt;Just to be sure, can you double-check PRIMASK?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thanks,&lt;/P&gt;
&lt;P&gt;BR, Daniel&lt;/P&gt;</description>
      <pubDate>Mon, 27 Mar 2023 08:26:05 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32-SDK/LPIT-Interrupt-is-not-working-after-VLPS-to-RUN-mode-transition/m-p/1622406#M2986</guid>
      <dc:creator>danielmartynek</dc:creator>
      <dc:date>2023-03-27T08:26:05Z</dc:date>
    </item>
    <item>
      <title>Re: LPIT Interrupt is not working after VLPS to RUN  mode transition</title>
      <link>https://community.nxp.com/t5/S32-SDK/LPIT-Interrupt-is-not-working-after-VLPS-to-RUN-mode-transition/m-p/1627333#M3005</link>
      <description>&lt;P&gt;Hi &lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/160001"&gt;@danielmartynek&lt;/a&gt; ,&lt;/P&gt;&lt;P&gt;I checked the PRIMASK, before mode change, it is 0, and after wakeup it turns to 1 and remains 1. I tried to change it manually to 0 so I could get the interrupt. But I didn't understand the reason why it's happening.&lt;/P&gt;</description>
      <pubDate>Tue, 04 Apr 2023 05:59:54 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32-SDK/LPIT-Interrupt-is-not-working-after-VLPS-to-RUN-mode-transition/m-p/1627333#M3005</guid>
      <dc:creator>ab1995</dc:creator>
      <dc:date>2023-04-04T05:59:54Z</dc:date>
    </item>
    <item>
      <title>Re: LPIT Interrupt is not working after VLPS to RUN  mode transition</title>
      <link>https://community.nxp.com/t5/S32-SDK/LPIT-Interrupt-is-not-working-after-VLPS-to-RUN-mode-transition/m-p/1627334#M3006</link>
      <description>&lt;P&gt;Hi &lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/160001"&gt;@danielmartynek&lt;/a&gt; ,&lt;/P&gt;&lt;P&gt;I checked the PRIMASK, before mode change, it is 0, and after wakeup it turns to 1 and remains 1. I tried to change it manually to 0 so I could get the interrupt.&lt;/P&gt;&lt;P&gt;The function EXECUTE_WAIT() is called when entering low power modes by driver. It is implemented as bellow:&lt;/P&gt;&lt;P&gt;#define EXECUTE_WAIT() \&lt;BR /&gt;do \&lt;BR /&gt;{ \&lt;BR /&gt;OsIf_ResumeAllInterrupts(); \&lt;BR /&gt;ASM_KEYWORD(" wfi"); \&lt;BR /&gt;OsIf_SuspendAllInterrupts(); \&lt;BR /&gt;} while (0)&lt;/P&gt;&lt;P&gt;if we enter run mode after wakeup interrupts stay suspended (PRIMASK = 1) because of OsIf_SuspendAllInterrupts(), so we need to resume interrupts and the driver doesn't do this.&lt;/P&gt;&lt;P&gt;If we repeatedly enter vlps mode interrupts get executed because of OsIf_ResumeAllInterrupts before wfi, my question is why are interrupts suspended in driver code after wakeup?&lt;/P&gt;</description>
      <pubDate>Tue, 04 Apr 2023 08:40:52 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32-SDK/LPIT-Interrupt-is-not-working-after-VLPS-to-RUN-mode-transition/m-p/1627334#M3006</guid>
      <dc:creator>ab1995</dc:creator>
      <dc:date>2023-04-04T08:40:52Z</dc:date>
    </item>
    <item>
      <title>Re: LPIT Interrupt is not working after VLPS to RUN  mode transition</title>
      <link>https://community.nxp.com/t5/S32-SDK/LPIT-Interrupt-is-not-working-after-VLPS-to-RUN-mode-transition/m-p/1627462#M3008</link>
      <description>&lt;P&gt;I don't understand why do we need to suspend interrupts after wfi.&lt;/P&gt;</description>
      <pubDate>Tue, 04 Apr 2023 08:55:15 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32-SDK/LPIT-Interrupt-is-not-working-after-VLPS-to-RUN-mode-transition/m-p/1627462#M3008</guid>
      <dc:creator>ab1995</dc:creator>
      <dc:date>2023-04-04T08:55:15Z</dc:date>
    </item>
    <item>
      <title>Re: LPIT Interrupt is not working after VLPS to RUN  mode transition</title>
      <link>https://community.nxp.com/t5/S32-SDK/LPIT-Interrupt-is-not-working-after-VLPS-to-RUN-mode-transition/m-p/1627647#M3009</link>
      <description>&lt;P&gt;The S32K3xx RTD resumes the interrupts within the same function after the wakeup but not the S32K1xx RTD.&lt;/P&gt;
&lt;P&gt;Let me trigger a discussion with the RTD team.&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="danielmartynek_0-1680608752236.png" style="width: 400px;"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/217701i8319C83B4D32AD16/image-size/medium?v=v2&amp;amp;px=400" role="button" title="danielmartynek_0-1680608752236.png" alt="danielmartynek_0-1680608752236.png" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;BR, Daniel&lt;/P&gt;</description>
      <pubDate>Tue, 04 Apr 2023 11:48:13 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32-SDK/LPIT-Interrupt-is-not-working-after-VLPS-to-RUN-mode-transition/m-p/1627647#M3009</guid>
      <dc:creator>danielmartynek</dc:creator>
      <dc:date>2023-04-04T11:48:13Z</dc:date>
    </item>
    <item>
      <title>Re: LPIT Interrupt is not working after VLPS to RUN  mode transition</title>
      <link>https://community.nxp.com/t5/S32-SDK/LPIT-Interrupt-is-not-working-after-VLPS-to-RUN-mode-transition/m-p/1630577#M3030</link>
      <description>&lt;P&gt;The issue will be fixed in the next revision.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thank you,&lt;/P&gt;&lt;P&gt;BR, Daniel&lt;/P&gt;</description>
      <pubDate>Mon, 10 Apr 2023 14:25:43 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32-SDK/LPIT-Interrupt-is-not-working-after-VLPS-to-RUN-mode-transition/m-p/1630577#M3030</guid>
      <dc:creator>danielmartynek</dc:creator>
      <dc:date>2023-04-10T14:25:43Z</dc:date>
    </item>
  </channel>
</rss>

