Hello, Sir,
In S32K3_SPD_BIST_UM.pdf, chapter 3.1 Supported BIST configurations, there are the following two options: BIST_SAFETYBOOT_CFG and BIST_DIAGNOSTIC_CFG.
The difference between the two is confusing to me.
BIST_SAFETYBOOT_CFG:
Safety Boot configuration is supposed to be triggered from the custom bootloader/startup code that follows BootROM - HSE firmware execution Table 3-[1]. It affects the main reset domain (RD0) Table 3-[1], it means end of the execution is followed by the functional reset.
BIST_DIAGNOSTIC_CFG:
Diagnostic configuration contains every single BIST available on the platform. It is designed for the "garage" use case. It means, this configuration is supposed to be running only when no other (or just limited number) of jobs are in progress on the chip (execution time of this configuration is longer then 10 ms which is required for the startup BIST configuration. The results of the DIAGNOSTIC selftest can be evaluated after the STCU2 functional reset.
Switching the description for these two options, there is no conflicts.
"BIST_SAFETYBOOT_CFG" contains every single BIST, and it should run when no other jobs in progress, and its result can be evaluated after ST_DONE reset.
The only difference might be the execution time short vs long.
Could you please advise the difference between the two configurations?
Hi Jason,
The validation and verification team creates BIST_SAFETYBOOT_CFG as a compromise which takes less than 10 ms and still has sufficient coverage. This configuration is recommended for the startup use case.
BIST_DIAGNOSTIC_CFG includes all the BIST available on the platform. Execution time is longer than 10 ms, which is a timeslot for the startup BISTs. It mean this configuration can be run in garage or don’t need to be run at all.
Hope I it helps.
Regards,
NaveenM