Atari ST Troubleshooting Guide

This guide covers fault diagnosis and repair for the Atari 520ST, 520STM, 520STF, 520STFM, 1040ST, 1040STF, and 1040STFM computers. These machines share common motherboard architectures (including the C070789-001 used in both 520STFM and 1040STFM) and the same custom IC set, so troubleshooting procedures are largely identical. Differences between the 520ST and 1040ST (principally RAM population and PSU type) are noted where relevant.

For the Atari STE range (520STE / 1040STE), see Atari STE Troubleshooting Guide.

Prerequisites

Before beginning troubleshooting:

• A digital multimeter (DMM) capable of DC voltage, continuity, and resistance measurement is essential.
• An oscilloscope is helpful for diagnosing clock and timing issues but is not strictly required for most common faults.
• An Atari diagnostic cartridge is a valuable tool — it provides hardware-level testing via the cartridge port and can output diagnostics over the serial port even when the display is not functioning.
• A known-good external floppy drive, spare TOS ROMs, and spare RAM chips are useful for substitution testing.

Boot Sequence Overview

Understanding the ST boot sequence helps pinpoint where a failure occurs. This sequence is the same for the 520ST and 1040ST:

1. Power-on: PSU provides +5V and +12V rails. The 68000 is held in reset by the GLUE chip until voltages stabilise.
2. Reset release: GLUE releases the 68000 RESET line. The CPU reads the initial SSP (Supervisor Stack Pointer) from address $000000 and the initial PC (Program Counter) from address $000004, which points into TOS ROM space ($FC0000–$FEFFFF).
3. TOS initialisation: TOS performs a RAM sizing/test routine. On TOS 1.00–1.04, this is a brief test. The screen remains blank (white or black depending on the monitor type) during this phase.
4. GEM desktop: If all tests pass and no bootable floppy is detected, the GEM desktop appears. If a bootable floppy is present, the boot sector is loaded and executed.

Failure at each stage produces characteristic symptoms:

• No power LED → PSU failure or blown fuse
• Power LED on but no display → CPU not running, clock failure, or ROM space fault
• White screen (colour monitor) → CPU running but stuck in early TOS code; likely RAM fault, ROM fault, or MMU/GLUE failure
• Green screen with corrupted icons → Partial boot; likely bad RAM chip, video fault, or corrupted TOS
• Desktop appears but crashes → PSU instability, intermittent RAM fault, or software issue

Power Supply Diagnosis

The PSU is the most common source of problems in ageing ST machines. The 1040ST has an internal switched-mode PSU; the 520ST/520STM uses an external supply.

Voltage Rails

Rail	Wire Colour (1040ST internal header)	Nominal Voltage	Acceptable Range	Notes
+5V	Red	5.00V	4.75V – 5.25V	Primary logic supply; most critical rail. Below 4.75V causes instability; above 5.5V risks IC damage.
+12V	Blue	12.0V	11.0V – 13.0V	Floppy drive motor, RS-232 transceivers. The machine will operate without it but floppy and serial will not function.
GND	Black	0V	—	Common ground reference.

On the 520ST with external PSU, measure at the 7-pin DIN power connector: +5V (pins 1, 2), +12V (pin 6), GND (pins 3, 4, 5). Some external supplies also provide −12V (pin 7) for the RS-232 transceivers.

Testing procedure:

1. Do NOT test a switched-mode PSU disconnected from the motherboard (or a dummy load). Without a load, output voltages may be dangerously high or the PSU may not start at all.
2. With the machine assembled and powered on, measure the +5V rail at the motherboard power header (red wires to black wires).
3. If the voltage is below 4.9V under load, the PSU capacitors likely need replacement.
4. Check for AC ripple on the +5V rail if you have an oscilloscope. A healthy recapped PSU should show less than 200mV of ripple. More than 500mV indicates failing capacitors and will cause instability.

