<?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のトピックLIN communication failure during E-Flash write</title>
    <link>https://community.nxp.com/t5/S32K/LIN-communication-failure-during-E-Flash-write/m-p/2403537#M60387</link>
    <description>&lt;DIV&gt;A LIN communication failure is detected during the write operation of 100 bytes of data to the internal EEPROM. Please suggest an appropriate LIN communication recovery method.&lt;/DIV&gt;</description>
    <pubDate>Tue, 11 Aug 2026 04:37:05 GMT</pubDate>
    <dc:creator>SivaB</dc:creator>
    <dc:date>2026-08-11T04:37:05Z</dc:date>
    <item>
      <title>LIN communication failure during E-Flash write</title>
      <link>https://community.nxp.com/t5/S32K/LIN-communication-failure-during-E-Flash-write/m-p/2403537#M60387</link>
      <description>&lt;DIV&gt;A LIN communication failure is detected during the write operation of 100 bytes of data to the internal EEPROM. Please suggest an appropriate LIN communication recovery method.&lt;/DIV&gt;</description>
      <pubDate>Tue, 11 Aug 2026 04:37:05 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32K/LIN-communication-failure-during-E-Flash-write/m-p/2403537#M60387</guid>
      <dc:creator>SivaB</dc:creator>
      <dc:date>2026-08-11T04:37:05Z</dc:date>
    </item>
    <item>
      <title>Re: LIN communication failure during E-Flash write</title>
      <link>https://community.nxp.com/t5/S32K/LIN-communication-failure-during-E-Flash-write/m-p/2403966#M60426</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/207388"&gt;@SivaB&lt;/a&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Could you please let us know which exact S32K device you are using?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;One possible explanation is that the Emulated EEPROM operation takes a relatively long time, and the resulting delay may prevent the software from servicing LIN interrupts within the required timing constraints. Another possibility is a Read-While-Write conflict. During flash erase/program operations, code or data located in the flash block currently being programmed or erased cannot be fetched/read. If such code or data is required by the application, this could cause the application to crash, which would subsequently result in the observed LIN communication failures.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Could you also clarify what happens when the issue occurs? Does the application crash completely, or does it continue running and only the LIN communication stop working?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Regards,&lt;/P&gt;
&lt;P&gt;Lukas&lt;/P&gt;</description>
      <pubDate>Wed, 12 Aug 2026 05:54:30 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32K/LIN-communication-failure-during-E-Flash-write/m-p/2403966#M60426</guid>
      <dc:creator>lukaszadrapa</dc:creator>
      <dc:date>2026-08-12T05:54:30Z</dc:date>
    </item>
  </channel>
</rss>

