Amiga Error Codes

SOURCE: www.lemonamina.com

AMIGA BOOT SEQUENCE

1 Clear all of the chips of old data
2 Disable DMA and interrupts during the test
3 Clear the screen
4 Check the Hardware to make sure the 68000 is working
5 Change the screen to Black, the screen stays Black (or with red Stripes) if CPU fault
6 Do a checksum test on all the ROMS
7 Change screen to Red if ROMs are faulty, or change to Dark Gray if ROMs are OK
8 Begin the system startup
9 Check the Ram at $C0000, and move SYS_BASE there
10 Test all of the chip RAM
11 Change screen color to Green if RAM is faulty, or change to Light Grey if RAM is OK
12 Check to see if the ROM software is coming in OK and being executed
13 Change color to White if the software test is OK, stays Light Grey if faulty, or Blue if Custom Chip error
14Set up the chip ram to receive data
15Link the ROM libraries so the machine can identify connected devices and peripherals
16Check for additional memory in these devices and link it to the computer
16BChance screen color to Yellow if there is an error with external cards/devices
17Turn the DMA and Interrupts back on
18Start a default task
19Check to see if there are additional CPUs on the system, accelerators or a maths coprocessor
20Check to see if there CPUs are OK
21AIf there is an Exception (processor error), or issue reported, the system will reboot
21BThe Kickstart Image is Displayed showing that the rom has been installed to memory, is running, and everything so far has reported OK. After this, the ROM GURU trap handler will display errors as codes on the screen

AMIGA BOOT COLORS

AMIGA BOOT COLORS / ERROR CODES

AMIGA BOOT BLINKS ON THE POWER LED

Fast steady power LED blink; dark screen74S51 (U9I) & 74F74 (U8I) damaged from expansion port (A100)
A Dim LED with no blinksCan indicate a Buster issue (A200)
4 Blinks then a 5 second pauseThis is normal and part of its boot sequence, but can also indicate a bad Kickstart disk. If there is no Kickstart image appearing after the blinks, check and replace the disk drive (A1000)
6 or 7 BlinksIs usually broken tracks around the battery area after an acid leak, or battery issues with an expansion
9 Short Blinks + 1 long (with Red Screen)Continuously means bad ram (A2000)
10 BlinksSystem is waiting to connect to a remote debugger or terminal
10 Short + 1 Long Blink (with Green Screen)Faulty Agnus Chip (try clean and re-insert)
Constant Blink (with Yellow Screen)Indicated either faulty capacitors on the main PCB, or a general issue with the +5V power or power supply

AMIGA BOOT BLINKS ON THE KEYBOARD CAPS-LOCK LED

1 BlinkKeyboard ROM checksum failure or ROM fault.
2 BlinksKeyboard RAM test failed
3 BlinksKeyboard Watchdog timer failed (IC 741s 123 or associated circuitry)
4 BlinksA short exists between two row lines or one of the seven special keys (not implemented)
No FlashesMain PCB fault

* When the Caps Lock key is repeatedly pressed approx. 10 times, the Caps Lock LED turning on and off each time indicates the CPU is correctly reading the CIAs. If the Caps Lock LED sticks on or off, the CPU is not servicing CIA interrupt requests. If the Caps Lock key blinks with a fault, simply replace the keyboard.

GURU MEDITATION ERROR CODES

Amiga Guru Meditation Error

The alert itself appears as a black rectangular box located in the upper portion of the screen. Its border and text are red for a normal Guru Meditation, or green/yellow for a Recoverable Alert, another kind of Guru Meditation. The screen goes black, and the power and disk-activity LEDs may blink immediately before the alert appears. In AmigaOS 1.x, programmed in ROMs known as Kickstart 1.1, 1.2, and 1.3, the errors are always red. In AmigaOS 2.x and 3.x, recoverable alerts are yellow, except for some very early versions of 2.x where they were green.

 

Dead-end alerts are always red and terminal in all OS versions except in a rare series of events, as in when a deprecated Kickstart program conditionally boots from disk on a more advanced Kickstart 3.x ROM Amiga running in compatibility mode (therefore eschewing the on-disk OS) and crashes with a red Guru Meditation but subsequently restores itself by pressing the left mouse button, the newer Kickstart recognizing an in advised low-level chipset call for the older ROM directly poking the hardware, and addressing it.

 

The alert occurred when there was a fatal problem with the system. If the system had no means of recovery, it could display the alert, even in systems with numerous critical flaws. In extreme cases, the alert could even be displayed if the system’s memory was completely exhausted.

 

The error is displayed as two fields, separated by a period. The format is #0000000x.yyyyyyyy in case of a CPU error, or #aabbcccc.dddddddd in case of a system software error.

 

The first field is either the Motorola 68000 exception number that occurred (if a CPU error occurs) or an internal error identifier (such as an ‘Out of Memory’ code), in case of a system software error. The second can be the address of a Task structure or the address of a memory block whose allocation or deallocation failed. It is never the address of the code that caused the error. If the cause of the crash is uncertain, this number is rendered as 48454C50, which stands for “HELP” in hexadecimal ASCII characters (48=H, 45=E, 4C=L, 50=P).

 

The text of the alert messages was completely baffling to most users. Only highly technically adept Amiga users would know, for example, that exception 3 was an address error and meant the program was accessing a word on an unaligned boundary. Users without this specialized knowledge would have no recourse but to look for a “Guru” or to simply reboot the machine and hope for the best.

GENERAL ERROR CODES