Common PSU Symptoms (Both 520ST and 1040ST)

Symptom	Possible Cause	Recommended Action
No power at all (no LED)	Blown mains fuse in cable or PSU; failed power switch (1040ST); open fusible resistor in PSU; failed external PSU brick (520ST)	Check mains fuse. On 1040ST: check PSU internal fuse and continuity through power switch. On 520ST: test external PSU output voltages with DMM.
Power LED flickers	PSU attempting to start but shutting down (overcurrent protection)	Likely shorted component on motherboard or PSU. Disconnect motherboard from PSU and test PSU with dummy load (1040ST) or try a different external PSU (520ST).
Random crashes during use	Low or noisy +5V rail	Measure +5V under load. Recap PSU if voltage below 4.9V or ripple exceeds 300mV.
Screen dims when floppy drive activates	Poor peak power delivery on +5V rail (1040ST internal PSU)	Recap PSU. On Mitsumi SR98 PSUs, the biasing resistors R201/R202 may need adjustment — replace R202 with 1KΩ and R201 with 1.2KΩ, then readjust the voltage trimmer to 5.00V.
Audio noise/hum	Ripple on +5V rail coupling into YM2149 audio output	Recap PSU. Check ground connections.
Intermittent floppy read errors	Unstable +12V rail (floppy motor speed variation) or noisy +5V (logic errors)	Measure both rails under load. Recap PSU.

Display / Video Troubleshooting

The video subsystem (Shifter, GLUE, and related circuitry) is identical across the 520ST and 1040ST.

No Display at All

Symptom	Possible Cause	Recommended Action
No display, no power LED	PSU failure	See Power Supply Diagnosis section above.
Power LED on, completely blank screen	CPU not running; no clock signal; or monitor cable/connection fault	Verify monitor cable is connected and monitor is set to correct input. Check 32 MHz crystal oscillator with oscilloscope. Reseat CPU, Shifter, GLUE.
Power LED on, white screen only (colour monitor)	CPU running but failing during early TOS initialisation. Common causes: RAM fault, TOS ROM fault, MMU failure, GLUE failure.	Reseat all socketed ICs. Try known-good TOS ROMs. Try with diagnostic cartridge — if cartridge menu appears, motherboard is partially functional and fault is likely in RAM or TOS ROMs. If no cartridge output, fault is in ROM address space decoding (GLUE/MMU).
Power LED on, white screen only (monochrome monitor)	As above, plus: mono detect pin not being grounded (faulty cable/connector) causing Shifter to output colour mode to mono monitor	Check pin 4 on the 13-pin DIN connector. It should be grounded for monochrome mode.
Display appears briefly then goes blank	PSU voltage droop under full load; thermal fault in Shifter or GLUE	Measure +5V rail under load. If voltage is stable, suspect thermal failure in Shifter — use freeze spray to isolate.

Display Corruption

Symptom	Possible Cause	Recommended Action
Vertical or horizontal bars/stripes	Shifter failure; bad connection between Shifter and data bus; failing RAM affecting video memory area	Reseat Shifter chip. Check Shifter retaining clips for adequate tension. If problem persists, try known-good Shifter from donor board.
Wrong or garbled colours	Shifter output fault; bad solder joint on RGB output path; monitor cable fault	Check 13-pin DIN cable for continuity on R, G, B pins (6, 7, 10). Check monitor connector for bent pins. Reseat Shifter.
Screen jitter or rolling	Sync signal fault; HSync or VSync not being generated correctly by GLUE	Check HSync (pin 9) and VSync (pin 12) on monitor port with oscilloscope. If absent, suspect GLUE chip. Check 32 MHz crystal.
Ghosting or wavy lines	PSU ripple; poor grounding; RF interference from internal PSU (1040ST)	Recap PSU. Check ground connections.
"Jail bars" (thin vertical lines on solid colours)	Impedance issues on the video output path; common on STFM boards	Sometimes improved by replacing decoupling capacitors near the Shifter. A known characteristic of the ST video circuit rather than a definitive fault.

