MV2F only Crosshatch

paoloMVS

n00b
Joined
Aug 20, 2020
Posts
17
Hi guys... I have 3 MV2F boards with same issue..

- solved all previous problems and tesed with Neo Diagnostic Bios and "all tests passed" but...did not read the carts and stay in Crosshatch..

- I have cleaned the slots and tried with few carts
-cecked the traces of A1-A19 from the slot to NEO-GO

any suggestion please

THANKS
 

ack

Ninja Combat Warrior
15 Year Member
Joined
Apr 9, 2009
Posts
538
What I normally do in this case is use unibios and put a cart in. At unibios's crosshatch screen there is an option to do the memory viewer, pick that then scroll down to 000100. At that location, on a working cart, you should see "NEO-GEO".

https://www.mvs-scans.com/misc/IMG_0474.jpg

On yours the "NEO-GEO" will likely be corrupt in some way. Use that corruption to point you in the direction of the issue.
 

paoloMVS

n00b
Joined
Aug 20, 2020
Posts
17
What I normally do in this case is use unibios and put a cart in. At unibios's crosshatch screen there is an option to do the memory viewer, pick that then scroll down to 000100. At that location, on a working cart, you should see "NEO-GEO".

https://www.mvs-scans.com/misc/IMG_0474.jpg

On yours the "NEO-GEO" will likely be corrupt in some way. Use that corruption to point you in the direction of the issue.

thanks bro will try tomorrow and will make some photoes for more help
 

paoloMVS

n00b
Joined
Aug 20, 2020
Posts
17
What I normally do in this case is use unibios and put a cart in. At unibios's crosshatch screen there is an option to do the memory viewer, pick that then scroll down to 000100. At that location, on a working cart, you should see "NEO-GEO".

https://www.mvs-scans.com/misc/IMG_0474.jpg

On yours the "NEO-GEO" will likely be corrupt in some way. Use that corruption to point you in the direction of the issue.

I started with two of them and have had a different response..
one have noting....no letter at all and the otherone have two "E" of the NEO GEO.....

How can translate now those messages...
Thanks

140459714_785421708679014_1463422061134735739_n.jpg
140685390_1085577645280770_3080445759554199150_n.jpg
 
Last edited:

ack

Ninja Combat Warrior
15 Year Member
Joined
Apr 9, 2009
Posts
538
The first one, maybe a address lines issue or the cart roms aren't getting enabled. Can you scroll down some more and see if you get any non-zero data.

The 2nd one, data bit 14 is stuck high.
 

paoloMVS

n00b
Joined
Aug 20, 2020
Posts
17
The first one, maybe a address lines issue or the cart roms aren't getting enabled. Can you scroll down some more and see if you get any non-zero data.

The 2nd one, data bit 14 is stuck high.

thanks ack I solved the first one changing the NEO-GO @G2.5...now read the cart perfectly..

About the second one... thanks for the advice...but how can now go on and ceck the data bit 14

TIA
 

Xian Xi

JammaNationX,
15 Year Member
Joined
Dec 1, 2005
Posts
27,748
thanks ack I solved the first one changing the NEO-GO @G2.5...now read the cart perfectly..

About the second one... thanks for the advice...but how can now go on and ceck the data bit 14

TIA

I’m assuming data bit 14 on the VRAM. Each ram has 8 bits, lower vram is 1-8(D0-D7) and upper vram is 9-16 (D8-D15).
 

Xian Xi

JammaNationX,
15 Year Member
Joined
Dec 1, 2005
Posts
27,748
Actually I can’t remember if VRAM bits are reversed from WRAM, either way check the data lines.
 

ack

Ninja Combat Warrior
15 Year Member
Joined
Apr 9, 2009
Posts
538
I believe the issue is with data bit 14 (prog A19) of the cart slot. If the bit was a stuck high in vram/wram the diag bios would have caught it. I assume its happening on both slots, so I think it will likely either be whatever IC sits between the slots' PROM data lines and the CPU or a trace between that IC and the CPU.

