Jump to content

Atari Falcon Troubleshooting Guide: Difference between revisions

From RetroTechCollection

Josh (talk | contribs)

8 user groups
18,376 edits
undo
VisualWikitext
Created page with "{{Infobox computer | name = Atari Falcon030 Troubleshooting Guide | image = | manufacturer = Atari Corporation | type = Troubleshooting Guide }} This guide covers common faults, diagnostic procedures, and repair approaches for the '''Atari Falcon030'''. The Falcon has several well-documented failure modes, particularly relating to its PSU, clock distribution, and DSP subsystem. == Diagnostic Tools == * '''YAART''' — RAM testing utility * '''TOS memory test'''..."
 
Rewrite on Atari's Falcon030 Service Guide: dead-unit procedure, diagnostic cartridge, bombs table, full symptom checklist, DS1287 clock; remove wrong claims (floppy controller in COMBEL, DS12887A 'replaceable battery', CR2032 mod, 8 MHz fallback) and unverifiable forum clock-patch advice; Atari troubleshooting category
 
(One intermediate revision by the same user not shown)
Line 1: Line 1:
{{Infobox computer
<templatestyles src="Template:StyledTable/styles.css" />
| name = Atari Falcon030 Troubleshooting Guide
[[File:Atari-Falcon030.jpg|thumb|right|300px|Atari Falcon030]]
| image =
Fault-finding on the '''[[Atari Falcon030]]''' follows Atari's ''Falcon030 Service Guide'' (C303062-001, 1 October 1992): its procedure for a dead unit, the Falcon030 diagnostic cartridge, and the symptom checklist in section 5.<ref name="sg">Atari Corporation, ''Atari Falcon030 Service Guide'', C303062-001, 1 October 1992. Section 1.3 (power supply, pp. 4–5), Section 2.4–2.5 (system start-up and bombs, pp. 61–62), Section 3 (testing, pp. 65–97), Section 5 (symptom checklist, pp. 103–105), Section 7 (parts list). Hosted here as [[:File:Atari Falcon030 Service Guide C303062-001.pdf]].</ref>
| manufacturer = Atari Corporation
| type = Troubleshooting Guide
}}


This guide covers common faults, diagnostic procedures, and repair approaches for the '''[[Atari Falcon030]]'''. The Falcon has several well-documented failure modes, particularly relating to its PSU, clock distribution, and DSP subsystem.
== Before you start ==


== Diagnostic Tools ==
* Check the power supply first: +5 V and +12 V at the main board. Atari sets +5 V to 5.05 ± 0.1 V with a 4.0 A load and allows 5 % regulation on +5 V and 10 % on +12 V, with ripple and noise of 100 mV p-p each.<ref name="sg" />
* Check that the monitor works and is the right type. The board reads the monochrome-detect line at power-up; if it does not see a low there, the VIDEL drives RGB instead of mono.<ref name="sg" />
* Before blaming the hardware for a crash, check the disk and drive: Atari notes that errors loading files from disk can crash the system.<ref name="sg" />


