<?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>S32G中的主题 Re: Intermittent Boot Failure Due to Synchronous Exception</title>
    <link>https://community.nxp.com/t5/S32G/Intermittent-Boot-Failure-Due-to-Synchronous-Exception/m-p/2095094#M13401</link>
    <description>&lt;P&gt;Hello,&amp;nbsp;&lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/187012"&gt;@zyz&lt;/a&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thanks for your reply.&lt;/P&gt;
&lt;P&gt;Seems the issue is not related with BSP from your description, and it is more likely a debug phase on your own OS, I feel sorry that it is difficult for us to analyze it without code/reproduced setup from our end, since it is found when testing with Vxworks, I suggest also consulting WindRiver for querying tips on the analysis.&lt;/P&gt;
&lt;P&gt;I apologize for your inconvenience.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;BR&lt;/P&gt;
&lt;P&gt;Chenyin&lt;/P&gt;</description>
    <pubDate>Mon, 12 May 2025 03:32:35 GMT</pubDate>
    <dc:creator>chenyin_h</dc:creator>
    <dc:date>2025-05-12T03:32:35Z</dc:date>
    <item>
      <title>Intermittent Boot Failure Due to Synchronous Exception</title>
      <link>https://community.nxp.com/t5/S32G/Intermittent-Boot-Failure-Due-to-Synchronous-Exception/m-p/2093679#M13386</link>
      <description>&lt;P&gt;During repetitive power cycling tests, we observed intermittent boot failures on the device. The issue has been preliminarily traced to a synchronous exception triggered during OS initialization, causing the system to hang. Details are as follows:&lt;/P&gt;&lt;OL&gt;&lt;LI&gt;&lt;P&gt;&lt;STRONG&gt;Failure Context&lt;/STRONG&gt;:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;&lt;P&gt;CPU is stuck at the synchronous exception vector entry, with the PC pointer frozen.&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;PC,&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;ELR_EL1, and&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;FAR_EL1&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;all point to the exception entry address&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;STRONG&gt;0xFFFFFFFF802E6200&lt;/STRONG&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;(VBAR_EL1 = 0xFFFFFFFF802E6000).&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;ESR_EL1 = 0x86000004&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;(EC=0x21, IFSC=0x04: Instruction Abort, Translation fault at level 0).&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;DDR memory content is unreadable via Lauterbach debugger.&lt;/P&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;&lt;STRONG&gt;Hypothesis&lt;/STRONG&gt;:&lt;BR /&gt;The CPU enters a deadlock when attempting to jump to the synchronous exception handler (VBAR_EL1 + 0x200), likely due to invalid page table mappings for this address, causing recursive exceptions.&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;&lt;STRONG&gt;Open Questions&lt;/STRONG&gt;:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;&lt;P&gt;How to identify the original exception trigger point (the initial faulting instruction)?&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;Why is DDR memory inaccessible via the debugger during this state?&lt;/P&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;/LI&gt;&lt;/OL&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;&lt;SPAN class=""&gt;How should I proceed with the next step of troubleshooting?&lt;/SPAN&gt;&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;&lt;DIV class=""&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV class=""&gt;&amp;nbsp;&lt;/DIV&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="2335fbff-5343-4d81-aa7b-19bf019e1328.png" style="width: 400px;"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/336722iA1BD76E114E259A1/image-size/medium?v=v2&amp;amp;px=400" role="button" title="2335fbff-5343-4d81-aa7b-19bf019e1328.png" alt="2335fbff-5343-4d81-aa7b-19bf019e1328.png" /&gt;&lt;/span&gt;&lt;P&gt; &lt;/P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="异常时CPU寄存器.png" style="width: 400px;"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/336723iDC04C3D48E98FD4A/image-size/medium?v=v2&amp;amp;px=400" role="button" title="异常时CPU寄存器.png" alt="异常时CPU寄存器.png" /&gt;&lt;/span&gt;&lt;P&gt; &lt;/P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="a0efb996-7f2d-4421-87a2-0fdb9e583185.png" style="width: 400px;"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/336724i80159E6DEC484114/image-size/medium?v=v2&amp;amp;px=400" role="button" title="a0efb996-7f2d-4421-87a2-0fdb9e583185.png" alt="a0efb996-7f2d-4421-87a2-0fdb9e583185.png" /&gt;&lt;/span&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="b1af47b0-3359-4f36-84b1-47ad396b633d.png" style="width: 400px;"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/336725iC0049084F708BEF0/image-size/medium?v=v2&amp;amp;px=400" role="button" title="b1af47b0-3359-4f36-84b1-47ad396b633d.png" alt="b1af47b0-3359-4f36-84b1-47ad396b633d.png" /&gt;&lt;/span&gt;&lt;P&gt; &lt;/P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="40ff3413-3e90-4082-a581-81a86c7e802c.png" style="width: 400px;"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/336726i72DCD1389A643830/image-size/medium?v=v2&amp;amp;px=400" role="button" title="40ff3413-3e90-4082-a581-81a86c7e802c.png" alt="40ff3413-3e90-4082-a581-81a86c7e802c.png" /&gt;&lt;/span&gt;&lt;P&gt;  &lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;/DIV&gt;</description>
      <pubDate>Thu, 08 May 2025 13:08:34 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32G/Intermittent-Boot-Failure-Due-to-Synchronous-Exception/m-p/2093679#M13386</guid>
      <dc:creator>zyz</dc:creator>
      <dc:date>2025-05-08T13:08:34Z</dc:date>
    </item>
    <item>
      <title>Re: Intermittent Boot Failure Due to Synchronous Exception</title>
      <link>https://community.nxp.com/t5/S32G/Intermittent-Boot-Failure-Due-to-Synchronous-Exception/m-p/2094090#M13392</link>
      <description>&lt;P&gt;Hello,&amp;nbsp;&lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/187012"&gt;@zyz&lt;/a&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thanks for your post.&lt;/P&gt;
