CC1 / CC2
Attach and PD negotiation activity. Exact levels depend on role and protocol state.
Trace charging from the connector through Type-C detection, protection, charger/sub-PMIC, system rail, battery path, NTC logic and fast-charge negotiation.
Visualizes the diagnostic path only; exact rails and IC names vary by board.
Unknown fields stay unknown. The engine should not invent missing measurements.
The uploaded source separates Type-C PD, QuickCharge and legacy USB profiles. AIFlasher keeps those as different diagnostic paths.
Protocol-specific bench interpretation will appear here.
Compare CC1 and CC2 at the receptacle, protection path and Type-C/PD controller. A one-sided fault can leave VBUS present while attach/PD behavior fails in one orientation.
Modern Android boards may split charger, main-system and performance/display power domains across multiple ICs.
Enter measured voltage, GR and signal state at each stage. The matrix highlights where the path first diverges from the selected reference profile.
| # | Stage | Expected Voltage | Measured V | Expected GR | Measured GR | Signal / State | Verdict |
|---|
Source-derived generic references are labelled as baselines. Exact model-specific data should override them.
| Rail / Signal | Origin | Expected Voltage | GR / Diode | Resistance | Role | Evidence Note |
|---|
IC-specific references are kept separate from generic Android data. The first integrated family is BQ25601 / BQ25601D from your uploaded source.
Keep deep bench tools available without forcing the technician through another long page.
Normal simulated divider state.
Attach and PD negotiation activity. Exact levels depend on role and protocol state.
Transaction activity is stronger evidence than a static pull-up voltage.
Switching activity helps separate disabled charger logic from power-stage faults.
Relevant for legacy and some QC negotiations; protocol implementation varies.
VBUS → attach → OVP → charger/sub-PMIC input → control bus.
Check CC/DPDM, enable, NTC/BATT_ID, battery path and charger state.
Verify actual battery current, gauge/BMS, thermal inputs and system load.
Separate cable/source, negotiation, charger limit and battery-temperature restrictions.
Connector/FPC, VBUS droop, thermal limit, BMS reset or protocol retry.
Identify the exact rail and compare GR/Ω before controlled localization.