Safety documentation for sCheck integration

[AlexAlba]

• Device: NXP S32K388 microcontroller
• Components: SAF Package -  SW32K3_SAF_1.0.6_HF01_D2603, sCheck plugin ( SRAM ECC test)
• Available artifacts: S32K3xx Reference Manual (S32K3XXRM_Rev12_2025_11_11.pdf / S32K3XXRM 1_fullReferenceManual.pdf, sCheck UserManual, sCheck SRAM ECC test source code.
• Gap: lack of end-to-end tehnical specification, device register mapping, dependecny interactions and expected outcomes.
• Release Note : specifies that following release has limitations

Information requested:

• Precise safety goal(s) and ECC scheme assumed
• Which SRAM instances/banks/partitions are in scope and out of scope on S32K388
• Step-by-step flow including initialization, fault injection method, verification, and restoration
• Required operating conditions (clock, MPU/XRDC settings, caches/TCM state, run-from-RAM/Flash)
• Cross-plugin preconditions/postconditions; example initialization sequence across components
• Version compatibility matrix for SAF/sCheck/eMcem/SafetyBase on S32K388
• Pass/fail criteria, result codes, and how to interpret them
• Interrupts, NMI, or error reporting paths used; hooks/callbacks for application-level handling

[petervlna]

Hello,

For sCheck integration, please refer primarily to the sCheck User Manual, especially the chapter"Software Integration". This chapter contains the integration requirements, assumptions, memory section definitions, linker file updates, MPU configuration requirements, and any test-specific prerequisites.

In addition to the sCheck User Manual, please review the corresponding S32K3 Safety Manual, which identifies the safety mechanisms covered by sCheck (SM2.*.SCHECK) and explains their role within the overall safety concept.

The SAF documentation package also contains module-specific integration guidance for the other SAF components (sBoot, mSel, eMCEM, BIST, etc.). The integration requirements are therefore distributed across the SAF module User Manuals rather than being collected in a single standalone safety integration document.

As a minimum, we recommend reviewing:

sCheck User Manual → Software Integration
sCheck User Manual → Conditions, Limitations and Side Effects
S32K3 Safety Manual → safety mechanisms covered by SAF/sCheck
SAF integration documentation for linker, MPU, startup, and API integration requirements

These documents provide the information required to integrate sCheck into a safety application.

Best regards,

Peter