Amiga 2000 Green Screen

[Frankencelery]

I've got an Amiga 2000 rev 6.x motherboard that gives an instant green screen on power on.  There WAS slight battery leakage, but the damage, if any, appears to be superficial.  

I know that green screen means chip ram, but I've had no luck so far.  I've installed sockets and replaced all the RAM.  Replaced Agnus AND the socket (gotta love desoldering an 84-pin PLCC socket) and also the CPU socket, because that's the one that always gets the battery damage.  No luck so far.  

Couple other items I forgot to mention.  I am working with the bare board on my bench, so no peripherals are attached.  Also, I don't know if this is important, but the green is instant as soon as power is applied.  There are no levels of gray first.

Any other ideas to try?  I'm open to suggestions!

[Frankencelery]

I haven't tried Gary, but I did swap the 8250s as you suggested.  

That cap was not shorting.  I checked.

RAM sockets are installed.  CPU socket was replaced, Agnus socket was replaced, no corroded pins or anything shorted that I've been able to find yet.

I have not checked for Rev 6 mods.  I suppose that's something I can google and verify.

[Frankencelery]

I would recommend you run John Hertells diagrom and see what it tells you. If you dont have an eprom burner to make one I can help you out for the cost of the eprom.

http://www.diagrom.com/index.php/download/

Fascinating!  I had no idea such a thing existed.  This might give me just the edge I was looking for.  Funny you should mention that today.  My company just shut down its legacy business, and among the interesting toys I got to bring home just yesterday was a PROM burner.  My old one was never capable of doing Amiga sized ROMs, maybe this one will.  Now to see if there's any 27C400s around here....

Thanks for the awesome tip.  I'll be sure to come back here and post an update when I have one.

[Frankencelery]

Ok...progress made.  First, the unrelated stuff:

1. Found out my new-to-me eeTools TopMax programmer DOES work, but I had to drag out an old WinXP machine to make it work.  32-bit and Parallel Port only!

2. Found out that I DO indeed have 3 27C400 EPROMS available.  2 of them are bad, but one programmed with the 0.8 DIAGROM successfully!

Now back to the original subject...my ailing Amiga 2000:

3. DIAGROM boots, gives some flashes (green/red), which is consistent with Chip RAM problems.  Connected Null Modem cable.  Wow, this guy has done some awesome work!  The system appears to detect 512K of RAM (should be 1MB), but it fails to scan any of it.  Here's what I get, if anyone can help me decipher this:

Checking memory from $00080400 to $00100000 - Press any key/mousebutton to stop

Checking Address: $00000003  |  Bit error shows max $FF errors due to space

            8|7|6|5|4|3|2|1| 8|7|6|5|4|3|2|1| 8|7|6|5|4|3|2|1| 8|7|6|5|4|3|2|1|
Bit errors: 0000000000000000 0000000000000000 0000000000000000 0000000000000000
Byte errors: 0         0         0         0         Number of errors: 0

Checked memory: 0KB       Usable memory: 0KB        NONUsable memory: 0KB
--------------------------------------------------------------------------------
Bad Block start at $FFFFFFFF and ends at $00000003 with a size of 0KB


Shadowmemory detected. Scan stopped. You can ignore the last error if any!

[Frankencelery]

Hi and thank you for your help!  Is this what you needed?



Amiga DiagROM V0.8 - 22-Oct-16  - By John (Chucky/The Gang) Hertell

- Parallel Code $ff - Start of ROM, CPU Seems somewhat alive
    Checking status of mousebuttons for different startups:

    Set all Interrupt enablebits (INTENA $dff09a) to Disabled: Done
    Set all Interrupt requestbits (INTREQ $dff09c) to Disabled: Done
    Set all DMA enablebits (DMACON $dff096) to Disabled: Done
- Parallel Code $fe - Start of chipmemdetection

