S32G3 RDB3 board LLCE CAN Innitial fail

[jiajun]

Hi:

    Recently I started to learn how to use LLCE, I imported the routines of the optical amplifier into S32DS, but the initialisation failed in "Can_43_LLCE_IPW_Init", according to my previous experience of debugging peripherals, the official routines usually don't have any problems, please help me to analyse what's wrong with me; my environment: S32DS 3.5 / RTD 4.0.2 / LLCE 1.0.8;One more question, I see inside the forum, people's questions about LLCE are basically under Linux, is LLCE not supported by M core at the moment?

S32G-VNP-RDB3 S32G3 

[Daniel-Aguirre]

Hi,

Are you using any NXP reference board? Also, are you using any LLCE example?

We understand that the M core is still being supported under the LLCE-FW.

Please, let us know.

[jiajun]

Hi, @Daniel-Aguirre 

I am currently using the S32G-VNP-RDB3 development board and an example of use is the following screenshot;

[Daniel-Aguirre · Accepted solution]

Hi,

Thanks for your feedback. For the available defects under LLCE v1.0.8, we don't see any of them referring to initialization problems. Have you modified anything under the example? Have you changed the properties of the project?

One of the reasons for the initialization to fail is changing the optimization level to None, have you changed the optimization level?

Please, let us know.

[Redder]

For anyone else who has this issue - if you need to set the optimization level to -O0 for any reason (debugging, for example), it looks like you can work around it by using -O0 combined with -fsection-anchors. You can further reduce the impact by only applying -fsection-anchors to driver files, basically anything that includes *MemMap.h. My findings are that the custom toolchain "#pragma GCC section" flags don't interact well with -O0.