q 8d7721c775 B7: add network time bootstrap and persistent B7C cache

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).

2026-10-02 20:18:25 +03:00

2.5 KiB

Raw Permalink Blame History

R3A — autonomous cold boot → LTE: PASS

2026-10-02. One clean run. CH340 TX→RX disconnected, UART read-only, no fastboot, no manual commands until START OK. Power-off ~11:54 (≥ 90 s, ~2 min), on 11:56 battery → USB.

Class

PM8916 RTC at boot = 3 s (setting system clock to … (3)) → class A (full PMIC reset). SBL1 pm_device_init Δ 11254 µs, pm_driver_init Δ 10522 µs (class A range).

Timeline (host clock / board uptime)

Step	Time	Evidence
SBL1 Start	11:56:14 (UART buffered)	r3a-uart-markers.txt
lk eMMC	`MMC card: H4G2a`, HS200, `Done initialization of the card`	no CMD2/CID error
lk	`Trying to boot 't4'`
Linux	7.2.7-aurora-bam1; `EMMC-RO-SUMMARY devices=30 all_ro=YES`
NCM up / telnetd	uptime 6.99 / 7.01 s; host first ping OK 11:56:26.97	no ping loss after that (139 OK)
B1_OK=1, aurora-modem start	uptime 9.15 s
MSS running / QMI / SIM	9.92 / 12.97 / 13.04 s	3× DeviceNotReady on online SET — expected, retried by design
DMS online	16.30 s
Registered Beeline 250-99, PS attached	23.25 s (7.0 s after online)	PCI 55, TAC , EARFCN 1275, RSRP −99, RSRQ −15
MM modem detected	64.08 s (40.3 s after MM start)	slowest step
Bearer connected	75.18 s; START OK in 66.0 s at 11:57:31.5	service rc=0

Power-on → working LTE ≈ 77 s.

State after boot (telnet, read-only)

usb0 172.16.42.1/24, route to 172.16.42.2 via usb0; telnetd pid 615.
controller BEARER_CONNECTED; MM: connected, lte, home, Beeline, signal 67 %.
wwan0 10.41.212.24/28 gw .25, MTU 1500; DNS 10.10.22.3, 194.186.191.1.
Routes via wwan0: /32 to 77.88.8.8, 1.1.1.1, both DNS (no default route — by design).
ping -I wwan0 77.88.8.8 3/3 (~56 ms), 1.1.1.1 3/3 (~51 ms).
DNS: 10.10.22.3 resolves ya.ru (A + AAAA); 194.186.191.1 timed out (secondary DNS — note, not a criterion fail).
lifecycle FAIL/rollback/lost count = 0; dmesg-errs 0; rmtfs writes 0; eMMC writes 0.
/etc/resolv.conf absent (controller does not write it).

Notes (not failures)

lk MMC card failed to respond, try for SD card at [100] — second SDHC (SD slot) probe after eMMC is done; present on normal boots.
Board clock 1970 (not set) — HTTPS not tested in R3A.

Files

r3a-meta.txt, r3a-uart.log (copy of logs/uart/r3a-20261002-115402.log), r3a-uart-markers.txt, r3a-host-ping.txt, r3a-nm.txt, r3a-snap.cmds, r3a-telnet-snapshot.txt, host-ping-observer.sh.

2.5 KiB Raw Permalink Blame History Unescape Escape