EivoTech Laptop & Mobile Repair Master Course
Part 12 — USB, USB 2.0, USB 3.x aur USB-C Complete Mastery
Chapter 12: USB Port Power, Data aur USB-C Charging ka Complete System
Laptop repair mein USB faults bohat common hain:
USB port bilkul dead
USB mein 5V nahi
5V hai lekin device detect nahi
Pendrive detect hoti hai lekin USB 3 speed nahi
Mouse work karta hai lekin external HDD nahi
USB port short hai
USB-C se laptop charge nahi hota
USB-C se data chalta hai lekin charging nahi
Charging hoti hai lekin display output nahi
USB-C port ek side se kaam karta hai, doosri orientation se nahi
Type-C charger connect karne par 5V hi milti hai, higher voltage negotiate nahi hoti
USB repair ko samajhne ke liye humein power aur data ko separate dekhna hoga.
1. USB Kya Hai?
USB:
Universal Serial Bus
USB ka use hota hai:
Data transfer
Power supply
Keyboard
Mouse
Pendrive
External HDD/SSD
Phone connection
Camera
Audio devices
Charging
Display adapters
Aur USB-C mein additional advanced functions.
2. USB mein Power aur Data Separate Hain
Ye sabse important concept hai.
USB port par:
Power present hona
aur
Data working hona
do different cheezen hain.
Example:
Pendrive light ON ho rahi hai.
Iska matlab:
USB power aa rahi hai.
Lekin agar computer pendrive detect nahi karta:
Data section fault ho sakta hai.
3. Traditional USB Port ka Basic Flow
Simplified:
5V Rail
↓
Fuse / Load Switch
↓
USB VBUS
↓
USB Device
Data side:
CPU / PCH / SoC USB Controller
↓
Protection / Filter
↓
USB Connector
↓
USB Device
4. USB VBUS Kya Hai?
VBUS USB ki main power line hai.
Traditional USB ports mein commonly:
5V
supply hoti hai.
Ye connected device ko power provide karti hai.
5. USB Port par 5V Kahan Se Aati Hai?
Motherboard par 5V source:
↓
USB power switch / load switch
↓
Current protection
↓
USB connector VBUS
Controller USB port ko power ON/OFF kar sakta hai.
6. USB Power Load Switch
USB port ko direct main 5V rail se connect karne ke bajaye load switch use kiya ja sakta hai.
Iska kaam:
Port power control.
Current limiting.
Short-circuit protection.
Over-temperature protection.
Fault reporting.
7. Load Switch ke Common Pins
IC ke according:
VIN
Input power.
VOUT
USB output.
EN
Enable.
GND
Ground.
OC# / FLG#
Overcurrent/fault indicator.
Exact names datasheet-specific.
8. USB Port Dead — Example
Suppose:
Main 5V = 5V
Load switch VIN = 5V
Load switch EN = HIGH
Load switch OUT = 0V
Port rail ground ke against normal.
Then:
Load switch fault stronger suspect.
9. Enable Missing Example
VIN = 5V
EN = 0V
OUT = 0V
Is case mein load switch ko replace mat karo.
Trace:
Enable signal kahan se aana chahiye?
EC?
PCH?
Power state logic?
10. USB Short Protection
Agar USB connector ke andar:
VBUS aur ground short ho jaye
to load switch protection activate kar sakta hai.
Result:
Sirf us port ki 5V off.
Ya multiple shared ports off.
11. One USB Port Dead, Baqi Work
Possible:
Individual fuse/load switch.
Connector damage.
ESD protection fault.
Data-line issue.
Broken track.
12. All USB Ports Dead
Possible:
Main USB 5V rail missing.
Common power switch.
PCH/SoC USB controller problem.
BIOS/firmware.
Power state issue.
Software/driver.
13. USB 2.0
USB 2.0 data ke liye main differential pair:
D+
D-
use hota hai.
Ye two wires data communication karti hain.
14. USB 2.0 Basic Connector
Traditional USB 2.0 Type-A mein basic lines:
VBUS
D-
D+
GND
15. D+ aur D- Differential Pair
D+ aur D- ek pair ke taur par data carry karte hain.
USB controller voltage difference ko interpret karta hai.
In lines ko random voltage apply nahi karna.
16. 5V Present but USB Device Not Detected
Possible:
D+ open.
D- open.
ESD component short.
Connector pin damaged.
PCH/SoC USB port fault.
Software/driver.
USB device itself faulty.
17. USB D+ / D- par Multimeter
Unpowered board par:
Diode/resistance comparison useful ho sakti hai.
Especially known-good same board available ho.
But universal diode value yaad mat karo.
18. D+ ya D- Ground Short
If one data line abnormal direct ground short:
Device detect fail.
Possible:
ESD protector.
Connector damage.
PCH/SoC internal damage.
Corrosion.
19. ESD Protection
USB connector external world se connected hota hai.
Static discharge motherboard ko damage kar sakti hai.
Isliye D+/D- ke paas:
ESD protection array
mil sakta hai.
20. ESD Component Fail
Possible:
D+ short.
D- short.
Both lines abnormal.
USB detect nahi.
Port intermittent.
Removing/replacing any protection component should only follow confirmed diagnosis; protection should be restored with a correct replacement.
21. USB Connector Physical Fault
Common:
Bent VBUS pin.
Broken data pin.
Loose connector.
Cracked solder.
Corrosion.
Plastic damage.
Foreign metal.
Microscope inspection first.
22. USB 3.x Kya Hai?
USB 3.x USB 2.0 se higher-speed communication support karta hai.
USB 3 port mein:
USB 2 D+/D-
ke saath additional:
SuperSpeed TX/RX pairs
hoti hain.
23. USB 3 Port mein Do Data Systems
Ye important hai.
USB 3.x port par:
USB 2.0 D+ / D-
USB 3.x SuperSpeed differential pairs
dono ho sakte hain.
Isliye:
USB 2 device work kar sakta hai.
Lekin USB 3 speed fail ho sakti hai.
24. USB 3 SuperSpeed Lines
Simplified:
TX+
TX-
RX+
RX-
High-speed differential pairs.
Exact generation/lane architecture interface ke according.
25. USB 2 Works, USB 3 Doesn't
Strong direction:
SuperSpeed path problem.
Possible:
Connector pins.
TX/RX pair.
Coupling capacitor.
ESD/filter.
PCH/SoC SuperSpeed controller.
26. USB 3 Device USB 2 Speed par Chalna
If SuperSpeed link fail:
Device sometimes USB 2 fallback kar sakta hai.
Symptoms:
Detect hota hai.
Transfer slow.
USB 3 indicator absent.
27. High-Speed Coupling Capacitors
USB SuperSpeed TX lines par coupling capacitors ho sakti hain.
Agar one open/missing:
SuperSpeed link fail ho sakti hai.
28. Common-Mode Choke
USB 3 high-speed lines par filtering component:
Common-mode choke.
Purpose:
Noise reduce.
Signal integrity.
EMI control.
Open internal line:
SuperSpeed failure.
29. USB Speed Generations
Technician ko naming confusing lag sakti hai.
Basic idea:
USB 2.0 = lower-speed D+/D- system.
USB 3.x = additional SuperSpeed lanes.
Modern naming marketing ke saath change hoti rahi hai, isliye diagnosis mein actual controller/link capability dekho, sirf printed name nahi.
30. USB Controller Kahan Hota Hai?
Older architecture:
PCH.
Modern:
CPU/SoC ke andar integrated ho sakta hai.
Isliye all USB data failure mein platform controller suspect ho sakta hai, lekin external circuits pehle check karo.
31. USB Power aur Controller Separate Fault
Example:
Port mein 5V nahi.
Lekin D+/D- controller perfectly okay ho sakta hai.
Ya:
5V present.
Data controller dead.
Isliye separate diagnosis.
32. USB Overcurrent Signal
Load switch fault detect kar ke:
OC#
OVC#
FAULT#
signal EC/PCH ko de sakta hai.
Platform affected port disable kar sakta hai.
33. Overcurrent False Trigger
Possible:
Fault resistor.
Bad switch.
Short connector.
Corrosion.
Fault signal line issue.
Port 5V repeatedly off/on.
34. External HDD USB Port par Nahi Chalta
Mouse works.
Pendrive works.
External HDD fails.
Possible:
USB port current capability problem.
High-resistance connector.
Load switch current limiting early.
Cable.
External drive.
Power drop under load.
35. Voltage Drop under USB Load
No-load:
5.0V.
Device connect:
Voltage significantly collapse.
Possible:
Weak load switch.
High-resistance fuse.
Damaged connector.
Power rail issue.
36. USB-C Kya Hai?
USB-C ek reversible connector standard hai.
Important:
USB-C connector shape hai.
USB-C ka matlab automatically:
Fast charging.
Thunderbolt.
Display.
USB 4.
sab available nahi.
Capabilities laptop design par depend karti hain.
37. USB-C Reversible Kyun Hai?
Connector ko dono orientations mein lagaya ja sakta hai.
Iske liye duplicate/mirrored contacts aur orientation detection system hota hai.
38. USB-C ke Important Signals
USB-C connector mein possible:
VBUS.
GND.
CC1.
CC2.
USB 2 D+/D-.
SuperSpeed TX/RX.
SBU1/SBU2.
Depending implementation.
39. CC1 aur CC2
CC:
Configuration Channel
USB-C system mein bohat important.
CC lines use hoti hain:
Cable orientation detect.
Source/sink role.
Current capability indication.
USB Power Delivery communication.
40. USB-C Plug Orientation
Ek orientation mein:
CC1 active.
Doosri orientation mein:
CC2 active.
Controller identify karta hai cable kaunsa way connected hai.
41. USB-C One Side Works, Other Side Doesn't
Strong possible direction:
CC1/CC2 problem.
Connector contact damage.
One mirrored data lane issue.
ESD/protection.
USB-C mux.
42. USB-C VBUS
USB-C connection ke initial stage mein typical default VBUS:
5V
ho sakti hai.
Higher voltages Power Delivery negotiation ke baad mil sakti hain.
43. USB Power Delivery — PD
USB PD:
Power Delivery
Source aur sink electronically communicate karke power contract decide karte hain.
Laptop charger aur laptop agree karte hain:
Voltage.
Current capability.
Power level.
44. USB-C Charger Connect Karte hi 20V Kyun Nahi?
Because system pehle safe default state se start karta hai.
Simplified:
Cable connect
↓
CC detection
↓
5V default VBUS
↓
PD communication
↓
Laptop higher power request karta hai
↓
Charger approve karta hai
↓
Higher negotiated voltage
45. PD Voltages
USB PD systems different power profiles support kar sakte hain.
Common examples historically:
5V.
9V.
15V.
20V.
Newer extended ranges bhi exist karti hain.
But technician ko actual charger/laptop PD specification check karni chahiye.
46. 20V Fixed Rule Nahi
Har USB-C laptop 20V par charge nahi hota.
Exact negotiated voltage:
Laptop design.
Charger.
Battery/system state.
PD revision/profile.
ke according.
47. PD Controller Kya Hai?
USB-C laptop mein dedicated:
PD Controller
ho sakta hai.
Ye handle karta hai:
CC detection.
PD communication.
Power role.
Cable orientation.
VBUS control.
Protection.
Alternate modes.
48. PD Controller Manufacturers
Various IC vendors USB-C/PD controllers banate hain.
Specific laptop mein exact IC part number schematic/datasheet se identify karo.
49. USB-C Charging Basic Flow
USB-C Charger
↓
CC1/CC2 Detect
↓
PD Controller
↓
Negotiation
↓
VBUS MOSFETs
↓
System/Charging Circuit
↓
Main Rail / Battery
50. VBUS MOSFETs
USB-C power path par MOSFETs use hote hain:
VBUS isolation.
Reverse-current protection.
Source/sink control.
Overvoltage protection.
Power-path control.
51. USB-C Port par 5V Hai, Laptop Charge Nahi
Possible:
PD negotiation fail.
CC line problem.
PD controller.
VBUS path MOSFET.
Charging controller.
Insufficient charger power.
Cable incompatibility.
Firmware.
52. 5V Present but No Higher Negotiation
Check conceptually:
CC detection.
Correct charger/cable.
PD controller power.
PD communication.
Controller reset/firmware.
VBUS sensing.
System requesting higher contract?
53. USB-C Cable bhi Important Hai
All USB-C cables same capability nahi.
Some:
Basic charging.
High-current support.
USB 2 data only.
SuperSpeed.
Display/Thunderbolt.
different capabilities.
Known-good correct-rated cable diagnosis ke liye important.
54. USB-C Charger Wattage
Laptop may require:
45W.
65W.
90W.
100W.
or other.
Underpowered charger:
Slow charging.
No charging under load.
Warning.
Performance limitation.
55. USB-C CC Line Damage
Possible:
No charger detection.
No PD negotiation.
Only one plug orientation works.
No data role detection.
No charging.
56. CC Line Protection
CC1/CC2 external connector lines hain.
Protection/filter components ho sakte hain.
ESD damage CC line short/open kar sakti hai.
57. CC Lines ko External Voltage Mat Do
CC lines sensitive control/communication lines hain.
Random voltage injection controller damage kar sakti hai.
Use schematic, diode/resistance comparison aur normal powered measurements.
58. USB-C SBU Lines
SBU:
Sideband Use
Alternate modes mein auxiliary signals carry karti hain.
Example applications:
DisplayPort AUX-type routing depending implementation.
Not normally USB 2 data path.
59. USB-C Alternate Mode
USB-C connector other protocols carry kar sakta hai.
Common example:
DisplayPort Alternate Mode
USB-C port se external display output possible.
60. USB-C Data Works but Display Doesn't
Possible:
Port supports no DP Alt Mode.
SBU/mux issue.
High-speed lanes.
Display mux.
PD/alt-mode controller.
Firmware.
Cable.
61. USB-C Display Works but Charging Doesn't
Display data path and power-delivery path partly separate hain.
Possible:
Charging IC.
VBUS MOSFET.
PD power contract.
Cable/charger wattage.
62. USB-C Charging Works but Data Doesn't
Possible:
D+/D-.
SuperSpeed lanes.
USB mux.
Connector.
PCH/SoC USB controller.
Charging path separately okay.
63. USB-C MUX Kya Hai?
Connector reversible hai.
High-speed signals ko orientation ke according route karna hota hai.
Iske liye:
High-Speed MUX
use ho sakta hai.
64. MUX ka Kaam
Connector orientation A:
Lanes route one way.
Orientation B:
MUX routes appropriate lane mapping.
If mux fault:
One orientation failure.
No SuperSpeed.
No display output.
65. Retimer / Redriver
High-speed USB-C/Thunderbolt systems mein:
Retimer
ya
Redriver
use ho sakta hai.
Purpose:
High-speed signal quality restore/improve.
Fault:
USB high-speed unavailable.
Display issue.
Thunderbolt issue.
66. Thunderbolt
Thunderbolt USB-C connector use kar sakta hai, lekin every USB-C port Thunderbolt nahi.
Thunderbolt architecture includes high-speed PCIe/display capabilities and dedicated controller/retimer depending generation.
67. USB4
USB4 USB-C connector ecosystem ka advanced high-speed protocol hai.
Repair logic mein external path:
Power.
CC.
High-speed lanes.
Controllers.
Retimers.
Firmware.
important rehte hain.
68. USB-C Port Board Inspection
Microscope se check:
Bent contacts.
Burnt VBUS pins.
Corrosion.
Foreign material.
Cracked solder.
Connector shell movement.
Missing ESD components.
69. USB-C Connector mein Bohat Dense Pins
Direct live probing risky.
Adjacent pins short ho sakte hain.
Prefer:
BoardView se test points.
Protection components.
Resistors.
VBUS fuse.
CC resistors.
70. USB-C VBUS Short
If VBUS line ground ke against short:
Charger may protect/shut down.
Possible:
TVS/OVP device.
Input capacitor.
MOSFET.
PD/power-path IC.
Charging circuit.
71. USB-C OVP
OVP:
Over-Voltage Protection
USB-C VBUS path mein protection IC ho sakta hai.
It prevents abnormal charger voltage from reaching system.
72. OVP Fault
Possible:
5V port par present.
OVP output 0V.
Enable/control correct.
No downstream short.
OVP switch fault suspect.
73. VBUS Path Example
USB-C connector VBUS:
5V initial
↓
Protection/OVP
↓
Input MOSFET
↓
Charging/system circuit
After negotiation voltage change ho sakti hai.
74. USB-C Laptop Completely Dead
If laptop supports only USB-C charging:
Start:
Known-good correct PD charger.
↓
Known-good capable cable.
↓
Port inspection.
↓
Initial VBUS.
↓
CC1/CC2.
↓
PD controller supply.
↓
PD negotiation.
↓
VBUS path.
↓
Main system rail.
↓
3V/5V standby.
75. USB-C 5V Present, Main Rail 0V
Possible:
PD contract not established.
Power-path switch off.
Charging IC not accepting input.
OVP fault.
System protection.
76. Higher PD Voltage Present but Laptop Still Dead
Now USB-C negotiation has at least progressed.
Check:
VBUS after protection MOSFET.
Main system rail.
Charging controller.
3V/5V ALW.
77. USB-C No VBUS at All
Possible:
Charger/cable issue.
CC detection fail.
Port damage.
Severe VBUS short causing charger protection.
PD source behavior.
First test correct known-good charger/cable and unpowered board resistance where appropriate.
78. USB-C Charger Cycling
Charger repeatedly connects/disconnects.
Possible:
VBUS short.
PD negotiation failure.
Power-path protection.
CC intermittent.
Connector issue.
Controller reset loop.
79. USB-C Current Meter / PD Meter
Technician-compatible USB-C PD analyzer can be useful to see:
Negotiated voltage.
Current.
PD state/profile.
But meter interpretation alone final diagnosis nahi.
80. PD Meter Shows 5V Only
Could mean:
Laptop only requesting 5V at that moment.
PD communication missing.
Cable issue.
PD controller.
Charger doesn't support required profile.
Do not immediately replace PD IC.
81. PD Meter Shows 20V but 0A
Could indicate:
Power contract established.
System not drawing current.
Possible power-path open or laptop downstream not starting.
Need board measurements.
82. PD Meter Shows Voltage Collapsing
Possible:
Short.
Overload.
Protection cycle.
Bad cable/connector.
Charging input fault.
83. USB-A Charging Port
Traditional USB-A port phone charging mein special data resistor schemes/protocols use kar sakta hai.
But laptop USB port repair mein first:
5V + D+/D- + power switch
diagnose karo.
84. Always-On USB Port
Some laptops one USB port laptop off state mein bhi phone charge kar sakta hai.
It may use:
5V ALW.
Special load switch.
EC control.
So power-state behavior port-specific.
85. USB Port Laptop Off mein 0V — Fault?
Not always.
Some ports only S0 state mein powered.
Always-on port different.
Schematic/power state check karo.
86. USB Wake
USB keyboard/mouse laptop ko wake kar sakta hai if platform supports/enabled.
Requires standby USB-related power and controller logic.
87. USB Port Causes Laptop Not to Boot
Possible:
VBUS short.
Data line severe short into PCH/SoC.
Damaged connector bridging lines.
Load switch fault.
Remove external device and inspect port.
88. Broken USB Port Pins Touching
Bent VBUS pin touching ground:
Port short.
Bent VBUS touching data:
Can damage USB controller.
Physical inspection critical.
89. Customer Says "USB Dead"
First ask/test:
No power?
No data?
Only one device?
Only USB 3?
Only charging?
All ports?
This classification diagnosis ko fast karta hai.
90. USB Fault Classification
Type A — No Power
Check VBUS.
Type B — Power but No Data
Check D+/D- or SuperSpeed.
Type C — USB 2 Works, USB 3 Fails
Check SuperSpeed path.
Type D — Intermittent
Connector/cable/solder/power.
Type E — USB-C No Charge
Check CC/PD/VBUS path.
91. USB 2 Diagnostic Flow
Known-good USB device.
↓
Port VBUS 5V.
↓
Connector physical condition.
↓
D+/D- ESD/filter.
↓
D+/D- comparison.
↓
PCH/SoC/controller.
↓
Software/driver if hardware okay.
92. USB 3 Diagnostic Flow
USB 2 function works?
YES
Then:
SuperSpeed connector pins.
↓
ESD/filter.
↓
Coupling components.
↓
TX/RX pairs.
↓
MUX/retimer if present.
↓
PCH/SoC.
93. USB-C Charging Diagnostic Flow
Step 1
Correct charger/cable.
↓
Step 2
Connector inspection.
↓
Step 3
Initial VBUS.
↓
Step 4
CC1/CC2 behavior.
↓
Step 5
PD controller power/reset.
↓
Step 6
Negotiated VBUS.
↓
Step 7
Protection/OVP.
↓
Step 8
Power-path MOSFETs.
↓
Step 9
Main rail.
↓
Step 10
Laptop charging controller / standby rails.
94. USB-C Data Diagnostic Flow
Power works?
↓
USB 2 D+/D-?
↓
SuperSpeed lanes?
↓
Connector orientation?
↓
MUX?
↓
Retimer/redriver?
↓
SoC/PCH controller?
95. USB-C One Orientation Fault Flow
Plug Side A:
Works.
Plug Side B:
Fails.
Strong focus:
CC1 vs CC2.
Mirrored connector contacts.
MUX orientation.
One set of high-speed lanes.
Physical connector damage.
96. USB-C Port Replacement
USB-C connector replacement advanced microsoldering task hai because:
Dense contacts.
Ground tabs.
Multilayer pads.
High-speed traces.
Heat management.
Wrong alignment se board damage possible.
Professional hot-air/preheater technique aur magnification required hoti hai.
97. USB-C Pad Damage
Port ripped off:
Pads/tracks break.
Before repair:
Schematic/boardview se each missing connection identify.
High-speed lines especially sensitive to trace geometry.
98. High-Speed Trace Jumpers
USB 2 D+/D- repair relatively forgiving ho sakti hai.
USB 3/USB-C SuperSpeed differential lanes high-frequency sensitive hoti hain.
Long random jumper wires signal integrity destroy kar sakti hain.
Advanced high-speed board repair requires controlled routing.
99. USB-C PD Firmware
Some PD controllers programmable firmware use karte hain.
Corrupt firmware:
No charging.
No display mode.
Port malfunction.
But firmware write only exact board/controller procedure se.
100. PD Controller vs Charging IC
Do not confuse.
PD Controller
USB-C negotiation/role/CC manage karta hai.
Charging IC
Adapter/system/battery charging power manage karta hai.
Kuch modern systems mein functions partly integrated ho sakte hain.
101. USB-C Power Flow Example
Charger
↓
USB-C Connector
↓
CC Detection
↓
PD Controller
↓
Power Contract
↓
VBUS Protection
↓
Input MOSFET
↓
Charging Controller
↓
Main System Rail
↓
Battery/System
102. Traditional Barrel Jack vs USB-C Difference
Barrel Jack
Adapter output voltage already fixed.
Example ~19.5V.
Input circuit immediately sees it.
USB-C
First detection/communication.
Then negotiated voltage.
So USB-C fault diagnosis mein communication stage extra hai.
103. USB-C and Battery Removed
Some laptops require specific system/battery conditions for expected PD behavior.
Do not assume every board behaves identically with battery removed.
Use service information where available.
104. Static Electricity Risk
USB data/CC lines sensitive hain.
Use proper ESD-safe work setup when handling boards and connectors.
105. USB Port Schematic Search Terms
Search:
USB
USB2
USB3
D+
D-
USB_DP
USB_DN
VBUS
USB_PWR
OC#
USB_EN
106. USB-C Search Terms
Search:
TYPEC
TYPE-C
CC1
CC2
PD
VBUS
SBU
MUX
TCPC
USBC
PORT_CONTROLLER
107. TCPC Kya Hai?
TCPC:
Type-C Port Controller
USB Type-C/PD system controller ko refer kar sakta hai.
Host system ke saath communication kar ke port state manage karta hai.
108. BoardView USB Strategy
First locate:
Connector.
Power switch/fuse.
ESD protection.
D+/D- filter.
SuperSpeed protection.
CC resistors/protection.
PD controller.
Mux/retimer.
Then CPU/PCH side only if necessary.
109. USB Port Diagnostic Worksheet
Laptop Model: __________
Board Number: __________
Port Type: USB-A / USB-C
USB 2 Works: Yes / No
USB 3 Works: Yes / No
VBUS: __________
Power Switch VIN: __________
Power Switch EN: __________
Power Switch OUT: __________
OC#/Fault: __________
D+ Reading: __________
D- Reading: __________
Connector Condition: __________
Known-Good Device: __________
Final Fault: __________
110. USB-C Diagnostic Worksheet
Port: __________
Charger Wattage: __________
Cable Type: __________
Initial VBUS: __________
Orientation A: __________
Orientation B: __________
CC1: __________
CC2: __________
PD Controller VCC: __________
Negotiated Voltage: __________
OVP Input: __________
OVP Output: __________
Main Rail: __________
Charging Status: __________
Data Status: __________
Display Alt Mode: __________
Final Fault: __________
111. Case Study 1 — USB Port 0V
Main 5V present.
Load-switch VIN = 5V.
EN = HIGH.
OUT = 0V.
Port unplugged and output rail not shorted.
Load switch stronger suspect.
112. Case Study 2 — 5V Present, Mouse Not Detected
Mouse gets power.
D+ line abnormal short to GND.
Disconnect protection device path and compare using schematic.
ESD/data path fault possible.
113. Case Study 3 — Mouse Works, USB 3 SSD Slow
USB 2 functionality okay.
SuperSpeed not linking.
Check:
USB 3 connector contacts.
SuperSpeed TX/RX path.
Filters/coupling.
Controller.
114. Case Study 4 — USB-C Charger 5V Only
Laptop requires PD higher voltage.
Correct charger and cable confirmed.
Check:
CC lines.
PD controller.
PD controller supply/reset.
Communication conditions.
115. Case Study 5 — USB-C 20V Negotiated, Laptop Dead
PD section at least negotiating.
Check:
OVP output.
Input MOSFETs.
Main rail.
3V/5V standby.
Don't replace USB-C port just because laptop dead.
116. Case Study 6 — One USB-C Orientation Works
Orientation A:
Charging + data okay.
Orientation B:
Nothing.
Focus:
Connector pins.
CC1/CC2.
Orientation mux.
Mirrored lane path.
117. Case Study 7 — Charging Works, USB Data Dead
VBUS/PD okay.
Focus:
D+/D-.
SuperSpeed.
Mux.
PCH/SoC.
118. Case Study 8 — USB Data Works, No Charging
Data path okay.
Focus:
PD power contract.
VBUS power path.
Charging controller.
Charger wattage.
119. Case Study 9 — Port Gets Very Hot
Immediately disconnect external power.
Inspect:
Shorted connector.
VBUS protection.
Load switch.
Physical metal bridge.
No repeated power tests until short is understood.
120. Case Study 10 — All USB Ports Work in BIOS but Not Windows
Strong direction:
Driver/software/OS configuration.
Motherboard hardware less likely.
121. Case Study 11 — USB Doesn't Work in BIOS or Windows
Hardware/firmware/platform controller becomes stronger suspect.
Check power/data circuits first.
122. Case Study 12 — USB-C External Monitor Works, USB Device Doesn't
Display Alt Mode path works.
USB data path can still be separate.
Check USB D+/D- / SuperSpeed routing and mux configuration.
123. USB Repair Golden Rules
1. USB power aur USB data ko separate diagnose karo.
2. 5V present = USB port fully healthy nahi.
3. USB 2 D+/D- aur USB 3 SuperSpeed separate paths hain.
4. ESD protector common data-line fault point hai.
5. USB-C connector shape capability guarantee nahi karta.
6. CC1/CC2 USB-C detection ke liye critical hain.
7. USB-C higher voltage negotiation ke baad aati hai.
8. PD controller aur charging IC same cheez nahi.
9. One orientation failure mein connector/CC/mux strong suspects hain.
10. High-speed data lines par random voltage/jumpers use mat karo.
124. Part 12 Quick Revision
USB
Universal Serial Bus.
VBUS
USB power line.
D+ / D-
USB 2 differential data pair.
SuperSpeed
USB 3.x high-speed data path.
Load Switch
USB port power control/protection.
ESD
Static-discharge protection.
USB-C
Reversible connector.
CC1 / CC2
Type-C configuration channels.
USB PD
Power Delivery negotiation system.
PD Controller
Type-C charging/power-role controller.
PER Orientation
CC1/CC2 and mux determine cable orientation.
SBU
Sideband Use signals.
MUX
Reversible high-speed signal routing.
Retimer
High-speed signal quality restoration.
125. Part 12 ka Sabse Important Lesson
USB fault aate hi ye 3 questions poochho:
1. Port ko power mil rahi hai?
2. USB 2 data work kar rahi hai?
3. High-speed / USB-C functions work kar rahe hain?
USB-C charging ke case mein:
Cable Connect
↓
CC Detection
↓
PD Negotiation
↓
VBUS
↓
Protection / MOSFET
↓
Charging Circuit
↓
Main Rail
Agar kisi stage par process ruk jaye:
Usi stage ko diagnose karo.
Ye approach tumhe random USB controller, PD IC ya charging IC replace karne se bachayegi.
Part 12 Complete
Next — Part 13: Audio Circuit Complete Mastery
Part 13 mein hum cover karenge:
Audio codec kya hai.
Speaker amplifier.
Internal speakers.
Headphone jack.
Microphone.
Digital microphone.
Analog microphone.
Codec power rails.
I2S / HDA audio communication.
Speaker enable.
Speaker amp power.
Headphone detect.
Mic bias.
No sound.
One speaker dead.
Headphone works but speaker doesn't.
Speaker works but headphone doesn't.
Mic not working.
Crackling/noisy sound.
Audio device BIOS/Windows mein missing.
Aur complete CPU/PCH se speaker aur microphone tak audio signal flow.
0 Comments