Amiga 500 Troubleshooting Guide

Fault-finding on the Amiga 500, built on two sources. Commodore's Service Manual A500 (PN-314981-04, October 1990) gives the start-up sequence and a signal-by-signal troubleshooting procedure for the Rev. 5 and Rev. 6A/7 boards.[1] Ian Perry's Amiga Troubleshooter chart (1993) maps symptoms to chips on the A500 and A2000.[2] Commodore takes all readings with an oscilloscope, to a ±10 % tolerance.[1]
Before anything else, remove every add-on (memory, hard drive, external drive, printer, modem) and try the machine with a known good power supply and drive.[2] For the supply itself see the maintenance guide.
Start-up colours
[edit | edit source]Kickstart 1.3 changes the screen colour as it starts. Commodore's sequence:[1]
| Stage | Screen |
|---|---|
| Hardware set up, screen turned on | Dark grey |
| ROM checksum bad | Red |
| Spurious exception before the error handler is set up | Yellow |
| Local memory configuration (boundaries, size) fails | Green |
| Custom chip register check fails | Blue |
| Software running | Light grey, then the Workbench prompt |
Wikipedia's Kickstart article says blue is used by Kickstart 3.0 and higher;[3] Commodore's own A500 manual lists it in the 1.3 sequence.[1]
The keyboard has its own self-test, reported on the Caps Lock light. Commodore's Amiga Hardware Reference Manual gives one blink for a ROM checksum failure, two for a failed RAM test, three for a failed watchdog timer test, and four for a short between two row lines; the keyboard sends the blinks in bursts about once a second.[4] One flash when the machine is switched on is normal.[5] Perry's chart blames the keyboard's 6570-036 controller for one or two flashes, and the 555, 74LS123 or 74LS27 on the keyboard for three.[2]
Preliminary checks
[edit | edit source]Commodore's minimum conditions for any picture at all. Points marked (P) are measured as power is applied.[1]
| Step | Measure | Expect | If wrong |
|---|---|---|---|
| 1 | CN12 pin 1 (right pin) | +5 V | Power supply section |
| 2 | CN12 pin 4 (left pin) | +12 V | Power supply section |
| 3 | U38 (MC1488) pin 1 | −12 V | Power supply section |
| 4 (P) | U5 (Gary) pin 41, RST | 0 V rising to +5 V shortly after power-up | Reset section |
| 5 (P) | U37 (74LS32) pin 11, RESET | As step 4 | Reset section |
| 6 (P) | U37 pin 8, IORESET | As step 4 | Reset section |
| 7 | U1 (68000) pin 15, CLK | 7 MHz | Clock section |
| 8 | U33 (74F04) pin 4, CCK | About 3.58 MHz | Clock section |
| 9 | U33 pin 6, CCKQ | About 3.58 MHz | Clock section |
| 10 | U33 pin 10, CDAC | About 7 MHz | Clock section |
If all ten are right and there is still no picture, work through the 68000, CIA and video checks below.
Power
[edit | edit source]Commodore's power supply checks follow each rail through the line filter LF1 to the supply. If a rail is missing at CN12 with the drive unplugged as well, measure LF1's output pin (pin 7 for +5 V, pin 5 for +12 V, pin 6 for −12 V) and its input pin (2, 4 and 3). Good at the input but bad at the output means a faulty filter; bad at the input means a faulty supply or a component shorting the rail. If the rail returns when the drive is unplugged, the drive is at fault.[1]
| Symptom | Check | Source |
|---|---|---|
| Black screen, no power-up | Try a known good supply; 68000 U1 (too hot to touch means bad); Agnus U2; crystal X1 (no clocks); U3 and U33 | Perry[2] |
| Machine works but the serial port does not | −12 V missing; the machine runs without it | Perry[2] |
| Rails good with drive unplugged, bad with it connected | Faulty drive assembly | Commodore[1] |
Reset and clocks
[edit | edit source]The power-on reset comes from the 555 timer U42 through transistor Q711 to Gary's KBRESET input (U5 pin 5). The keyboard can also pull it through CN13. With KBRESET good, check RST at U37 pin 12, then RESET (pin 11) and IORESET (pin 8) on U37; Commodore lists U5, U1, U2, U37, U7 and U8 as possible causes.[1] Sams gives the expected behaviour at 68000 pin 18: low for about half a second after power-up, then high.[6]
All clocks start at Agnus. Commodore's checks:[1]
- 28 MHz at U2 (Agnus) pin 34. If missing, suspect the oscillator X1 or U2.
- 7 MHz at U2 pin 38. If missing, suspect U2, U1 or U4.
- CCK at Gary pin 28, CCKQ at pin 27 and CDAC at pin 26. Missing at Gary points at U5, U2, U3, U4 or U33; present at Gary but missing after U33 points at U33.
Sams gives the NTSC figures as 28.636 MHz at Agnus pin 34, 7.159 MHz at pins 37 and 38, and 3.5795 MHz at pins 39 and 40.[6]
Processor and CIAs
[edit | edit source]Commodore checks the 68000's control lines in turn. HLT (pin 17) should sit at +5 V; UDS and LDS (pins 7 and 8), R/W (pin 9), AS (pin 6), DTACK (pin 10), VMA and VPA (pins 19 and 21) and E (pin 20) should all show activity. The manual notes that the 68000 may start with control signals around 2.5 V, but levels that do not reach close to +5 V indicate a fault. Most failing steps point at U1, U5 (Gary) or U2 (Agnus).[1]
The two 8520 CIAs are U7 and U8. U7's TICK input (pin 19) should carry vertical sync and U8's horizontal sync; a missing TICK points at Agnus or the CIA. Chip selects come through U37 (74LS32) from address lines A12 and A13.[1]
| Symptom | Check, in order |
|---|---|
| Green screen | Agnus U2; the A501 or other RAM expansion; Gary U5; RAM on the main board (a chip too hot to touch is bad); the U2 socket; U7 and U8 |
| Dark grey goes to light grey but no Workbench prompt | CIA U7; Paula U3; EMI301 (1 Ω), or R309 on Rev. 6A/7 boards; Agnus U2; U37 (74LS32); the U2 socket |
| Screen breaks up after 15 to 30 minutes | Agnus U2; Denise U4; the U2 socket |
| Locks up when an icon is double-clicked | Agnus U2; Denise U4; CIA U7; U37 |
Agnus sits in a PLCC socket, and Perry lists the socket itself for several faults. Reseat it with a PLCC extraction tool.[7]
Video
[edit | edit source]Denise (U4) produces digital RGBI, buffered by U40 and U41 (74HCT245). The video hybrid HY1 turns that into analogue RGB and composite video. Work back from the output:[1]
| Fault | Commodore's check | Perry's suspects[2] |
|---|---|---|
| No or wrong analogue RGB | HY1 outputs AR, AG, AB, then U40/U41 outputs, then their inputs. Good at HY1: EMI filters or connector CN9. | Denise U4; U40, U41; the video hybrid |
| No composite | HY1 composite output to CN10 | |
| Wrong colours (red, green or blue missing) | U40/U41 inputs and outputs | Denise U4; U40, U41; video hybrid |
| No vertical or horizontal sync on the RGB port | RP403 pins 5 and 3; then Agnus U2 | |
| Scrambled picture, loss of composite sync | U41 B7 output and A7 input | Agnus U2; U41; RP403 |
| Black screen with the machine running | R405 and R406 (4.7 Ω); Denise U4; video hybrid; U40, U41 |
Floppy drive
[edit | edit source]Try a known good drive first, and clean the heads; see Floppy Drive Repair. Commodore's checks for the internal drive:[1]
- Motor: MTR and SEL at Gary pins 7 and 16, MTRON at Gary pin 46, then U36 (74LS38) pin 6 and transistor Q503 to CN11.
- SIDE (pin 12), STEP (pin 10) and INDEX (pin 24) on CIA U8.
- RDY (pin 7), TRK0 (pin 6), WPROT (pin 5), CHNG (pin 4) and the LED output (pin 3) on CIA U7.
- Read data DKRD at Paula pin 37; write data and write enable through Gary pins 45 and 44 and U36.
Perry's chart gives CIA U8 for a drive that is not recognised, U8, Gary U5 or U36 for motor problems, CIA U7 for disk-change and write-protect faults, and Paula U3, the 68000 or Agnus for read and write errors.[2]
Keyboard, mouse and joystick
[edit | edit source]- Keyboard data and clock on CN13 pins 2 and 1 go to CIA U7. If they are missing, check U7, RP501 and CN13.[1]
- If the machine cannot be reset with Ctrl and both Amiga keys, Perry's first suspect is Q2, then the keyboard's 74LS27. On the main board he lists CIA U7, Agnus and Gary.[2]
- Mouse and joystick direction lines pass through U15 (74LS157) to Denise; the fire buttons go to CIA U7 through EMI415 and EMI425.[1]
- Mouse pointer does not move but buttons work: EMI401 (5.1 Ω, the 5 V feed to the mouse), Denise U4, U15. Left button and fire button dead: CIA U7. Right button dead: Paula U3.[2]
CIA failures show as dead fire buttons, disks not recognised or key presses not registered.[5] Hot-plugging a joystick or mouse can short a pin to the connector shell and damage a CIA.[8]
Audio
[edit | edit source]Paula outputs left audio on pin 31 and right on pin 30. Each channel passes through a section of U14 (LF347) and a filter stage, then the output capacitor (C324 left, C334 right) and an EMI filter to the RCA jacks. Commodore expects about 200 mV of audio at the jack side of the EMI filters. Check in order: Paula output, U14 inputs and outputs, the capacitor, resistors and EMI filter.[1] Perry adds the filter FETs Q321 and Q331, and cracked solder joints on the jacks CN3 and CN4.[2]
Serial and parallel ports
[edit | edit source]- Serial transmit fails: U38 (1488), Paula U3, CIA U8. Receive fails: U39 (1489), Paula U3, CIA U8.[2]
- Printer does not work: CIA U8 and the EMI filters on the port; printing wrongly: CIA U7.[2] Commodore checks the data lines through EMI512-EMI519 back to CIA U7.[1]
Diagnostic software
[edit | edit source]Commodore's service manual describes an A500/A2000 System Test disk. Its commands include KEYTEST (keyboard and matrix), SCREENTEST (colour bars and grey scales), SHOW BALLOON (a HAM picture that shows up a bad Agnus or Denise), CUBEROTE, and SYSTEST, which tests the clock, the blitter, chip and fast RAM, sprites and disk I/O with options for A500s with and without an A501.[1]
Related pages
[edit | edit source]- Amiga 500
- Amiga 500 Maintenance Guide
- Amiga 500 Capacitor Replacement Guide
- Amiga 500 Service Manual (314981-04)
- Sams Computerfacts CSCS26 Amiga 500
- Amiga 2000 Troubleshooting Guide
References
[edit | edit source]- ↑ 1.00 1.01 1.02 1.03 1.04 1.05 1.06 1.07 1.08 1.09 1.10 1.11 1.12 1.13 1.14 1.15 1.16 1.17 Commodore Business Machines, Service Manual A500, PN-314981-04, October 1990, hosted at Amiga 500 Service Manual (314981-04). System test, PDF pp. 32-33; start-up sequence, PDF p. 33; troubleshooting sections 1 to 10, PDF pp. 34-46; parts lists, PDF pp. 50-53.
- ↑ 2.00 2.01 2.02 2.03 2.04 2.05 2.06 2.07 2.08 2.09 2.10 2.11 2.12 Ian Perry, Amiga Troubleshooter (1993), original chart at sacc.org; reproduced as Commodore Amiga problems—link(accessed 2026-10-01)
- ↑ Kickstart (Amiga)—link(accessed 2026-10-01)
- ↑ Commodore-Amiga, Amiga Hardware Reference Manual, keyboard section, appendix G, Keyboard Interface / Power-Up Sequence—link(accessed 2026-10-01)
- ↑ 5.0 5.1 Gareth Knight, Amiga History Guide, What your Amiga is telling you—link(accessed 2026-10-01)
- ↑ 6.0 6.1 Howard W. Sams & Co., Computerfacts CSCS26, Commodore Amiga A500 (1988), troubleshooting, reset circuit, printed p. 25, hosted at Sams Computerfacts CSCS26 Amiga 500.
- ↑ Reseating Agnus—link(accessed 2026-10-01)
- ↑ SukkoPera, OpenAmigaJoyMouseSwitcher—link(accessed 2026-10-01) "blowing a resistor (or worse an 8520 CIA chip!)".