Atari 600XL Troubleshooting Guide: Difference between revisions
No edit summary |
Add representative photo (sourced from Wikimedia Commons, attributed on file page) ย |
||
| Line 7: | Line 7: | ||
=== Voltage Test Points === | === Voltage Test Points === | ||
<templatestyles src="Template:StyledTable/styles.css" /> | <templatestyles src="Template:StyledTable/styles.css" /> | ||
[[File:Atari 600XL (photo).jpg|thumb|right|300px|Atari 600XL. Source: Wikimedia Commons.]] | |||
{| class="wikitable styled-table" style="width:80%; text-align:center;" | {| class="wikitable styled-table" style="width:80%; text-align:center;" | ||
Latest revision as of 12:52, 16 July 2026
This is the troubleshooting guide for the Atari 600XL home computer. It covers voltage test points, IC diagnostics, RAM chip identification, PBI connector testing, and common failure modes. A multimeter, oscilloscope, and logic probe are recommended for advanced diagnostics.
Power Supply and Voltage Verification
[edit | edit source]The Atari 600XL has no onboard voltage regulator for the main +5V rail. The external power supply must provide clean, regulated +5V DC. Incorrect voltage will damage ICs.
Voltage Test Points
[edit | edit source]
| Test Point | Expected Voltage | Tolerance | Notes |
|---|---|---|---|
| +5V rail (Pin 40 of CPU / U1) | +5.0V DC | ยฑ0.25V | Main logic supply โ measure directly at the CPU VCC pin |
| +5V rail (Pin 24 of ANTIC / U7) | +5.0V DC | ยฑ0.25V | Verify supply reaches custom chips |
| +5V rail (Pin 28 of POKEY / U19) | +5.0V DC | ยฑ0.25V | POKEY supply โ also affects keyboard scanning |
| +5V rail (Pin 20 of GTIA / U4) | +5.0V DC | ยฑ0.25V | GTIA supply |
| GND (any ground pin) | 0V | โ | Reference ground |
| +5V at power connector | +5.0V DC | ยฑ0.1V | Measure at the barrel jack before board insertion |
Always verify the power supply output BEFORE connecting it to the computer. Voltages above +5.5V can destroy the 6502C, ANTIC, GTIA, and POKEY. These custom chips are irreplaceable. |
Power Rail Integrity
[edit | edit source]If the +5V rail reads low (below +4.75V) at the CPU but correct at the power connector:
- Check for dry or cracked solder joints at the power connector pads.
- Measure resistance along the +5V trace from the power connector to the CPU. Resistance should be less than 0.5ฮฉ.
- Inspect the main filter capacitor C95 (470ยตF 16V) โ a failed capacitor here will cause voltage sag under load.
- Check for short circuits between +5V and GND caused by failed ICs or tantalum capacitors.
CPU Diagnostics (6502C / SALLY)
[edit | edit source]The CPU is located at position U1 on the motherboard.
6502C Pinout Reference (40-pin DIP)
[edit | edit source]| Pin | Signal | Description | Expected State |
|---|---|---|---|
| 1 | VSS | Ground | 0V |
| 2 | RDY | Ready | HIGH (pulled up); LOW when ANTIC halts CPU |
| 3 | ฮฆ1 (OUT) | Phase 1 clock output | 1.79 MHz clock signal (NTSC) |
| 4 | IRQ | Interrupt Request | HIGH (inactive) unless interrupt pending |
| 5 | โ | Not connected | โ |
| 6 | NMI | Non-Maskable Interrupt | HIGH (inactive); pulled LOW by ANTIC for DLI/VBI |
| 7 | SYNC | Opcode fetch indicator | Pulses HIGH during opcode fetch cycles |
| 21 | VSS | Ground | 0V |
| 37 | ฮฆ0 (IN) | Phase 0 clock input | 1.79 MHz from system oscillator |
| 39 | ฮฆ2 (OUT) | Phase 2 clock output | 1.79 MHz (system bus timing reference) |
| 40 | RES | Reset | HIGH during normal operation; LOW during reset |
CPU Failure Symptoms
[edit | edit source]- Completely dead (no video output, no activity on address/data bus): If +5V is confirmed at pin 40 and GND at pin 1, and the clock is present at pin 37, the CPU has likely failed.
- Boots to self-test but fails: Indicates the CPU is partially functional. Suspect RAM or ROM before replacing the CPU.
- Random crashes during operation: May indicate an intermittent socket contact. Reseat the CPU; if symptoms persist, replace the socket with a machine-pin type.
ANTIC Diagnostics (U7)
[edit | edit source]The ANTIC chip is the display co-processor, responsible for generating the display list and fetching screen data from RAM.
Key ANTIC Signals
[edit | edit source]| Pin | Signal | Description | Expected State |
|---|---|---|---|
| 1 | VSS | Ground | 0V |
| 14 | HALT | CPU halt request | Pulses LOW during DMA cycles |
| 15 | NMI | Non-Maskable Interrupt output | Pulses LOW for Display List Interrupts (DLI) and Vertical Blank Interrupts (VBI) |
| 24 | VCC | +5V supply | +5.0V DC |
| 32 | ฮฆ0 | Clock output to CPU | 1.79 MHz |
ANTIC Failure Symptoms
[edit | edit source]- Blank screen (no video output at all): ANTIC is not generating display data. Verify clock signal at pin 32. If the clock is absent, ANTIC has failed.
- Screen full of random characters/garbage: ANTIC is running but reading corrupt data. Check RAM first, then ANTIC.
- No colour (monochrome only): This is a GTIA issue, not ANTIC.
- Self-test screen displays but system hangs: ANTIC is functional; issue is elsewhere (typically RAM or ROM).
GTIA Diagnostics (U4)
[edit | edit source]The GTIA generates the final colour video output, handles player/missile (sprite) graphics, and manages collision detection.
GTIA Failure Symptoms
[edit | edit source]- No colour output / monochrome display: GTIA colour generation has failed. Verify +5V at pin 20.
- Garbled colours or incorrect palette: Suspect a cracked solder joint under the GTIA socket or partial chip failure.
- No player/missile graphics (sprites missing in games): GTIA sprite registers are not being updated. Could be GTIA failure or address bus issue.
POKEY Diagnostics (U19)
[edit | edit source]POKEY handles audio output, keyboard scanning, serial I/O (SIO), paddle inputs, and random number generation.
POKEY Failure Symptoms
[edit | edit source]- No sound: Verify +5V at pin 28. If supply is good, POKEY audio section has failed.
- Keyboard completely dead: POKEY drives the keyboard scan. However, check the CD4051 multiplexers (U22/U23) first โ these fail more often than POKEY.
- SIO devices not detected: POKEY handles serial communication. Verify the SIO port connections first, then suspect POKEY.
- No random numbers (games behave deterministically): POKEY random number generator failure.
RAM Diagnostics
[edit | edit source]RAM Configuration by Revision
[edit | edit source]The 600XL's 16 KB of RAM is implemented differently depending on the board revision:
| Board Revision | RAM Chips | Type | Positions |
|---|---|---|---|
| Early revisions | 2 ร 4164 | 64Kร1-bit DRAM (only 16 KB used) | U9, U10 |
| Later revisions | 1 ร 4416 | 16Kร4-bit DRAM | U10 |
| 64 KB upgrade (typical) | 2 ร 4464 | 64Kร4-bit DRAM | U9, U10 (with wiring mod) |
Built-in Self-Test
[edit | edit source]The Atari 600XL includes a built-in self-test in ROM, accessible by holding the OPTION key during power-on. The self-test performs:
- RAM test โ Tests all available RAM and reports errors by address.
- ROM checksum โ Verifies the integrity of the OS and BASIC ROMs.
- POKEY audio test โ Plays a sequence of tones through each channel.
- Keyboard test โ Displays key presses on screen.
If the system boots directly to the self-test screen without holding OPTION, this typically indicates a ROM or BASIC failure โ the OS cannot find a valid BASIC ROM and falls through to self-test.
RAM Testing with a Logic Probe
[edit | edit source]For units that do not boot at all:
- Verify +5V and GND at the RAM chip power pins.
- Check for activity on the RAS (Row Address Strobe) and CAS (Column Address Strobe) lines โ these should show regular pulsing during operation.
- Verify address line activity (A0โA7 should show toggling patterns during memory access).
- If no activity is present on the RAM address/data lines but the CPU is running (verified by address bus activity at the CPU), suspect the address decoder logic.
4164 DRAM Pinout (16-pin DIP)
[edit | edit source]| Pin | Signal |
|---|---|
| 1 | NC (Not Connected) |
| 2 | DIN (Data In) |
| 3 | WE (Write Enable) |
| 4 | RAS (Row Address Strobe) |
| 5 | A0 |
| 6 | A2 |
| 7 | A1 |
| 8 | VCC (+5V) |
| 9 | A7 |
| 10 | A5 |
| 11 | A4 |
| 12 | A3 |
| 13 | A6 |
| 14 | DOUT (Data Out) |
| 15 | CAS (Column Address Strobe) |
| 16 | VSS (Ground) |
Compatible DRAM Replacements
[edit | edit source]The following DRAM types are confirmed compatible with the 600XL:
- 4164 (direct replacement) โ ยตPD4164, HM4864, KM4164, TMS4164, MB8264, MT4264
- 4264 (backward compatible with 4164)
- 41256 (will function at 64K density, operates as a drop-in for 4164)
- 4464 (for 64 KB upgrades, requires wiring modification)
Speed ratings of -10 (100ns), -15 (150ns), or -20 (200ns) are all suitable. Mixed speed ratings on the same board will function correctly, with all chips operating at the speed of the slowest IC.
PBI (Parallel Bus Interface) Diagnostics
[edit | edit source]The PBI is a 50-pin edge connector providing direct access to the system bus.
PBI Connector Pinout
[edit | edit source]| Pin (Top) | Signal | Pin (Bottom) | Signal |
|---|---|---|---|
| 1 | D0 | 2 | D1 |
| 3 | D2 | 4 | D3 |
| 5 | D4 | 6 | D5 |
| 7 | D6 | 8 | D7 |
| 9 | A0 | 10 | A1 |
| 11 | A2 | 12 | A3 |
| 13 | A4 | 14 | A5 |
| 15 | A6 | 16 | A7 |
| 17 | A8 | 18 | A9 |
| 19 | A10 | 20 | A11 |
| 21 | A12 | 22 | A13 |
| 23 | A14 | 24 | A15 |
| 25 | GND | 26 | GND |
| 27 | R/W | 28 | ฮฆ2 |
| 29 | IRQ | 30 | RDY |
| 31 | HALT | 32 | MATH (active = external device selected) |
| 33 | EXTSEL | 34 | RST (active low reset) |
| 35 | MPD (Memory Present Detect) | 36 | REF (Refresh) |
| 37 | S4 (ROM select) | 38 | S5 (ROM select) |
| 39 | CCTL (cartridge control) | 40 | RD4 (RAM select) |
| 41 | RD5 (RAM select) | 42 | CAS |
| 43 | CASINH (CAS Inhibit) | 44 | EXTENB (External Enable) |
| 45 | +5V | 46 | +5V |
| 47 | +5V | 48 | +5V |
| 49 | GND | 50 | GND |
PBI Diagnostic Checks
[edit | edit source]- Verify +5V at pins 45โ48 and GND at pins 25โ26, 49โ50.
- Check for address bus activity at pins 9โ24 using a logic probe or oscilloscope. All address lines should show toggling during CPU operation.
- Check for data bus activity at pins 1โ8. Data lines should toggle during read/write operations.
- Verify ฮฆ2 clock at pin 28 โ should show a clean 1.79 MHz square wave.
- Check R/W at pin 27 โ should toggle between HIGH (read) and LOW (write) during operation.
- If EXTSEL (pin 33) is stuck LOW: No external device is being selected. Check that any PBI peripheral is properly seated.
- If CASINH (pin 43) is not asserted during external memory access: The expansion memory will conflict with internal RAM.
Known Issues
[edit | edit source]16 KB RAM Limitation
[edit | edit source]The most significant issue with the 600XL is its base 16 KB RAM. Many Atari 8-bit programs require 48 KB or 64 KB to run. Symptoms include:
- Programs fail to load from disk or cassette โ they may start loading but crash immediately or report an "Error 2" (insufficient memory).
- BASIC programs that work on an 800XL crash on the 600XL โ the BASIC interpreter reports "ERROR-2" (out of memory).
- Games display a blank screen after loading โ the game initialises but cannot allocate sufficient memory for graphics and game data.
Resolution: Upgrade the RAM to 64 KB using the Atari 1064 module or an internal modification (see Atari 600XL General Maintenance#RAM Expansion Care).
CD4051 Multiplexer Failure (Keyboard)
[edit | edit source]The CD4051 analogue multiplexers at U22 and U23 are the most common point of failure for the keyboard. Symptoms range from individual dead keys to a completely non-functional keyboard. These are standard CMOS ICs and readily available as replacements (CD4051BE or CD4051BCN).
OS ROM Boot to Self-Test
[edit | edit source]If the system boots directly to the self-test screen without the OPTION key being held:
- Check the BASIC ROM at U3 โ remove and reseat. If the issue persists, the ROM may have failed.
- Check the OS ROM at U2 โ reseat in socket.
- Verify the OPTION key is not stuck or shorted โ a stuck OPTION key contact in the membrane can trigger self-test on every boot.
Oxidised IC Sockets
[edit | edit source]The factory-fitted single-wipe IC sockets are a known reliability issue on XL-series computers. Over time, oxidation builds up on the contact surfaces, causing intermittent failures. Symptoms include:
- Random crashes or lockups
- Failure to boot on some attempts
- Garbled graphics or missing colours
Resolution: Remove all socketed ICs, clean contacts with IPA, and preferably replace the sockets with machine-pin (dual-wipe) types.
Diagnostic Flowchart
[edit | edit source]System will not power on:
- Verify PSU output is +5.0V DC โ If not, replace PSU
- Verify +5V at CPU pin 40 โ If not, trace power path; check for shorts
- Verify clock at CPU pin 37 โ If not, check system oscillator
- Verify RESET (CPU pin 40) goes HIGH after power-on โ If stuck LOW, check reset circuit
System powers on but no display:
- Check for CPU activity (address bus toggling) โ If no activity, CPU or clock fault
- Check ANTIC clock output (pin 32) โ If absent, ANTIC failure
- Check composite/RF video output with oscilloscope โ If no signal, check video output circuit and RF modulator
- Reseat all socketed ICs โ Retry
- Run self-test (hold OPTION during power-on) โ Identifies RAM/ROM failures
System boots but with garbled display:
- Run self-test โ Check RAM test results
- Replace DRAM chips one at a time โ Test after each replacement
- Reseat GTIA โ Check for improved colour output
- Check for cold solder joints under IC sockets with a magnifying glass
Related Pages
[edit | edit source]