01Not enough memory
02Couldn't make library
03Can't open library
04Can't open device
05Can't open resource
06I/O error
07No signal
08Bad parameters
09Close library failed: usually too many closes
0AClose device failed: or a mismatched close
0BProcess creation failed

CPU EXCEPTIONS

0002Bus Error
0003Addressing error
0004Illegal instruction
0005Divide by zero
0006CHK instruction
0007TRAPV instruction
0008Privilege violation
0009Trace
000AOpCode 1010
000BOpCode 1111
000EStack frame format error
0018Spurious interrupt error
0019 to 001FAutoVector Level 1 to 7 int error

GRAPHICS LIBRARY

0000Graphics out of memory
0001MonitorSpec alloc, no memory
0006Long frame, no memory
0007Short frame, no memory
0009Text, no memory for TmpRas
000ABitBitMap, no memory
000BRegions, memory not available
0030Make V Por, no memory
000C(GFX New Error)
000D(GFX Free Error)
1234Emergency memory not available
0401Unsupported font description used

LAYERS LIBRARY

0000Layers out of memory

EXPANSION LIBRARY

0001Freed free memory

TRACKDISK DEVICE

0001Calibrate: seek error
0002Delay: error on timer wait

DISK RESOURCE

0001Get unit: already has a disk
0002Interrupt: no active unit

CONSOLE DEVICE

0001Console can't open initial window

BOOTSTRAP

0001Boot code returned an error

ALERT OBJECTS

8001ExecLib
8002GraphicsLib
8003LayersLib
8004Intuition
8005MathLib
8007DOSLib
8008RAMLib
8009IconLib
800AExpansionLib
800BDiskfontLib
800CUtilityLib
800DKeyMapLib
8010AudioDev
8011ConsoleDev
8012GamePortDev
8013KeyboardDev
8014TrackDiskDev
8015TimerDev
8020CIARsrc
8021DiskRsrc
8022MiscRsrc
8030BootStrap
8031Workbench
8032Diskcopy
8033GadTools
8035Unknown

EXEC LIBRARY

000168000 exception vector checksum (obs)
0002Execbase checksum bad (obs)
0003Library checksum failure
0005Corrupt memory list detected in FreeMem
0006No memory for interrupt servers
0007InitStruct() of an APTR source (obs)
0008A semaphore is in an illegal state of Rem Semaphore()
0009Freeing memory that is already free
000AIllegal 68K exception taken (obs)
000BAttempt to reuse active OIRequest
000CSanity check on memory list failed during AvailMem (MEMF_LARGEST)
000DIO attempted on close IORequest
000EStack appears to extend out of range
000FMemory header not located. Usually an invalid address passed to FreeMem
0010An attempt was made to use the old message semaphores
00FFA quick interrupt has happened to an uninitialised vector

INTUITION LIBRARY

0001Unknown gadget type
0002Create port, no memory
0003Item plane alloc, no memory
0004Sub alloc, no memory
0005Plane alloc, no memory
006Item box top
0007Open screen, no memory
0008Open screen, raster alloc, no memory
0009Open sys screen, unknown type
000AAdd SW gadgets, no memory
000BOpen window, no memory
000CBad Stare Return entering Intuition
000DBad message received by IDCMP
000EWeird echo causing incomprehension
000FCouldn't open the Console Device
0010Intuition skipped obtaining a sem
0011Intuition obtained a sem in bad order

WORKBENCH

0001No fonts
0001WB Bad Startup Msg1
0002WB Bad Startup Msg2
0003WB Bad IO Msg
0004WB Init Potion Alloc Drawer
0005WB Create WB Menus Create Menus1
0006WB Create WB Menus Create Menus2
0007WB Layout WB Menus Layout Menus
0008WB Add Tool Menu Item
000AWB InitTimer
000BWB Init Layer Demon
000CWB Init WB Gels
000DWB Init Screen and Windows1
000EWB Init Screen and Windows2
000FWB Init Screen and Windows3
0010WBMAlloc

RAMLIB LIBRARY

0001Overlays are illegal for library segments

TIMER DEVICE

0001Bad request
0002Power supply: no 50/60 Hz ticks

DOS LIBRARY

0001No memory at startup
0002EndTask didn't
0003Qpkt failure
0004Unexpected packet received
0005Freevec failed
0006Disk block sequence error
0007Bitmap corrupt
0008Key already free
0009Invalid checksum
000ADisk error
000BKey out of range
000CBad overlay
000DInvalid init packet for CLI/SHELL

AMIGADOS ERROR CODES Displayed in CLI or Shell

103No free store
105Task table full
114Bad temlate
115Bad number
116Required arg missing
117Key needs arg
118Too many args
119Unmatched quotes
120Line too long
121File no object
122Invalid resident library
201No default dir
202Object in use
203Object exists
204Dir not found
205Object not found
206Bad stream name
207Object too large
209Action not known
210Invalid component name
211Invalid lock
212Object wrong type
213Disk not validated
214Disk write protected
215Rename across devices
216Directory not empty
217Too many levels
218Device not mounted
219Seek error
220Comment too big
221Disk full
222Delete protected
223Write protected
224Read protected
225Not a DOS disk
226No disk
233Is soft linked
234Object linked
235Bad hunk
236Not implemented
240Record no locked
241Lock collision
242Lock timeout
243Unlock error
303Buffer overflow
304***Break
305File not executable
Retrospection Logo Landscape

Leave a Reply

Your email address will not be published. Required fields are marked *