(Topic ID: 228580)

ballys viking u6 rom

By gameover1173

5 years ago


Topic Heartbeat

Topic Stats

  • 21 posts
  • 3 Pinsiders participating
  • Latest reply 5 years ago by barakandl
  • No one calls this topic a favorite

You

Linked Games

Topic Gallery

View topic image gallery

Untitled (resized).png
#1 5 years ago

i have changed the jumpers for 2732's to run on a original mpu (2518-35)already
i burned u2 without a problem but u6 is giving me problems.
tried several blank chips and same thing.
is there a special way to burn this chip??

#2 5 years ago
Quoted from gameover1173:

is there a special way to burn this chip??

U6 was originally a 2716/9316 type ROM (half the memory capacity of a 2732). Did you double the ROM file to effectively program both halves of the 2732 with the same code?

#3 5 years ago

There were a couple sites online where it said the rom was already converted to 2732
http://arcarc.xmission.com/Pinball/Roms/Pinball/Bally/

#4 5 years ago
Quoted from gameover1173:

There were a couple sites online where it said the rom was already converted to 2732
This was one of them
http://arcarc.xmission.com/Pinball/Roms/Pinball/Bally/

#5 5 years ago
Quoted from gameover1173:

There were a couple sites online where it said the rom was already converted to 2732
http://arcarc.xmission.com/Pinball/Roms/Pinball/Bally/

Which U6 ROM file from that archive are you using?

BTW, what problems are you having? you didn't specify.

#6 5 years ago

I'm getting a buffer error from the file
720-3532.u6 on that site.

#7 5 years ago

Using a gq- 4x4 programmer
Here is the error
Write failed address=0x00087d
Buffer=0xfe device=0xff
This is what is says when trying to write it

#8 5 years ago
Quoted from gameover1173:

I'm getting a buffer error from the file
720-3532.u6 on that site.

Yep, "720-3532.U6" is the right file. I don't get any errors from the downloaded zip file.

Try the one on IPDB.
https://www.ipdb.org/files/2737/Bally_1980_Viking_ROMs.zip

Load the "720-35_6.716" file in the upper half of the 2732 buffer or just double it to fill the whole 2732 ROM space.

#9 5 years ago
Quoted from gameover1173:

Buffer=0xfe device=0xff
This is what is says when trying to write it

Your 2732 might be bad.

#10 5 years ago

I have tried 4 different 2732's
How do you double it?

#11 5 years ago

Is it failing at the same address with every chip?
If you're using MS Windows, open a command prompt.
Go to the folder that has your U6 ROM downloaded from IPDB and type:
copy "720-35_6.716" /b + "720-35_6.716" /b "720-35_6.732"

"720-35_6.732" will be your doubled up file (lower half and upper half will contain the same ROM data).

Or just use the GQ-4X programmer software to load the "720-35_6.716" file at buffer address 0x000, and also at buffer address 0x800

BTW, have you tried to program the chip a second or third time *without* erasing it between programs?

#12 5 years ago

Its seems to fail at the same point
These chips are erased and blank before starting. I'll giving that a shot with that type command and report back later.
Thanks for the help this far

#13 5 years ago

How do you do this
Or just use the gq- 4x4 programmer software to load the "720-35_6.716" file at buffer address 0x000, and also at buffer address 0x800
Fairly new on this

#14 5 years ago
Quoted from gameover1173:

How do you do this
Or just use the gq- 4x4 programmer software to load the "720-35_6.716" file at buffer address 0x000, and also at buffer address 0x800
Fairly new on this

Sorry, I don't have a GQ-4X programmer so can't tell you exactly how, but a standard feature with EPROM programmers is that when you load a file there's an option to tell it where in the RAM buffer you want to load it.
The RAM buffer for a 2732 will be 0x1000 hex bytes long. The "720-35_6.716" ROM file is half that size so loading it at offset 0x000 and 0x800 (these are hex number offsets), will effectively program both halves of a 2732 with that half length file.

Having said all that, I don't believe this is your problem. If your programmer is failing to program the chips, that's another matter.
What brand/model of 2732 chips are you using? And are you matching the type exactly in the software?

#15 5 years ago

I am matching the brand with the correct software. Just not familiar with this rom burner with doubling. Same with using dos
I haven't used it in many years. I couldn't get it to work in dos either. Any chance I could get someone to send me the file doubled?

#16 5 years ago

if gq-4x gives you a write error the issue is not with the file. The burner is just not able to flip the bits on that chip for some reason. The chip could be defective or you are using the wrong programming voltage / eprom type profile.

What does the marking on your chip say and what profile in GQ4X software are you picking?

Are you using a powered USB hub or an AC adapter wall wart with the GQ-4X? For the 25v burning chips like many 2732 it has to kick up 5v to 25v to write the chip. When on a weenie USB port there is not enough current and the programming voltage doesnt get high enough and the burn fails. (write error).

#17 5 years ago
Quoted from gameover1173:

Any chance I could get someone to send me the file doubled?

Your programmer is having trouble programming your 2732 chips. Doubling the ROM isn't going to fix it - this mixup came from us both posting above at the same time before I saw the error you were getting.

Try programming the 2732 file you have multiple times without erasing between programs to see if you can get that bit to program properly.
Also, what brand/model of 2732 chips are you using?

#18 5 years ago

I tried these chips multiple times without erasing too. Chip says nec d2732
I have tried burning with just USB and with an adapter same issue. Maybe try a different batch of chips?

#19 5 years ago

It appears there may be three different types of NEC D2732 EPROMS each having different programming voltages: 12.7V, 21V and 25V
What programming voltage is the software using for the chip you select?
Do your 2732 chips indicate the programming voltage? Post a picture of the EPROMs if you can.

#20 5 years ago

I installed the GQ-4X4 software and there's no 2732 devices listed under NEC.

From the NEC programming voltages listed at:
http://proshivka.com.ru/listprom.php

D2732 25V
D2732A 21V
D2732B 12.5V
D2732D comes up as 25V in my programmer software but it's been known to be wrong

Try programming from the lowest voltage (to minimise potentially damaging the chip) and go up if the program fails. So from the (All Generic) EPROM device selection in the GQ-4X4 software, try "2732B(12.7V VPP)" if it fails, then try 2732A(21V VPP) and lastly 2732(25V VPP).

#21 5 years ago

If it D2732 plain, no letter suffix, its a 25v chip. If you not using a powered usb hub or a wall wart into the gq4x, try that.

Also do they blank check OK? If they are not blank you need to bake them in the UV light before burning or you will get a write error.

I use the generic profiles for 2732. If your chip has no letter after 2732 it is 25v. If it is a 2732A it is 21v. If it is 2732B it is 12.5v.

Untitled (resized).pngUntitled (resized).png

Promoted items from Pinside Marketplace and Pinside Shops!
$ 8.00
Electronics
Third Coast Pinball
 
$ 18.00
Electronics
Yorktown Arcade Supply
 
5,999
Machine - For Sale
Sewickley, PA
$ 18.95
Eproms
Pinballrom
 
$ 10.00
$ 119.95
Boards
Allteksystems
 
$ 25.00
Cabinet Parts
Volcano Pinball
 
$ 22.50
$ 9.95
Eproms
Pinballrom
 
Hey modders!
Your shop name here

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 https://pinside.com/pinball/forum/topic/ballys-viking-u6-rom- 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.