What's new
sorry I had the volume down on my computer and was only looking at the graphics. It sounds like its playing the right sounds, just distorted. I believe this will point to a PCM data path issue from the carts prog board.

Based on this page

https://wiki.neogeodev.org/index.php?title=MV2F#V_ROM_.2F_YM2610_access

It sounds like the PCM data path is: slots -> NEO-G0 @ K9 -> YM2610. With the NEO-G0 picking which slot's data to pass along. Since its only effecting slot 2, I would check continuity between slot 2's SDRAD0-SDRAD7, SDPAD0-SDPAD7 pins to the NEO-G0.
thanks. I'll check it out
 
thanks. I'll check it out


YM2610 RAD0~RAD7 goes through NEO-G0 @ K9 and out to each cart slot through a separate set of pins. (NEO-G0 needs a proper set of pin names).


NEO-G0YM2610
(2)RAD0(17)
(3)RAD1(16)
(4)RAD2(15)
(5)RAD3(14)
(15)RAD4(13)
(16)RAD5(12)
(17)RAD6(11)
(18)RAD7(10)

NEO-G0PROG slot #1
(6)SDRAD0(B49)
(7)SDRAD1(B50)
(8)SDRAD2(B51)
(9)SDRAD3(B52)
(11)SDRAD4(B53)
(12)SDRAD5(B54)
(13)SDRAD6(B55)
(14)SDRAD7(B56)

NEO-G0PROG slot #2
(62)SDRAD0(B49)
(63)SDRAD1(B50)
(64)SDRAD2(B51)
(1)SDRAD3(B52)
(21)SDRAD4(B53)
(22)SDRAD5(B54)
(23)SDRAD6(B55)
(24)SDRAD7(B56)

Control signals and other address lines buffered through NEO-E0 to both cart slots @ F8.


NEO-E0YM2610
A7(16)RA8(23)
A8(17)RA9(22)
A9(18)RA20(35)
A10(19)RA21(36)
A11(20)RA22(37)
A12(21)RA23(38)
A13(31)RMPX(20)
A14(32)/ROE(21)

NEO-E0PROG slot #1 & #2
Y6(12)SDRA8(A49)
Y7(13)SDRA9(A50)
Y8(14)SDRA20(A51)
Y9(22)SDRA21(A52)
Y10(23)SDRA22(A53)
Y11(24)SDRA23(A54)
Y12(27)SDRMPX(A55)
Y13(28)SDROE(A56)
NEO-G0PROG slot #2
(35)SDPAD0(B41)
(36)SDPAD1(B42)
(37)SDPAD2(B43)
(38)SDPAD3(B44)
(53)SDPAD4(B45)
(54)SDPAD5(B46)
(55)SDPAD6(B47)
(56)SDPAD7(B48)
I checked these lines. everything is OK
 
YM2610 RAD0~RAD7 goes through NEO-G0 @ K9 and out to each cart slot through a separate set of pins. (NEO-G0 needs a proper set of pin names).


NEO-G0YM2610
(2)RAD0(17)
(3)RAD1(16)
(4)RAD2(15)
(5)RAD3(14)
(15)RAD4(13)
(16)RAD5(12)
(17)RAD6(11)
(18)RAD7(10)

NEO-G0PROG slot #1
(6)SDRAD0(B49)
(7)SDRAD1(B50)
(8)SDRAD2(B51)
(9)SDRAD3(B52)
(11)SDRAD4(B53)
(12)SDRAD5(B54)
(13)SDRAD6(B55)
(14)SDRAD7(B56)

NEO-G0PROG slot #2
(62)SDRAD0(B49)
(63)SDRAD1(B50)
(64)SDRAD2(B51)
(1)SDRAD3(B52)
(21)SDRAD4(B53)
(22)SDRAD5(B54)
(23)SDRAD6(B55)
(24)SDRAD7(B56)

Control signals and other address lines buffered through NEO-E0 to both cart slots @ F8.


NEO-E0YM2610
A7(16)RA8(23)
A8(17)RA9(22)
A9(18)RA20(35)
A10(19)RA21(36)
A11(20)RA22(37)
A12(21)RA23(38)
A13(31)RMPX(20)
A14(32)/ROE(21)

