For my sins I've decided to reverse engineer the sprite handling section of a pretty cool game. Unfortunately it's got a sodding great custom attached so I can't use the normal methods for identifying which sprite RAM is duff.
So far I've used IDApro to disassemble the 68k code and identify the self test routines, mame debug to watch the code and modify it to recreate the fault in emulation, a 68k assembler to write my own boot code which uses the byte memory mapped custom register to talk to the sprite custom IC and stuff I'm sure I've blanked out! Because the sprite RAM is accessed via a memory mapped register I can't really use a Fluke without some super funky coding. To top it all off, when the self test code runs and detects the error it STOPs the 68k so the busses die and I can't even scope the RAMs
So the current plan is to document this part of the circuit so I can figure out what to capture on my logic analyser and identify the data pathways to monitor the reads/writes and trigger on a difference.
There is very little fix info available for this popular game so even though I could take a slight shortcut - I've figured out 95% of talking to the video hardware, so I reckon I can write a new boot ROM which sets up the display, does consecutive reads/writes to sprite RAM through the register, prints to the screen the logical failing address and strobes the /CS line so I can ident the physical RAM - I figure it'll be useful for others if I finish making the schem for this part of the board.
I'll release my test boot ROM when it's done as well as as much of the schem as I need to draw. If anyone is interested in the processes I mention above I'll write this up as a full repair doc?
Below is the result of my first few hours efforts
. Anyone who can guess what it is before I upload the final version tomorrow is my hero and should tell me where they've seen it before!
http://i.imgur.com/P1LagQo.png - it's a few-k pixels wide.
So far I've used IDApro to disassemble the 68k code and identify the self test routines, mame debug to watch the code and modify it to recreate the fault in emulation, a 68k assembler to write my own boot code which uses the byte memory mapped custom register to talk to the sprite custom IC and stuff I'm sure I've blanked out! Because the sprite RAM is accessed via a memory mapped register I can't really use a Fluke without some super funky coding. To top it all off, when the self test code runs and detects the error it STOPs the 68k so the busses die and I can't even scope the RAMs
There is very little fix info available for this popular game so even though I could take a slight shortcut - I've figured out 95% of talking to the video hardware, so I reckon I can write a new boot ROM which sets up the display, does consecutive reads/writes to sprite RAM through the register, prints to the screen the logical failing address and strobes the /CS line so I can ident the physical RAM - I figure it'll be useful for others if I finish making the schem for this part of the board.
I'll release my test boot ROM when it's done as well as as much of the schem as I need to draw. If anyone is interested in the processes I mention above I'll write this up as a full repair doc?
Below is the result of my first few hours efforts
http://i.imgur.com/P1LagQo.png - it's a few-k pixels wide.