RE: Major Havoc fluke 9010a rom testing

Nope, one way trip.

-----Original Message-----
From: "John Robertson" <pinball@telus.net>
Sent: ‎1/‎23/‎2013 11:31 AM
To: "vectorlist@vectorlist.org" <vectorlist@vectorlist.org>
Subject: Re: VECTOR: Major Havoc fluke 9010a rom testing

David Shoemaker wrote:
> Video buffer and sprite ram are often used write only from CPU. And
> the vector generator stack is write only for the CPU though the state
> machine reads from it.

Ah, so what you are referring to is the RAM that is Written by the CPU
but normally only Read by the Vector State Machine. Is this ram not
Readable by the CPU for self-testing purposes?

John :-#)#
> ------------------------------------------------------------------------
> From: John Robertson <mailto:pinball@telus.net>
> Sent: ‎1/‎23/‎2013 8:13 AM
> To: vectorlist@vectorlist.org <mailto:vectorlist@vectorlist.org>
> Subject: Re: VECTOR: Major Havoc fluke 9010a rom testing
>
> akswanson@ntelos.net wrote:
> >
> > Ive used the scripts alot when I had my 9010. They were accurate for
> > the addresses, but for the RAM, all of it is marked R/W and a fair
> > amout of the ram in these games is write only..
> >
>
> That doesn't make any sense. RAM is Random Access Memory and by design
> must be Write/Read (R/W). When the power is removed all data vanishes
> after all - unless it is battery (or other) backed up.
>
> If you can't Write to the memory and then Read what you wrote then you
> either have something wrong with the RAM or in your Write/Read script.
>
> When you think about it calling the control line R/W is ass-backwards -
> if you don't Write to the RAM first there is nothing to Read!
>
> John :-#)#
> >
> > > Well as we've seen on the MH those scripts aren't all they are
> > cracked up
> > > to be.
> > >
> > > While yes some may work out of the box, I prefer to do my testing a
> > little
> > > different, which is why I manually do them.
> > >
> > > For example you could write a script that asks you what rom
> version you
> > > are
> > > testing, then have it test each one and ask for input before
> > continuing to
> > > the next, and as is the case in MH you will need to write in a text
> > script
> > > reminding you to hook up the WD Dis to ground, then have it page and
> > > check.
> > >
> > > The scripting is pretty easy to do, I've just not had time to
> write up a
> > > better script. The QA site scripts would be a good starting place
> if you
> > > wanted to add to it, and make changes. I have a feeling that most of
> > those
> > > scripts were automatically written and never checked for inaccuracy. I
> > > tend
> > > to use them for Locations and sigs.
> > >
> > >
> > > On Wed, Jan 23, 2013 at 7:51 AM, Pat Danis <patdanis@verizon.net>
> wrote:
> > >
> > >> Andre
> > >>
> > >> I spent several hours yesterday with Kevin working on Major Havoc and
> > >> was
> > >> extremely helpful. I was able to stand around with my hands in my
> > >> pockets
> > >> and ask dumb questions but I did learn where the scripts are all
> on my
> > >> own.
> > >>
> > >> Go to www.quarterarcade.com/tech
> > >>
> > >> At the bottom of the page, type in the name of the game you are
> looking
> > >> for under mame virtual machine. Then press search key. When you
> get to
> > >> the game's page. Under the driver column, pick the version of the
> board
> > >> you want. Then under the "emulated CPUs" column, you will see the
> blue
> > >> Fluke 9010a script link. Click that and you will have all the scripts
> > >> to
> > >> test the various areas. You can edit as necessary.
> > >>
> > >> Pat
> > >>
> > >> Sent from my iPad
> > >>
> > >> On Jan 23, 2013, at 4:35 AM, Andre Huijts <a.huijts@upcmail.nl>
> wrote:
> > >>
> > >> Good info for a beginning Fluke user...
> > >> Makes sense that the watchdog kicks in if it isn't being reset
> > >> continuously by a running processor....
> > >>
> > >> So basically this is like bank- switching like f.i. the Atari 130XE
> > does
> > >> to access more RAM then normally possible ?
> > >>
> > >> By the way where do you find the Quarterarcade scripts ? Searched the
> > >> site
> > >> but can't seem to find them...
> > >>
> > >> Thanks, André
> > >>
> > >> Op 23 jan. 2013 om 05:52 heeft Kevin Moore <talon.k@gmail.com> het
> > >> volgende geschreven:
> > >>
> > >> Success..
> > >>
> > >> After splitting the roms, and running Calcsig on them, then tying
> > the WD
> > >> Dis to ground. I was then able to write 00 01 02 etc to 1740 and
> > get the
> > >> MMUPAGE0 1 to toggle..
> > >>
> > >> I'm now able to read the paged roms and get the correct sigs.
> > >>
> > >> Just needed to tie the Watchdog to ground..
> > >>
> > >> Guess someone should let quarterarcade know their script is wrong :)
> > >>
> > >> Solved that problem.
> > >>
> > >> Thanks for all the help.
> > >>
> > >> Kevin
> > >>
> > >>
> > >> On Tue, Jan 22, 2013 at 10:41 PM, Rodger Boots <rlboots2@gmail.com>
> > >> wrote:
> > >>
> > >>> Make real sure the reset line isn't doing anything. Make sure other
> > >>> processor is off board.
> > >>>
> > >>>
> > >>>
> > >>> On Tue, Jan 22, 2013 at 10:39 PM, Kevin Moore <talon.k@gmail.com>
> > >>> wrote:
> > >>>
> > >>>> Yes it is plugged into the alpha socket. You are correct that
> 1740 is
> > >>>> write only.. As of yet, trying to use the fluke to write 00 01 02
> > >>>> etc..
> > >>>> hasn't changed the states of the MMUPAGE0 or MMUPAGE1
> > >>>>
> > >>>> Kevin
> > >>>>
> > >>>>
> > >>>>
> > >>>> On Tue, Jan 22, 2013 at 9:21 PM, vectorlist-steve <
> > >>>> vectorlist@arcadehacking.com> wrote:
> > >>>>
> > >>>>> Hey Kevin, you do have the fluke plugged into the "Alpha"
> (primary)
> > >>>>> processor socket right????
> > >>>>>
> > >>>>> 0x1740 address should be WRITE ONLY according to the mame
> source and
> > >>>>> only latches the two LSB bits.
> > >>>>>
> > >>>>> http://mamedev.org/source/src/mame/drivers/mhavoc.c.html
> > >>>>>
> > >>>>> If I have time later I will check one of my MH boards and post the
> > >>>>> results.
> > >>>>>
> > >>>>>
> > >>>>>
> > >>>>> On 1/22/2013 5:51 PM, Kevin Moore wrote:
> > >>>>>
> > >>>>> Well, I must be doing something wrong..
> > >>>>>
> > >>>>> I do a write to 1740 = 00
> > >>>>> then do a rom 2000-3FFF
> > >>>>>
> > >>>>> I come up with a 2057
> > >>>>>
> > >>>>> Do a write to 1740 = 01
> > >>>>>
> > >>>>> Rom 2000-3FFF still get 2057
> > >>>>>
> > >>>>> So then I did a Read at 1740 and it's showing FF no matter what I
> > >>>>> write
> > >>>>> to it.
> > >>>>>
> > >>>>> This is a known working board that I'm trying to do this on. I
> > should
> > >>>>> be able to do this right?
> > >>>>>
> > >>>>> Kevin
> > >>>>>
> > >>>>>
> > >>>>> On Tue, Jan 22, 2013 at 6:16 PM, Jess Askey <jess@askey.org>
> wrote:
> > >>>>>
> > >>>>>> Yes, page 0 and 1 are in one ROM and page 2 and 3 in the other. I
> > >>>>>> didn’t think about that. J
> > >>>>>>
> > >>>>>>
> > >>>>>>
> > >>>>>> *From:* owner-vectorlist@vectorlist.org [mailto:
> > >>>>>> owner-vectorlist@vectorlist.org] *On Behalf Of *Kevin Moore
> > >>>>>> *Sent:* Tuesday, January 22, 2013 5:26 PM
> > >>>>>>
> > >>>>>> *To:* vectorlist@vectorlist.org
> > >>>>>> *Subject:* Re: VECTOR: Major Havoc fluke 9010a rom testing
> > >>>>>>
> > >>>>>>
> > >>>>>>
> > >>>>>> That's what I was thinking.
> > >>>>>>
> > >>>>>> But the sigs are for the two roms.. will I need to split the
> roms,
> > >>>>>> and
> > >>>>>> run sig calc on the halves to get the right sigs?
> > >>>>>>
> > >>>>>> Kevin
> > >>>>>>
> > >>>>>> On Tue, Jan 22, 2013 at 6:05 PM, Jess Askey <jess@askey.org>
> wrote:
> > >>>>>>
> > >>>>>> The 2 ROM’s are broken down into 4 pages… so in order to access
> > >>>>>> them….
> > >>>>>>
> > >>>>>>
> > >>>>>>
> > >>>>>> Page 0: Write 00 to 0x1740 then read 0x2000-3fff
> > >>>>>>
> > >>>>>> Page 1: Write 01 to 0x1740 then read 0x2000-3fff
> > >>>>>>
> > >>>>>> Page 2: Write 02 to 0x1740 then read 0x2000-3fff
> > >>>>>>
> > >>>>>> Page 3: Write 03 to 0x1740 then read 0x2000-3fff
> > >>>>>>

[The entire original message is not included.]

---------------------------------------------------------------------------
** Unsubscribe, subscribe, or view the archives at http://www.vectorlist.org
** Please direct other questions, comments, or problems to chris@westnet.com
Received on Wed Jan 23 14:48:17 2013