<?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 S32K3: reset reason problem in S32K</title>
    <link>https://community.nxp.com/t5/S32K/S32K3-reset-reason-problem/m-p/1656459#M23243</link>
    <description>&lt;P&gt;Hello NXP team,&lt;/P&gt;&lt;P&gt;We want to get power up reason by calling interface&amp;nbsp;Power_Ip_GetResetReason() at bootloader stage and the value is as expected,&amp;nbsp;&amp;nbsp;&lt;/P&gt;&lt;P&gt;After system is run from bootloader to APP stage, we also call&amp;nbsp;Power_Ip_GetResetReason() to get reset reason, but can't get the right value. It seems that the reset reason is cleared by&amp;nbsp;Power_Ip_GetResetReason() .&lt;/P&gt;&lt;P&gt;Here is log information of&amp;nbsp; bootloader and APP.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;........
S32K314 Bootloader SW version:2.0.0
bootloader: ResetReason = 0X0
error **bleep** = 0 wd err = 0
APP:reset reason = 0x19
.........&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P class=""&gt;I wonder if there is a good way to solve this problem.&lt;/P&gt;&lt;P class=""&gt;Thanks!&lt;/P&gt;</description>
    <pubDate>Wed, 24 May 2023 08:35:58 GMT</pubDate>
    <dc:creator>gumu</dc:creator>
    <dc:date>2023-05-24T08:35:58Z</dc:date>
    <item>
      <title>S32K3: reset reason problem</title>
      <link>https://community.nxp.com/t5/S32K/S32K3-reset-reason-problem/m-p/1656459#M23243</link>
      <description>&lt;P&gt;Hello NXP team,&lt;/P&gt;&lt;P&gt;We want to get power up reason by calling interface&amp;nbsp;Power_Ip_GetResetReason() at bootloader stage and the value is as expected,&amp;nbsp;&amp;nbsp;&lt;/P&gt;&lt;P&gt;After system is run from bootloader to APP stage, we also call&amp;nbsp;Power_Ip_GetResetReason() to get reset reason, but can't get the right value. It seems that the reset reason is cleared by&amp;nbsp;Power_Ip_GetResetReason() .&lt;/P&gt;&lt;P&gt;Here is log information of&amp;nbsp; bootloader and APP.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;........
S32K314 Bootloader SW version:2.0.0
bootloader: ResetReason = 0X0
error **bleep** = 0 wd err = 0
APP:reset reason = 0x19
.........&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P class=""&gt;I wonder if there is a good way to solve this problem.&lt;/P&gt;&lt;P class=""&gt;Thanks!&lt;/P&gt;</description>
      <pubDate>Wed, 24 May 2023 08:35:58 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32K/S32K3-reset-reason-problem/m-p/1656459#M23243</guid>
      <dc:creator>gumu</dc:creator>
      <dc:date>2023-05-24T08:35:58Z</dc:date>
    </item>
    <item>
      <title>Re: S32K3: reset reason problem</title>
      <link>https://community.nxp.com/t5/S32K/S32K3-reset-reason-problem/m-p/1657075#M23260</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/211858"&gt;@gumu&lt;/a&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;To avoid multiple reset reasons when the user calls Power_Ip_MC_RGM_GetResetReason() should ensure that the reset reason is cleared once it has been read. This function is called by Power_Ip_GetResetReason(), therefore when you call this function the reset reason can only read one time.&lt;/P&gt;
&lt;P&gt;If you want to read the reset reason more than once you need to do some changes to the functions, but this is up to you.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;B.R.&lt;/P&gt;
&lt;P&gt;VaneB&lt;/P&gt;</description>
      <pubDate>Wed, 24 May 2023 20:58:20 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32K/S32K3-reset-reason-problem/m-p/1657075#M23260</guid>
      <dc:creator>VaneB</dc:creator>
      <dc:date>2023-05-24T20:58:20Z</dc:date>
    </item>
  </channel>
</rss>

