RE: Tempest resetting problem

That's kind of interesting. I can run a working Tempest board fine with
my pod. The "May need Reset" message on the Fluke is normal. The Tempest
manual does say that it won't run correctly unless it's using a 6502A
processor. I wonder if some pods were made with a 6502 and others a
6502A?

Can a tempest even run at all with a slightly different CPU?

Just a thought.

Matt

_____________________________________________________________________

On Tue, 19 Oct 1999, Clay Cowgill wrote:

> > Almost ANY chip in the Microprocessor, Address Decode, RAM, etc,
> > etc circuit can cause a WD reset problem. I think you said you weren't
> > able to write to RAM using the Fluke. That is your clue. Most likely you
> > hav eeither an address decode problem, or a write-enable generation
> > problem.
> >
> For what it's worth... When I was developing the Tempest Multigame if I
> tried to "run" the boardset from the Fluke 6502 POD it would *sorta* work,
> but I was obviously getting RAM errors. Looked like zero-page corruption to
> me. I do believe it was able to test RAM OK though.
>
> (I've never tried to figure out exactly *why*, but the 9010 won't run
> certain boards in-circuit. In particular, Tempest is twitchy, and the Exidy
> 440 System doesn't work-- Cheyenne, Chiller, Crossbow, etc. I can
> read/write/checksum everything OK always, just won't fly with "run". I
> wrote off the 6809 stuff to probably not having the special purpose lines
> configured right, but the 6502 doesn't have many options, and since it
> "runs" a known-good board but corrupts data I figure it's the Fluke's
> fault...)
>
> > Watchdog problems suck, in general, but it looks like yours has to
> > do with a RAM or RAM interface problem.
> >
> I concur with Joe on this one. Give the 9010's RAM and BUS tests a try and
> see if anything turns up...
>
> -Clay
>
>
Received on Tue Oct 19 11:12:44 1999