<?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: S32K312 FEE FLS INIT time</title>
    <link>https://community.nxp.com/t5/S32K/S32K312-FEE-FLS-INIT-time/m-p/2027403#M45078</link>
    <description>&lt;P&gt;It's probably caused by RAM initialization. This piece of RAM should be initialized conditionally. If the source of reset power-on reset, the RAM must be initialized. If it is not power-on reset, you can skip the initialization.&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="lukaszadrapa_0-1736842544510.png" style="width: 400px;"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/319470i3690D26A4723C130/image-size/medium?v=v2&amp;amp;px=400" role="button" title="lukaszadrapa_0-1736842544510.png" alt="lukaszadrapa_0-1736842544510.png" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Tue, 14 Jan 2025 08:15:52 GMT</pubDate>
    <dc:creator>lukaszadrapa</dc:creator>
    <dc:date>2025-01-14T08:15:52Z</dc:date>
    <item>
      <title>S32K312 FEE FLS INIT time</title>
      <link>https://community.nxp.com/t5/S32K/S32K312-FEE-FLS-INIT-time/m-p/2024041#M44918</link>
      <description>&lt;P&gt;hello,expert&lt;/P&gt;&lt;P&gt;there ia a question in my boot and app,&lt;/P&gt;&lt;P&gt;before step into boot ,i will write a flag ( program request ) in eeprom ,and use jump function jump to boot, after download all the data ,i will write a flag ( app valid ) , then i will jump to app.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;but i find that every cyclic,the&amp;nbsp;Fee_MainFunction loop and&amp;nbsp;MemAcc_MainFunction loop will take longer time. for example, the 1st is 10ms,the 2nd cyclic is 20ms&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="PINKMAN_0-1736336377646.png" style="width: 400px;"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/318601iDD257AB104C80664/image-size/medium?v=v2&amp;amp;px=400" role="button" title="PINKMAN_0-1736336377646.png" alt="PINKMAN_0-1736336377646.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="PINKMAN_1-1736336410874.png" style="width: 400px;"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/318602i91F2CC68A9D33912/image-size/medium?v=v2&amp;amp;px=400" role="button" title="PINKMAN_1-1736336410874.png" alt="PINKMAN_1-1736336410874.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;it will lead to the fault of uds timer&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 08 Jan 2025 11:41:25 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32K/S32K312-FEE-FLS-INIT-time/m-p/2024041#M44918</guid>
      <dc:creator>PINKMAN</dc:creator>
      <dc:date>2025-01-08T11:41:25Z</dc:date>
    </item>
    <item>
      <title>Re: S32K312 FEE FLS INIT time</title>
      <link>https://community.nxp.com/t5/S32K/S32K312-FEE-FLS-INIT-time/m-p/2024662#M44953</link>
      <description>&lt;P&gt;Hi &lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/193092"&gt;@PINKMAN&lt;/a&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;This is natural and expected behavior of Fee module. The more data is present in Fee blocks, the more time will initialization take. If there are a lot of records, it can take much(!) more time than tens of milliseconds. Also cluster swap may be necessary sometimes during initialization which will significantly affect the timing.&lt;/P&gt;
&lt;P&gt;If timing is critical, don't use Fee module for this. Either program some flash directly, so you can read the flash immediately without any delays after reset or use RAM only - if it is sufficient to keep the information only during reset and not during power off.&lt;/P&gt;
&lt;P&gt;Regards,&lt;/P&gt;
&lt;P&gt;Lukas&lt;/P&gt;</description>
      <pubDate>Thu, 09 Jan 2025 08:47:42 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32K/S32K312-FEE-FLS-INIT-time/m-p/2024662#M44953</guid>
      <dc:creator>lukaszadrapa</dc:creator>
      <dc:date>2025-01-09T08:47:42Z</dc:date>
    </item>
    <item>
      <title>Re: S32K312 FEE FLS INIT time</title>
      <link>https://community.nxp.com/t5/S32K/S32K312-FEE-FLS-INIT-time/m-p/2024859#M44971</link>
      <description>thanks</description>
      <pubDate>Thu, 09 Jan 2025 13:00:18 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32K/S32K312-FEE-FLS-INIT-time/m-p/2024859#M44971</guid>
      <dc:creator>PINKMAN</dc:creator>
      <dc:date>2025-01-09T13:00:18Z</dc:date>
    </item>
    <item>
      <title>Re: S32K312 FEE FLS INIT time</title>
      <link>https://community.nxp.com/t5/S32K/S32K312-FEE-FLS-INIT-time/m-p/2025631#M44992</link>
      <description>&lt;P&gt;accoring to your advice, i&amp;nbsp;allocate a RAM(ORIGIN = 0x20407E00, LENGTH = 0x00000100)section for flag which app jump to boot.&lt;/P&gt;&lt;P&gt;i am sure that the ram section will not be&amp;nbsp;affected by DATA and BSS init.&lt;/P&gt;&lt;P&gt;then in app i set address&amp;nbsp;0x20407E00&amp;nbsp; as 0x55aa55aa,&lt;/P&gt;&lt;P&gt;and use jump function to boot ,&lt;/P&gt;&lt;P&gt;in boot read the address value is always zero.&lt;/P&gt;&lt;P&gt;that's why?&lt;/P&gt;</description>
      <pubDate>Fri, 10 Jan 2025 08:36:41 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32K/S32K312-FEE-FLS-INIT-time/m-p/2025631#M44992</guid>
      <dc:creator>PINKMAN</dc:creator>
      <dc:date>2025-01-10T08:36:41Z</dc:date>
    </item>
    <item>
      <title>Re: S32K312 FEE FLS INIT time</title>
      <link>https://community.nxp.com/t5/S32K/S32K312-FEE-FLS-INIT-time/m-p/2027403#M45078</link>
      <description>&lt;P&gt;It's probably caused by RAM initialization. This piece of RAM should be initialized conditionally. If the source of reset power-on reset, the RAM must be initialized. If it is not power-on reset, you can skip the initialization.&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="lukaszadrapa_0-1736842544510.png" style="width: 400px;"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/319470i3690D26A4723C130/image-size/medium?v=v2&amp;amp;px=400" role="button" title="lukaszadrapa_0-1736842544510.png" alt="lukaszadrapa_0-1736842544510.png" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 14 Jan 2025 08:15:52 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32K/S32K312-FEE-FLS-INIT-time/m-p/2027403#M45078</guid>
      <dc:creator>lukaszadrapa</dc:creator>
      <dc:date>2025-01-14T08:15:52Z</dc:date>
    </item>
  </channel>
</rss>