NEO-E0PROG slot #1 & #2
Y6(12)SDRA8(A49)
Y7(13)SDRA9(A50)
Y8(14)SDRA20(A51)
Y9(22)SDRA21(A52)
Y10(23)SDRA22(A53)
Y11(24)SDRA23(A54)
Y12(27)SDRMPX(A55)
Y13(28)SDROE(A56)
NEO-G0PROG slot #2
(35)SDPAD0(B41)
(36)SDPAD1(B42)
(37)SDPAD2(B43)
(38)SDPAD3(B44)
(53)SDPAD4(B45)
(54)SDPAD5(B46)
(55)SDPAD6(B47)
(56)SDPAD7(B48)
I checked these lines. everything is OK
I managed to fix the sound bug.
both slots work fine.
NEO-G0 was at fault.

Thanks for the help!
 

Attachments

  • IMG_20230126_180938.jpg
    IMG_20230126_180938.jpg
    191.9 KB · Views: 38
This is a completely different board then your previous 2slot?

I would start by validating the bios is good, then verify the continuity of data/address lines between the bios and cpu
 
This is a completely different board then your previous 2slot?

I would start by validating the bios is good, then verify the continuity of data/address lines between the bios and cpu
It a new type board
It has Unibios 4.0. not faulty.
ok, I check the path between the bios and the CPU.
Is there a guide to this on wikipedia? exactly which pin should go where?
 
This is a completely different board then your previous 2slot?

I would start by validating the bios is good, then verify the continuity of data/address lines between the bios and cpu
All data/address lines are connected between BIOS and CPU.
 
  • Check the reset line of the CPU with a logic probe. When you power on the board you should expect it to start low and go high (it may end up pulsing because watchdog is resetting the board over and over)
  • Use logic probe on pin 20 (output enable) of the bios chip, verify its pulsing
  • Is there any obvious signs of damage (ie battery leakage) or re-work done on the board?
 
  • Check the reset line of the CPU with a logic probe. When you power on the board you should expect it to start low and go high (it may end up pulsing because watchdog is resetting the board over and over)
  • Use logic probe on pin 20 (output enable) of the bios chip, verify its pulsing
  • Is there any obvious signs of damage (ie battery leakage) or re-work done on the board?
I tested it with a logic tester. high level is visible after switching on. it pulses with the same frequency as you can see in the video.

I checked the battery for leaks. There are no leaks on the pcb.

I saw damage to the NEO-G0, so I soldered it off.
NEO-G0 41pin shows damage. does not connect anywhere (41pin)
I did NOT put NEO-G0 back in the sheet. I turned on the board.
The watchdog image has stopped and "MAIN RAM TEST" is displayed.

I put another NEO-G0 back in the board. the watchdog is back.

Will the fault be on this line?
 

Attachments

  • 2.jpg
    2.jpg
    245 KB · Views: 45
  • 3.jpg
    3.jpg
    84.6 KB · Views: 42
  • 4.jpg
    4.jpg
    205.9 KB · Views: 41
Sounds like that NEO-G0 is getting enabled when it shouldn't be.

https://wiki.neogeodev.org/index.php?title=NEO-G0

If you look at the internal logic section it shows that pins 39 and 51 are what could enable parts of the program rom to pass to the CPU data bus. I would check to see what those pins are doing.

Also, In the lower left of the page it has the pinout for J4 on MV2B which should be the same as MV2F. In the comments for that it gives the impression those enable pins come from the NEO-I0 chip.

Your MAIN RAM TEST likely just means you have all your hard dips in the ON position. You also seem to have a 32K/slow vram related issue given the dupe/corrupt text.
 
Sounds like that NEO-G0 is getting enabled when it shouldn't be.

https://wiki.neogeodev.org/index.php?title=NEO-G0

If you look at the internal logic section it shows that pins 39 and 51 are what could enable parts of the program rom to pass to the CPU data bus. I would check to see what those pins are doing.

Also, In the lower left of the page it has the pinout for J4 on MV2B which should be the same as MV2F. In the comments for that it gives the impression those enable pins come from the NEO-I0 chip.

Your MAIN RAM TEST likely just means you have all your hard dips in the ON position. You also seem to have a 32K/slow vram related issue given the dupe/corrupt text.
I followed the line between NEO-G0 pin 39-51 and NEO-I0. NEO-G0 pin 39 goes to NEO-I0 pin28.
NEO-G0 pin 51 goes to NEO-I0 pin27.
That's why I replaced the NEO-I0.
unibios 4.0 did not start. Black screen.
Original BIOS started.
View: https://youtu.be/a9fxrB-dr1Q
 
