The Nintendo Switch — Platform Overview and Fault Landscape

Section Overview

The volume's device work opens with a platform, not a repair — because a bench that knows how the Switch is built can place any symptom on the map before lifting a screwdriver (research-before-you-open-the-device). The architecture is a textbook portable power chain. A USB-C inlet feeds the M92T36 power-delivery controller, the BQ24193 charges the single lithium cell, and the MAX77620 PMIC fans the cell out into the rails that the processor lives or dies by (the-universal-tree-power-heartbeat-path). The processor side is three parts that work as one. The Tegra system on chip carries the CPU, GPU, and controllers on one die, flanked by its LPDDR4 RAM and by the eMMC storage that holds the operating system — and is married to this one console by unique encryption. Revisions change the repair. Original Erista, die-shrunk Mariko, the Lite, and the OLED are identified from model and board numbers before any part is ordered (finding-schematics-and-board-diagrams). The fault landscape has a center of gravity. The charging front end — port damage, dock-killed negotiators, shorted rails — dominates, with backlight, card reader, and liquid damage as the supporting cast. One instrument triages it all. A USB power meter inline on the charger sorts a dead console into one of three working hypotheses in thirty seconds. And the platform has its points of no return. The console-unique storage leads the list, and Chapter 1's assessment discipline writes the Switch-specific sheet (risk-assessment-before-repair). Chain, revisions, landscape, triage, irreversibles — the platform, mapped before the first repair.

Why This Matters

The Switch is the modern bench's most-requested handheld repair, and everything this section maps converts directly into faster, safer, cheaper work (research-before-you-open-the-device). This matters because the platform map is the diagnostic head start: a no-charge Switch is not a mystery — it is a fault somewhere on a five-stage chain this section names part by part, and the bench that knows the chain starts three questions ahead (the-universal-tree-power-heartbeat-path). This matters because revision mistakes waste money in both directions: an Erista part ordered for a Mariko board does not fit or does not work, and the difference is printed on the console and the board for anyone who knows where to look (finding-schematics-and-board-diagrams). It matters because the fault landscape is genuinely concentrated: one region — the charging front end — accounts for the bulk of dead-console intakes, which means two sections of this chapter repair what one region breaks, and the bench that masters that region masters most of the platform's grief. It matters because the triage is absurdly cheap: a USB power meter costs less than one misdiagnosis and sorts dead consoles into working hypotheses at intake, in front of the customer, before any quote. And it matters because the eMMC changes the stakes of everything nearby: board work near a chip that cannot be replaced by any donor is work near the console's identity, and the assessment sheet has to say so before the hot air comes out (risk-assessment-before-repair). Map the platform once, and every Switch that crosses the bench afterward arrives half-diagnosed.

Required Prerequisites

• Risk Assessment Before Repair — Chapter 1's verdict discipline, which this section applies to a specific platform: the Switch's hazards, irreversibles, and disclosure lines.
• The Universal Tree — Power, Heartbeat, Path — Volume 5's universal diagnostic tree, whose power-first logic this platform's triage and power chain make concrete.

Recommended Consumables

• A USB power meter — to read the charging conversation this section teaches you to interpret (the-universal-tree-power-heartbeat-path)
• A known-good USB-PD charger — ideally the official 15 V adapter — and a C-to-C cable — to make every current reading mean the console, not the accessories: a 5 V-only brick can never show negotiation, and misclassifies every healthy front end as stuck-low
• A printed Switch board photo per revision on the bench — to mark fault regions and part locations as they come up (finding-schematics-and-board-diagrams)
• The platform research folder from Chapter 1's method — to file model numbers, board numbers, and community threads where the next Switch finds them

Recommended Practice Hardware

• Any Switch — working or dead — to check every claim in this section against a real console (research-before-you-open-the-device)
• A second revision, if available — to practise telling Erista from Mariko, Lite, and OLED on real hardware
• A donor or parts board — to locate the M92T36, BQ24193, MAX77620, and eMMC packages without risking a customer unit (finding-schematics-and-board-diagrams)
• Community boardview or schematic on a second screen — to cross-reference every located part against its documented position
• A dead-console intake story from any repair forum — to practise placing a described symptom on the platform map before seeing the board

