0 Members and 1 Guest are viewing this topic.
Thanks everyone for your help.. very much appreciated. Ironically I got my 500 to work using these techniques LOL I'd still like to get my 2000 working. But that will have to wait a while. At least the offending battery has been removed!Again Thanks!
(1) Amiga system routineAmiga system test is a complicated set of routines which it must gothrough before you can do any work on it. During the system test the Amigais attempting to let you know if the system is well. Here is a list of thestart-up activities:1. Clear all chips of old data2. Disable DMA and interrupts during the test.3. Clear the screen.4. Check the hardware ....checks to see if 68000 is functioning.5. Change screen color.6. Do a checksum test on all ROMS.7. Change screen color.8. Beginning of system startup.9. Check RAM at $C0000,and move SYSBASE there10. Test All CHIP RAM.11. Change screen color.12. Check that software is coming in ok.13. Change screen color.14. Setup CHIP RAM to receive data.15. Link the libraries16. Check for additional memory and link it17. Turn the DMA and interrupts back on.18. Start a default task.19. Check for 68010,68020, and or 68881.20. Check to see if there is an exception ...processor error21. If so do a system reset.During this system test the Amiga is sending vital information to thescreen with colors. If the system checks out ok, you will see the followingsequence that you have seen so many times.DARK GRAY: The initial hardware tested OK. the 68000 is runningand the registers are readable.LIGHT GRAY: The software is coming in and seems OK.WHITE: The initialization test have passed.If something is wrong with your system, you may see the following:RED: Error was found in ROMS.GREEN: Error found in the CHIP RAM.BLUE: Error was found in the custom chips.YELLOW: If 68000 found an error before the error trapping software (GURU)was running.
(2) The AmigaOS has built in to it a way to let you know what is wrong ifsomething happens to fail.When you reset or first start up, the system performs the following testsequence1.. Delays beginning the tests a fraction of a second to allow thehardware to stabilize.2.. Jumps to ROM code in diagnostic card (if found)3.. Disables and clears all DMA and interupts.4.. Turns on the screen.5. Checks the general hardware configuration. Ifthe screen remains a light gray colours and the tests continue, the hardwareis OK. If an error occurs, the system halts.5.. Performs checksum test on ROMs. If the system fails the ROM test, thescreen display turns red and the system halts.If anything is wrong a color is flashed upon the screen as a visual resultcode. These are:a.. Passed Test Light Grey Initial hardware configuration tests passed.b.. Initial system software tests passed.c.. Final initialization test passed.d.. Failed Test Red ROM Error - Reseat or replacee.. Green CHIP RAM error (reset AGNUS and re-test)f.. Blue Custom Chip(s) Errorg.. Yellow 68000 detected error before software trapped it (GURU)Also the Caps lock light will/may blink to diagnose certain ailments.a.. One Blink ROM Checksum failureb.. Two blinks RAM test failedc.. Three Blinks Watchdog timer failed