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).
998 B
998 B
B7C c3 — INVALID (not a class-A cold boot; boot interrupted). Nothing touched on the board.
- UART: board (c2b Linux) alive until 13:38:13 (MM debug lines), first SBL1 Start 13:38:27.9 → off ≈ 14 s, not ≥ 90 s.
Three SBL1 starts in 6 s (13:38:27.9, 13:38:29.1, 13:38:33.7 = fastboot entry attempts), fastboot 13:38:34.5,
fastboot boot10:38:35 UTC rc=0. - Linux: RTC at boot 1277 s → class B. EMMC-RO 30/30, /firmware mounted ro at 13:38:41.5 — then the UART went completely silent (logger alive, .raw stops at the same byte).
- Host: NCM never appeared; ~3 min later the board is in lk fastboot again (lsusb 18d1:d00d) with no UART trace of that reset → UART RX/GND most likely disturbed during handling, and the board was reset into fastboot again (RESET held) after 13:38:41.
- Operator: "в fastboot попал не с первой попытки, конструкция неудобная". Driver now prints the RTC-based class right after NCM comes up.