<?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 SAF sCheck Shutdown Test in S32G</title>
    <link>https://community.nxp.com/t5/S32G/SAF-sCheck-Shutdown-Test/m-p/2173474#M14973</link>
    <description>&lt;P&gt;Hi Team,&lt;/P&gt;&lt;P&gt;im working on SAF module particularly on scheck. i found the scheck shutdown test API. where we can run the scheck during the shutdown phase.&amp;nbsp;&lt;/P&gt;&lt;P&gt;just a question. what if? i run the SRAM test. the test has reported the error. scheck result is stored in NvM that is used to select the operation mode in next operation cycle.&amp;nbsp;&lt;/P&gt;&lt;P&gt;what if the error is cleared. let's say uncorrectable error has been detected by scheck and the error is reported and stored. may be after POR the error has been corrected on its own. but since the error is stored in NvM even if the error is corrected the msel is going to read from the NvM during the next cycle?&amp;nbsp;&lt;/P&gt;&lt;P&gt;how is it expected to be handled?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Br,&lt;/P&gt;&lt;P&gt;Harish R&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Mon, 22 Sep 2025 09:49:47 GMT</pubDate>
    <dc:creator>Harish_R</dc:creator>
    <dc:date>2025-09-22T09:49:47Z</dc:date>
    <item>
      <title>SAF sCheck Shutdown Test</title>
      <link>https://community.nxp.com/t5/S32G/SAF-sCheck-Shutdown-Test/m-p/2173474#M14973</link>
      <description>&lt;P&gt;Hi Team,&lt;/P&gt;&lt;P&gt;im working on SAF module particularly on scheck. i found the scheck shutdown test API. where we can run the scheck during the shutdown phase.&amp;nbsp;&lt;/P&gt;&lt;P&gt;just a question. what if? i run the SRAM test. the test has reported the error. scheck result is stored in NvM that is used to select the operation mode in next operation cycle.&amp;nbsp;&lt;/P&gt;&lt;P&gt;what if the error is cleared. let's say uncorrectable error has been detected by scheck and the error is reported and stored. may be after POR the error has been corrected on its own. but since the error is stored in NvM even if the error is corrected the msel is going to read from the NvM during the next cycle?&amp;nbsp;&lt;/P&gt;&lt;P&gt;how is it expected to be handled?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Br,&lt;/P&gt;&lt;P&gt;Harish R&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 22 Sep 2025 09:49:47 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32G/SAF-sCheck-Shutdown-Test/m-p/2173474#M14973</guid>
      <dc:creator>Harish_R</dc:creator>
      <dc:date>2025-09-22T09:49:47Z</dc:date>
    </item>
    <item>
      <title>Re: SAF sCheck Shutdown Test</title>
      <link>https://community.nxp.com/t5/S32G/SAF-sCheck-Shutdown-Test/m-p/2173801#M14980</link>
      <description>&lt;P&gt;Hello&amp;nbsp;&lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/242921"&gt;@Harish_R&lt;/a&gt;,&lt;/P&gt;
&lt;P&gt;Thanks for reaching out to us once again. That is a good question, in cases where the information in the NVM was lost, the SAF code does not define how the system should react. If you check the following functions, you can see that the reaction will depend on your implementation of the function to read the NVM:&lt;/P&gt;
&lt;P&gt;in&amp;nbsp;Std_ReturnType mSel_StorePreservedNvmData(), the real NVM read is done by&amp;nbsp;mSel_NvmWrite():&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="alejandro_e_0-1758577805593.png" style="width: 400px;"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/358032i7EE09B6C48905864/image-size/medium?v=v2&amp;amp;px=400" role="button" title="alejandro_e_0-1758577805593.png" alt="alejandro_e_0-1758577805593.png" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;And in the SAF demo you can see that the mSel_NvmWrite() function is left for the developer to implement:&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="alejandro_e_1-1758577904923.png" style="width: 400px;"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/358033iA40C19218B41570A/image-size/medium?v=v2&amp;amp;px=400" role="button" title="alejandro_e_1-1758577904923.png" alt="alejandro_e_1-1758577904923.png" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;You will need to decide the return value of&amp;nbsp;mSel_NvmWrite(), either&amp;nbsp;E_NOT_OK or&amp;nbsp;E_OK.&amp;nbsp;this will define the behavior in&amp;nbsp;Std_ReturnType mSel_StorePreservedNvmData().&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Let me know if you have more questions&lt;/P&gt;</description>
      <pubDate>Mon, 22 Sep 2025 22:09:00 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32G/SAF-sCheck-Shutdown-Test/m-p/2173801#M14980</guid>
      <dc:creator>alejandro_e</dc:creator>
      <dc:date>2025-09-22T22:09:00Z</dc:date>
    </item>
    <item>
      <title>Re: SAF sCheck Shutdown Test</title>
      <link>https://community.nxp.com/t5/S32G/SAF-sCheck-Shutdown-Test/m-p/2177220#M15043</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/238460"&gt;@alejandro_e&lt;/a&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks for your support!.&lt;/P&gt;&lt;P&gt;understood the backup concept through NvM but question was, lets say,&lt;/P&gt;&lt;P&gt;1. im performing&amp;nbsp;sCheck_ExecuteShutdownTests (enabled SRAM0 test) during this test the SRAM reported failed status. some uncorrectable error was reported.&lt;/P&gt;&lt;P&gt;2. msel_mSel_ShutDown - to store the scheck shutdown results. (so here the failure of sram UE will be stored in NVM).&lt;/P&gt;&lt;P&gt;3. Now i do a POR(Power on reset)- lets say the the UE error has been corrected after POR.&lt;/P&gt;&lt;P&gt;UE is correctable during POR.&lt;/P&gt;&lt;P&gt;4. next Power ON cycle. the Msel_selectmode() is called and it reads the stored result from NvM its actually reading the fault stored. (but the fault is cleared during the POR).&lt;/P&gt;&lt;P&gt;how this situation is expected to be handled where the fault is cleared but the msel is still reading it form NvM&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Harish R&lt;/P&gt;</description>
      <pubDate>Mon, 29 Sep 2025 06:43:10 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32G/SAF-sCheck-Shutdown-Test/m-p/2177220#M15043</guid>
      <dc:creator>Harish_R</dc:creator>
      <dc:date>2025-09-29T06:43:10Z</dc:date>
    </item>
    <item>
      <title>Re: SAF sCheck Shutdown Test</title>
      <link>https://community.nxp.com/t5/S32G/SAF-sCheck-Shutdown-Test/m-p/2178397#M15056</link>
      <description>&lt;P&gt;Hello&amp;nbsp;&lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/242921"&gt;@Harish_R&lt;/a&gt;,&lt;/P&gt;
&lt;P&gt;Checking the both documentation and code you can see that the mode selection process has quite a complicated logic to it. Please check section&amp;nbsp;&lt;STRONG&gt;2.2 Operational Mode Selection&amp;nbsp;&lt;/STRONG&gt;in&amp;nbsp;&lt;EM&gt;S32G_SAF_MSEL_UM.pdf&lt;/EM&gt;. There you will see more details on how the module selects the operational mode depending on the type of errors present.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Best regards&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 30 Sep 2025 20:12:48 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32G/SAF-sCheck-Shutdown-Test/m-p/2178397#M15056</guid>
      <dc:creator>alejandro_e</dc:creator>
      <dc:date>2025-09-30T20:12:48Z</dc:date>
    </item>
  </channel>
</rss>