Real-World Applications

The platform map runs every Switch intake. A bench handed a console that died in a third-party dock goes straight to the front end — the dock generation that negotiated voltage badly is community-documented history, and the M92T36 region is checked before anything else is opened (research-before-you-open-the-device). A technician with a Switch that only charges when the cable is held at an angle reads it as the platform's signature mechanical failure — a worn or ripped USB-C port — and quotes the port replacement the next section teaches, with the meter confirming at intake. Someone facing a console that runs but shows nothing hears the game in the speakers, recognizes the backlight path rather than the power chain, and skips the front-end rabbit hole entirely (the-universal-tree-power-heartbeat-path). A shop ordering parts for a no-boot repair reads HAC-001(-01) off the case and Mariko off the board number before purchasing — because the two Tegra generations do not interchange (finding-schematics-and-board-diagrams). And a bench assessing water damage near the card reader writes the Switch-specific sheet: reader replacement is routine, but corrosion spreading toward the eMMC region raises the stakes to console-identity territory, and the owner hears that at intake (risk-assessment-before-repair). The failures this prevents: wrong-revision parts, front-end rabbit holes for backlight faults, quotes issued blind, and hot-air work near an irreplaceable chip that nobody priced.

Common Challenges

• The part numbers blur together. M92T36, BQ24193, MAX77620 — three alphanumerics with adjacent jobs — the difficulty dissolves when each is tied to its stage: the negotiator at the port, the charger at the cell, the rail-maker behind everything, in that order along the chain (the-universal-tree-power-heartbeat-path).
• Revision identification feels like trivia until it costs money. Erista and Mariko boards look alike at arm's length — the difficulty is making the check a reflex: model number off the case, board number off the board, before any part order or donor purchase (finding-schematics-and-board-diagrams).
• The meter reading tempts over-conclusion. A ~0.4 A reading narrows the search; it does not name a component — the difficulty is holding triage and diagnosis apart: the meter buys a working hypothesis, and Volume 5's evidence discipline still does the convicting.

Safety Notes

Risk Level: Low. This is a platform-study section — reading, mapping, and meter observation from outside the case — but the console it studies carries a lithium cell and an irreplaceable chip, and both shape the sections that follow.

Professional Tips Before Starting

• Put the meter on every intake. Thirty seconds inline on a known-good charger, in front of the customer — the reading anchors the quote and starts the case record with evidence (the-universal-tree-power-heartbeat-path).
• Photograph the board number at every opening. HAC-CPU-whatever, filed in the platform folder — it identifies the revision forever and feeds the document hunt (finding-schematics-and-board-diagrams).
• Keep one dead board as the bench's atlas. A scrap Switch board with the four famous parts labeled — it turns every community thread's 'top-left of the M92' into a place your eyes already know.

The Platform Map — Chain, Revisions, Landscape, Triage, Irreversibles

Recap and Frame

Chapter 1 built a preparation discipline that works on any device; this chapter aims it at specific ones, and the Switch goes first for three reasons (research-before-you-open-the-device). It is the repair bench's volume seller. No handheld crosses modern repair benches more often, which means every hour spent on its map repays weekly. It is the best-documented board of its kind. Schematics, boardviews, donor boards, and a decade of community fault threads exist for every revision — the document hunt that Chapter 1 taught has, for this platform, already been run by thousands of benches (finding-schematics-and-board-diagrams). And it is a teaching architecture. The Switch's power chain — inlet, negotiator, charger, cell, rail-maker, processor — is the same chain inside every USB-C portable this volume will touch; learn it here and the later chapters' laptops and phones are variations, not new subjects (the-universal-tree-power-heartbeat-path). The section's frame is map before repair. Nothing here fixes a console; everything here decides how the next two sections' fixes begin — which region, which hypothesis, which parts, which warnings on the assessment sheet (risk-assessment-before-repair). Hold the frame — one platform, mapped stage by stage, so every symptom that follows has an address.

The Power Chain — Inlet to Processor

