- Credits
- 763CR
So.... It feels like I've tested or replaced almost every IC on the Battlezone.
After I got my Data IO 29B working I checked all the PROMs (main and aux) and replaced 5 of them.
Then I found that the halt circuit was goosed, so I replaced the 74-74 @ M9.
That seemed like a step back - as the junk vectors I was getting vanished and I ended up with a very brief inverted L shape (vertical line upward from centre to X0,Y+ then a short line along +ve X) that flickered on just as the board reset.
I found that the _RESET was firing 42ms after the _VGGO signal. If I stick the fluke in the board and get it to loop writing to the _WDRESET address the board doesn't reset - so the whole wd and wdreset side of things is working fine.
I can only assume that the CPU is waiting for something from the state machine which causes a long pause between _WDRESET pulses and causes the PCB to reset.
So I set about checking the state machine.
With the logic comparator I see output differences on:
e6 74-670, f6 74-670, h6 74-670,f7 74-367, h7 74-367
But I think those are the outputs competing with each other.... as a check I replaced F7 and E6 with known good ICs but the "faults" on the logic comparator persist.
I found actual faults (IC fails test out of circuit) on:
B7 (74-86), c6 (74-00), f10 (74-191), b6 (74-14)
And I've reached the stage where the "game" screen looks like this:
The "test mode" is trying, but still resetting.
(I had to video the scope and frame grab this image... it's only there for a fraction of a second!)
Before I found the fault @ C6 I seemed to be getting nowhere - I've tested or replaced around 45 ICs on the board so far.... I was starting to run out of things to check and beginning to lose hope!
(Thanks to ColinD for keeping me going with handy hints!)
After I got my Data IO 29B working I checked all the PROMs (main and aux) and replaced 5 of them.
Then I found that the halt circuit was goosed, so I replaced the 74-74 @ M9.
That seemed like a step back - as the junk vectors I was getting vanished and I ended up with a very brief inverted L shape (vertical line upward from centre to X0,Y+ then a short line along +ve X) that flickered on just as the board reset.
I found that the _RESET was firing 42ms after the _VGGO signal. If I stick the fluke in the board and get it to loop writing to the _WDRESET address the board doesn't reset - so the whole wd and wdreset side of things is working fine.
I can only assume that the CPU is waiting for something from the state machine which causes a long pause between _WDRESET pulses and causes the PCB to reset.
So I set about checking the state machine.
With the logic comparator I see output differences on:
e6 74-670, f6 74-670, h6 74-670,f7 74-367, h7 74-367
But I think those are the outputs competing with each other.... as a check I replaced F7 and E6 with known good ICs but the "faults" on the logic comparator persist.
I found actual faults (IC fails test out of circuit) on:
B7 (74-86), c6 (74-00), f10 (74-191), b6 (74-14)
And I've reached the stage where the "game" screen looks like this:
The "test mode" is trying, but still resetting.
(I had to video the scope and frame grab this image... it's only there for a fraction of a second!)
Before I found the fault @ C6 I seemed to be getting nowhere - I've tested or replaced around 45 ICs on the board so far.... I was starting to run out of things to check and beginning to lose hope!
(Thanks to ColinD for keeping me going with handy hints!)