Repair log: MV1F. No picture, no sound.

kissedin

Enthusiast
Joined
Jan 28, 2023
Messages
116
Reaction score
96
Location
Sweden
Got this board in a lot of three broken MV1F on eBay.

First issue to solve: no sync. Isolated and probed the sync pin on lspc-a2. No signal and the chip itself also got pretty warm. Put in a new chip and was greeted with a white screen.

All data- and adress lines on the system rom looked ok. Changed to uni-bios and got to a very corrupt looking crosshatch screen consisting of big, solid colored blocks.

IMG_20260126_204055.jpg

I could swap through the different menus. Noticed a blue color instead of green on the gradient screen. This made me suspect the ls273 chips and the resistors in the green-circuit. But when trying to boot a game the green color was there.

Speaking of games, cartridges did boot with uni-bios but no sound, sprites or text. Just ... Glitchiness.
IMG_20260114_170720.jpg
Probed randomly and decided to swap Neo b1 which was a speculative and stupid move. Got no change what so ever.

Probed lspc-a2. Found a short between pin 126 (p12) and ground. Fixed this and to my big relief p12 was still working. Still the same corrupt crosshatch though.

If only there were a fix layer so I could use the diag rom... Probed sfix-rom and noticed no activity on the adress pins. Looked at NEO-I0. The p-bus was working flawless but the Q-outputs to the sfix were dead. Changed NEO-I0 to a known working one.

Probed NEO-I0 again. Still dead outputs but this time I noticed that the PCK2B was low. Looked at neo dev wiki. This signal derives from an AS04 inverter. Both the input and the inverted output that is supposed to be the PCK2B were dead.

Traced the input side of the as04 to the NEO-B1 and got confused since I'd already put in a known working b1 there. Looked up the pin out on neo dev and this pin was registered as an input "PCK2"- not an output as I had assumed.

Traced the pin even more and sure enough, it derives from lspc-a2 and goes to neo-b1 (PCK2) but it also goes (in parallell) to the AS04 and then, as an inverted signal to neo-io as "PCK2B". Found and patched a rotten trace from the lspc-a2. Finally some.progress.

IMG_20260126_224531~2.jpg

Now I booted to a cross hatch screen. Ran a game with uni-bios which played good except no sound.

Diagrom errored on no slot switch and then error code 4 - sound ram error.
IMG_20260127_221009.jpg
This turned out to be quite easy. The ram data pins looked suspicious on the oscilloscope so decided to trust the diagrom and changed the sound RAM.

This gave me the sound back and the satisfaction of bringing another beautiful NEO GEO back to life.
 
Last edited:
So... an update on this. I'd been running this board for maybe 4 hours straight. Then all of a sudden:
IMG_20260202_111541.jpg
"WARNING THIS ROM CARTRIDGE IS FOR USE WITH ORIGINAL SNK BOARDS ONLY..." Did I really change that many components? LOL.

Rebooted and now I got "System rom error". According to the almighty Neo dev this may be caused by faulty higher adress lines and is considered a rare error.

For a moment I sat there with my system rom error and felt really special. Then I probed the adress lines on the bios rom but they all seemed to be ok.

Ran diagrom and it got to the backup ram test before the system rebooted - over and over.

Put in a uni bios which booted to a system bios error. Pushed A for resume and got to the cross hatch. Put in a cart and ocassionally the system tried to boot and then presented this error message:
IMG_20260202_132441.jpg

Looked up the adress on neo dev: https://wiki.neogeodev.org/index.php?title=68k_memory_map

The adress changed somewhat from time to time but were always in the lower part of the $000000-$0FFFFF range.

To be honest I don't understand half of what's written on neo dev but it is a great place for getting clues. The description for the adress range in question read "Vector table, first fixed bank of the 68k program ROM (P ROM)"...

Vector table ... I looked up my own repair log: https://www.arcade-projects.com/thr...ick-of-death-calendar-error-bios-error.34290/

The Vector table swap is made by the Neo-E0 chip. But the vec seemed ok - as well as the ani0-ani1-and0.

Probed Neo-E0 during the the uni bios error screen. I found that output pins 8, 11, 12 and 13 were stuck high - while their corresponding input pins (3, 15, 16, 17) were pulsing. These outputs "Y" are the memory card adress bus. I couldn't understand why this would prevent the system to boot. But since this part of the circuit obviously was broken I changed the Neo-E0 anyway.

And ... This got the whole operation running again.
 
Last edited:
Back
Top