Every portable lives on one chain, and the Switch's is worth learning by heart because this volume will meet it again and again (the-universal-tree-power-heartbeat-path). The inlet is mechanical first. The USB-C receptacle takes every insertion's wear and every trip-over-the-cable's leverage — it is soldered to the board through pins and pads that the next section will teach you to replace. The negotiator speaks before power flows. The M92T36 sits behind the port handling USB power-delivery negotiation — the conversation that decides whether the console gets 5 V at modest current or the 15 V fast-charge contract — and routing what arrives; when it dies, the console goes quiet at the port no matter what the charger offers. The charger manages one cell. The BQ24193 takes the negotiated input and charges the single lithium cell to its limits — current, voltage, temperature — and its health decides whether a console with a good port still fills its battery. The rail-maker feeds everything else. The MAX77620 power management IC takes the cell's voltage, fans it out into regulated rails — memory, storage, peripherals — and sequences the processor domain's supplies, which dedicated regulators beside it deliver; Volume 5's power-first tree starts its Switch walk here (the-universal-tree-power-heartbeat-path). The processor side is three parts working as one. The NVIDIA Tegra system on chip carries CPU, GPU, and system controllers on a single die, its LPDDR4 RAM beside it, and its eMMC storage holding the operating system — the trio that everything upstream exists to feed. Around the spine hang the limbs. Display and its backlight driver, the game-card reader, the microSD slot, wireless, audio, and the Joy-Con rails — each a branch off the map with its own fault stories (finding-schematics-and-board-diagrams). Inlet, negotiator, charger, cell, rail-maker, processor, limbs — one chain, learned once, recognized everywhere. Know the chain and every symptom acquires an address.

Revisions — Erista, Mariko, Lite, OLED

The Switch is four consoles wearing one name, and repair treats them as different boards (finding-schematics-and-board-diagrams). The original is Erista. The 2017 launch console — model HAC-001 — carries the original Tegra X1; it is the revision most community repair lore was written about, and the hungriest for battery. The refresh is Mariko. The 2019 HAC-001(-01) looks nearly identical outside but carries the die-shrunk, more efficient Tegra X1+ and revised board circuitry — the famous battery-life bump — and its parts are not interchangeable with Erista's where the silicon differs. The Lite trades the dock for the pocket. The HDH-001 integrates the controls, drops TV output, and shrinks the board — same chain, same famous ICs' jobs, tighter geometry and its own part numbers. The OLED is the premium refit. The HEG-001 carries the new panel, a revised board, and the same Mariko-generation silicon — beautiful screen, different display path, different teardown. Identification is a two-step reflex. The model number on the case back narrows the family; the board number printed on the mainboard — the HAC-CPU, HDH-CPU, HEG-CPU series — confirms exactly which board is on the bench, and both go into the case record before any part is ordered (research-before-you-open-the-device). What changes for repair is concrete. Part compatibility across the Tegra generations, battery and display part numbers, board layouts that move test points, and teardown differences the guide for the wrong revision will not warn about. Erista, Mariko, Lite, OLED — identified from case and board before money moves. Read the numbers first, and the wrong-part order never happens.

The Fault Landscape — Where the Platform Breaks

Every platform concentrates its failures somewhere, and the Switch concentrates them at the front of the power chain (research-before-you-open-the-device). The port takes the mechanical beating. Thousands of insertions plus the occasional yank leave worn, loose, or pin-ripped USB-C receptacles — the charges-only-at-an-angle console, the no-charge console with visible port damage — the platform's bread-and-butter repair and the next section's whole subject. The negotiator has a famous enemy. A generation of third-party docks and cheap cables negotiated power badly enough to kill M92T36 chips in numbers — a community-documented history any Switch bench inherits — and the dead-after-a-dock intake story still points there first. The front end also dies quietly. Shorted capacitors on the rails around the negotiator and charger, and BQ24193 failures that leave a working console unable to fill its cell — the board-level work of Section 2.3. The display path fails separately. A console that plays sound with a black screen is a backlight-path suspect — driver, connector, or panel — an entirely different map region from the power chain, and the triage that separates them costs one careful listen (the-universal-tree-power-heartbeat-path). The limbs have their own stories. Game-card readers fail from wear and liquid and are routinely replaced; microSD slots die mundanely; liquid damage goes wherever liquid went, with the card-reader region a common landing zone. And some famous faults belong to another chapter. Joy-Con drift is a controller ailment — Chapter 6's subject — and a bench keeps console and peripheral landscapes separate (risk-assessment-before-repair). Port, negotiator, quiet front-end deaths, backlight, limbs, and the drift that is not the console's fault — the landscape, by weight. Learn where the platform breaks, and intakes sort themselves.