Addr $00000400  Write: $F0F0F0F0  Read: $FFFFFFFF  FAILED
Addr $00000400  Write: $0F0F0F0F  Read: $FFFFFFFF  FAILED
Addr $00000400  Write: $00000000  Read: $FFFFFFFF  FAILED
Addr $00008400  Write: $F0F0F0F0  Read: $FFFFFFFF  FAILED
Addr $00008400  Write: $0F0F0F0F  Read: $FFFFFFFF  FAILED
Addr $00008400  Write: $00000000  Read: $FFFFFFFF  FAILED
Addr $00010400  Write: $F0F0F0F0  Read: $FFFFFFFF  FAILED
Addr $00010400  Write: $0F0F0F0F  Read: $FFFFFFFF  FAILED
Addr $00010400  Write: $00000000  Read: $FFFFFFFF  FAILED
Addr $00018400  Write: $F0F0F0F0  Read: $FFFFFFFF  FAILED
Addr $00018400  Write: $0F0F0F0F  Read: $FFFFFFFF  FAILED
Addr $00018400  Write: $00000000  Read: $FFFFFFFF  FAILED
Addr $00020400  Write: $F0F0F0F0  Read: $FFFFFFFF  FAILED
Addr $00020400  Write: $0F0F0F0F  Read: $FFFFFFFF  FAILED
Addr $00020400  Write: $00000000  Read: $FFFFFFFF  FAILED
Addr $00028400  Write: $F0F0F0F0  Read: $FFFFFFFF  FAILED
Addr $00028400  Write: $0F0F0F0F  Read: $FFFFFFFF  FAILED
Addr $00028400  Write: $00000000  Read: $FFFFFFFF  FAILED
Addr $00030400  Write: $F0F0F0F0  Read: $FFFFFFFF  FAILED
Addr $00030400  Write: $0F0F0F0F  Read: $FFFFFFFF  FAILED
Addr $00030400  Write: $00000000  Read: $FFFFFFFF  FAILED
Addr $00038400  Write: $F0F0F0F0  Read: $FFFFFFFF  FAILED
Addr $00038400  Write: $0F0F0F0F  Read: $FFFFFFFF  FAILED
Addr $00038400  Write: $00000000  Read: $FFFFFFFF  FAILED
Addr $00040400  Write: $F0F0F0F0  Read: $FFFFFFFF  FAILED
Addr $00040400  Write: $0F0F0F0F  Read: $FFFFFFFF  FAILED
Addr $00040400  Write: $00000000  Read: $FFFFFFFF  FAILED
Addr $00048400  Write: $F0F0F0F0  Read: $FFFFFFFF  FAILED
Addr $00048400  Write: $0F0F0F0F  Read: $FFFFFFFF  FAILED
Addr $00048400  Write: $00000000  Read: $FFFFFFFF  FAILED
Addr $00050400  Write: $F0F0F0F0  Read: $FFFFFFFF  FAILED
Addr $00050400  Write: $0F0F0F0F  Read: $FFFFFFFF  FAILED
Addr $00050400  Write: $00000000  Read: $FFFFFFFF  FAILED
Addr $00058400  Write: $F0F0F0F0  Read: $FFFFFFFF  FAILED
Addr $00058400  Write: $0F0F0F0F  Read: $FFFFFFFF  FAILED
Addr $00058400  Write: $00000000  Read: $FFFFFFFF  FAILED
Addr $00060400  Write: $F0F0F0F0  Read: $FFFFFFFF  FAILED
Addr $00060400  Write: $0F0F0F0F  Read: $FFFFFFFF  FAILED
Addr $00060400  Write: $00000000  Read: $FFFFFFFF  FAILED
Addr $00068400  Write: $F0F0F0F0  Read: $FFFFFFFF  FAILED
Addr $00068400  Write: $0F0F0F0F  Read: $FFFFFFFF  FAILED
Addr $00068400  Write: $00000000  Read: $FFFFFFFF  FAILED
Addr $00070400  Write: $F0F0F0F0  Read: $FFFFFFFF  FAILED
Addr $00070400  Write: $0F0F0F0F  Read: $FFFFFFFF  FAILED
Addr $00070400  Write: $00000000  Read: $FFFFFFFF  FAILED
Addr $00078400  Write: $F0F0F0F0  Read: $FFFFFFFF  FAILED
Addr $00078400  Write: $0F0F0F0F  Read: $FFFFFFFF  FAILED
Addr $00078400  Write: $00000000  Read: $FFFFFFFF  FAILED
Addr $00100400   OK  Number of 32K blocks found: $10
Startaddr: $00080400  Endaddr: $00100000
  Using $000EE24E as start of workmem

