S32G2 LLCE CAN Receive Interrupt fail using QSPI boot from M7 core

[Ganesh_Pawar]

Hi NXP Team,

      The mail is regarding the LLCE CAN reception failure from the M7 core and the query is as follows:

a) S32G2 processor is used with RTD 4.0.0 , LLCE v1.0.5 SDK using S32DS 3.5 ,

In the debug mode , both LLCE CAN transmission and reception data is observed and captured.

b) Upon loading of the IVT binary of the same project, upon QSPI boot  , the CAN transmission packets are captured  ,

but the CAN Reception packets/Interrupts are not observed for the same code tested in debug mode.

This is a very strange observation , we cannot suspect whether it is regarding the LLCE firmware or the IVT issue .

Please look into this as a priority and revert back with your inputs if there is any dependency to be taken care .

Thanks and regards

Ganesh Pawar 

[Ganesh_Pawar]

Hi Daniel,

 a) "Is this behavior happening under an NXP reference board? Or it is under a custom board?"

  we are using S32G274A series in a custom board, considering RDB2 board as reference. 

 b) "Also, is this happening under the NXP examples? Or is it under a different code?"

This is an example from the NXP RTD 4.0.0 for S32G2 series supported SDK .

c) "can you help us elaborate more on the following comment:

"but the CAN Reception packets/Interrupts are not observed for the same code tested in debug mode."

How are you able to observe this behavior if you are not in debug mode? "

As per the NXP documents the IVT binaries are created and flashed to QSPI using S32 Flash Tool, selecting boot mode as M7 core.

Using the uart implementation, the received can data is printed in the terminal once the received interrupt is hit, using this method we had validated the received frames in debug mode using S32 debugger probe.

Once the IVT binary is flashed and upon boot, we are observing that CAN transmission frames, but CAN reception is not observed with multiple trials.

I hope you have understood the procedure and problem statement, do revert back with your inputs on this.

Thanks and regards,

Ganesh Pawar

[Daniel-Aguirre]

Hi,

Thanks for your feedback. For the information you have provided, we understand that, even if you are using an NXP example as a base, you are modifying the example itself. Also, even if your board takes RDB2 as a base, it is still a custom board.

Since we do not have the same project as the one you have and this is related to a custom board, help us create a ticket under the NXP online services, in which help us share the project you are working with, for the respective team to provide the required support.

We do apologize for the inconvenience.

Please, let us know.

[Daniel-Aguirre]

Hi,

Is this behavior happening under an NXP reference board? Or it is under a custom board?

Also, is this happening under the NXP examples? Or is it under a different code?

Also, can you help us elaborate more on the following comment:

"but the CAN Reception packets/Interrupts are not observed for the same code tested in debug mode."

How are you able to observe this behavior if you are not in debug mode?

Please, let us know.