Sega SG-1000¶
Sega's first console (1983), launched the same day as the Famicom in Japan. Classic 8-bit hardware (Z80 + TMS9918A) and the direct ancestor of the Master System: its games run on the Mark III and the Japanese Master System.
Identification¶
| Field | Value |
|---|---|
| Manufacturer | Sega |
| Release | 1983 (Japan) |
| Generation | 3rd (8-bit) |
| Models | SG-1000 · SG-1000 II · SC-3000 (computer) · Mark III (1985) |
| Media | Cartridge + Sega My Card (via Card Catcher) |
Architecture¶
| Block | Chip | Clock | Role |
|---|---|---|---|
| CPU | Zilog Z80A | 3.58 MHz | (part rated for 4 MHz) |
| Video | Texas Instruments TMS9918A | 256×192, 16 colours, 32 sprites | |
| Sound | Texas Instruments SN76489AN (PSG) | 3 voices + noise | |
| Memory | 1 KB RAM + 16 KB VRAM | (SC-3000: 2 KB RAM) | |
| Media | ROM cartridge + My Card | 51 cartridge games, 29 on My Card |
The TMS9918A and SN76489 were very common chips at the time (MSX, ColecoVision…), which explains how close several contemporary machines are.
Models & family¶
- SG-1000 (1983): joystick hardwired to the console.
- SG-1000 II (1984): detachable controllers (basis of the Master System pad).
- SC-3000: a home-computer version with a keyboard; BASIC cartridges add up to 32 KB of RAM, plus cassette support.
- Sega Mark III (1985): the evolution that became the Master System for export.
Media & compatibility¶
- Sega My Card: thin, cheap game cards read via the Card Catcher accessory (cartridge adapter).
- Backward compatibility: all SG-1000 games run on the Mark III and the Japanese Master System — an 8-bit thread of continuity at Sega.
Common faults¶
| Symptom | Likely cause | Lead |
|---|---|---|
| Cartridge not read | Connector oxidation | Clean the contacts |
| No image | Power, VDP, RF output | Diagnosis |
| Yellowed plastic | UV / ABS | Retrobright |
| Controller (SG-1000) | Cable/solder joints | Re-solder / replace |
(Few electrolytic capacitors: recap is secondary, like the Master System.)
Procedure — a dead console, step by step ✅¶
What this adds
Ordered for a console, not for an arcade board: what kills these is almost never the CPU. It is, in real order, the power supply, the capacitors, the drive or the cartridge slot, and only then the logic. → PCB diagnosis
1. The power supply. Two cases, depending on the machine. External brick: ⚠️ read the marking on the machine, next to the socket, and check the adapter against it — voltage and polarity. A centre-negative machine fed centre-positive loses its fuse, sometimes its regulator; do not trust a third-party label or a generic tip. Internal supply (the machine plugs straight into the wall): mains is inside the shell. Unplug, wait, and confirm the large capacitors are discharged before touching the board. Either way, measure under load: a failing supply holds its voltage until it is asked for current.
2. The fuse. Many of these machines have one right behind the socket — it is the part designed to die. Test it in continuity, out of circuit. A fuse that blows again is a short, not a fuse problem.
3. Capacitors. On most machines of this age this is the default suspect rather than a last resort — leaking SMD electrolytics eat the tracks underneath before they give any other sign. ⚠️ Not all of them are like that: some carry very few and are not recapped on principle. Read what this page says about it before reaching for the iron. → Recap
4. The cartridge connector. Cartridge contacts with isopropyl alcohol, never an abrasive eraser: it takes the gold plating off and the problem comes back worse. On the machine side, inspect the slot pins — splayed, bent or oxidised — and check continuity between slot and board.
5. Video output. Isolate the machine from the display: another cable, another TV, another input. A sizeable share of "dead consoles" are a dead cable, or a display that will not lock onto what this machine outputs — see the video section of this page for what that is.
6. Still nothing. Now, and only now, the logic: rails on the board, reset, clock, bus. → PCB diagnosis
Preservation & emulation¶
- Flashcart / adapters: as the machine is rare, emulation is the common route (MAME, Genesis Plus GX, SMS emulators that cover the SG-1000).
- Backward compat: see Master System to play SG-1000 games on more common hardware (Mark III / Japanese SMS).
Mods & repair — what to buy, how¶
Priority: get off RF
The SG-1000 is RF-only from the factory (poor, noisy picture). The most useful mod is a direct composite/AV output.
- Composite/AV mod 🟠: tap the composite video ahead of the RF modulator (at the TMS9918A VDP / video buffer) and route it to an RCA jack → clean picture. Wiring documented by the SMS Power community (the TMS9918A VDP is the same as MSX/ColecoVision, so those mods transpose).
- Backward compat to play: the simplest route for the library is a Mark III / Japanese Master System (SG-1000-cart compatible) + a Master EverDrive → see Master System.
- Recap: few electrolytics → secondary (check power). Prioritise cartridge/controller contact cleaning.
Photos / assets¶
(To add: SG-1000 vs SG-1000 II, SC-3000, My Card + Card Catcher, board.)
Advanced repair
Discrete logic: contacts, RAM, PSU; few electrolytics. Methods: PCB fault-finding · Recap · Traces & vias.
Archived technical documentation ✅¶
Manufacturer documentation archived locally: schematics, block diagrams, expected voltages, parts lists. The reference when a symptom matches no known fault.
Status
Manufacturer documents kept for preservation (machines out of production for decades), with no explicit licence — the same position as for the cabinet manuals already archived here.
Sources & attribution¶
- Wikipedia — SG-1000 (specs, models, compat) — CC-BY-SA — https://en.wikipedia.org/wiki/SG-1000
Image:
-
sg-1000.jpg— Evan-Amos, public domain — https://commons.wikimedia.org/wiki/File:Sega-SG-1000-Console-Set.jpg
Review & corrections
How this space is used
Spotted a wrong value, an outdated procedure, a chip reference that does not match your board? Say so here, with what you observed (model, board revision, serial number, measurement). Every report is cross-checked against a source before anything changes — an unverifiable correction is published as “reported by …, not cross-checked” rather than silently applied.
Reading is open to everyone; posting requires signing in with Discord. Reports from the wiki's declared reviewers are handled first; anyone else's are read too, but go through a human before anything is changed.