The Thirty-Second Triage — What the Meter Says

Before any opening, a USB power meter inline between a known-good charger and the console sorts a dead Switch into a working hypothesis — and the charger must be USB-PD capable, ideally the official 15 V adapter on a C-to-C cable, because a 5 V-only brick can never show negotiation and misreads every healthy front end as stuck-low (the-universal-tree-power-heartbeat-path). Near zero is a silent front end. A reading around 0.00 A means no charging conversation is happening at all — a dead port, a dead M92T36, or a hard short on a rail pulling the handshake down — and the search starts at the front of the chain. Stuck low is a half-alive chain. A console that draws roughly 0.4–0.5 A at 5 V and never negotiates higher is showing a charger that works and a system that does not finish the deal — the fast-charge contract is not being agreed or the system is not booting to ask — and the hypothesis moves past the port toward the charger, rails, and boot path. A negotiated fast charge clears the front end. A meter showing the 15 V contract at an amp or more says the port, negotiator, and charger are earning their keep — and a console that is still dead is dead somewhere else: rails, processor domain, or display path. The numbers are classes, not convictions. Real consoles blur the boundaries — a cycling draw, a reading that shifts as the cell fills — and the meter's job is to hand Volume 5's method a starting region, not to name a component; the evidence discipline still does the convicting (research-before-you-open-the-device). The reading is intake evidence. Taken on a known-good charger and cable so the number means the console, logged on the case record, quoted from, and compared against after the repair (risk-assessment-before-repair). Zero, stuck-low, negotiated — three classes, thirty seconds, one working hypothesis before a single screw moves. Let the meter speak first, and the opening starts aimed.

Points of No Return — The eMMC and the Platform's Assessment Sheet

Chapter 1 taught the assessment in general; the Switch fills in the blanks with unusually sharp answers (risk-assessment-before-repair). The eMMC leads every list. The storage chip holds the operating system and is married to this one console by unique encryption — no donor board's chip substitutes, and no fresh chip restores a stock console without the console's own keys and backup — so its failure is not a part swap, it is the console's identity at stake: a failing eMMC is backed up while it still reads, and every hot-air job in its neighborhood is priced like the console it is. The battery is an adhesive job with a temper. The cell is glued in place — its removal is a Section 1.4 adhesive-softening task with lithium's full Volume 2 rules, and its planned disconnect leads every teardown. The board work has blast radii. Rework at the M92T36 and BQ24193 happens near small passives and, more importantly, on the same board as the irreplaceable chip — the assessment marks the regions and the skill bar before the job is accepted (research-before-you-open-the-device). Revision traps are assessment items too. A donor purchase or part order made before the board number is read is money gambled on a coin flip — the identification step goes on the sheet as a control, not a hope (finding-schematics-and-board-diagrams). The disclosure lines write themselves. 'Board-level work near the storage carries a small risk to the console's data and identity' is an intake sentence; 'adhered battery, replacement priced in if it deforms' is another — both spoken before work, per the last section's rule. The eMMC's marriage, the glued cell, the rework blast radii, the revision traps, the intake sentences — the Switch's sheet, written once, reused every intake. Assess the platform once on paper, and every console after inherits the discipline.

Common Mistakes

• Ordering parts before reading the board number. Erista and Mariko do not interchange where the silicon differs — model number off the case, board number off the board, then money (finding-schematics-and-board-diagrams).
• Chasing the power chain for a backlight fault. Sound with a black screen is the display path, not the front end — one careful listen separates two map regions (the-universal-tree-power-heartbeat-path).
• Reading the meter as a verdict. ~0.4 A narrows the region; it convicts nothing — triage hands the method a hypothesis, and the evidence still does the convicting.
• Treating the eMMC as a part. It is the console's identity, encrypted to this board alone — back it up while it reads, and price nearby work accordingly (risk-assessment-before-repair).
• Skipping the accessory control. A reading taken on the customer's questionable cable means nothing — known-good charger and cable, every intake, so the number means the console.

