LLCE Flexray

[PXH1]

Hello,

I want to implement LLCE Flexray function on S32G2. My versions are S32G_LLCE_1_0_6 and SW32G_RTD_4.4_S32CC_4.0.10. Add LLCE Flexray functionality to projects that already implement LLCE CAN and LLCE LIN functionality;

In EB configuration, the Fr_43_LLCE and FrIf modules and routines are the same.

The LLCE0_INT3_IRQn interrupt is enabled on the interrupt module.

Call the LLCE Flexray routine after initializing the LLCE CAN, and LLCE LIN functions：

 In the while loop, the get state is always FR_POCSTATE_DEFAULT_CONFIG.

After debugging step by step, it is found that the Fr_43_LLCE_ControllerInit() function fails to write instructions, resulting in a timeout.

What is the cause? I can do something about it.

[Daniel-Aguirre]

Hi,

We understand that this is a custom application, is this correct? Have you verified if you were able to run the NXP LLCE FlexRay example? From our side we don't see any problems with initializing the FlexRay part of the LLCE.

Also, are you using any NXP reference board? Or is this a custom board?

Please, let us know.

[PXH1]

Hi,

We tried it on both the development board and the homemade board, using an application that had no features other than LLCE functionality

We think it may have nothing to do with the hardware, and guess that the LLCE driver Flexray part is not used properly.

For the example program, we use S32G_LLCE_1_0_6, which has no Flexray routines

[Daniel-Aguirre]

Hi,

Thanks for your feedback. We apologize for our comments, it is true that under LLCE v1.0.6 the FR examples were missed. We do apologize.

Given that under LLCE v1.0.6 there are no FR examples, we can recommend moving to LLCE v1.0.7 since an example for FlexRay is provided under it. The overall initialization scheme made under the FlexRay examples is provided below:

Please, let us know.

[PXH1]

hello,

It is not convenient for us to change LLCE v1.0.6 to LLCE v1.0.7

So we changed the configuration of the Fr module in our EB to the same routine as LLCE v1.0.7. And changed our initializer according to the initialization of the routine, but the effect is still the same as before, no change, is I overlooking something?

[Daniel-Aguirre]

Hi,

Thanks for your feedback. For the application you have, we understand that there are several modules being used which cannot help us isolate the possible cause for this behavior.

Can you help us isolate only the FlexRay functionality under your application? Similar to the code we are showing. 

We also understand that your application itself cannot be migrated to LLCE v1.0.7, but you should be able to confirm if you are able to reproduce the behavior with LLCE v1.0.7 under the available examples. This for us to understand if the problem is indeed with the NXP drivers/firmware.

Please, let us know.

[PXH1]

hello,

We mask the other features and just run Flexray and LLCE v1.0.7 routines as shown. The following diagram shows all the functions we have running so far, but the phenomenon remains the same

[Daniel-Aguirre]

Hi,

Thanks for your feedback.

We might be misunderstanding this last request. Were you able to use the LLCE v1.0.7 example? This since the code does not seem to be the one provided by NXP.

Given that LLCE v1.0.7 is the one that provides an example, we recommend using it to understand if the example works out-of-the-box. At the end, your application is a custom application and configurations might be missing, that is why we would like to use the same base example to understand the behavior.

As told before, we are unable to reproduce the outcome, we do apologize.

Please, let us know.

[css71]

Do you have FlexRay LLCE example code for S32DS 3.5?

NXP  S32G_LLCE_1_09 package is not possible to configure components and compile it.