https://wiki.neogeodev.org/index.php?title=MVS_cartridge_pinout
 

paoloMVS

n00b
Joined
Aug 20, 2020
Posts
17
I believe the issue is with data bit 14 (prog A19) of the cart slot. If the bit was a stuck high in vram/wram the diag bios would have caught it. I assume its happening on both slots, so I think it will likely either be whatever IC sits between the slots' PROM data lines and the CPU or a trace between that IC and the CPU.

https://wiki.neogeodev.org/index.php?title=MVS_cartridge_pinout

I follow the prog A19... that goes on pin 41 of the NEO-EO @E/G3 ....

(https://wiki.neogeodev.org/index.php?title=NEO-E0)

now I have to go on to pin 38 and follow it till the CPU ???

thanks
 

ack

Ninja Combat Warrior
15 Year Member
Joined
Apr 9, 2009
Posts
538
I follow the prog A19... that goes on pin 41 of the NEO-EO @E/G3 ....

(https://wiki.neogeodev.org/index.php?title=NEO-E0)

now I have to go on to pin 38 and follow it till the CPU ???

thanks

Sorry, I see the confusion. When I said prog A19 I meant pin 19 on the A side of the prog board, which carries data line 14.

Doing a couple probes it looks like D14 is wired up using this pin mapping

SLOT 1 PROG PIN 19 <=> NEO-G0 @ H2.5 PIN 45
SLOT 2 PROG PIN 19 <=> NEO-G0 @ H2.5 PIN 55
NEO-G0 @ H2.5 PIN 49 <=> 68K PIN 55

I didn't test all pins but looks like the pinout of that NEO-G0 matches this

https://wiki.neogeodev.org/index.php?title=File:Neo-g0_J4_pinout.png
 

paoloMVS

n00b
Joined
Aug 20, 2020
Posts
17
Thanks ack.. will try tomorrow the PROG line.

Meanwhile a take a small video of the third MV2F that I have stucking in Crosshatch... this one make a different thing...the NEO GEO is complete at address 0000100 but it's like flickering...

thanks

 

ack

Ninja Combat Warrior
15 Year Member
Joined
Apr 9, 2009
Posts
538
Thanks ack.. will try tomorrow the PROG line.

Meanwhile a take a small video of the third MV2F that I have stucking in Crosshatch... this one make a different thing...the NEO GEO is complete at address 0000100 but it's like flickering...

thanks


I haven't see that before. What happens if you only have a cart in slot 2? and if there are carts in both slots?

One possibility could be the PIN 51 (DS0) and/or PIN 39 (DS1) of the NEO-G0.
 

paoloMVS

n00b
Joined
Aug 20, 2020
Posts
17
I haven't see that before. What happens if you only have a cart in slot 2? and if there are carts in both slots?

One possibility could be the PIN 51 (DS0) and/or PIN 39 (DS1) of the NEO-G0.

thanks ack... what schould I ceck on DS0 or DS1...

I mean where have them to go or came from or I have to ceck the state with logic probe...
 

paoloMVS

n00b
Joined
Aug 20, 2020
Posts
17
Sorry, I see the confusion. When I said prog A19 I meant pin 19 on the A side of the prog board, which carries data line 14.

Doing a couple probes it looks like D14 is wired up using this pin mapping

SLOT 1 PROG PIN 19 <=> NEO-G0 @ H2.5 PIN 45
SLOT 2 PROG PIN 19 <=> NEO-G0 @ H2.5 PIN 55
NEO-G0 @ H2.5 PIN 49 <=> 68K PIN 55

I didn't test all pins but looks like the pinout of that NEO-G0 matches this

https://wiki.neogeodev.org/index.php?title=File:Neo-g0_J4_pinout.png

ack !!! You was perfectly right...was pin 55 of the 68k not connected...now read perfeectly the cart
THANKS !!!

Still working on the third MV2F...the one with NEO GEO flickering01
 
Last edited:
Top