Troubleshooting Guidance

The platform walk runs identify, meter, map, then open under Chapter 1's rules. If a Switch arrives dead: known-good charger, meter inline, thirty seconds — near zero says front end, stuck-low says half-alive chain, negotiated fast charge says look past the front end (the-universal-tree-power-heartbeat-path). If it charges only at a cable angle: the port's mechanical wear is the platform's signature — inspect the receptacle and quote the next section's repair. If it died in or after a third-party dock: the community's M92T36 history applies — front end first, with the documented dock generations in mind (research-before-you-open-the-device). If it runs with a black screen but plays sound: backlight path — driver, connector, panel — not the power chain. If the fault is drifting sticks: that is Chapter 6's peripheral landscape, not this board's. If parts are about to be ordered: stop — model number, board number, revision confirmed against the community's documents first (finding-schematics-and-board-diagrams). If the job involves heat or probing near the storage: the assessment sheet speaks — eMMC backed up while it reads, blast radius priced, owner told at intake (risk-assessment-before-repair). If liquid is involved: map where it went — card-reader region is routine, eMMC neighborhood is identity territory — and let the corrosion's geography set the quote. The throughline: identify the revision, let the meter pick the region, place the symptom on the map, and open only with the sheet written.

Verification & Testing Methods

Confirm the platform map is real knowledge before the repairs begin:

• [ ] I can trace the Switch power chain from memory — inlet, M92T36 negotiation, BQ24193 charging, cell, MAX77620 PMIC rails, and the Tegra system on chip with its RAM — and say what each stage does and what its failure looks like.
• [ ] I can identify Erista, Mariko, Lite, and OLED from model and board numbers, and I check both before any part order or donor purchase.
• [ ] I can classify a dead Switch from the meter — near-zero, stuck-low at 5 V, or negotiated 15 V — into a region hypothesis with a next step, on a known-good USB-PD charger and C-to-C cable, without over-concluding.
• [ ] I can place the platform's common faults on the board map — port wear, dock-killed negotiators, quiet front-end shorts, backlight path, card reader, liquid — and I know which famous fault belongs to the controllers chapter instead.
• [ ] I treat the eMMC as the console's identity — backed up while it reads, its neighborhood priced like the console — and I can write the Switch's assessment sheet: glued cell, rework blast radii, revision traps, and the intake disclosure lines.

Then try the practice exercises below — desk and meter work; scenarios differ from the quiz.

Practice Exercises

1. Drill the revisions (5 minutes, desk). From memory, list the four revisions with their model-number families and Tegra generations; then take three real or forum-sourced consoles and identify each from case and board numbers, noting one repair-relevant difference per revision — which parts, which teardown, which expectations (finding-schematics-and-board-diagrams).
2. Draw the chain (5 minutes, desk). Sketch the power chain from USB-C inlet to processor — port, M92T36, BQ24193, cell, MAX77620, system on chip, RAM, eMMC — annotating each stage with its job and its signature failure; then locate all four famous packages on a donor board or board photo against a community boardview (the-universal-tree-power-heartbeat-path).
3. Run the triage table, then place two intakes (5 minutes, meter and any Switch). With a known-good USB-PD charger, a C-to-C cable, and the meter, read a real console — working or dead — and classify it; write the three-class table from memory: reading, hypothesis region, next step for each; then take two forum intake stories — one with a backlight-pattern symptom, one involving liquid — and place each on its board-map region from the described evidence alone, noting which limb or chain stage each lands on (research-before-you-open-the-device).
4. Write the platform's assessment sheet (5 minutes, desk). Produce the Switch-specific Section 1.5 sheet: the eMMC's marriage and its backup rule, the glued cell's adhesive plan and lithium handling, the rework blast radii near the front end, the revision-check control, and the two intake disclosure sentences an owner hears before board-level work (risk-assessment-before-repair).

These core steps — the power chain, revision identification, the meter triage, the fault map, and the platform's assessment sheet — are tested in the Chapter Quiz at the end of this chapter, where a score of 80% is required to continue.

Key Takeaways

