<?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: S32K3 FEE_Read problem</title>
    <link>https://community.nxp.com/t5/S32K/S32K3-FEE-Read-problem/m-p/2274511#M55858</link>
    <description>&lt;P&gt;Hi@&lt;SPAN&gt;xingyun&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;Please tell me what RTD version you are currently using and what demo you are referencing, and what modifications you have made.&lt;/P&gt;</description>
    <pubDate>Mon, 05 Jan 2026 10:31:16 GMT</pubDate>
    <dc:creator>Senlent</dc:creator>
    <dc:date>2026-01-05T10:31:16Z</dc:date>
    <item>
      <title>S32K3 FEE_Read problem</title>
      <link>https://community.nxp.com/t5/S32K/S32K3-FEE-Read-problem/m-p/2269590#M55759</link>
      <description>&lt;P&gt;The S32K3 implements FEE. However, FEE_Read always fails and its return valueRetVal is 1.Do not use the following "else" statement:&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="xingyun_1-1766997765170.png" style="width: 400px;"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/371322iEECC3D333DAFF517/image-size/medium?v=v2&amp;amp;px=400" role="button" title="xingyun_1-1766997765170.png" alt="xingyun_1-1766997765170.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="xingyun_2-1766997886668.png" style="width: 400px;"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/371323i1329F9685164A17F/image-size/medium?v=v2&amp;amp;px=400" role="button" title="xingyun_2-1766997886668.png" alt="xingyun_2-1766997886668.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;When reaching the "Fee_ExampleAssert" point, it is impossible to exit the while loop directly. May I ask what the problem is? Below is the EB configuration:&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="xingyun_3-1766997989563.png" style="width: 400px;"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/371324iBFFA35C4284DD042/image-size/medium?v=v2&amp;amp;px=400" role="button" title="xingyun_3-1766997989563.png" alt="xingyun_3-1766997989563.png" /&gt;&lt;/span&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="xingyun_4-1766998012930.png" style="width: 400px;"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/371325i2BFF24A17FC036FC/image-size/medium?v=v2&amp;amp;px=400" role="button" title="xingyun_4-1766998012930.png" alt="xingyun_4-1766998012930.png" /&gt;&lt;/span&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="xingyun_5-1766998023577.png" style="width: 400px;"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/371326i96E921BCAF07CE4B/image-size/medium?v=v2&amp;amp;px=400" role="button" title="xingyun_5-1766998023577.png" alt="xingyun_5-1766998023577.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;memory:&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="xingyun_0-1766998396800.png" style="width: 400px;"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/371329i1A68A073627F420C/image-size/medium?v=v2&amp;amp;px=400" role="button" title="xingyun_0-1766998396800.png" alt="xingyun_0-1766998396800.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="xingyun_1-1766998408642.png" style="width: 400px;"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/371330iA23B2185E37367F3/image-size/medium?v=v2&amp;amp;px=400" role="button" title="xingyun_1-1766998408642.png" alt="xingyun_1-1766998408642.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Hope the passing engineers could take a look and offer some help.&lt;/P&gt;&lt;P&gt;Thank you very much.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 29 Dec 2025 08:53:46 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32K/S32K3-FEE-Read-problem/m-p/2269590#M55759</guid>
      <dc:creator>xingyun</dc:creator>
      <dc:date>2025-12-29T08:53:46Z</dc:date>
    </item>
    <item>
      <title>Re: S32K3 FEE_Read problem</title>
      <link>https://community.nxp.com/t5/S32K/S32K3-FEE-Read-problem/m-p/2274511#M55858</link>
      <description>&lt;P&gt;Hi@&lt;SPAN&gt;xingyun&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;Please tell me what RTD version you are currently using and what demo you are referencing, and what modifications you have made.&lt;/P&gt;</description>
      <pubDate>Mon, 05 Jan 2026 10:31:16 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32K/S32K3-FEE-Read-problem/m-p/2274511#M55858</guid>
      <dc:creator>Senlent</dc:creator>
      <dc:date>2026-01-05T10:31:16Z</dc:date>
    </item>
    <item>
      <title>Re: S32K3 FEE_Read problem</title>
      <link>https://community.nxp.com/t5/S32K/S32K3-FEE-Read-problem/m-p/2289020#M55908</link>
      <description>&lt;P&gt;Thank you very much for your reply. I have carefully checked it and found that it was a problem with the underlying configuration. I found that the Fee Block Size and the Fee Virtual Page Size need to be in a multiple relationship for the operation to succeed.&lt;/P&gt;</description>
      <pubDate>Wed, 07 Jan 2026 02:04:57 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32K/S32K3-FEE-Read-problem/m-p/2289020#M55908</guid>
      <dc:creator>xingyun</dc:creator>
      <dc:date>2026-01-07T02:04:57Z</dc:date>
    </item>
    <item>
      <title>Re: S32K3 FEE_Read problem</title>
      <link>https://community.nxp.com/t5/S32K/S32K3-FEE-Read-problem/m-p/2289151#M55920</link>
      <description>&lt;P&gt;&lt;SPAN&gt;For FEE here, is there any other question you can help me with? The reference I used is SW32K3_RTD_R21-11_3.0.0_P07 - Fee_TS_T40D34M30I0R0 (S32K344)&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;At present, before the FEE configuration and debugging were carried out, there was no problem with the ADC sampling. However, after adding the FEE module, when the initialization, triggering and interrupt functions of the ADC are commented out, the FEE storage is normal. However, once the ADC is turned on, a situation where it gets stuck at Adc_StartGroupConversion and then enters a hard fault occurs.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Then I attempted to comment out all the relevant content of FEE and only focused on the ADC part. However, I found that there was a problem with the ADC's trigger for sampling, and it entered a hard fault when it reached the Adc_StartGroupConversion stage.&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 07 Jan 2026 06:24:26 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32K/S32K3-FEE-Read-problem/m-p/2289151#M55920</guid>
      <dc:creator>xingyun</dc:creator>
      <dc:date>2026-01-07T06:24:26Z</dc:date>
    </item>
    <item>
      <title>Re: S32K3 FEE_Read problem</title>
      <link>https://community.nxp.com/t5/S32K/S32K3-FEE-Read-problem/m-p/2289185#M55926</link>
      <description>&lt;P&gt;Hi@&lt;SPAN&gt;xingyun&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;建议你不要使用QQ邮箱来注册NXP的账户，使用你们的单位邮箱来注册NXP的账户来提高处理你们问题的优先级。&lt;/P&gt;
&lt;P&gt;Regarding your new question, firstly, I'd like to know why you're using an older version of RTD. Could you try using a newer version? If the problem persists after upgrading to the newer version, please provide a project that reproduces the issue, and I will take the time to check it for you.&lt;/P&gt;
&lt;P&gt;Again, please do not use email addresses like QQ to create topics, as such accounts will not receive priority technical support.&lt;/P&gt;</description>
      <pubDate>Wed, 07 Jan 2026 07:20:37 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32K/S32K3-FEE-Read-problem/m-p/2289185#M55926</guid>
      <dc:creator>Senlent</dc:creator>
      <dc:date>2026-01-07T07:20:37Z</dc:date>
    </item>
  </channel>
</rss>