- Parallel Code $fd - Start of motherboard fastmemdetection
- Parallel Code $fc - Memorydetection done
- Parallel Code $fb - Starting to use detected memory
Detecting if we have a working raster: DETECTED
Detected Chipmem: 512KB
Detected Motherboard Fastmem: 15360KB
Basememory address: $000EE24E
- Parallel Code $fa - Detected memory in use, we now have a stack etc
    Set Start of copper (COP1LCH $dff080): Done
    Starting Copper (COPJMP1 $dff088): Done
    Set all DMA enablebits (DMACON $dff096) to Enabled: Done
    Set Beam Conter control register to 32 (PAL) (BEAMCON0 $dff1dc): Done
    Set POTGO to all OUTPUT ($FF00) (POTGO $dff034): Done
- Parallel Code $f9 - Starting up screen, text echoed to serialport
Amiga DiagROM V0.8 - 22-Oct-16  - By John (Chucky/The Gang) Hertell


























                             DiagROM V0.8 - 22-Oct-16

[Frankencelery]

Here also is the dump from the System Info menu option, which may be what you were wanting in the first place!

Information of this machine:

               Dump of all readable Custom Chipset HW Registers:
BLTDDAT ($dff000): $FFFF   DMACONR  ($dff002): $4380   VPOSR   ($dff004): $B000
VHPOSR  ($dff006): $BD9D   DSKDATR  ($dff008): $FFFF   JOY0DAT ($dff00a): $1404
POT0DAT ($dff012): $E0E0   POT1DAT  ($dff014): $E0E0   POTINP  ($dff016): $5500
SERDATR ($dff018): $0B0D   DSKBYTR  ($dff01a): $9000   INTENAR ($dff01c): $0000
INTREQR ($dff01e): $0028   DENISEID ($dff07c): $FFFF   HHPOSR  ($dff1dc): $0064

[Frankencelery]

Yeah, Mouser is the only place that seems to have those 74F244s.  I ordered some of those, and the 245s.  Gonna be a few days to get those.

I'm glad you mentioned that you were getting good results from an Ebay seller in China.  I bought some Commodore CIAs a couple months back and not only were they counterfeit, but they were all defective.  Made me nervous about buying from China sellers.  I do need some more 27C400s as well.

I didn't want to muddy the waters with too much information, but I thought I might share some more information about this board.  I bought it as a spare, a couple years ago and it has never worked.  I bought it because it was Rev6 and looked to be in good condition with no battery damage.

[Frankencelery]

OH!  

Acill, you are the MAN!

Tonight, I decided to unsolder U540 and U541 and put in sockets.  My replacement chips are supposed to be here on Friday.  

Then I looked closer at U541....do you see it?

[Frankencelery]

The trace going to Pin 8 was making no connection.  This is _RAS0, which I can only assume stands for Row Address Strobe 0.  Memory Access...of course!

The pic I posted was AFTER I picked at it with an X-acto knife.  There was just the tiniest bit of green fuzz there at the pin that was totally obscuring the broken trace.  

Repaired that trace, and....TA DA!!!!

[Frankencelery]

I haven't had any time to get it back together yet, but I hope to this weekend.  

This all started when I bought another A2000 a couple weeks ago.  The seller gave the ever popular "it worked when I used it X years ago, but now I have no way of testing it", and I fell for it because I thought he was a stand up guy.  Anyway, it was an early model with a rev 4.4 motherboard, and it had pretty severe battery damage, which he also failed to mention.  That one has a yellow screen.  But I figured if I was going to get this thing going, it would be a better bet to fix my spare rev 6 board, and put that one in the machine.  

So now I might try my hand at fixing the old 4.4 board.  If I need help (which I probably will) I will start a new thread.  

Thanks again for your help everyone!