A4000 yellow screen

[cpiac64]

add log



Amiga DiagROM V1.3 BETA - 21-Feb-22 - 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 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 $001F0400 OK Number of 64K blocks found: $20
Startaddr: $00000400 Endaddr: $001FFFFF
- Testing detected Chipmem for addresserrors
- Filling memoryarea with addressdata
...............................
- Checking block of ram that it contains the correct addressdata

- Addresserror at: 00000408 00000000000000000000010000001000 00000400
- Addresserror at: 0000040C 00000000000000000000010000001100 00000404
- Addresserror at: 00000418 00000000000000000000010000011000 00000410
- Addresserror at: 0000041C 00000000000000000000010000011100 00000414
- Addresserror at: 00000428 00000000000000000000010000101000 00000420
- Addresserror at: 0000042C 00000000000000000000010000101100 00000424
- Addresserror at: 00000438 00000000000000000000010000111000 00000430
- Addresserror at: 0000043C 00000000000000000000010000111100 00000434
- Addresserror at: 00000448 00000000000000000000010001001000 00000440
- Addresserror at: 0000044C 00000000000000000000010001001100 00000444
- Addresserror at: 00000458 00000000000000000000010001011000 00000450
- Addresserror at: 0000045C 00000000000000000000010001011100 00000454
- Addresserror at: 00000468 00000000000000000000010001101000 00000460
- Addresserror at: 0000046C 00000000000000000000010001101100 00000464
- Addresserror at: 00000478 00000000000000000000010001111000 00000470
- Addresserror at: 0000047C 00000000000000000000010001111100 00000474
- Addresserror at: 00000488 00000000000000000000010010001000 00000480
- Addresserror at: 0000048C 00000000000000000000010010001100 00000484
- Addresserror at: 00000498 00000000000000000000010010011000 00000490
- Addresserror at: 0000049C 00000000000000000000010010011100 00000494
- Addresserror at: 000004A8 00000000000000000000010010101000 000004A0
- Addresserror at: 000004AC 00000000000000000000010010101100 000004A4
- Addresserror at: 000004B8 00000000000000000000010010111000 000004B0
- Addresserror at: 000004BC 00000000000000000000010010111100 000004B4
- Addresserror at: 000004C8 00000000000000000000010011001000 000004C0
- Addresserror at: 000004CC 00000000000000000000010011001100 000004C4
- Addresserror at: 000004D8 00000000000000000000010011011000 000004D0
- Addresserror at: 000004DC 00000000000000000000010011011100 000004D4
- Addresserror at: 000004E8 00000000000000000000010011101000 000004E0
- Addresserror at: 000004EC 00000000000000000000010011101100 000004E4
- Addresserror at: 000004F8 00000000000000000000010011111000 000004F0
- Addresserror at: 000004FC 00000000000000000000010011111100 000004F4
- Addresserror at: 00000508 00000000000000000000010100001000 00000500
- Addresserror at: 0000050C 00000000000000000000010100001100 00000504
- Addresserror at: 00000518 00000000000000000000010100011000 00000510
- Addresserror at: 0000051C 00000000000000000000010100011100 00000514
- Addresserror at: 00000528 00000000000000000000010100101000 00000520
- Addresserror at: 0000052C 00000000000000000000010100101100 00000524
- Addresserror at: 00000538 00000000000000000000010100111000 00000530
- Addresserror at: 0000053C 00000000000000000000010100111100 00000534
-- Addresserror reading CHIPRAM, but there was some available
Reducing numer of available 64Kb blocks to: $82
This might not be an issue, if memory is according to correct size of your system
It is just an issue in DiagROM chipmemdetectroutine!
but if not. you have issues to handle!

- 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


The following special action will be taken:
NONE
- Fastmemcheck skipped as we found chipmem
- Parallel Code $fb - Memorydetection done

Using $2080C486 as start of workmem (Base)

- Testing Workarea Address-access

- Addresserror at: 2080C486 00100000100000001100010010000110 FFFFFFFE
- Addresserror at: 2080C48A 00100000100000001100010010001010 FFFFFFFE
- Addresserror at: 2080C48E 00100000100000001100010010001110 FFFFFFFE
- Addresserror at: 2080C492 00100000100000001100010010010010 FFFFFFFE
- Addresserror at: 2080C496 00100000100000001100010010010110 FFFFFFFE
- Addresserror at: 2080C49A 00100000100000001100010010011010 FFFFFFFE
- Addresserror at: 2080C49E 00100000100000001100010010011110 FFFFFFFE
- Addresserror at: 2080C4A2 00100000100000001100010010100010 FFFFFFFE
- Addresserror at: 2080C4A6 00100000100000001100010010100110 FFFFFFFE




the screen change some colours and stop on white screen




need force reset

[alexh]

This is typical of battery leak damage that area over by the SIMM sockets will probably need lots of minor fixes.

Could be the SIMM sockets themselves

[cpiac64]

only chip ram on board

[elenachen]

Originally Posted by cpiac64

only chip ram on board

The chip ram is also a simm module. So you'd have to look for broken traces or vias. But first maybe test another simm module in the chip ram socket.



But beware! those sockets are very brittle....


Good luck finding the problem

[cpiac64]

i want clean with flux the slot cpu

[DigitalKeeper]

Typical "Typo" from broken trace.....

-> first check _UDS & _LDS Line for broken traces

then

-> the _BCAS Lines for broken traces

If above all ok, then Check all Adress- and Datalines for broken traces...