2333721_en-US

[#1]

[S32K566 SAF] MCU will be stucked in reset after bist test

Hi Teams

         Customer use SAF and found MCU will be always stucked in reset after bist. There is no way to boot MCU except power-off. so customer want to know the workaround way and route cause. But there are no any descriptions for this. 

Best Regards

Junjie 

Safety_SWRe: [S32K566 SAF] MCU will be stucked in reset after bist test

Hi @MariusC 

Thanks for your support.

• BSSM Contract:  No
• Customer Company*: PATAC
• Project Name*: Zonal Controller
• Customer Contact Point* (Name & Email): Liek Li  ([email protected])
• Software & Hardware Information: Customer is developing the safety feature based on S32k566 A0 sample 
• SW Package Info*: SW32K5_RTD_R23-11_0.8.0 + SW32K5_SAF_0.8.0_HF01_D2602
• HW* (Board/Chipset/Platform):S32K566 CVB
• SW Version*: 0.8.0

Best Regards

Junjie

Re: [S32K566 SAF] MCU will be stucked in reset after bist test

Hello @Junjie ,

Please provide the following information so we can help your customer better:

If you are supporting a Direct Customer, please provide:

• BSSM Contract: Yes / No
• Customer Company*:
• Project Name*:
• Customer Contact Point* (Name & Email):
• Software & Hardware Information:
• SW Package Info*:
• HW* (Board/Chipset/Platform):
• SW Version*:

*required

Re: [S32K566 SAF] MCU will be stucked in reset after bist test

Hi @Junjie 

The problem can have multiple causes at this early boot stage (e.g., BIST exit/restore not completing).

A possible cause is that a destructive reset event stays latched, so repeated resets hit the destructive reset escalation threshold (DRET), keeping the device in reset until a power‑on reset.

To pinpoint the root cause, the following register dumps/logs would be helpful, captured immediately after a reset cycle (hex values/screenshots).

• MC_RGM_DES (Destructive Event Status)
• MC_RGM_FES (Functional/External Event Status)
• MC_RGM_DRET, MC_RGM_FRET (escalation thresholds)

Re: [S32K566 SAF] MCU will be stucked in reset after bist test

Hi @DenisSas 

      MCU is repeat reset and debugger could not attach the MCU, except power-off. But once power-on, There is no signal on MC_RGM. you can also get this issue if run the SAF example in SAF driver.

Best Regards

Junjie

Re: [S32K566 SAF] MCU will be stucked in reset after bist test

Hi @Junjie,

Thank you for the clarification.

I’m continuing to investigate this behavior. At the moment I don’t have immediate access to an S32K5 board to reproduce the SAF example scenario, but I am reviewing the SAF initialization flow and the early reset sequence to understand why the MCU enters a reset loop before the debugger can attach.

Re: [S32K566 SAF] MCU will be stucked in reset after bist test

Hi @Junjie,

For s32k566, we are in contact with the Validation team, as the problem is also present on our side. There is a planned meeting with them on Monday, so i will come back with info afterwards.

Best regards,
Denis

Re: [S32K566 SAF] MCU will be stucked in reset after bist test

Hi @DenisSas 

Could I have some updates? Customer push us to close this ticket because customer is doing evaluate the boot time and optimize app boot process. Thank you!

Best Regards

Junjie 

Re: [S32K566 SAF] MCU will be stucked in reset after bist test

Hi @Junjie,

The issue is HW (errata for A0, LBIST CPE not working) and SW. I would not suggest trying to write BIST registers directly to make BIST work.
The roadmap would be waiting until the new release of SAF ZE 0.8.1, coming 29 May 2026. The functional demo comes separately next week from today. The fix means making it work without CPE.

Best regards,
Denis

Re: [S32K566 SAF] MCU will be stucked in reset after bist test

Hi @DenisSas 

      Thanks for your update, and could you please share more details about it? It is hardware issue or softeware configure issue or sbaf issue? customer want to configure the bist by writing bist registers directly to make bist work if it is not hardware issue and sbaf issue. For another question,Can we get the update roadmap?

Best Regards

Junjie

Re: [S32K566 SAF] MCU will be stucked in reset after bist test

Hi @Junjie ,

BIST execution time 8.3ms
Please be aware this is preliminary BIST exec. time as there is Errata for cut A0 where it is not possible to run LBIST for CPE, this will be fixed with cut B0.

On SAF side we are about to finish BIST execution in SAF Demo example running without LBIST5 and LBIST11 (CPE and HSE).

Regarding BootRom execution times with and without HSE, I'm waiting for response from architect.

Kind Regards,
Radoslav

Re: [S32K566 SAF] MCU will be stucked in reset after bist test

Hi @RadoslavB 

     Thanks for your update, It is really great helpfull to let customer evaluate the startup-time .

Best Regards

Junjie 

Re: [S32K566 SAF] MCU will be stucked in reset after bist test

Hi @Junjie,

The issue was found in the meeting, now the BIST owner is doing the necessary updates to make it work with the SAF demo example.

Thank you for your patience.

Regards,
Denis