Sharp X68000¶
The "arcade at home" machine (1987): a 68000 + graphics customs (sprites, planes, 65536 colours) and YM2151 + OKI ADPCM sound — exactly the toolkit of period Capcom boards, hence near-perfect ports (Final Fight, SF2…). A cult "Manhattan" case. Emergencies: the PSU and the RTC battery.

Sharp X68000 (teardown) — photo by Dave Jones, CC BY 2.0 (Wikimedia Commons).
Identification / models¶
| Model | Year | CPU | Note |
|---|---|---|---|
| X68000 (Pro / ACE / EXPERT / SUPER) | 1987-90 | 68000 @ 10 MHz | the "twin tower" case |
| X68000 XVI | 1991 | 68000 @ 16 MHz | faster |
| X68000 Compact | 1992 | 68000 @ 16 MHz | smaller form factor |
| X68030 | 1993 | 68030 @ 25 MHz | the last model |
Architecture¶
| Block | Chip/role |
|---|---|
| CPU | Motorola 68000 (68030 on the X68030) |
| Video | Sharp customs: hardware sprites, multiple planes, scroll, 65536 colours |
| Sound | Yamaha YM2151 (8-voice FM) + OKI ADPCM (MSM6258) — the arcade sound |
| Storage | 2× 5.25″ drives + SASI/SCSI (HDD) per model |
Repair (technician)¶
1) The PSU — the No. 1 fault
The X68000's switching PSU is notorious for dying (dead/leaking caps, drifting regulation) → no boot or instability. Recap the PSU (or fit a modern PSU / Pico) → Recap.
2) Leaking RTC battery
The clock battery leaks and eats the board → remove/replace it ASAP (lithium + diode) → backup batteries.
- 5.25″ drives: tired mechanism / belt → Gotek (HD/FD emulator) for preservation.
- Board recap: period electrolytics → recap if video/sound degrade.
- Graphics customs: rare → corrupt video = test VRAM + buffers first, the custom next (donor).
- Yellowing plastic (like much retro): cosmetic retrobright.
- Video output: 15/31 kHz per mode → multi-sync monitor / SCART (video mods).
Original service manual ✅¶
Manufacturer manual archived locally. It typically carries the schematics, the block diagram, the expected voltages and waveforms, the parts list and the disassembly procedures — the reference when a symptom matches no known fault.
- Sharp X68030 (CZ-147) — service manual — PDF
Status
A manufacturer document with no explicit licence, kept for preservation (machine long out of production). Source: Internet Archive.
Common faults¶
| Symptom | Likely cause | Lead |
|---|---|---|
| No boot / unstable | PSU (caps) | Recap PSU / modern PSU |
| Corrosion near the clock | RTC battery | Remove, repair traces |
| Floppy not read | 5.25″ mechanism | Clean / Gotek |
| Degraded video/sound | caps / customs | Recap, substitution |
Modernisation & mods — what to buy, how¶
Fragile X68000: recap + PSU + battery BEFORE anything
-
Recap is mandatory 🟠: the SMD caps leak and eat the board — the X68000 plague (clean the electrolyte, repair traces).
-
The original PSU dies → a modern PSU (documented PicoPSU / Mean Well kits) 🟠.
- A leaking RTC battery → lithium + diode (no recharge).
Modern storage - SCSI → BlueSCSI / SCSI2SD 🟢: the X68000 is SCSI → an SD card as a hard disk (SCSI port); CF on later IDE interfaces. - Floppy → Gotek + FlashFloppy or HxC 🟡 (the eject mechanism breaks — see below).
Video - Switchable 15/31 kHz RGB output 🟢 → SCART/VGA then OSSC / RetroTINK or RGB2HDMI.
Mechanics & expansion - A broken floppy eject gear (classic defect) → a remade (3D-printed) gear 🟡. - 060turbo accelerator + RAM 🟠 for compatible models.
⚠️ Do not host ROMs/games — method only.
See also¶
- MSX · NEC PC-88/98 · Backup batteries · Recap.
Sources & attribution¶
- Photo Sharp X68000 (teardown) — Dave Jones, CC BY 2.0, Wikimedia Commons — https://commons.wikimedia.org/wiki/File:Sharp_X68000_Personal_Computer_Teardown.jpg
- Wikipedia — Sharp X68000 (68000, sprite customs, YM2151+ADPCM, models) — CC-BY-SA — https://en.wikipedia.org/wiki/X68000
- Established X68000 community knowledge (dying PSU, RTC battery, Capcom ports) — synthesis.
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.