(Topic ID: 252795)

What am I doing wrong with EPROM

By jgadzia

4 years ago


Topic Heartbeat

Topic Stats

  • 21 posts
  • 5 Pinsiders participating
  • Latest reply 4 years ago by pincoder
  • Topic is favorited by 1 Pinsider

You

Linked Games

Topic Gallery

View topic image gallery

20191007_185828 (resized).jpg
20191007_185542 (resized).jpg
20191007_185452 (resized).jpg
20191006_220104 (resized).jpg
IMG_20191004_193146297 (resized).jpg
pasted_image (resized).png
#1 4 years ago

Ok i have been trying to burn leons rom, and i tried the newest version and recently tried the older version. I can get neither of them to work appropriately. I have included a video of start to stop, hoping someone can figure out what i am doing wrong. I would appreciate any help.
i did notice when i look at the buffer, it appears to be full of FF's through most of the buffer, which seems that it is blank?

#2 4 years ago

The Leon system 11/data east chip from pinwiki anyway is supplied on a 27512 chip. It looks like it's just a doubled up 27256 image though, I split it in half and both halves verified with each other.

Looking at the code split in pinmame, there are 3 bytes starting at offset $257 that are 00 00 00 - this is an illegal opcode. Now, pinmame just skips right over these because it might not be 100% cpu accurate, or a later revision cpu fixes this error (illegal opcodes usually do something unpredictable in a microprocessor).

You can change those 3 00 bytes in your editor to be "01 01 01" which is the 6800/02/08 opcode for "nop" (no operation) and see if it works that way.

#3 4 years ago

i am not seeing what you are seeing. when i open this file in a hex editor this is what i see. this appears identical to what i see in the buffer on the eprom burning software.

pasted_image (resized).pngpasted_image (resized).png
#4 4 years ago
Quoted from jgadzia:

Ok i have been trying to burn leons rom, and i tried the newest version and recently tried the older version. I can get neither of them to work appropriately. I have included a video of start to stop, hoping someone can figure out what i am doing wrong. I would appreciate any help.
i did notice when i look at the buffer, it appears to be full of FF's through most of the buffer, which seems that it is blank?

What is the 27256 Leon checksum?

#5 4 years ago

Remove J5 and connect J4 to run a 27256 in C5
retest chip

IMG_20191004_193146297 (resized).jpgIMG_20191004_193146297 (resized).jpg
#6 4 years ago
Quoted from PINTEC:

What is the 27256 Leon checksum?

007DAB2C

#7 4 years ago

ok only have jumpers in J3 and J4. Verified continuity.

Erased EProms. verified they were blank. Rewrote Eprom. Verified Write. removed Eprom and re-read it get the same checksum. put EProm in board and get the same thing. +5v and Pia light stay lit.

#8 4 years ago
Quoted from jgadzia:

ok only have jumpers in J3 and J4. Verified continuity.
Erased EProms. verified they were blank. Rewrote Eprom. Verified Write. removed Eprom and re-read it get the same checksum. put EProm in board and get the same thing. +5v and Pia light stay lit.

What is your email I'll send the 27256 Leons I have confirmed working.

#9 4 years ago
Quoted from jgadzia:

i am not seeing what you are seeing. when i open this file in a hex editor this is what i see. this appears identical to what i see in the buffer on the eprom burning software.

Looks like that's a different version of the chip then what I downloaded from pinwiki. Pinwiki's said it was version 5, and your offset is the text part (which is never executed).

Quoted from PINTEC:

What is your email I'll send the 27256 Leons I have confirmed working.

Pintec can you compare what you have to what is on pinwiki - seems like the pinwiki one might be wrong as there shouldn't be 3 illegal opcodes in the middle of the test. The pinwiki is a 512 image but it's just a doubled up 256.

#10 4 years ago

ok i burned the smaller leons rom and put it in the non-working board, and I got the pia flashing (after i changed the jumpers at J4 and J5). put it back in the supposedly working board and still couldnt get the pia to flash. I went ahead and tested the non-working board and found that the PIA for the DMD was bad and replaced it. Stuck Leons rom back in and tested it and everything seems to be working ok. So now i am left with the board that i still cant get leons rom to run, went a little further into the wiki. It says that i should get 4 volts at pin 40, and i am only getting 0.19 volts. but i checked the working board and i was getting the exact same voltage there, so not sure if that is a problem or not. I took my oscilloscope and checked the vma, the clock and the e signal. I think the problem might be the vma. here is the pic of my vma signal on the oscilloscope. If i trace that back to 7E is there some test that i can do there to see if it goes back further to 7c or 7D?

20191006_220104 (resized).jpg20191006_220104 (resized).jpg
#11 4 years ago

For a more meaningful display, set your scope to 2V/div and 500ns or 1us/div, this is a 5 volt and 1MHz system.