• The Switch is a textbook portable power chain — inlet, M92T36 negotiator, BQ24193 charger, cell, and the MAX77620 PMIC feeding the Tegra system on chip and its LPDDR4 RAM — and every symptom on the platform has an address somewhere on that chain (the-universal-tree-power-heartbeat-path).
• The platform is four consoles wearing one name — Erista, Mariko, Lite, OLED — identified from the case's model number and the board's number before any part order, because the Tegra generations do not interchange (finding-schematics-and-board-diagrams).
• The fault landscape concentrates at the charging front end — worn ports, dock-killed negotiators, quiet shorts — with the backlight path, card reader, and liquid damage as the supporting cast, and Joy-Con drift belonging to the controllers chapter entirely (research-before-you-open-the-device).
• The thirty-second meter triage sorts any dead Switch into three classes — near-zero (silent front end), stuck-low at 5 V (half-alive chain), negotiated 15 V (look elsewhere) — as a working hypothesis for the method, never a conviction.
• The eMMC is the platform's hardest point of no return — married to its console by unique encryption, replaceable by no donor — so it is backed up while it still reads, its neighborhood is priced like the console, and the Switch's assessment sheet leads with it (risk-assessment-before-repair).

Skills Learned

• You can now trace the Switch's power chain from inlet to processor — port, M92T36, BQ24193, cell, MAX77620, system on chip, RAM, and eMMC — and say what each stage does.
• You can now identify a Switch's revision from its model and board numbers and state what that revision changes for parts and repair.
• You can now classify a dead Switch from a USB power-meter reading into one of three triage classes, each with its next diagnostic step.
• You can now place the platform's common faults — front-end, backlight, card reader, liquid — on the board map before opening the console.
• You can now write the Switch-specific assessment: its points of no return, led by the console-unique eMMC, and its hazard and disclosure notes.

Glossary Additions

• system on chip — a single integrated circuit that carries what once took a motherboard's worth of parts: CPU cores, graphics, memory controllers, and system peripherals on one die. In the Switch it is the NVIDIA Tegra X1 (original 'Erista' consoles) or the die-shrunk, more efficient Tegra X1+ ('Mariko' revisions, including the Lite and OLED) — a distinction with hard repair consequences, since parts do not interchange across the generations. For the bench, the system on chip is the power chain's destination: everything upstream — port, negotiator, charger, PMIC rails — exists to feed it, its RAM sits beside it as separate packages, and board-level work in its neighborhood carries the platform's highest stakes.
• PMIC — power management integrated circuit: the chip that takes a device's single supply — in a portable, the battery — and fans it out into the multiple regulated rails the rest of the board drinks from: core voltage, memory, storage, and peripheral rails, sequenced in the right order at power-on. The Switch's main PMIC is the MAX77620, sitting between the cell and the Tegra system on chip; when a console has a good port, a charging cell, and still no life, Volume 5's power-first tree walks its rails next. A PMIC failure mimics many other deaths — which is exactly why the platform map places it explicitly on the chain rather than leaving it a mystery stage.
• eMMC — embedded MultiMediaCard: a soldered-down flash storage package — controller and NAND in one chip — that acts as a portable device's internal drive. The Switch's eMMC holds the operating system and is married to its specific console by unique encryption: no donor board's chip substitutes, and no blank chip restores a stock console without the console's own keys and backup — which makes it the platform's hardest point of no return. The bench's rules follow directly: a failing eMMC is backed up while it still reads, every hot-air or probing job in its neighborhood is priced like the console itself, and liquid damage spreading toward its region converts a routine quote into an identity-of-the-console conversation at intake.

Suggested Next Sections

Must read next:

• Replacing the Switch's USB-C Charging Port — Section 2.2 repairs the platform's most-broken part: reading port damage, choosing the replacement, and the board-safe hot-air and soldering sequence that swaps the receptacle without collateral damage.

Recommended:

• Research Before You Open the Device — the research discipline this platform map is a worked example of: bench records, community knowledge, and documents gathered before the first screw.
• Finding Schematics and Board Diagrams — the document hunt that, for the Switch, has already been run by thousands of benches: where this platform's schematics and boardviews live and how to read them.