Update bump: 019 just got posted. The inputs for controlling what is/isn't tested were changed to be more intuitive and less surprising. Also, in response to this I've added a timed watchdog delay indicator to make it obvious that a system is stuck in watchdog. It's just a text message that either disappears quickly if the system is OK, or appears stuck on screen if it isn't. Hopefully these changes make it more usable. Details are in the changelog.txt file and also on the main page.
There's also a new section in the sub-menu for seeing real time updates on a few memcard and system config inputs. I think this was originally done for testing a memory card project for NTM but can also help fixing a system that thinks cards aren't inserted or has issues with write protection.
Nice work. So now for an MV1C I don't need to hold anything on boot? Before I had to hold B and D.
Ex: 3C
Ac: 50
Z80 Reporting Error 10
YM2610 I/O Error
There's a few others to check on top of data for the I/O error:
-Z80 D0~D7 -> YM D0~D7
-Z80 A0/A1 -> YM A0/A1
-NEO-D0 2610WR,2610RD,2610CS -> YM WR,RD,CS
-Z80 A2~A4 -> NEO-D0 SDA2~SDA4
Pretty sure it'll be done of these assuming that system has a NEO-D0.
WR and RD from the NEO-D0 to the YM2610 weren't connected but even after patching the traces the error still exists.
Only other traces involved with 2610 I/O are (on NEO-D0 to Z80) IORQ,SDRD,SDWR but they would stop the Z80 from getting this far to begin with so I didn't list them. If everything on that list checks out then are you sure the 2610 itself is powered and live? Not much else to suggest apart from stuff you've probably already gone through.
Hi XX,
It could be an issue related to a resistor or a capacitor in the Yamaha circuit.
Saludos
Do you by chance know which one?
I can rule out the Z80 and YM2610 as they work fine so it has to be something in the circuit.
Do you by chance know which one?
I can rule out the Z80 and YM2610 as they work fine so it has to be something in the circuit.
Super late bump but did you figure this one out? Completely forgot about it. I would've tried checking NEO-D0 outputs to 2610 and seeing if they are live. Or was it something unrelated?
I have an MV1 that when it starts the test and gets to the WRAM/BRAM test it kicks a reset over and over at that part. I already checked all the connections for a watchdog and it ins't that.
This one is confusing:
http://www.neo-geo.com/forums/showthread.php?246020-AES-3-5-Fast-Video-RAM-WE
Sounds like a C1 issue now. Pins 6,7,92, and 93 are the ones of interest for work ram.
Have you checked continuity on the lines between the 68k and c1?