Helloqiuju ye,
I would like to answer your question:
Yes, I know Lin module in MCAL4.3 do not ingegrate a LinStack like S32DS sdk, but if I want to use MCAL to develop S32K14X instead of S32DS sdk, whether need to have a LinStack like S32DS sdk?
[Hung] The LinStack just a upper layer of the LinDriver. So I cannot say that you need or do not need the LinStack. It is base on your application. The LinStack support to send the Frame as the schedule, transport layer, diagnostic frame, .... by provide APIs which mention in the Lin_specification_2.2A. But the LinDriver just support basic feature as send/receive,.. frame and application want to have schedule table, transport layer,... . It is needed to have a LinStack or application need to handle by itself.
if need, shuold transplant LinStack in S32DS sdk or use FSL_LIN_2.X_STACK without S32K1xx series supported, which methode is better? if no need a lin stack, whether have any lin examples for reference?
[Hung] If you want to porting the LinStack for the MCAL 4.3, from my point of view, porting from LinStack in S32SDK is better, but I think it will not easy to porting it.
For the example which use the lindriver of MCAL4.3, I just have a simple example which can send/receive frame(do not have schedule, transport layer,......)
Best regards,
Hung.