Craig, you have the link wrong for the new version of the file (or the file name is wrong). You have it pointing to version 2015 and it should be 2051. Correct link:
http://pincoder.reversion.ca/ccn/ROMS/pincoder_roms-2716_2018-09-26_2051.zip

In the end there is nothing wrong with the 27C256 image or the schematics for the adapter board, i was just misreading the information from my ROM burner. So have confidence with burning a 27C256 chip and making an adapter board.

I haven't tested any of the ROMS other than 00. I'm stuck at the 00 Bus ROM ROM. neither of my boards will run the 01 LED ROM.

With 00 ROM I have all the correct signals at IC1 (CPU) except for pin 9 A0, which is low, and should be high. I can't find a short of any kind and there is continuity from pin 9 to the buffer chip and from the buffer chip to the IC17 ROM.

I am testing on a workbench and if I detach the driver board all the datalines are low, I don't know if this is normal or if it is a clue.

Tonight, I will test with Leon's test chip, I have already tested with Marco's and I get 1 long flash then a locked LED, if I am interpreting correctly it means that the first ROM is not testing correctly, but replacing the ROM makes no difference.

Good way to check for dead address / data buffers or a short is to take out everything but the CPU. The address and data lines all go active (cpu looks for program?). So in that state you can check on each side of the buffers.

Indeed....the testprogram fails to test RAM IC13 ($00~$7f). If replacing IC13 doesn't change anything, the chip select circuit should be checked. A missing address- or databus signal can be the culprit too.

I didn't have a chance to do more testing, the board just started to work again, there must be an intermittent connection or short on the board. Hard to find now, so I'll just wait until it fails again.

I have another board with a similar problem, but I am fairly sure the issue is caused by previous battery damage that was not cleaned up fully.

With my System 6 board now working, I tested all of the ROMs. Well most, I didn't try 06 RAM3 test because that is for System 7, I also did not try 14, 15 or 16 for clearing Init and Edit of CMOS.

Everything worked as expected, the Switch test in particular is very handy when testing the trough switches as it shows up to 12 switch closures at the same time.

Thanks for writing these ROMs.

The title of this thread suggests the ROMs are for System 3, 4 and 6, but in the documents there is reference to System 7.
Can I use these ROMs for System 7? Which IC socket on the System 7 board should I insert the ROM into?

If they work with system 7 they'd probably need to be doubled up on a 2532 in IC17

Have you posted the source for these? I haven't done any Williams specific coding but I have customized some 6800 Bally code and done a lot of 6800 based programming.

Does this work with Hans's single rom adapter? Would be great if it did, I eliminated sockets on my boards
and would be nice to easily reprogram a single chip with this and then easily revert to the entire code of game with just one chip. I know this is still one chip but this way I can burn it in the 2764 and then reburn it for the game code and not have to order and stock other chips OR sockets

A 2764 can only hold four 2716s, so you couldn't fit all of these on it (although maybe if they were compiled together to save space it'd work). You can definitely burn one of these at a time to a 28c64 and stick it in the adapter though.

How about one at a time? On a 2764 which is what that board is built to use. Could I do it? Should I quadruple them? Or maybe fill free space with zeroes to offset it correctly?

It does specifically use a 2764 not the one you said

It can use a 28c64 too. Electronically erasable like a 28c16 so you can rr burn it quickly, no uv eraser needed.

Just putting it in the same position in the rom that I 17 normally goes should be enough. Rest doesn't matter.

The 28c64 is compatible to a 2764. You could quadruple them which is the easiest way to ensure you're getting the code 'where it belongs' but in general, anytime you combine roms the highest one in the series is the one that a 2716 would be on a single chip setup (which the test roms are).

This is because the bootup address pointer needs to be in the last 2 bytes of rom.

Hi! Just simple questions: I have a 27256 rom, I can create the adapter, but I cannot understand how to select the specific test rom via dip switch
Then, I'm trying these amazing software (thanks Pincoder!!! ) on a partially working sys6 board. Test 01-Led is ok, also the test 02-Blanking but with 00-BUS I noticed that pin 9 (address A0) is LOW instead HIGH as it should be.. What can cause this wrong signal?
Thanks

Nice to see this being updated.... ill be trying this out in the near future

....

Can some one make me one of these. Dont really want to buy a programer for one time use, unless some one knows of a cheap one

I have one of these. At $33, a bargain.

ebay.com link: USB MiniPro TL866CS Universal BIOS Programmer EEPROM FLASH 8051 AVR GAL PIC SPI

I have heard peoplw say they dont program 2716 properly

Might be if you have really old 2716's. But you can always use a 2732, they are easier to find anyway.

25v 2716s from certain manufacturers don't work, but I've never had a problem. Plus you can just use. 28c16 instead, way easier

Make sure you get the CS version. Minipro started shipping the "II" version and it removes the ability to program anything about 18 or 16 volts, and there are lots of pinball chips that you need the 21 volts the cs maxes out at.

Hey Pincoder.... I finally got a chance to continue working on my dead MPU board for Flash and finally (with the help of your ROMs) I found the issue. The 7410 that decodes the read/write for the data buffers had one input not working, so when doing a read, it was OK, but on the write, the data transceivers were not being enabled at the right time so I would always write 0's . Never been so happy as seeing the LED blink!!! It wasn't an obvious failure - the IC wasn't hot, and the input pin was toggling correctly. Anyway, that was the only issue keeping the game from booting - now to do fix the drop targets and rebuild the flippers and I'll be a happy camper!

it made it nice to run the RAM and Light tests w/o enabling everything else at first with the Game ROMs.

Hi Craig, thanks for making these! I'm trying them out to figure out a misbehaving firepower and gorgar now.

Can I ask for a clarification on step 1? Instructions say "Top and bottom LEDs should alternate flashing." The LEDs are flashing together. I'm not sure if that's the expected result and the word "alternate" is misleading, or if that's an error and they're supposed to flash but at different times from each other.

Thanks!

Update: it's failing test 01 in ways not tackled in the instructions. I'm an outlier. Yay. It sometimes boots up silently, and the lights flash. Sometimes they don't. Sometimes they flash slower and slower with each flash. Sometimes it fires the top saucer kickout solenoid, sometimes it doesn't. Sometimes it plays sounds, sometimes it doesn't. TP4 remains low, even though a solenoid occasionally fires, and the displays get a brief flicker of power when machine is turned on. I'm so confused. Video pending, my phone won't let me upload to youtube, will have to return to desktop.

Wow, that was a fast reply!

When it boots, which isn't every time, I see 4.99V across TP 9/10. TP 8 is low for a split second then goes high. When it doesn't boot, no volts at 9/10 and 8 stays low.

I think the rom looks good, here's the code, as read back from the rom:
IMG_20190404_083251161 (resized).jpg

Reading what I typed, I guess the first thing I should do is figure out what components make up the reset circuit and replace them.

Your site is not responding. Is it down?

Protip is that ROMs are ROMs, not BINs. Rewrote the chip as a rom and it passes test 1 with flying colors. Now the chips are all in the uv bath so I can rewrite the rest.

Gq-4x with newest available drivers. No renaming. I'm not experienced enough to know the difference, but opening with file format .rom seems to be what I need to do.

IMG_20190406_160625475 (resized).jpg