[masarray]

Root cause and operator goal

The firmware's SV AUTO phase-valid gate was permanently false; even a correctly disciplined sample clock could never advertise a measured smpSynch=1. Operators need direct PTP On → SMV Start for vendor-neutral IEC 61850 relay testing, not dialogs or manual flag workarounds.

Change

• Add platform-independent SvLocalSyncEvidenceGate: canonical SV hardware descriptor timestamps must remain coherently near integer PTP seconds across two adjacent 16-second comparisons (three actual observations), within ±4µs, with matching source/session/fault generations, no missed slots or stalled descriptor.
• Independent GPTimer↔EMAC observer must concurrently report software tracking and ≤4µs combined phase/read uncertainty. Eligible only in SOURCE mode, while fresh (≤17 SV epochs); no global synchronization claim.
• Connect the gate to smpSynch=AUTO: qualify local value 1 only when the measurements support it; revoke on STOP, PTP role change/stop, failed canonical TX, missed samples, discontinuity, stale evidence and loss of software phase.
• Keep real-time ISR unchanged. Common-case 4kHz work unchanged until qualification; only when local-qualified, verify PTP SOURCE live generation per frame to prevent a stale wire claim.
• Add negative/positive hardware-evidence gate tests; document hardware/relay acceptance.

Validation contract

CI PTP Core GCC/Clang/MSVC; guarded ESP32-P4 SOURCE (phase servo + sparse hardware stamp enabled, broadcast mirror OFF), RECEIVER and default SMV build. This is an experimental M3 branch. The 4µs software/egress admission values are conservative implementation thresholds, not a universal standards tolerance. Without physical MAC phase measurements no claim that these gates can actually promote on a board, nor an alarm-free SIPROTEC relay. No vendor-specific wire hacks and no new GUI warnings or dialogs.

[chatgpt-codex-connector]

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review	Status	Commit	Review trigger
📝 Code Review	⚠️ Failed 2026-10-17T12:19:23.247889Z	8e2faba	PR opened

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

[chatgpt-codex-connector]

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.
To continue using code reviews, you can upgrade your account or add credits to your account and enable them for code reviews in your settings.