The application development of LIN communication in I2C peripherals

benjieming — Tue, 20 Jan 2026 02:53:16 GMT

Hi everyone:
During the application of the KEAZN32 single-chip microcontroller based on LIN communication and I2C host interrupt peripheral, I encountered problems such as abnormal LIN communication when calling the I2C interrupt in the program, and the UART1 interrupt used also failed. The engineering development environment I am using is the S32DS platform and the official FRDM-KEA-QSP driver library. Regarding the issues mentioned above, I sincerely hope for the support of all technical experts.
Thank you very much.

Re: The application development of LIN communication in I2C peripherals

Celeste_Liu — Thu, 22 Jan 2026 09:46:11 GMT

Hello @benjieming ,

Thanks for your post.

Have you ever referred to our LIN2.x stack for KEA:

https://www.nxp.com/webapp/swlicensing/sso/downloadSoftware.sp?catid=SW-LIN2X-J2602-D

In addition, based on your description, I suspect the issue may be related to the following points:

1. TheISR name does not match the vector table in the startup file.
This is especially common when porting the LIN_Stack to S32DS, you usually need to rename the UART1 ISR in lin_isr.c so that it matches the vector name defined in startup_*.s.
If the names don’t match, the UART1 interrupt will never be triggered.

2. Improper interrupt priority configuration or excessive use of global interrupt masking.
If the I2C interrupt has a higher priority, runs for too long, or global interrupts are disabled in certain critical sections, the UART1 interrupt used by LIN may be blocked for an extended period.
As a result, LIN may miss critical timing windows such as Break, Sync, and Response.
Therefore, UART1/LIN should be assigned a higher priority than I2C, and all ISRs must remain as short as possible.

3. Incorrect flag‑clearing sequence or register access order.
For example, UART requires reading UARTx_S1 before reading/writing the D register in order to clear RDRF/TDRE correctly.
If the order is wrong, the system may exhibit the classic symptom of “the ISR fires once and never fires again.”
The I2C module also requires flags to be cleared strictly in the sequence specified by the reference manual.

Additionally, others have performed similar migrations and have shared their experience.
I have found a useful reference link for you to review.

如何使用S32DS开发KEA系列的LIN功能（二）_nxp kea lin协议栈生成-CSDN博客

Celeste

topic Re: The application development of LIN communication in I2C peripherals in Kinetis Microcontrollers

The application development of LIN communication in I2C peripherals

Re: The application development of LIN communication in I2C peripherals