RF Modulator Issues (FM Models — 520STFM / 1040STFM)

Symptom	Possible Cause	Recommended Action
No RF output, RGB works fine	RF modulator failure; modulator not connected	Check modulator solder connections. A composite video mod bypassing the modulator is a common upgrade.
RF output is snowy/noisy	Modulator mistuned; weak signal	Adjust tuning slug on modulator. Clean modulator connections.
RF output with herringbone pattern	Ground loop or interference	Ensure proper grounding. Consider composite/RGB output instead.

RAM Fault Diagnosis

RAM faults are a common cause of white screens, crashes, and corrupted displays on both the 520ST and 1040ST.

RAM Architecture

• 520ST/520STM/520STF/520STFM (512 KB): Typically 16× 41256 (256K×1) DRAMs arranged as two banks of 8, or 8× 44256 (256K×4) DRAMs on later boards. RAM is soldered on most revisions.
• 1040ST/1040STF/1040STFM (1 MB): 32× 41256 or 16× 44256, depending on board revision. On the shared C070789-001 board, the 1040 simply has more RAM positions populated than the 520. RAM is soldered.

The MMU handles row/column address multiplexing (MAD0–MAD9), RAS (Row Address Strobe), and CAS (Column Address Strobe) signals to the DRAM array.

Diagnosing RAM Faults

Symptom	Likely Cause	Diagnostic Steps
White screen at power-on	One or more RAM chips completely dead; multiple data lines stuck	Use diagnostic cartridge with serial output — it will report stuck data lines and the address of the failing location. If no diagnostic cartridge, desoldering RAM to test in isolation may be necessary.
Machine detects less RAM than installed (e.g., 512 KB on a 1040ST)	Failed RAM chip(s) in upper bank; MMU configuration register mismatch	Boot with diagnostic software and run memory test. Check the MMU bank configuration register at $FF8001.
Random crashes during use	Intermittent RAM failure; marginal cell that fails under thermal stress	Run extended RAM test software (YAART is recommended). If crashes worsen as the machine warms up, use freeze spray on RAM chips to isolate the failing device.
Corrupted graphics (random pixels, garbled text)	RAM fault in the video display area (ST-RAM is shared between CPU and video)	Specific corrupted patterns can indicate which data bit is failing. A single stuck bit produces a repeating pattern every N pixels. Use diagnostic software to identify the failing bit.
Bomb screen (row of bombs at top of display)	Software crash; the number of bombs indicates the 68000 exception type	While not always a RAM fault, persistent bomb screens at random addresses suggest RAM corruption. Run memory diagnostics.

68000 Exception Types (Bomb Count)

Bombs	Exception	Common Hardware Cause
2	Bus Error	GLUE timeout — accessed unmapped address space. Often caused by bad ROM contact, failed GLUE, or bus contention.
3	Address Error	68000 attempted word/long access at odd address. Usually a software bug, but can indicate RAM corruption of pointer values.
4	Illegal Instruction	CPU fetched invalid opcode. Corrupt ROM, failing RAM in code area, or bus noise.
5	Division by Zero	Almost always a software issue.
8	Privilege Violation	Software attempted supervisor-mode instruction in user mode.

Custom IC Failure Diagnosis

The same custom IC set is used across all 520ST and 1040ST models:

IC	Failure Symptoms	Diagnostic Steps	Notes
Shifter (C025914)	No display output or grossly corrupted display; no video sync signals on RGB pins; vertical/horizontal bars	Check for video output on monitor port pins with oscilloscope. Reseat Shifter. If socketed, try known-good replacement.	On boards where Shifter is in a metal can with retaining clips, check clip tension. The Shifter is the most commonly failing custom IC.
GLUE (C025915)	Machine does not boot at all; no bus activity; bus error (2 bombs) on every access; no video sync; interrupts not generated	Check with logic probe for activity on AS, DTACK, and address bus lines. If CPU is running but getting no DTACK, GLUE is likely faulty.	GLUE generates all chip select signals — a GLUE failure can mimic almost any other chip failure.
MMU (C025912 / C100109)	White screen; reduced RAM detected; video DMA not fetching data (display shows content of address $000000 repeating)	With diagnostic cartridge serial output, check if RAM can be written and read. If all reads return the same value, MMU is likely not multiplexing addresses correctly.	On the 1040ST, the full 1 MB RAM requires correct MMU bank selection — a partial MMU failure may cause the 1040ST to report only 512 KB.
DMA (C025913)	Floppy drive not working (no data transfer despite motor spinning); ACSI hard disk not responding	Floppy motor/head select are controlled via YM2149, not DMA. If drive motor spins but no data is read, and WD1772 appears responsive, the DMA chip may be at fault.	Relatively uncommon failure. Check WD1772 first.
WD1772	No floppy drive response; drive seeks endlessly; read/write errors on all disks	Verify floppy drive itself works (try known-good drive). Check drive select and motor-on signals via YM2149 Port A. If drive motor runs and head moves but data is never transferred, WD1772 is suspect.	Socketed on most boards; can be directly swapped.
YM2149F	No sound output; parallel printer not working; floppy drive select lines not toggling (drive won't spin); serial RTS/DTR not working	Test each function independently: sound on monitor port; printer data on DB-25; floppy activity. If multiple YM2149-controlled functions fail simultaneously, the chip is likely bad.	The YM2149 controls many non-obvious functions. A failed YM2149 can make the floppy appear completely dead.
MC68901 (MFP)	System timers not running (no cursor blink); keyboard not responding; RS-232 serial not working	If machine boots to desktop but cursor doesn't blink and keyboard doesn't respond, MFP timer or interrupt system is likely faulty.	Socketed on most boards. Try reseating first.
MC6850 (ACIA ×2)	Keyboard ACIA failure: no keyboard/mouse input. MIDI ACIA failure: no MIDI I/O.	Swap the two 6850s to determine which is faulty (keyboard vs MIDI).	Two physically identical chips; one handles IKBD, the other MIDI.
MC68000 (CPU)	Machine completely dead despite good PSU; random and unpredictable behaviour; consistent wrong data on bus	Check for clock signal (8 MHz) on CLK pin. Check that RESET is being released. If clock present and reset releases but no bus activity, CPU is likely faulty.	CPU failure is relatively rare. Verify 32 MHz crystal and clock chain before condemning the CPU.

Floppy Drive Troubleshooting

The floppy subsystem is the same across 520ST (with external drive) and 1040ST (internal drive). The WD1772 controller and DMA chip are on the motherboard; drive select and motor control are handled by the YM2149.

Symptom	Possible Cause	Recommended Action
Drive motor does not spin	YM2149 not asserting drive select/motor on; bad cable; drive motor failure	Check YM2149 Port A bits for drive select and motor on. Check ribbon cable (1040ST) or DIN cable (520ST external). Try known-good drive.
Drive seeks but cannot read	Dirty heads; misaligned heads; failing WD1772; bad data cable	Clean heads with IPA. Try multiple known-good disks. Try known-good drive. If external drive also fails, suspect WD1772 or DMA.
Drive seeks to track 0 repeatedly (clicking)	Drive cannot find track 0 sensor; head mechanism stuck; belt failure	Check track 0 sensor. Clean and lubricate head carriage rails. Replace drive belt if stretched.
Drive reads but cannot write	Write-protect switch stuck or misread; WD1772 write circuit fault	Check write-protect sensor. Try a different disk with the tab in the correct position.
Intermittent read errors	Dirty heads; ageing media; PSU instability; thermal WD1772 issue	Clean heads. Try fresh disk. Check PSU voltages. If errors appear only after warm-up, suspect thermal WD1772 failure.
Very slow boot (30+ seconds)	TOS searching for bootable disk on drive A with no disk inserted	Not a fault. Insert a non-bootable disk or upgrade to TOS 1.04 for improved boot behaviour.

Audio Troubleshooting

Symptom	Possible Cause	Recommended Action
No sound at all	YM2149 failure; bad solder joint on audio output path; monitor cable not carrying audio	Check pin 1 (audio out) on 13-pin DIN. If no signal, check YM2149. If signal present, check cable and monitor.
Distorted or crackling sound	Failing electrolytic capacitors in the audio output path	Replace audio-path caps. See Atari ST Capacitor Replacement Guide.
Constant hum or buzz	PSU ripple; ground loop with monitor	Recap PSU. Try a different monitor.
Sound from only some programs	Software compatibility issue with specific TOS version	Not a hardware fault.

Keyboard Troubleshooting

Applies equally to 520ST and 1040ST (same keyboard design and IKBD controller):

Symptom	Possible Cause	Recommended Action
Keyboard completely dead	Keyboard ribbon cable disconnected/damaged; keyboard ACIA (MC6850) failure; IKBD controller (HD6301) failure	Check ribbon cable. Swap the two MC6850 ACIAs to test keyboard ACIA. If still dead, suspect IKBD controller.
Some keys not working	Degraded keyboard membrane; dirty contacts; cracked membrane trace	Clean membrane contacts with IPA. Inspect membrane for cracks. Replace membrane if damaged.
Key repeat stuck	Shorted key on membrane; IKBD controller glitch	Check for debris under affected key. Power-cycle. Inspect membrane for short circuits.
Mouse not working, keyboard works	Mouse port connector fault; faulty mouse; IKBD issue	Try a different mouse. Check DE-9 port for bent pins. Clean connector.

Using the Diagnostic Cartridge

The Atari diagnostic cartridge is an essential repair tool for both 520ST and 1040ST machines:

• It runs hardware diagnostics independent of TOS ROMs and can test RAM, keyboard, display timing, floppy drives, and other subsystems.
• If the machine cannot produce a display, the diagnostic cartridge outputs test results over the RS-232 serial port. Connect a null modem cable to a PC running a terminal emulator at 9600 baud, 8N1.
• During boot, it sends a memory test report over serial showing written values, read values, and failing addresses — allowing identification of specific stuck data lines.
• If the diagnostic cartridge menu does not appear on screen OR via serial: The fault is likely in ROM address space decoding (GLUE) or the cartridge port edge connector. Clean the connector and check for proper contact.
• Modern alternatives include the exxos multi-diagnostic cartridge with Atari diagnostics, EmuTOS, and YAART memory testing on a single cartridge with rotary selector.

Diagnostic Flowchart

A suggested order of operations when confronted with a non-working 520ST or 1040ST:

1. Check PSU: Measure +5V and +12V. If out of spec, recap PSU (1040ST) or replace/test external PSU (520ST) before proceeding.
2. Reseat all socketed ICs: This alone resolves a significant percentage of faults after decades of thermal cycling.
3. Try diagnostic cartridge: If it works, use it to test RAM, keyboard, floppy, and timings.
4. Check TOS ROMs: Swap with known-good set if available. White screen is often caused by ROM issues.
5. Check RAM: Use diagnostic cartridge serial output or substitution testing.
6. Check clock: Verify 32 MHz crystal and derived clocks (8 MHz CPU, 2 MHz YM2149, 500 kHz ACIA) with oscilloscope.
7. Check custom ICs: If all of the above are good, fault is likely in Shifter, GLUE, MMU, or DMA — substitution testing is the most reliable method.

Related Pages

• Atari 520ST
• Atari 1040ST
• Atari ST General Maintenance
• Atari ST Capacitor Replacement Guide
• Atari STE Troubleshooting Guide