topic Re: S32K310 Lin conformity test in S32K

S32K310 Lin conformity test

Chenxu1 — Mon, 15 Sep 2025 09:03:03 GMT

Hi，NXP专家，在使用S32K310进行Canoe自带LIN一致性测试时，我们遇到如下两个问题需要协助，谢谢。
1.用例11.3

根据脚本和标准，这条用例，不应该置位LIN Reponse Error，但实际Log显示，LIN Reponse Error被置位如下

调试发现是软件检测到 LIN_ERR_RESP_STOPBIT，导致LIN Reponse Error置位。

2.如下四个用例在外围电路相同的情况下，一些芯片能测试通过，另一些测试不通过，canoe显示超过合理波特率范围。

软件版本为RTD5.0.0，LinStack2.0.5

Re: S32K310 Lin conformity test

danielmartynek — Mon, 15 Sep 2025 11:29:32 GMT

Hi @Chenxu1,

Could you please use an oscilloscope or logic analyzer to measure and compare the actual LIN baud rates of both devices?

Also, could you clarify which LPUART instance is being used for LIN communication?
It would be helpful if you could dump the LPUART register values after LIN initialization to verify the configuration.

What is your system clock setup?
Please ensure that you're using one of the recommended configurations listed in Reference Manual section 24.7.2 – System Clocking Configurations

Regards,

Daniel

Re: S32K310 Lin conformity test

Chenxu1 — Tue, 16 Sep 2025 03:09:44 GMT

Hi，Daniel.Thanks for your reply.
The clock configuration is in line with the recommended configurations listed in Reference Manual section 24.7.2.
The Uart0 channel is used and the clock is AIPS_PLAT_CLK 60M.
Attached is the LPUART register values after LIN initialization.
@danielmartynek

Re: S32K310 Lin conformity test

danielmartynek — Tue, 16 Sep 2025 06:41:51 GMT

Hi @Chenxu1,

Based on the register values, BAUD register = 0x0F00804E.

OSR = bits [24:28] = 0x0F = 15
SBR = bits [0:12] = 0x04E = 78

Baud Rate = 60000000 / (16 × 78) = 48076 bps

This is not a typical LIN baud rate.

Have you measured the baud rate of both nodes?

Thank you,

BR, Daniel

Re: S32K310 Lin conformity test

Chenxu1 — Fri, 19 Sep 2025 03:02:24 GMT

Hi，Daniel
Thanks For your help.
Modifying the baud rate,The question 2 has been solved.
Do you have any suggestions regarding question 1?

Re: S32K310 Lin conformity test

danielmartynek — Fri, 19 Sep 2025 07:30:59 GMT

Hi @Chenxu1,

Glad to hear the second issue has been resolved.

For future cases, please create a separate thread for each issue to help maintain clarity and traceability.

Regarding the first issue, it is likely caused by an incorrect period configured for Gpt_StartTimer. This could be the reason why Switch_TimeOut() is never called. Please verify the timer configuration to ensure it aligns with the expected timeout behavior.

Refer to the attached screenshots.

Regards,

Daniel

Any support, information, and technology (“Materials”) provided by NXP are provided AS IS, without any warranty express or implied, and NXP disclaims all direct and indirect liability and damages in connection with the Material to the maximum extent permitted by the applicable law. NXP accepts no liability for any assistance with applications or product design. Materials may only be used in connection with NXP products. Any feedback provided to NXP regarding the Materials may be used by NXP without restriction.