q/uzbek-plus
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
uzbek-plus/logs/b10/b10b5/W-10-cache-write.log
q 58dcb3d121 B10: battery charging — PM8916 LBC supervisor v4 (CHARGE/HOLD, FAULT safe clamp to 4.00 V) and persistent B10B-5 cache 
- LBC supervisor v1..v4 (linux/patches/b10b3-lbc-supervisor-v3.patch + b10/b10b3/lbc-v3-to-v4-fault-clamp.diff):
  CHARGING 4.20 V/450 mA -> HOLD 4.05 V after 60 min CV -> battery -> new cycle on USB insert; FAULT = VDD_MAX 4.00 V clamp
- RAM tests C/B/D/D2/D3/D4 (safety timer only ends fast charge), B10B-4 actuator audit (VDD_MAX works, USB_SUSP does not),
  B10B-5 FAULT clamp regression, production run, warm reboot via PON reboot reason
- cache = B10B-5 c3732515 (HW EDL write, readback + full partition verify), class-A persistent validation
- test-only hooks/images are not part of the production kernel; images with the AP PSK are not published
2026-10-04 19:00:27 +03:00

93 KiB
Raw Blame History

Qualcomm Sahara / Firehose Client V3.62 (c) B.Kerler 2018-2025.
main - Using loader firehose/007050e100000000_394a2e47cf830150_fhprg_peek.bin ...
main - Waiting for the device
main - Device detected :)
main - Mode detected: firehose
firehose
firehose - [LIB]: Host's payload to target size is too large
firehose
firehose - [LIB]: logbuf@0x0801D0A0 fh@0x08019F08
firehose
firehose - [LIB]: Sector size in XML 4096 does not match disk sector size 512
Progress: |██████████| 100.0% Write (Sector 0x3FF80 of 0x40000, ) 4.09 MB/s MB/s
Progress: |██████████| 100.0% Write (Sector 0x3FFA0 of 0x40000, ) 4.75 MB/s
Progress: |██████████| 100.0% Write (Sector 0x3FFC0 of 0x40000, ) 11.13 MB/s
Progress: |██████████| 100.0% Write (Sector 0x3FFE0 of 0x40000, ) 4.56 MB/s
Progress: |██████████| 100.0% Write (Sector 0x40000 of 0x40000, ) 10.85 MB/s
Wrote b10/b10b3/cache-v4/cache-extlinux-b10b5.img to sector 2133088.