I followed the line between NEO-G0 pin 39-51 and NEO-I0. NEO-G0 pin 39 goes to NEO-I0 pin28.
NEO-G0 pin 51 goes to NEO-I0 pin27.
That's why I replaced the NEO-I0.
unibios 4.0 did not start. Black screen.
Original BIOS started.
View: https://youtu.be/a9fxrB-dr1Q
The black screen on the unibios 4.0 is likely a bug. On some multi slot boards it will boot to the black screen if there are no cart(s) installed. Even if you have multiple of the same model number, one may always boot to black screen while the other to cross hatch. I've never been able to figure out the exact trigger.

I would try booting with the diag bios and see what it says. Something is going on with either your slow/32k vram or maybe accessing the sfix rom on the board. The wavy disappearing video in your video is likely a symptom of a broken trace somewhere. So you might just try logic probing your video ram / SFIX rom to see if any of the pins are dead.
 
The black screen on the unibios 4.0 is likely a bug. On some multi slot boards it will boot to the black screen if there are no cart(s) installed. Even if you have multiple of the same model number, one may always boot to black screen while the other to cross hatch. I've never been able to figure out the exact trigger.

I would try booting with the diag bios and see what it says. Something is going on with either your slow/32k vram or maybe accessing the sfix rom on the board. The wavy disappearing video in your video is likely a symptom of a broken trace somewhere. So you might just try logic probing your video ram / SFIX rom to see if any of the pins are dead.
unfortunately, I can't find the DIAG ROM. :((( I don't have the eprom erasing uv lamp here. I can write another one on Monday. I'll check the SFIXROM pins with a Logic probe.
 
unfortunately, I can't find the DIAG ROM. :((( I don't have the eprom erasing uv lamp here. I can write another one on Monday. I'll check the SFIXROM pins with a Logic probe.
began to probe with a logic probe.
I saw something strange in the SFIX rom 9 pin. when I touch the logic probe, the picture changes. SFIX pin9 connects to NEO-I0 pin 45.
 
The black screen on the unibios 4.0 is likely a bug. On some multi slot boards it will boot to the black screen if there are no cart(s) installed. Even if you have multiple of the same model number, one may always boot to black screen while the other to cross hatch. I've never been able to figure out the exact trigger.

I would try booting with the diag bios and see what it says. Something is going on with either your slow/32k vram or maybe accessing the sfix rom on the board. The wavy disappearing video in your video is likely a symptom of a broken trace somewhere. So you might just try logic probing your video ram / SFIX rom to see if any of the pins are dead.
I inserted the diag bios.
Unfortunately, it doesn't show anything.
 

Attachments

  • IMG_20230130_081148.jpg
    IMG_20230130_081148.jpg
    219.5 KB · Views: 39
Normally I would suggest trying to find that main tile/char being repeated over 90% of the screen in the sfix rom. This should be the empty/space tile (0x020), but as you can see its something else.

https://wiki.neogeodev.org/images/1/15/Fixref01.png

But I can't seem to find the tile on your screen in the sfix. You might try looking yourself, if you cant find it either I would suspect something with the sfix rom or the traces going to it.
 
Normally I would suggest trying to find that main tile/char being repeated over 90% of the screen in the sfix rom. This should be the empty/space tile (0x020), but as you can see its something else.

https://wiki.neogeodev.org/images/1/15/Fixref01.png

But I can't seem to find the tile on your screen in the sfix. You might try looking yourself, if you cant find it either I would suspect something with the sfix rom or the traces going to it.
I replaced the sfix ROM. unfortunately nothing changes.

is it possible that the NEO-I0 is still faulty?
I put an untested NEO-I0 in it...
 
Its possible, it carries the SFIX address lines. Might double check there is continuity between the 2. You mentioned before doing a logic probe on the sfix caused the chars to change, which is weird.
 
Its possible, it carries the SFIX address lines. Might double check there is continuity between the 2. You mentioned before doing a logic probe on the sfix caused the chars to change, which is weird.
I started tracing the line from SIFX.
All lines connect somewhere. most pins are connected to NEO-I0.
5 pins connect to PRO-CO
1 PIN is connected to LSPC-A0.
I will replace the NEO-I0 again, I hope there will be a change.
 
I started tracing the line from SIFX.
All lines connect somewhere. most pins are connected to NEO-I0.
5 pins connect to PRO-CO
1 PIN is connected to LSPC-A0.
I will replace the NEO-I0 again, I hope there will be a change.
wow !!!! the NEO-I0 was bad. 1-2 slots same error screen. I look at the NEO-G0 lines.
 

Attachments

  • IMG_20230131_170420.jpg
    IMG_20230131_170420.jpg
    262.3 KB · Views: 35
  • IMG_20230131_170703.jpg
    IMG_20230131_170703.jpg
    205.1 KB · Views: 37
Back
Top