#12 4 years ago
Quoted from Tuukka:

For a more meaningful display, set your scope to 2V/div and 500ns or 1us/div, this is a 5 volt and 1MHz system.

i will do that when i get home tonight, but this was the only setting where i felt i could see anything, everything else looked like a line.

#13 4 years ago

Start with the clock or E signal at 2V/1us /div and you should see a more or less perfect square wave. Adjust trigger level if necessary until the waveform "freezes" in display.

Then, you can move the scope probe to other signals but don't touch the scope settings. If you see a solid line near 0 or 5 volts that means the signal stays at logic 0 or 1, or doesn't change very often. Most, if not all, logic signals in game CPU do change states continuously so a solid 0 or 1 is usually a sign of problem. For signals changing only occasionally, such as IRQ, you need to tinker with scopes triggering settings, but anyway if you observe the clock and E signals and activity on data/address bus the CPU is definitely running. Next to check would be the /CE inputs of ROM and RAM, those should be periodically pulsing low.

#14 4 years ago

first pic is pin 39 clock
second pic is pin 37 e signal
third pic is vma which i am guessing is bad

20191007_185452 (resized).jpg20191007_185452 (resized).jpg20191007_185542 (resized).jpg20191007_185542 (resized).jpg20191007_185828 (resized).jpg20191007_185828 (resized).jpg
#15 4 years ago

Yes, your clock and E are fine but there is definitely something wrong with VMA, it should be mostly high. Try another 6802.

Edit: also might be possible that the CPU has problems reading ROM and gets a WAI instruction and then halts waiting for interrupt with VMA low. Anyway, testing with another CPU chip will help.

#16 4 years ago

can someone explain what the vma stands for and what it does?

#17 4 years ago

VMA stands for valid memory address. CPU sets VMA high when it has set a memory address on the bus, for reading or writing memory. So whenever the CPU is running a program the VMA should show activity.

The CPU can be set to a state in which it does nothing, but waits for an interrupt (a low in IRQ or NMI pins) and in that state it does not assert VMA.

#18 4 years ago
Quoted from Tuukka:

VMA stands for valid memory address. CPU sets VMA high when it has set a memory address on the bus, for reading or writing memory. So whenever the CPU is running a program the VMA should show activity.
The CPU can be set to a state in which it does nothing, but waits for an interrupt (a low in IRQ or NMI pins) and in that state it does not assert VMA.

so if the cpu is sending out the vma and i am measuring no voltage at pin 5, does that mean the cpu is bad or the chip at 7e?

#19 4 years ago

I would try with another CPU first.

2 weeks later
#20 4 years ago
Quoted from Tuukka:

I would try with another CPU first.

just to close this thread, the cpu was bad. i replaced it and everything is working great. Thanks for all the help. it was greatly appreciated!

#21 4 years ago

Glad to see you got it working!

Just in case somebody reads through this topic later: You can troubleshoot problems like this (and more) by using these test ROMs: http://pincoder.ca They're free and can be used in-game as well.

Promoted items from Pinside Marketplace and Pinside Shops!
$ 45.00
Playfield - Toys/Add-ons
Pixels Arcade Games
 
€ 80.00
Playfield - Toys/Add-ons
Pino Pinball Mods Shop
 
5,250
Machine - For Sale
Mt Zion, IL
$ 79.99
Playfield - Toys/Add-ons
Lighted Pinball Mods
 
$ 49.00
Playfield - Toys/Add-ons
Pixels Arcade Games
 
$ 185.00
Cabinet - Toppers
Sparky Pinball
 
$ 54.00
Cabinet - Toppers
Slipstream Mod Shop
 
$ 85.00
Playfield - Plastics
Pinball Haus
 
From: $ 1.00
Boards
Slap Save Creations
 
$ 85.00
Playfield - Plastics
Pinball Haus
 
$ 14.95
Playfield - Toys/Add-ons
ULEKstore
 
$ 18.95
Eproms
Pinballrom
 
$ 9.95
Eproms
Pinballrom
 
$ 9.99
Eproms
Matt's Basement Arcade
 
$ 12.00
Playfield - Toys/Add-ons
UpKick Pinball
 
$ 18.95
Eproms
Pinballrom
 
$ 18.95
Eproms
Pinballrom
 
$ 60.00
Tools
Performance Pinball
 
$ 79.99
Playfield - Toys/Add-ons
Lighted Pinball Mods
 
$ 20.00
Playfield - Decals
Metal-Mods
 
$ 17.50
Playfield - Decals
Pinball Invasion
 
$ 65.00
Boards
Pinball Haus
 
$ 48.00
Playfield - Toys/Add-ons
Pixels Arcade Games
 
$ 30.00
Playfield - Other
YouBentMyWookie
 
5,200
Machine - For Sale
Denver, CO

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/what-am-i-doing-wrong-with-eprom?hl=pincoder 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.