MV1FZS And one cart problem

oguz

n00b
Joined
Oct 30, 2023
Posts
3
Hello everyone,

My MV1FZS has some problems =)

And also my sidekicks 11 has glitches and sound problems noises too (there were no sign of life when i bought but after deep cleaning on connector it started to show something)

P.S. sidekicks tried on working board.

see photos of universe bios and neo diag as well.

From what i have read forums. for the board; I should change pair of CXK5814P-35L chips but beforehand should i diag more?

but for the game i am out of ideas.
 

Attachments

  • IMG_9117.jpeg
    IMG_9117.jpeg
    2.3 MB · Views: 3
  • IMG_9118.jpeg
    IMG_9118.jpeg
    4.1 MB · Views: 3
  • IMG_9127.jpeg
    IMG_9127.jpeg
    2.6 MB · Views: 3
  • IMG_9071.jpeg
    IMG_9071.jpeg
    2.8 MB · Views: 3
  • IMG_9165.jpeg
    IMG_9165.jpeg
    2.4 MB · Views: 3
  • IMG_9162.jpeg
    IMG_9162.jpeg
    2.1 MB · Views: 4
  • IMG_9163.jpeg
    IMG_9163.jpeg
    2.3 MB · Views: 3
  • IMG_9220.jpeg
    IMG_9220.jpeg
    2.5 MB · Views: 3
  • IMG_9233.jpeg
    IMG_9233.jpeg
    2.3 MB · Views: 3

ack

Ninja Combat Warrior
15 Year Member
Joined
Apr 9, 2009
Posts
543
The combination of those 2 diag bios errors points to neither ram chip being writable. I would check for activity on the WE pin on both of the 2K ram chips. You might just have a cut/damaged trace.
 

oguz

n00b
Joined
Oct 30, 2023
Posts
3
Actually i did if we are talking about CXK5814P-35L chips. Both shows high/low activity
 

Attachments

  • IMG_9265.png
    IMG_9265.png
    615 KB · Views: 2
  • IMG_9266.jpeg
    IMG_9266.jpeg
    1.6 MB · Views: 2
  • IMG_9268.jpeg
    IMG_9268.jpeg
    1.8 MB · Views: 2

ack

Ninja Combat Warrior
15 Year Member
Joined
Apr 9, 2009
Posts
543
Yes those are the ones.
 

ack

Ninja Combat Warrior
15 Year Member
Joined
Apr 9, 2009
Posts
543
There is definitely something wrong related to those ram chips. I'm a bit suspect its not the chips themselves, as it seems unlikely they would both have the same fault (returning 0x00 after the diag rom wrote 0x55). I would probably do these things

- use logic probe to verify none of the address lines on the chips are floating
- verify none of the legs on the LSPC chip are loose
- try the piggyback and see if it makes any difference (even if its still bad)
 
Top