|
Re: MCUs for Vimana, Fire Shark and Teki Paki...
12/22/16 02:32 AM
|
|
|
> If anything, I like Moogly's netlist updates. Even though it is for getting a > computer system up and running, the netlist updates will also help arcade hardware > down the road such as ability to load roms or proms from non-cpu arcade games.
Thanks, man!
I have several hopes with the things that I've added to the netlist system:
1) I feel like a couple of the things - the way I implemented the ROM and RAM interface, mainly - weren't done entirely ideally, and I hope that by taking a stab at them, I will annoy couriersud enough to come back from being MIA, but not enough to quit.
2) I hope that by learning the netlist system, I will increase the "bus factor" of the netlist system above its current value of 1. For those not in the know, "bus factor" is a hypothetical number which is the number of people that, if killed, injured, or otherwise put out of commission, would cause a project or system to become unmaintainable.
3) I hope that by showing that even a relatively idiot-wonder-boy MAMEdev like me can work on the netlist system, other MAMEdevs will realize that the netlist system is nothing to be afraid of, and start taking a crack at implementing the devices that they want or need, or even start writing netlists themselves.
Just for kicks I had a glance at the schematics for Stunt Cycle, and although they're pretty illegible in places, I was able to suss out the necessary part numbers and locations, at least. What I found was heartening: We're only 10 IC implementations away from potentially being able to netlist Stunt Cycle, and only one of those 10 seems like it's going to be a PITA to emulate. This is less than the number of chips that I needed to emulate for the Hazeltine 1500's video board, and now that I'm further up the learning curve and have ironed out the most annoying part (loading ROMs), it wouldn't be that hard at all for someone to get it up and running using DICE as a reference for the fiddly bits.
|
|