(Topic ID: 74101)

WMS Sys 3-7 Andre Test ROM Usage Video V2

By barakandl

10 years ago


Topic Heartbeat

Topic Stats

  • 58 posts
  • 19 Pinsiders participating
  • Latest reply 2 years ago by pincoder
  • Topic is favorited by 22 Pinsiders

You

Linked Games

No games have been linked to this topic.

    Topic Gallery

    View topic image gallery

    db-04-011 standard_andre20.jpg
    There are 58 posts in this topic. You are on page 2 of 2.
    #51 3 years ago

    As near as I can tell, it looked like it is complaining about your 5101 RAM; I know you said yours was removed... I ran my test with it pulled, and it passed there. The second stint of flashing you're getting is to be expected- that is for the system7-only sound PIA.

    Have you ever seen this board run? Was/is there battery corrosion damage? What chips are socketed, and have you replaced the 40 pin CPU, the ROM sockets (I know you said the board was converted to 3 ROMs)? I guess I'd poke around the 5101 socket, and make sure there are no shorts, especially if the 5101 chip was recently removed/socketed. An extra close once-over looking at any previous rework too.

    If the board is behaving intermittently, I like to give them a little wiggle while they're powered up, to see if anything changes.. Please exercise caution here if you try this (don't try this at home) But, the idea is- if there's a change with a little wiggle, perhaps a cold/cracked solder joint, bad trace, etc. Nothing extreme enough to damage the board or break anything of course..

    Also I'm surprised your relay isn't a bit louder, but- maybe they vary in noise? Perhaps others have some ideas too.

    #52 3 years ago
    Quoted from sharkey1331:

    As near as I can tell, it looked like it is complaining about your 5101 RAM; I know you said yours was removed... I ran my test with it pulled, and it passed there. The second stint of flashing you're getting is to be expected- that is for the system7-only sound PIA.
    Have you ever seen this board run? Was/is there battery corrosion damage? What chips are socketed, and have you replaced the 40 pin CPU, the ROM sockets (I know you said the board was converted to 3 ROMs)? I guess I'd poke around the 5101 socket, and make sure there are no shorts, especially if the 5101 chip was recently removed/socketed. An extra close once-over looking at any previous rework too.
    If the board is behaving intermittently, I like to give them a little wiggle while they're powered up, to see if anything changes.. Please exercise caution here if you try this (don't try this at home) But, the idea is- if there's a change with a little wiggle, perhaps a cold/cracked solder joint, bad trace, etc. Nothing extreme enough to damage the board or break anything of course..
    Also I'm surprised your relay isn't a bit louder, but- maybe they vary in noise? Perhaps others have some ideas too.

    No, I have not seen this board work. The relay on the same driver board is a lot louder when I use a system 6 MPU from my Gorgar machine. There is no battery corrosion that I can see. The 5101 RAM is socketed and looks brand new. The CPU is socketed and looks new. I just replaced IC13 and socketed it with no change. There is no change when the board is flexed or wiggled at all. I have continuity at every pin on the 40 pin interconnect when checking to the next component downstream or upstream according to the schematics. I expected the flashing due to there being no RAM and this not being a system 7 board, I didn't expect everything to pass considering this board won't boot in the machine. Just wondering if I'm missing something obvious. I'll keep digging.

    Thanks!

    #53 3 years ago
    Quoted from johnboy1313:

    The relay on the same driver board is a lot louder when I use a system 6 MPU from my Gorgar machine.

    Relay click difference probably has to do with timing of the blanking circuit. I would not look to much into it.

    Quoted from johnboy1313:

    I didn't expect everything to pass considering this board won't boot in the machine. Just wondering if I'm missing something obvious. I'll keep digging.
    Thanks!

    If all test ROM passes but the MPU still does not boot up with known good ROMs then I would start to wonder if the other ROM sockets and enable circuitry is working OK. Test ROM only runs out of one ROM socket, but three are usually used, in some cases six.

    #54 3 years ago
    Quoted from barakandl:

    If all test ROM passes but the MPU still does not boot up with known good ROMs then I would start to wonder if the other ROM sockets and enable circuitry is working OK. Test ROM only runs out of one ROM socket, but three are usually used, in some cases six.

    I wondered the same thing. I ordered the single rom adapter from Siegecraft. I’m hoping that it will tell me for sure if that was part of the problem. Also, with guidance from @cheddar, it looks like IC3 is bad. If I test it with my meter on diode mode and the red lead to ground, pin 13 (address line A11) measures .155 both in and out of circuit. IC4 and IC8 both measure around .600. Also, when I traced that circuit through the schematic, I saw that A11 also measured .155 at pin 14 on ic15. Once I pulled ic3, that measured .697.

    #55 3 years ago
    Quoted from johnboy1313:

    I wondered the same thing. I ordered the single rom adapter from Siegecraft. I’m hoping that it will tell me for sure if that was part of the problem. Also, with guidance from Cheddar, it looks like IC3 is bad. If I test it with my meter on diode mode and the red lead to ground, pin 13 (address line A11) measures .155 both in and out of circuit. IC4 and IC8 both measure around .600. Also, when I traced that circuit through the schematic, I saw that A11 also measured .155 at pin 14 on ic15. Once I pulled ic3, that measured .697.

    Without digging into the schematic A11 is in the upper address range where things like enable the ROMs live. I could see a test ROM being able to run even tho an upper address is bad causing normal game software to not work.

    If IC3 is the address buffer chip (again i have not looked, i got a few min while pizza in the oven) you can compare the input to the output. Even with just a logic probe should be able to tell if the output is blown yet the input is good.

    10 months later
    #56 2 years ago

    The original video has been made private now. barakandl is there a way you can make it public or provide us with the link here?

    I've pulled out a system 4 MPU that I started working on 13 years ago! (my how time flies). I originally wanted to use Andre's but have a Leon's in there. This video would be helpful to me to see how it works.

    -Pat

    #57 2 years ago

    Bump, I reference that video myself from time to time.

    #58 2 years ago

    You can also try the Pincoder ROMs to help you troubleshoot:

    https://pincoder.ca

    Under the Support menu there is a link to "Community Usage Videos - YouTube" where a fellow pinsider (@troxel) has put together some quick videos for each test. The videos were done using the Pincoder Adapter:

    https://pincoder.ca/index.php/2020/07/10/adapter-2020-06-23-0506/

    But if you're already burning your own ROMs you can just download the images for free.

    There are a number of test ROMs you can use that isolate parts from the ground up. You may be especially interested in the 12-flippers ROM as it allows you to test all of the PIAs at once.

    The latest ROMs and their documentation are found in the Download menu.

    Hope you find them useful

    There are 58 posts in this topic. You are on page 2 of 2.

    Reply

    Wanna join the discussion? Please sign in to reply to this topic.

    Hey there! Welcome to Pinside!

    Donate to Pinside

    Great to see you're enjoying Pinside! Did you know Pinside is able to run without any 3rd-party banners or ads, thanks to the support from our visitors? Please consider a donation to Pinside and get anext to your username to show for it! Or better yet, subscribe to Pinside+!


    This page was printed from and we tried optimising it for printing. Some page elements may have been deliberately hidden.

    Scan the QR code on the left to jump to the URL this document was printed from.