S32K3 SPD BIST usage

[jinjingyang]

Hello, Sir,

I'm using S32K3 SPD (SAF) and tried to integrate the Bist component into an exmaple. (S32DS3.4 + SPD1.0.0).

In the SPD demo code, the eMcem_Init is called before Bist_Run is called.

According to "S32K3_SPD_BIST_UM" section "3.4.1  Self-Test prerequisities", FCCU reaction for all faults need be disabled. But in the demo code, FCCU reaction is enabled in eMcem_Init before calling Bist_Run.

Shall I move the eMcem_Init to somewhere after calling Bist_Run?

Another question is about the "S32K3_SPD_BIST_UM" section "3.3  On-line (Runtime) BIST configuration". It says " it is recommended to perform a reset at the end of the test sequence". I found that the MCU reset signal is asserted low immediately after triggering the BIST and the MCU reset signal stays asserted low for about 6msec before release. My understanding is the BIST is running with the MCU reset asserted and it takes about 6msec. Am I correct?

And there is no need to perform a reset at the end of the test sequence by user since the STCU automatically generate a self-test done functional reset?

Regards,
Jason Yang

[jinjingyang]

Hello, Martin,

After BIST is integrated into my application, the debug process becomes different.

Debugger can catch software functional reset. But the BIST ST_DONE functional reset cannot be caught by debugger.
And after BIST is executed, the debugger lost connection or synchronization with the MCU.

1) When I'm using Lauterbach T32 debugger, the MCU runs Bist_Run and ST_DONE reset occured. It looks like the debugger is still in communication with MCU, but all breakpoints are not working. I have to use sys.down and sys.attach to re-connect the debugger to MCU.
Is this expected impact of BIST?

2) When I'm using PE Multilink debugger, the MCU runs Bist_Run and ST_DONE reset occurred. The debugger lost synchronization with MCU. I have to use "restart" button to let MCU restart with a software functional reset. Is this expected behavior with BIST enabled?

[martinkaspar-r3]

1) We’re observing the same behavior in our tests

2) Sorry, we have no experience with PE Multilink debugger for the Bist testing

[martinkaspar-r3]

Hello,

We have verified with HW validation team and the note in Bist user manual is not correct (it is not applicable to S32K3). In K3xx devices there is only 1 domain and FCCU is lbisted, so no action is required from SW point of view for disabling the FCCU reaction. See also HW reference manual where this is documented:

Yes correct, there is no need to perform a reset by user as STCU will do it automatically. We will update the documentation to make it clear.