* '''YAART''' — RAM testing utility
== Start-up and bombs ==
* '''TOS memory test''' — Hold both Shift keys during boot
* '''Multimeter''' — PSU voltage and continuity checks
* '''Oscilloscope''' — Clock signal integrity, PSU ripple analysis
* '''DSP loopback adapter''' — Tests DSP port functionality (pinout: 1→26, 2→21 via 1kΩ, 3→22, 4→19, 6→21 via 1kΩ, 11→24, 12→13, 15→23)<ref>{{cite web |url=https://www.exxosforum.co.uk/forum/viewtopic.php?t=7353 |title=Almost dead Falcon 030 – DSP loopback |publisher=exxos Forum |access-date=2026-03-27}}</ref>
* '''RS-232 loopback adapter''' — Tests serial port (2→3, 7→8, 4→1, 4→9)


== Common Fault Table ==
After a reset the 68030 starts from the ROM, checks the cartridge port for a diagnostic or boot cartridge, initialises memory, the sound chip, the palettes, the MFP and the screen, then tries to boot from floppy and hard disk before loading the desktop from ROM.<ref name="sg" /> Exceptions without a handler draw bombs on the screen, one per exception number:<ref name="sg" />


<templatestyles src="Template:StyledTable/styles.css" />
{| class="wikitable styled-table" style="width:85%;"
{| class="wikitable styled-table"
|+'''Number of bombs (Service Guide p. 62)'''
! Symptom !! Possible Cause !! Recommended Action
! Bombs !! Meaning
|-
| Dead — no power, no fan || PSU failure; mains fuse blown || Check mains fuse. Test PSU output voltages off-load. Recap PSU capacitors (see [[Atari Falcon Capacitor Replacement Guide]]). Check bridge rectifier.
|-
| Black screen, CPU running (8 MHz clock) || Boot failure; ROM fault; critical chip failure || Measure CPU clock — should be 16 MHz. If 8 MHz, the system has fallen back to a failure state. Check COMBEL chip, VIDEL, and ROM. Ensure RAM daughter board is properly seated.
|-
| Black screen, CPU halted || Fatal hardware error; RAM failure; bus fault || Test with minimal configuration. Reseat RAM daughter board. Check for shorted or open traces near the CPU. Verify PSU voltages.
|-
| Boots to TOS but crashes randomly || PSU capacitor degradation; RAM fault; overheating || Recap PSU and motherboard. Run YAART extended memory test. Check fan operation. Verify +5V rail is within specification.
|-
| No DSP sound / DSP-related crashes || Clock signal integrity; DSP chip fault; SDMA fault || Apply the clock buffer patch (74HCT04). This resolves the majority of DSP-related issues. If patch is already applied, check the DSP chip and SDMA.<ref>{{cite web |url=https://www.atari-forum.com/viewtopic.php?t=20539 |title=Falcon DSP problems |publisher=Atari Forum |access-date=2026-03-27}}</ref>
|-
| SCSI errors — read/write failures, lockups || Clock signal integrity; termination error; cable || Apply clock buffer patch. Check SCSI termination. Verify SCSI cable integrity. Test with single known-good SCSI device.
|-
|-
| IDE drive not detected || IDE cable fault; drive incompatibility; COMBEL issue || Check IDE ribbon cable (40-pin to 44-pin adapter if using a 3.5″ drive). Try a different CF/SD adapter. The IDE interface has known compatibility issues with some modern adapters.
| 2 || Bus error, asserted by COMBEL
|-
|-
| Corrupted data on file copy/decompression || Clock signal integrity; RAM fault || Apply clock buffer patch. This is the classic symptom of the unfixed clock distribution issue. Test RAM with YAART.
| 3 || Address error: word or long word access at an odd address
|-
|-
| Floppy drive not working || WD controller (via COMBEL); drive failure; cable || Test with known-good drive or Gotek emulator. Check ribbon cable. The floppy controller is integrated into the COMBEL chip on the Falcon.
| 4 || Illegal instruction
|-
|-
| No audio output (PSG or DMA) || CODEC failure; SDMA fault; capacitor degradation || Test PSG sound (system beep) separately from DMA sound. If PSG works but DMA does not, check SDMA and CODEC chips. Recap motherboard capacitors near audio section.
| 5 || Divide by zero
|-
|-
| Audio input not working || Microphone-level input only; CODEC fault || The standard Falcon accepts microphone-level input only. Line-level sources require a pre-amplifier. If mic-level still fails, check CODEC chip and input capacitors.
| 6 || CHK instruction without a handler
|-
|-
| Keyboard not responding || Keyboard ribbon cable; keyboard processor; ACIA || Reseat keyboard ribbon cable. Test with an ST/STe keyboard (electrically compatible). Check keyboard processor chip.
| 7 || TRAPV instruction without a handler
|-
|-
| NVRAM settings lost on power cycle || Dead RTC battery || Replace Dallas DS1287A with DS12887A (replaceable battery). Or perform the CR2032 holder modification on the existing Dallas chip.
| 8 || Privilege violation
|-
|-
| Display shows wrong resolution / colours || VIDEL configuration; NVRAM corruption; monitor mismatch || Reset NVRAM (remove battery briefly). Ensure correct monitor type is connected (VGA vs RGB). Check VIDEL chip. Try booting with a different resolution (hold Control during boot on some TOS versions).
| 9 || Trace
|-
|-
| Jailbar pattern on display || RAM daughter board contact; VIDEL timing; capacitor degradation || Reseat RAM daughter board. Clean edge connector contacts. Recap motherboard. Check VIDEL decoupling capacitors.
| 10 || Line 1010 emulator
|-
|-
| System unstable after CT60/CT63 installation || Power supply insufficient; cooling; configuration || The CT60/CT63 accelerator significantly increases power draw and heat. Ensure PSU is freshly recapped and stable. Add supplementary cooling. Verify CT60 firmware version.
| 11 || Line 1111 emulator
|}
|}


== DSP Troubleshooting ==
== Dead unit ==


The Motorola 56001 DSP is central to the Falcon's audio and multimedia capabilities. Common DSP issues:
Atari's procedure when the unit is powered and correctly connected but shows no display (Section 3.3):<ref name="sg" />


=== No DSP Sound ===
# Connect a terminal to the RS-232 port at 9600 bps, 8 data bits, 1 stop bit, no parity (an STE running the VT52 emulator will do), with pins 2 and 3 crossed. Fit the diagnostic cartridge and switch on. If the cartridge's messages appear on the terminal, use the cartridge to find the fault.
The most common cause is poor clock signal integrity. The 32 MHz DSP clock is derived from the same oscillator as other system clocks, and degraded signal edges cause the DSP to malfunction intermittently or completely.
# Otherwise open the machine (see [[Atari Falcon General Maintenance]]). With a scope, check the 32 MHz clock to COMBEL; if it is missing, replace the oscillator. Check the 16 MHz clock to the 68030; if it is missing, replace COMBEL.
# Check the 68030's HALT pin. It should be at TTL high. If it is low the CPU is halted by a bad reset circuit, a double bus error or a bad CPU: watch the BERR input at power-on for low pulses (COMBEL raising bus errors), check the cartridge ROM chip selects XROM3 and XROM4 (replace COMBEL if they are missing), and check the VIDEL display-enable output.
# If the CPU is running, check the MFP serial output (pin 8) and the 1488 driver; RS-232 needs −12 V. Check the VIDEL's RGB or mono outputs; a picture that is present but unreadable points at the screen RAM.


'''Solution:''' Apply the clock buffer patch (74HCT04 hex inverter). This buffers the clock signal to the DSP, SDMA, and DMA chips. Adding 33Ω series resistors on the buffer outputs further reduces ringing and overshoot.<ref>{{cite web |url=https://www.atari-forum.com/viewtopic.php?t=30187 |title=Falcon Clock Patch method |publisher=Atari Forum |access-date=2026-03-27}}</ref>
A CPU too hot to touch for more than a second is, in Atari's words, a strong sign of a bad CPU.<ref name="sg" />


=== DSP Overclocking Issues ===
== Diagnostic cartridge ==
The DSP can be overclocked to 40 MHz or even 50 MHz by replacing the oscillator crystal or using a clock multiplier. Overclocked DSPs may exhibit:


* Intermittent audio glitches
Atari's Falcon030 diagnostic cartridge runs on power-up with loop-back plugs on the ports. If the machine fails before the menu appears, the last message on screen points to the fault; a recoverable failure turns the screen red with a message and several rapid tones. The lowest 2 KB of RAM is tested first and failures are reported to the RS-232 terminal.<ref name="sg" /> Only the diagnostic menu (D) is meant for field use; the unattended and operator sections are for factory testing. If the clock battery has failed, the menu may show fewer choices.<ref name="sg" />
* System crashes during heavy DSP load
* Increased heat generation


If DSP stability issues appear after overclocking, revert to the stock 32 MHz clock to isolate the cause.
The diagnostic menu offers RAM and DSP SRAM (R), OS ROMs (O), MIDI (M), SCC serial (S), timing (T), DSP port (D), floppy (F), printer, joystick and game ports (P), real-time clock (L), BLiTTER (G), SCSI (I) and expansion bus (X), plus audio, video, keyboard and IDE tests that need an operator.<ref name="sg" /> The real-time clock test reports C0 for no clock and C1 for an increment error.<ref name="sg" /> In the audio tests both outputs should give 4 V ± 0.2 V peak to peak.<ref name="sg" />


== PSU Troubleshooting ==
== Symptom checklist ==


The Falcon PSU is the most common single point of failure. Symptoms of a failing PSU:
{| class="wikitable styled-table" style="width:100%;"
 
|+'''Falcon030 symptom checklist (Service Guide Section 5)'''
* '''Gradual voltage drift''' — +5V rail climbing above 5.2V over months/years as capacitors degrade
! Symptom !! Probable cause (Atari)
* '''Intermittent reboots''' — Power dips under load when capacitors can no longer supply peak current
|-
* '''Complete failure''' — No output after capacitors short or open
| Black screen || No power (check the LED), COMBEL, VIDEL; see the dead-unit procedure
 
|-
=== Emergency Diagnostic ===
| White screen || VIDEL, COMBEL, SDMA, 68030; use the diagnostic cartridge with a terminal on the RS-232 port
 
|-
If the Falcon is completely dead:
| Dots or bars on screen || Memory board, COMBEL, VIDEL
# Check the mains fuse in the IEC inlet.
|-
# Disconnect the PSU from the motherboard.
| One colour missing || Video cable or connector, video DAC, VIDEL
# Power on the PSU alone and measure output voltages.
|-
# If no output, check the primary-side bulk capacitor and bridge rectifier.
| Monochrome monitor will not sync but colour works || Monochrome detect not grounded; MFP GPIP bit 7; replace the MFP
# If output is present but out of spec, recap the PSU (see [[Atari Falcon Capacitor Replacement Guide]]).
|-
 
| Scrambled screen || COMBEL
== RAM Troubleshooting ==
|-
 
| Bad TV output || Modulator, phase-locked loop
The Falcon uses a RAM daughter board with 1, 4, or 14 MB of RAM:
|-
 
| Disk will not boot || Power supply, AJAX, SDMA, sound chip (PSG), IRQ lines shorted to ground; check the drive select light and motor, swap the drive
* '''1 MB''' — Two 1 Mbit×4 DRAM chips (256 KB × 4)
|-
* '''4 MB''' — Eight 1 Mbit×4 DRAM chips
| Disk will not format || AJAX, SDMA, drive
* '''14 MB''' — Populated with 4 Mbit DRAM chips (16 MB physical, 14 MB addressable due to 24-bit address bus)
|-
| Crash after loading files || Disk, drive, AJAX, SDMA or COMBEL
|-
| Red screen: keyboard not responding || Keyboard, 6850, MFP
|-
| Red screen: MIDI errors || Opto-isolator, 6850, 74LS06 inverter
|-
| Red screen: SCC error || SCC, 1489 receiver, 1488 driver, PSG, ±12 V DC-to-DC inverting supply
|-
| Red screen: printer error || PSG, MFP
|-
| Shadow printing || Cables, terminator resistors, LS244 and LS245 drivers
|-
| Red screen: DMA error || SDMA, COMBEL, AJAX (loading the bus), 5380 SCSI controller
|-
| No DMA sound || +8 V regulator, ± supplies, DSP, CODEC, SDMA
|}


Contact problems between the RAM daughter board and the motherboard are common. Symptoms include:
In the parts list AJAX is the floppy controller, the MFP is an MC68901 (U31), the SCC a Z85C30 (U13), the RS-232 driver and receiver a 1488 (U5) and 1489A (U6, U14), the two ACIAs 68B50s (U24, U52), and the real-time clock a DS1287 (U64).<ref name="sg" />


* Black screen on boot
== Clock battery ==
* Memory test failures
* Jailbar patterns on display


'''Solution:''' Remove the RAM board, clean the edge connector contacts with IPA and a pencil eraser, clean the motherboard socket, and reseat firmly.
The real-time clock (U64) is a Dallas DS1287 with its own 3.6 V lithium cell and crystal; the cell cannot be changed separately. See [[Atari Falcon General Maintenance#Real-time clock battery]].<ref name="sg" />


== See Also ==
== Related pages ==
* [[Atari Falcon030]]
* [[Atari Falcon030]]
* [[Atari Falcon General Maintenance]]
* [[Atari Falcon General Maintenance]]
Line 115: Line 110:
<references />
<references />


{{Navbox-AtariVintageComputers}}
{{Navbox-AtariVintageComputers|state=collapsed}}


[[Category:Atari Systems]]
[[Category:Atari Troubleshooting Guides]]
[[Category:Atari Troubleshooting Guides]]
[[Category:Troubleshooting Guides]]

Latest revision as of 00:35, 1 October 2026

Atari Falcon030

Fault-finding on the Atari Falcon030 follows Atari's Falcon030 Service Guide (C303062-001, 1 October 1992): its procedure for a dead unit, the Falcon030 diagnostic cartridge, and the symptom checklist in section 5.[1]

Before you start

[edit | edit source]
  • Check the power supply first: +5 V and +12 V at the main board. Atari sets +5 V to 5.05 ± 0.1 V with a 4.0 A load and allows 5 % regulation on +5 V and 10 % on +12 V, with ripple and noise of 100 mV p-p each.[1]
  • Check that the monitor works and is the right type. The board reads the monochrome-detect line at power-up; if it does not see a low there, the VIDEL drives RGB instead of mono.[1]
  • Before blaming the hardware for a crash, check the disk and drive: Atari notes that errors loading files from disk can crash the system.[1]

Start-up and bombs

[edit | edit source]

After a reset the 68030 starts from the ROM, checks the cartridge port for a diagnostic or boot cartridge, initialises memory, the sound chip, the palettes, the MFP and the screen, then tries to boot from floppy and hard disk before loading the desktop from ROM.[1] Exceptions without a handler draw bombs on the screen, one per exception number:[1]

Number of bombs (Service Guide p. 62)
Bombs Meaning
2 Bus error, asserted by COMBEL
3 Address error: word or long word access at an odd address
4 Illegal instruction
5 Divide by zero
6 CHK instruction without a handler
7 TRAPV instruction without a handler
8 Privilege violation
9 Trace
10 Line 1010 emulator
11 Line 1111 emulator

Dead unit

[edit | edit source]

Atari's procedure when the unit is powered and correctly connected but shows no display (Section 3.3):[1]

  1. Connect a terminal to the RS-232 port at 9600 bps, 8 data bits, 1 stop bit, no parity (an STE running the VT52 emulator will do), with pins 2 and 3 crossed. Fit the diagnostic cartridge and switch on. If the cartridge's messages appear on the terminal, use the cartridge to find the fault.
  2. Otherwise open the machine (see Atari Falcon General Maintenance). With a scope, check the 32 MHz clock to COMBEL; if it is missing, replace the oscillator. Check the 16 MHz clock to the 68030; if it is missing, replace COMBEL.
  3. Check the 68030's HALT pin. It should be at TTL high. If it is low the CPU is halted by a bad reset circuit, a double bus error or a bad CPU: watch the BERR input at power-on for low pulses (COMBEL raising bus errors), check the cartridge ROM chip selects XROM3 and XROM4 (replace COMBEL if they are missing), and check the VIDEL display-enable output.
  4. If the CPU is running, check the MFP serial output (pin 8) and the 1488 driver; RS-232 needs −12 V. Check the VIDEL's RGB or mono outputs; a picture that is present but unreadable points at the screen RAM.

A CPU too hot to touch for more than a second is, in Atari's words, a strong sign of a bad CPU.[1]

Diagnostic cartridge

[edit | edit source]

Atari's Falcon030 diagnostic cartridge runs on power-up with loop-back plugs on the ports. If the machine fails before the menu appears, the last message on screen points to the fault; a recoverable failure turns the screen red with a message and several rapid tones. The lowest 2 KB of RAM is tested first and failures are reported to the RS-232 terminal.[1] Only the diagnostic menu (D) is meant for field use; the unattended and operator sections are for factory testing. If the clock battery has failed, the menu may show fewer choices.[1]

The diagnostic menu offers RAM and DSP SRAM (R), OS ROMs (O), MIDI (M), SCC serial (S), timing (T), DSP port (D), floppy (F), printer, joystick and game ports (P), real-time clock (L), BLiTTER (G), SCSI (I) and expansion bus (X), plus audio, video, keyboard and IDE tests that need an operator.[1] The real-time clock test reports C0 for no clock and C1 for an increment error.[1] In the audio tests both outputs should give 4 V ± 0.2 V peak to peak.[1]

Symptom checklist

[edit | edit source]
Falcon030 symptom checklist (Service Guide Section 5)
Symptom Probable cause (Atari)
Black screen No power (check the LED), COMBEL, VIDEL; see the dead-unit procedure
White screen VIDEL, COMBEL, SDMA, 68030; use the diagnostic cartridge with a terminal on the RS-232 port
Dots or bars on screen Memory board, COMBEL, VIDEL
One colour missing Video cable or connector, video DAC, VIDEL
Monochrome monitor will not sync but colour works Monochrome detect not grounded; MFP GPIP bit 7; replace the MFP
Scrambled screen COMBEL
Bad TV output Modulator, phase-locked loop
Disk will not boot Power supply, AJAX, SDMA, sound chip (PSG), IRQ lines shorted to ground; check the drive select light and motor, swap the drive
Disk will not format AJAX, SDMA, drive
Crash after loading files Disk, drive, AJAX, SDMA or COMBEL
Red screen: keyboard not responding Keyboard, 6850, MFP
Red screen: MIDI errors Opto-isolator, 6850, 74LS06 inverter
Red screen: SCC error SCC, 1489 receiver, 1488 driver, PSG, ±12 V DC-to-DC inverting supply
Red screen: printer error PSG, MFP
Shadow printing Cables, terminator resistors, LS244 and LS245 drivers
Red screen: DMA error SDMA, COMBEL, AJAX (loading the bus), 5380 SCSI controller
No DMA sound +8 V regulator, ± supplies, DSP, CODEC, SDMA

In the parts list AJAX is the floppy controller, the MFP is an MC68901 (U31), the SCC a Z85C30 (U13), the RS-232 driver and receiver a 1488 (U5) and 1489A (U6, U14), the two ACIAs 68B50s (U24, U52), and the real-time clock a DS1287 (U64).[1]

Clock battery

[edit | edit source]

The real-time clock (U64) is a Dallas DS1287 with its own 3.6 V lithium cell and crystal; the cell cannot be changed separately. See Atari Falcon General Maintenance#Real-time clock battery.[1]

[edit | edit source]

References

[edit | edit source]
  1. ↑ 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 Atari Corporation, Atari Falcon030 Service Guide, C303062-001, 1 October 1992. Section 1.3 (power supply, pp. 4–5), Section 2.4–2.5 (system start-up and bombs, pp. 61–62), Section 3 (testing, pp. 65–97), Section 5 (symptom checklist, pp. 103–105), Section 7 (parts list). Hosted here as File:Atari Falcon030 Service Guide C303062-001.pdf.


Retrieved from "https://wiki.retrotechcollection.com/index.php?title=Atari_Falcon_Troubleshooting_Guide&oldid=17036"