Hard fault issue on flex case E (S32K344)

[kanteshbondla]

#19368

Hello Audesse Team,

We are encountering a hard fault issue in the S32K344-based Flex Case E platform with the Red Beet variant. After the fault occurs, the entire software freezes without any further progress. We suspect the issue might be related to the CAN main function read interrupt handler.

This problem only arises in a specific state during DC charging. Could you please guide us to diagnose and resolve this issue?

To assist with the diagnosis, I am attaching the Design Studio log captured previously on the debugging board during the hard fault.

Thanks and Regards,
Kantesh

• This topic was modified 1 week, 3 days ago by kanteshbondla.

Attachments:

You must be logged in to view attached files.

[Connor]

#19386

Hi Kantesh,

It does look like there is some forbidden operation happening in the CAN interrupt logic.

– Is the CAN traffic when you are in this specific state of DC charging?
– Are all of your CAN reads handled by interrupt or do you have a mix of polling and interrupt?
– While in this specific state of DC charging, are you running an operation that blocks for a long time, creates it’s own interrupts, or disables other interrupts?

[kanteshbondla]

#19387

Hi Connor,

– The CAN traffic remains largely unchanged during DC charging. In fact, it’s lower during DC charging compared to when in driving mode.
– All CAN reads are managed via polling.
– Yes, during this specific DC charging state, an operation is being executed. This operation is internal to the DC charging stack, where the VCU continually sends requests to the charger until a response is received.

• This reply was modified 1 week, 2 days ago by kanteshbondla.

[Author]

Posts