I have an Amiga 312513 Rev 6a Rock Lobster with memory issues. Not booting and has a green screen.
When I got it had 512K in installed and someone had put in the sockets to upgrade to 1M. I removed all of the memory chip and tested them and they all tested good. Since memory chips had been removed and socketed thought there might be damage so tested the connections to all mem chips and they were ok. Then added mem chips for the full 1M and tried again but still no memory. Changes the J2 and J7 to the 1M settings and no change.
Running the DiagROM got the these results via the serial port RESULTS 1 (Below). Next I removed Fat Agnus and tested it is a working system and it worked fine. When putting it back in notices a bent pin in the socket which I straitened and put Agnus back in. With the fixed pin the DiagROM results changed to RESULTS 2.
This is my first time using the DiagROM so just learning as I go. Seems like it got worse with the fixed pin. Any suggestions of what could be causing this memory issue?
Thanks
Les
RESULTS 1
Amiga DiagROM V1.3 - 21-Apr-23 - By John (Chucky/The Gang) Hertell
- Parallel Code $ff - Start of ROM, CPU Seems somewhat alive
- Testing ROM Address-access
OK
Testing if serial loopbackadapter is installed: <> NOT DETECTED
Checking status of mousebuttons at power-on:
P1LMB
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
Testing if OVL is working: OK
- Parallel Code $fe - Test UDS/LDS line
- Test of writing word $AAAA to $400 OK
- Test of writing word $00AA to $400 OK
- Test of writing word $AA00 to $400 OK
- Test of writing word $0000 to $400 OK
- Test of writing byte (even) $AA to $400 OK
- Test of writing byte (odd) $AA to $401 OK
- Parallel Code $fd - Start of chipmemdetection
Addr $00100400 OK Number of 64K blocks found: $10
Chipmem Shadowram detected, guess there is no more chipmem, stopping here
Startaddr: $00000400 Endaddr: $000FFFFF
- Testing detected Chipmem for addresserrors
- Filling memoryarea with addressdata
...............
- Checking block of ram that it contains the correct addressdata
- Addresserror at: 00000420 00000000000000000000010000100000 00000400
- Addresserror at: 00000424 00000000000000000000010000100100 00000404
- Addresserror at: 00000428 00000000000000000000010000101000 00000408
- Addresserror at: 0000042C 00000000000000000000010000101100 0000040C
- Addresserror at: 00000430 00000000000000000000010000110000 00000410
- Addresserror at: 00000434 00000000000000000000010000110100 00000414
- Addresserror at: 00000438 00000000000000000000010000111000 00000418
- Addresserror at: 0000043C 00000000000000000000010000111100 0000041C
- Addresserror at: 00000460 00000000000000000000010001100000 00000440
- Addresserror at: 00000464 00000000000000000000010001100100 00000444
- Addresserror at: 00000468 00000000000000000000010001101000 00000448
- Addresserror at: 0000046C 00000000000000000000010001101100 0000044C
- Addresserror at: 00000470 00000000000000000000010001110000 00000450
- Addresserror at: 00000474 00000000000000000000010001110100 00000454
- Addresserror at: 00000478 00000000000000000000010001111000 00000458
- Addresserror at: 0000047C 00000000000000000000010001111100 0000045C
- Addresserror at: 000004A0 00000000000000000000010010100000 00000480
- Addresserror at: 000004A4 00000000000000000000010010100100 00000484
- Addresserror at: 000004A8 00000000000000000000010010101000 00000488
- Addresserror at: 000004AC 00000000000000000000010010101100 0000048C
- Addresserror at: 000004B0 00000000000000000000010010110000 00000490
- Addresserror at: 000004B4 00000000000000000000010010110100 00000494
- Addresserror at: 000004B8 00000000000000000000010010111000 00000498
- Addresserror at: 000004BC 00000000000000000000010010111100 0000049C
- Addresserror at: 000004E0 00000000000000000000010011100000 000004C0
- Addresserror at: 000004E4 00000000000000000000010011100100 000004C4
- Addresserror at: 000004E8 00000000000000000000010011101000 000004C8
- Addresserror at: 000004EC 00000000000000000000010011101100 000004CC
- Addresserror at: 000004F0 00000000000000000000010011110000 000004D0
- Addresserror at: 000004F4 00000000000000000000010011110100 000004D4
- Addresserror at: 000004F8 00000000000000000000010011111000 000004D8
- Addresserror at: 000004FC 00000000000000000000010011111100 000004DC
- Addresserror at: 00000520 00000000000000000000010100100000 00000500
- Addresserror at: 00000524 00000000000000000000010100100100 00000504
- Addresserror at: 00000528 00000000000000000000010100101000 00000508
- Addresserror at: 0000052C 00000000000000000000010100101100 0000050C
- Addresserror at: 00000530 00000000000000000000010100110000 00000510
- Addresserror at: 00000534 00000000000000000000010100110100 00000514
- Addresserror at: 00000538 00000000000000000000010100111000 00000518
- Addresserror at: 0000053C 00000000000000000000010100111100 0000051C
-- Addresserror reading CHIPRAM, marking chipram as unusable
- Checking status of mousebuttons for different startups, if still pressed
we assume not working and ignore those in the future.
Green newly pressed, Yellow pressed at startup - Startupaction taken.
Red = Pressed at both poweron and now so it is stuck and being ignored
P1LMB
The following special action will be taken:
P1LMB - Try to find fastmem and if found use it! if not use chipmem but no display
- Parallel Code $fc - Trying to find some fastmem (as requested at powerup)
- Parallel Code $fb - Memorydetection done
- Parallel Code $80 - NO Chipmem detected
NO MEMORY FOUND - HALTING SYSTEM
...
RESULTS 2
Amiga DiagROM V1.3 - 21-Apr-23 - By John (Chucky/The Gang) Hertell
- Parallel Code $ff - Start of ROM, CPU Seems somewhat alive
- Testing ROM Address-access
OK
Testing if serial loopbackadapter is installed: <> NOT DETECTED
Checking status of mousebuttons at power-on:
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
Testing if OVL is working: OK
- Parallel Code $fe - Test UDS/LDS line
- Test of writing word $AAAA to $400 FAILED
- Test of writing word $00AA to $400 FAILED
- Test of writing word $AA00 to $400 FAILED
- Test of writing word $0000 to $400 FAILED
- Test of writing byte (even) $AA to $400 FAILED
- Test of writing byte (odd) $AA to $401 FAILED
- Parallel Code $fd - Start of chipmemdetection
Addr $00000400
Write: $FFFFFFFF 11111111111111111111111111111111
Read: $00FFFFFF 00000000111111111111111111111111 FAILED
Write: $AAAAAAAA 10101010101010101010101010101010
Read: $00FFAAFF 00000000111111111010101011111111 FAILED
Write: $55555555 01010101010101010101010101010101
Read: $00FF55FF 00000000111111110101010111111111 FAILED
Write: $F0F0F0F0 11110000111100001111000011110000
Read: $00FFF0FF 00000000111111111111000011111111 FAILED
Write: $0F0F0F0F 00001111000011110000111100001111
Read: $00FF0FFF 00000000111111110000111111111111 FAILED
Write: $0F0FF0F0 00001111000011111111000011110000
Read: $00FFF0FF 00000000111111111111000011111111 FAILED
Write: $00000000 00000000000000000000000000000000
Read: $00FF00FF 00000000111111110000000011111111 FAILED
Addr $00010400
Write: $FFFFFFFF 11111111111111111111111111111111
Read: $00FFFFFF 00000000111111111111111111111111 FAILED
Write: $AAAAAAAA 10101010101010101010101010101010
Read: $00FFAAFF 00000000111111111010101011111111 FAILED
.
.......... Continues checking mem addresses all failed then ends :
.
NO Chipmem detected
- Checking status of mousebuttons for different startups, if still pressed
we assume not working and ignore those in the future.
Green newly pressed, Yellow pressed at startup - Startupaction taken.
Red = Pressed at both poweron and now so it is stuck and being ignored
P2RMB
The following special action will be taken:
- Parallel Code $fc - Trying to find some fastmem (as no chipmem found)
- Parallel Code $fb - Memorydetection done
- Parallel Code $80 - NO Chipmem detected
- NO MEMORY FOUND - HALTING SYSTEM
