Article View: pl.comp.sys.amiga
Article #66127Re: A500 problem
From: Vituniu
Date: Wed, 05 Aug 2009 13:12
Date: Wed, 05 Aug 2009 13:12
76 lines
3322 bytes
3322 bytes
> Witam chciałem się zapytać jaki problem sygnalizuje a500 miganiem > diody power przy podłączeniu zasilania ? Masz ja podpieta pod jakis monitor/tv? Cos sie dzieje na ekranie po wlaczeniu? > Mam uszkodzoną 500ke i chciałbym ją zreanimować ale nie wiem > czego się chwycić Na poczatek - mlotka. Metaforycznie. :) Podociskaj wszystkie uklady w podstawkach. Serio. > Dodam tylko że po włączeniu zasilania nic więcej poza zieloną diodą > power migającą raz ciemniej raz jeśniej się nie dzieje A500 nie próbuje > szukać systemu na FDD lampka od FDD nie zaświeca się Przeklejam po angielsku: ========================================== Problem: Amiga system will not boot. Screen flashes colors or keyboard lights flash. You may notice that when you turn on or reset your Amiga a few different colors flash by. These actually mean something. Here you go: RED Bad ROM YELLOW CPU Exception Before Bootstrap Code is Loaded GREEN Bad Chip RAM or Agnus (check seating of Agnus) BLACK No CPU WHITE Expansion passed GREY CPU Passed Constant white is failure of CPU. Or as taken from the Amiga 4000 Service Manual: Passed Test Light Gray Initial hardware configuration tests passed. Initial system software tests passed. Final initialization test passed. Failed Test Red ROM Error - Reseat or replace Green CHIP RAM error (reset AGNUS and re-test) Blue Custom Chip(s) Error Yellow 68000 detected error before software trapped it (GURU) The system performs the following test sequence: 1. Delays beginning the tests a fraction of a second to allow the hardware to stabilize. 2. Jumps to ROM code in diagnostic card (if found) 3. Disables and clears all DMA and interrupts. 4. Turns on the screen. 5. Checks the general hardware configuration. If the screen remains a light gray colors and the tests continue, the hardware is OK. If an error occurs, the system halts. 6. Performs checksum test on ROMs. If the system fails the ROM test, the screen display turns red and the system halts. Keyboard One Blink ROM Checksum failure Two blinks RAM test failed Three Blinks Watchdog timer failed Four blinks A short exists between two row lines or one of the seven special keys (not implemented) Five Blinks Your keyboard has become nuclear. RUN! ========================================== pozdrawiam, Vituniu.
Technical Details
Message-ID:
<h5c14i$8b7$1@nemesis.news.neostrada.pl>Path:
mbox-mo1.pugleaf.net!news-archive.icm.edu.pl!news.gazeta.pl!newsfeed.pionier.net.pl!newsfeed.neostrada.pl!atlantis.news.neostrada.pl!news.neostrada.pl!not-for-mailReferences:
<h5bu8h$i8l$1@news.wp.pl>Show Full Headers
Complete Article Headers
Path: mbox-mo1.pugleaf.net!news-archive.icm.edu.pl!news.gazeta.pl!newsfeed.pionier.net.pl!newsfeed.neostrada.pl!atlantis.news.neostrada.pl!news.neostrada.pl!not-for-mail From: "Vituniu" <vituniu@poczta.fm> Newsgroups: pl.comp.sys.amiga Subject: Re: A500 problem Date: Wed, 5 Aug 2009 15:12:48 +0200 Organization: TP - http://www.tp.pl/ Lines: 77 Message-ID: <h5c14i$8b7$1@nemesis.news.neostrada.pl> References: <h5bu8h$i8l$1@news.wp.pl> NNTP-Posting-Host: ffj58.internetdsl.tpnet.pl Mime-Version: 1.0 X-Trace: nemesis.news.neostrada.pl 1249478610 8551 83.13.139.58 (5 Aug 2009 13:23:30 GMT) X-Complaints-To: usenet@news.neostrada.pl NNTP-Posting-Date: Wed, 5 Aug 2009 13:23:30 +0000 (UTC) X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 6.00.2800.1933 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1933 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit