FCCU fault EMCEM_FCCU_MTR_REPAIR_ERROR root cause confirm

[Shenghao]

Hi NXP,

Customer bring up M core only (BL doesn't load A core ATF image) and there is a FCCU fault triggered.

According to the flow chart from S32G RM, EMCEM_FCCU_MTR_REPAIR_ERROR occur before software invloving.

Does it mean there is a hardware design issue in customer's platform.

Or is there more document for FCCU fault clarify?

Thanks.

[Shenghao]

Hi Daniel,

They use S32G274A on their design with multicore booting by refering AN13750.

Below are their test summary, they check FCCU fault by observing register.

CASE1 - M core only (Boot loader doesn't load A core ATF image)
Result: EMCEM_FCCU_MTR_REPAIR_ERROR fault occur.

CASE2 - A+M core (A core boot up to uboot)
Result: EMCEM_FCCU_CM7_1_LOCKUP and EMCEM_FCCU_MTR_REPAIR_ERROR fault occur.

CASE3 - A+M core (A core boot up to kernel)
Result: EMCEM_FCCU_CM7_1_LOCKUP and EMCEM_FCCU_MTR_REPAIR_ERROR fault occur.
According to the attached (memory_repare_flow_chart) FXC found the EMCEM_FCCU_MTR_REPAIR_ERROR happens before SW involve.

The FCCU fault map has delviered before.

Thanks.

[Daniel-Aguirre]

Hi,

Thanks for your feedback.

We are not seeing the same behavior as your customer.

We have followed AN13750 and can successfully enable M7_0 under CASE1. We have used a blink example to verify the M7_0 execution after the bootloader.

EMCEM is related to SPD/SAF packages, which are not used under the AN13750.

Can you provide more information on how your customer is following AN13750?

If you require a private channel, you can open a ticket under the NXP online services.

Please, let us know.

[Shenghao]

Hi Daniel,

Apologies for missing to add the SPD version they use, it is SPD 1.9.0 HF01.

I'll try private channel to update it.

Thanks.

[Daniel-Aguirre]

Hi,

Thanks for the feedback.

Still, AN13750 does not talk about the usage/integration of SPD/SAF packages. Have they followed the guide without adding these packages and the result was as expected?

Please, let us know.

[Daniel-Aguirre]

Hi,

Which S32G variant is your customer using? Are they using an NXP reference board?

Also, we may not understand, is the Fault "EMCEM_FCCU_MTR_REPAIR_ERROR" happening to the customer? Or is it a supposition?  How does the customer know which FCCU fault is happening?

Is the customer using an NXP provided example? Which boot interface are they using (SD/QSPI or DEBUG)?

As for more information on regards of the Faults inside the S32G, depending on the variant, there is a *.xlsx file attached to the Reference Manual, which can be seen with a pdf reader that can look into the attached documents on a pdf:

Please, let us know.