8d7721c775
B7A: QMI DMS time vs VNIIFTRI NTP (DMS = UTC - 0.28 s, sigma 1 ms; NITZ = DMS truncated to 1 s). B7B: a 1970 -> 2026 date -s step is harmless for the modem stack. B7C: aurora-modem probes DMS/NITZ along the start flow and steps CLOCK_REALTIME once at the first valid sample (REG registered/attached), never RTC; background SNTP check (query only) after START OK. 3/3 class-A cold boots PASS (residual +0.04/+0.36/+0.84 s), cache 14fe453a written (B7C_WRITE_VERIFIED) and verified by a normal power-on (V1, +0.26 s). Also publishes the prerequisite R2 (boot-hang / lk eMMC investigation, T4 telnet baseline that B7C builds on) and R3 (autonomous cold boot, NCM loss) material, and extends tools/publish-sanitize.py to r2/, r3/, b7/. Binary images, initramfs, busybox and raw logs stay out (see b7/*/SHA256SUMS).
823 B
823 B
B7C c4 — INVALID (three starts in 47 s; the B7C boot was cut after 2.5 s). Nothing touched on the board.
- Power-off: fastboot gone 15:59:03 UTC → first SBL1 16:01:59 UTC → off ≈ 176 s (OK).
- Start 1 (16:01:59): RESET not seen by lk → normal autoboot of the eMMC cache t4 image. RTC 3 s = class A. aurora-modem (t4, no B7C) reached MPSS_RUNNING.
- Start 2 (16:02:20, ~21 s later; operator retry): pm_driver_init 7564 µs, lk fastboot →
fastboot bootb7c 16:02:22 rc=0. RTC 25 s (no new POR: RTC kept counting from start 1). - Start 3 (16:02:45, ~2.5 s after EMMC-RO of start 2; operator retry): lk fastboot again. Board waits in fastboot since then. Driver aborted (no NCM).
- Cause: no feedback to the operator whether fastboot was reached; each retry was a short reset, not a ≥ 90 s power-off.