Hi @SivaB
Could you please let us know which exact S32K device you are using?
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.
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?
Regards,
Lukas