&lt;P&gt;Would you mind sharing us more details of the background and the steps for triggering such issue?&lt;/P&gt;
&lt;P&gt;Is the test done on custom board or RDB/EVB? with S32G2 or G3?&lt;/P&gt;
&lt;P&gt;The test seems is done on A53 side, is it based on BSP? which version?&lt;/P&gt;
&lt;P&gt;You mentioned&amp;nbsp;&lt;SPAN&gt;synchronous exception triggered during OS initialization, the OS here is Linux from BSP or others?&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;If the test is based on BSP, any modifications done from your side?&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;BR&lt;/P&gt;
&lt;P&gt;Chenyin&lt;/P&gt;</description>
      <pubDate>Fri, 09 May 2025 02:03:34 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32G/Intermittent-Boot-Failure-Due-to-Synchronous-Exception/m-p/2094090#M13392</guid>
      <dc:creator>chenyin_h</dc:creator>
      <dc:date>2025-05-09T02:03:34Z</dc:date>
    </item>
    <item>
      <title>Re: Intermittent Boot Failure Due to Synchronous Exception</title>
      <link>https://community.nxp.com/t5/S32G/Intermittent-Boot-Failure-Due-to-Synchronous-Exception/m-p/2094577#M13394</link>
      <description>&lt;P&gt;&lt;SPAN&gt;Hi&amp;nbsp;&lt;A href="https://community.nxp.com/t5/user/viewprofilepage/user-id/24163" target="_self"&gt;&lt;SPAN class=""&gt;chenyin_h&lt;/SPAN&gt;&lt;/A&gt;,&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Thank you for your reply.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;We tested this on our self-developed board with our own OS(vxworks). &lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;At this preliminary stage, it appears that the issue lies within our initialization code. &lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Currently, we are narrowing down the problem by adding debug prints. However, since the issue has a low reproduction rate and involves extensive code.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;we would like to consult on how to more efficiently pinpoint the source of such anomalies.&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 09 May 2025 10:42:49 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32G/Intermittent-Boot-Failure-Due-to-Synchronous-Exception/m-p/2094577#M13394</guid>
      <dc:creator>zyz</dc:creator>
      <dc:date>2025-05-09T10:42:49Z</dc:date>
    </item>
    <item>
      <title>Re: Intermittent Boot Failure Due to Synchronous Exception</title>
      <link>https://community.nxp.com/t5/S32G/Intermittent-Boot-Failure-Due-to-Synchronous-Exception/m-p/2095094#M13401</link>
      <description>&lt;P&gt;Hello,&amp;nbsp;&lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/187012"&gt;@zyz&lt;/a&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thanks for your reply.&lt;/P&gt;
&lt;P&gt;Seems the issue is not related with BSP from your description, and it is more likely a debug phase on your own OS, I feel sorry that it is difficult for us to analyze it without code/reproduced setup from our end, since it is found when testing with Vxworks, I suggest also consulting WindRiver for querying tips on the analysis.&lt;/P&gt;
&lt;P&gt;I apologize for your inconvenience.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;BR&lt;/P&gt;
&lt;P&gt;Chenyin&lt;/P&gt;</description>
      <pubDate>Mon, 12 May 2025 03:32:35 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32G/Intermittent-Boot-Failure-Due-to-Synchronous-Exception/m-p/2095094#M13401</guid>
      <dc:creator>chenyin_h</dc:creator>
      <dc:date>2025-05-12T03:32:35Z</dc:date>
    </item>
  </channel>
</rss>

