<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/">
	<channel>
		<title><![CDATA[Dr Vintage - Because it's worth it ! - Documentation]]></title>
		<link>https://dr-vintage.com/forum/</link>
		<description><![CDATA[Dr Vintage - Because it's worth it ! - https://dr-vintage.com/forum]]></description>
		<pubDate>Wed, 06 May 2026 17:50:23 +0000</pubDate>
		<generator>MyBB</generator>
		<item>
			<title><![CDATA[Amiga 500 : codes d'erreur au démarrage (non traduit)]]></title>
			<link>https://dr-vintage.com/forum/showthread.php?tid=182</link>
			<pubDate>Mon, 01 Oct 2018 15:47:56 +0200</pubDate>
			<dc:creator><![CDATA[<a href="https://dr-vintage.com/forum/member.php?action=profile&uid=2">Dr Vintage</a>]]></dc:creator>
			<guid isPermaLink="false">https://dr-vintage.com/forum/showthread.php?tid=182</guid>
			<description><![CDATA[<span style="font-weight: bold;" class="mycode_b">During boot-up, the Amiga is going through a series of system checks and routines.</span><br />
<ol type="1" class="mycode_list"><li>Clear all chips of old data<br />
</li>
<li>Disable DMA and interrupts during the test.<br />
</li>
<li>Clear the screen.<br />
</li>
<li>Check the hardware ....checks to see if 68000 is functioning.<br />
</li>
<li>Change screen color.<br />
</li>
<li>Do a checksum test on all ROMS.<br />
</li>
<li>Change screen color.<br />
</li>
<li>Beginning of system startup.<br />
</li>
<li>Check RAM at &#36;C0000 and move SYSBASE there<br />
</li>
<li>Test All CHIP RAM.<br />
</li>
<li>Change screen color.<br />
</li>
<li>Check that software is coming in ok.<br />
</li>
<li>Change screen color.<br />
</li>
<li>Setup CHIP RAM to receive data.<br />
</li>
<li>Link the libraries<br />
</li>
<li>Check for additional memory and link it<br />
</li>
<li>Turn the DMA and interrupts back on.<br />
</li>
<li>Start a default task.<br />
</li>
<li>Check for 68010, 68020, 68881 or other processor upgrades.<br />
</li>
<li>Check to see if there is an exception or processor error<br />
</li>
<li>If so do a system reset. <br />
</li>
</ol>
During this system test the Amiga is sending vital information to the<br />
screen with colors. If the system checks out ok, you will see the following<br />
sequence that you have seen so many times.<br />
 <br />
<span style="font-weight: bold;" class="mycode_b">DARK GRAY:</span>  The initial hardware tested OK. the 68000 is running and the registers are readable.<br />
<span style="font-weight: bold;" class="mycode_b">LIGHT GRAY:</span> The software is coming in and seems OK.<br />
<span style="font-weight: bold;" class="mycode_b">WHITE:</span> The initialization test have passed.<br />
<br />
<span style="font-weight: bold;" class="mycode_b">The failure mode screen colors:</span><ul class="mycode_list"><li>Turquoise (0x0CC) (A1000 only): RAM failure in the Kickstart WCS<br />
</li>
<li>Green (0x0F0) error in the lowest 256 bytes of Chip RAM. Possible causes, defective CIA-A IC or defective Agnus IC.<br />
</li>
<li>Yellow (0xFE5) an unexpected processor exception before the appropriate system failure message was prepared. This could mean defective hardware or an attempt to access a RAM address where no RAM exists.<br />
</li>
<li>Red (0xF00) invalid KickStart ROM checksum.<br />
</li>
<li>Magenta (0xF0F) single-task or cold-start initialization failed.<br />
</li>
</ul>
<span style="font-weight: bold;" class="mycode_b">Another listing of screen color interpretations:</span> <br />
<a href="https://flic.kr/p/2adKT2a" target="_blank" rel="noopener" class="mycode_url"><img src="https://farm2.staticflickr.com/1927/44120262855_c5de000eb8.jpg" loading="lazy"  alt="[Image: 44120262855_c5de000eb8.jpg]" class="mycode_img" /></a><br />
<br />
If the Amiga caps lock key LED blinks repeatedly at boot up, another series of error messages must be consulted:<ul class="mycode_list"><li>One blink: keyboard ROM checksum error<br />
</li>
<li>Two blinks: RAM failure<br />
</li>
<li>Three blinks: watchdog timer failure<br />
</li>
</ul>
If something is wrong with your system, you may see the following:<ul class="mycode_list"><li><span style="font-weight: bold;" class="mycode_b">RED:</span> Error was found in ROMS.<br />
</li>
<li><span style="font-weight: bold;" class="mycode_b">GREEN:</span> Error found in the CHIP RAM.<br />
</li>
<li><span style="font-weight: bold;" class="mycode_b">BLUE:</span> Error was found in the custom chips.<br />
</li>
<li><span style="font-weight: bold;" class="mycode_b">YELLOW:</span> If 68000 found an error before the error trapping software (GURU) was running.<br />
</li>
</ul>
 The Keyboard has it's own processor, RAM and ROM. A selftest is performed on power-up in the following sequence.<br />
<ol type="1" class="mycode_list"><li>Performs checksum on ROM's<br />
</li>
<li>Checks 64 bytes of RAM.<br />
</li>
<li>The timer is tested.<br />
</li>
<li>Performs handshake with computer and gives results of self-test.<br />
</li>
</ol>
If the keyboard does not pass the test it will notify you that it is not working properly. This information is indicated with the blinking of the CAPS-LOCK light.<ul class="mycode_list"><li><span style="font-weight: bold;" class="mycode_b">One Blink: </span>   Keyboard ROM check failed.<br />
</li>
<li><span style="font-weight: bold;" class="mycode_b">Two Blinks: </span>  Keyboard RAM checked failed.<br />
</li>
<li><span style="font-weight: bold;" class="mycode_b">Three Blinks:</span> Watch dog timer failed<br />
</li>
<li><span style="font-weight: bold;" class="mycode_b">Four Blinks:</span>  A short between two row lines or special control keys.<br />
</li>
</ul>
]]></description>
			<content:encoded><![CDATA[<span style="font-weight: bold;" class="mycode_b">During boot-up, the Amiga is going through a series of system checks and routines.</span><br />
<ol type="1" class="mycode_list"><li>Clear all chips of old data<br />
</li>
<li>Disable DMA and interrupts during the test.<br />
</li>
<li>Clear the screen.<br />
</li>
<li>Check the hardware ....checks to see if 68000 is functioning.<br />
</li>
<li>Change screen color.<br />
</li>
<li>Do a checksum test on all ROMS.<br />
</li>
<li>Change screen color.<br />
</li>
<li>Beginning of system startup.<br />
</li>
<li>Check RAM at &#36;C0000 and move SYSBASE there<br />
</li>
<li>Test All CHIP RAM.<br />
</li>
<li>Change screen color.<br />
</li>
<li>Check that software is coming in ok.<br />
</li>
<li>Change screen color.<br />
</li>
<li>Setup CHIP RAM to receive data.<br />
</li>
<li>Link the libraries<br />
</li>
<li>Check for additional memory and link it<br />
</li>
<li>Turn the DMA and interrupts back on.<br />
</li>
<li>Start a default task.<br />
</li>
<li>Check for 68010, 68020, 68881 or other processor upgrades.<br />
</li>
<li>Check to see if there is an exception or processor error<br />
</li>
<li>If so do a system reset. <br />
</li>
</ol>
During this system test the Amiga is sending vital information to the<br />
screen with colors. If the system checks out ok, you will see the following<br />
sequence that you have seen so many times.<br />
 <br />
<span style="font-weight: bold;" class="mycode_b">DARK GRAY:</span>  The initial hardware tested OK. the 68000 is running and the registers are readable.<br />
<span style="font-weight: bold;" class="mycode_b">LIGHT GRAY:</span> The software is coming in and seems OK.<br />
<span style="font-weight: bold;" class="mycode_b">WHITE:</span> The initialization test have passed.<br />
<br />
<span style="font-weight: bold;" class="mycode_b">The failure mode screen colors:</span><ul class="mycode_list"><li>Turquoise (0x0CC) (A1000 only): RAM failure in the Kickstart WCS<br />
</li>
<li>Green (0x0F0) error in the lowest 256 bytes of Chip RAM. Possible causes, defective CIA-A IC or defective Agnus IC.<br />
</li>
<li>Yellow (0xFE5) an unexpected processor exception before the appropriate system failure message was prepared. This could mean defective hardware or an attempt to access a RAM address where no RAM exists.<br />
</li>
<li>Red (0xF00) invalid KickStart ROM checksum.<br />
</li>
<li>Magenta (0xF0F) single-task or cold-start initialization failed.<br />
</li>
</ul>
<span style="font-weight: bold;" class="mycode_b">Another listing of screen color interpretations:</span> <br />
<a href="https://flic.kr/p/2adKT2a" target="_blank" rel="noopener" class="mycode_url"><img src="https://farm2.staticflickr.com/1927/44120262855_c5de000eb8.jpg" loading="lazy"  alt="[Image: 44120262855_c5de000eb8.jpg]" class="mycode_img" /></a><br />
<br />
If the Amiga caps lock key LED blinks repeatedly at boot up, another series of error messages must be consulted:<ul class="mycode_list"><li>One blink: keyboard ROM checksum error<br />
</li>
<li>Two blinks: RAM failure<br />
</li>
<li>Three blinks: watchdog timer failure<br />
</li>
</ul>
If something is wrong with your system, you may see the following:<ul class="mycode_list"><li><span style="font-weight: bold;" class="mycode_b">RED:</span> Error was found in ROMS.<br />
</li>
<li><span style="font-weight: bold;" class="mycode_b">GREEN:</span> Error found in the CHIP RAM.<br />
</li>
<li><span style="font-weight: bold;" class="mycode_b">BLUE:</span> Error was found in the custom chips.<br />
</li>
<li><span style="font-weight: bold;" class="mycode_b">YELLOW:</span> If 68000 found an error before the error trapping software (GURU) was running.<br />
</li>
</ul>
 The Keyboard has it's own processor, RAM and ROM. A selftest is performed on power-up in the following sequence.<br />
<ol type="1" class="mycode_list"><li>Performs checksum on ROM's<br />
</li>
<li>Checks 64 bytes of RAM.<br />
</li>
<li>The timer is tested.<br />
</li>
<li>Performs handshake with computer and gives results of self-test.<br />
</li>
</ol>
If the keyboard does not pass the test it will notify you that it is not working properly. This information is indicated with the blinking of the CAPS-LOCK light.<ul class="mycode_list"><li><span style="font-weight: bold;" class="mycode_b">One Blink: </span>   Keyboard ROM check failed.<br />
</li>
<li><span style="font-weight: bold;" class="mycode_b">Two Blinks: </span>  Keyboard RAM checked failed.<br />
</li>
<li><span style="font-weight: bold;" class="mycode_b">Three Blinks:</span> Watch dog timer failed<br />
</li>
<li><span style="font-weight: bold;" class="mycode_b">Four Blinks:</span>  A short between two row lines or special control keys.<br />
</li>
</ul>
]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[Amiga 500-600-1000-1200]]></title>
			<link>https://dr-vintage.com/forum/showthread.php?tid=33</link>
			<pubDate>Thu, 14 Dec 2017 11:41:22 +0100</pubDate>
			<dc:creator><![CDATA[<a href="https://dr-vintage.com/forum/member.php?action=profile&uid=1">TheDoc</a>]]></dc:creator>
			<guid isPermaLink="false">https://dr-vintage.com/forum/showthread.php?tid=33</guid>
			<description><![CDATA[<a href="http://classiccomputers.info/down/Commodore/Amiga/Amiga_A500_A2000_Technical_Reference%20Manual_1987.pdf" target="_blank" rel="noopener" class="mycode_url">Amiga 500-2000 Technical Manual</a>]]></description>
			<content:encoded><![CDATA[<a href="http://classiccomputers.info/down/Commodore/Amiga/Amiga_A500_A2000_Technical_Reference%20Manual_1987.pdf" target="_blank" rel="noopener" class="mycode_url">Amiga 500-2000 Technical Manual</a>]]></content:encoded>
		</item>
	</channel>
</rss>