RETRODREAMSAMIGA & SPECTRUM
Menu

Fault guides · Amiga CD32 rev 3

Amiga CD32 rev 3Screen stuck on one colour

Step-by-step diagnosis for the Amiga CD32 rev 3 board. Each step lights up the signal or chip to measure in the explorer below.

Kickstart tests the machine at boot and, if it finds a fault, stops on a colour. The colour tells you where to look.

  1. Red: the ROM (Kickstart 2.04 and later)

    The ROM failed its checksum. Only Kickstart 2.04 and later run this check: on 1.x, red does not point to the ROM. Clean the socket contacts and reseat it; if it stays red, the ROM is damaged.

    U6A · 62408Show on board →
  2. Green: Chip RAM

    Chip RAM error. The usual suspects are the RAM chips and the traces between them and Agnus or Alice, often eaten by a leaking capacitor. CIA-A can also cause it, if it fails to move the ROM out of the way at start-up.

    U16 · 512KX8Show on board →
  3. Blue: the custom chips

    Custom chip error: Agnus, Denise and Paula (Alice, Lisa and Paula on AGA), according to community lists; we have not found this test in the Kickstarts we could check (1.2 doesn't have it, it is switched off in the 3.1 source and 1.3 is unconfirmed). Start by pressing down the socketed ones; the A500’s Agnus tends to work loose.

    U2 · 8374 ALICEShow on board →
  4. Yellow: a processor exception

    The processor took an exception (a bus error, for example) before Kickstart had the handlers that show the Guru. It does not mean the processor is faulty: it can be a bad ROM read, the bus or an expansion. Remove any expansion first; if it persists, check the ROM, the processor and the sockets.

    U1 · MC68EC020Show on board →

Didn't fix it?

We repair these boards on our bench in Loures. The request already includes the board and the fault.

Request a repair →

Drag to move; mouse wheel or two fingers to zoom. Tap a pad to follow the signal.