SCPH-10000 drive problem

Try replacing the CR2032 battery on it's mainboard and ensuring that the clock can be set (and retains) to something sane. If replacing the battery doesn't help, your console might need some more help (l_Oliveira will have to advice you on that). The EEPROM must be able to retain the data, or replacing it's contents will be useless.

I think that the 'EEPROM' is actually within the MECHACON itself, so it's not replacable. :/
But then again, I never really studied the schematics of the Playstation 2 mainboards thoroughly, so I might be wrong.

I don't think that there is a difference in the electronics on both versions of the SCPH-10000. The only difference was the firmware that Sony put in the MECHACON and the boot ROM chip.

If you took my 10K's EEPROM dump and flashed it onto yours, you'll have a near-exact clone of my dead SCPH-10000 v1.01 console.

I could try to help you retain your console's unique ID and i.Link numbers if they are still intact, but I need you to make a dump of your console's EEPROM to verify that first. One way to do that would be to use the PCSX2 BIOS dumper. If you cannot use the PCSX2 dumper, wait for me to give you some tools (After we communicate via PM).

If you made a dump of your console's boot ROM (BIOS) with the PCSX2 dumper in the past, even better! You won't even need my 10K's EEPROM dump.

Once you make the dump, upload it to a file hosting site like Mediafire (No Rapidshare, please!) or send the EEPROM dump (.NVM file) to my e-mail address at ysai187@yahoo.com.

 

Tokimemofan, you sure the FMCB configuration is complete ? The problem with SCPH-10000 is that it's INCOMPATIBLE with the OSD hacks FMCB has. You have to disable that and configure FMCB to launch uLE or other elf launcher.

That's why it's launching the OSD after booting.

And do backup your EEPROM before trying someone else's EEPROM.

And finally the EEPROM is a separated chip until SCPH-50000 which then it became part of the mechacon.

 

Yeah, seems I was using it wrong, I wasn't aware of the osd incompatibility and the R1 thing. New problem lenschanger isn't cooperating with me, it tries to load but gives me a black screen, tried both PS2s.

 

Could probably be a old version. I have one that works on the 10k. I'll add to that stuff I promised you if I get hold of the guy who have the FTP tomorrow.

 

Dump Sent.

I was using v0.6, Found version 1.2b and while it isn't completely compatible, the dump/restore works.
I also got the tools from pool7 but no test point diagrams (My board is a GH-001 with a 1.01 bios). Also can the test jig be built cheaply or do you have a recommendation for one

 

For the JIG I recommend this circuit:



Which happens to be the very same circuit I use for EESIO commms (for Kermit).

Because it takes a VREF signal into a voltage comparator chip it can translate voltages as low as half a volt into 5V which is proper for the MAX232 chip.

 

I'll probably build this next week, after I go to All Electronics, they should have everything except for the max232

 

Out of interest - what is the latest version (or the version that works with the 10k) of lenschanger?

 

I use the version Dampro (the author) put my name into ... XD

I think if my memory does not betray me, it's version 1.2...

I figured out how the early PS2s stores the S/N on the eeprom. And had a lengthy chat with him about that through 2007, again if my memory does not betray me.

Also it's because of him I got the SONY tools for mechacon eeprom stuff.

 

Oh yea, I've finally figured out how the serial number corresponds to the console ID (As mentioned in the PCSX2 developers' blog).

Apparently it's stored as a 32-bit word, so it needs to be read in reverse. The first byte of the console ID seems to be the month of manufacture from the origin, and it seems to make sense to me lol. My SCPH-77006 has 88 (early 2007?), my SCPH-39006 has 34 (Mid 2002?) and my SCPH-10000 has 01 (Early 2000?).

The SCPH-50000 and above seem to have an additional checksum field for certain parts of the EEPROM like the console and i.Link ID, so maybe that's why we cannot just change those IDs anymore. But, I don't know what formula Sony uses to calculate the checksum for those new checksum fields.

Tokimemofan says that his console still can't read discs properly, even after the EEPROM was flashed over with a dump from my dead 10K (But with the IDs retained). Alright, so he hasn't posted here yet, but why would something like that happen?

 

The flatcables (both the one that goes from the laser to the RF frontend board and the one that connects the frontend board to the main board), the ROHM driver chips (Mostly the BA5810 which is the coils driver), cold joints on the RF frontend board (the tiny board that sits on the mechanism and connects to the laser pickup) cold joints on the DSP chip (the large 208 pin chip under the PCMCIA socket) are some of the issues I witnessed on such consoles in the past. The only console of that kind I was never able to fix had a dead RDRAM controller on it's EE chip. It would fail ram check. That was a sad problem and I still have the console here.

It used to be a SCPH-15000 when it worked.

 

The laser ribbon cable is good, works in my v3, the driver chips seem to work, I do not suspect the DSP, I would think that a cold solder joint on that would also screw up the PCMCIA port (which works enough to boot PSBBN at least). How can I properly test the drive cable and board?

 

The CD DSP has nothing to do with the PCMCIA slot. It just happens to be placed there. The other chip, CXD9566 is the PCMCIA port host interface. Also the DSP has two sides to it. The analog side interfaces with the motor control drive ICs and the frontend board which controls the laser pickup. If the DSP had issues with the digital interface to the console hardware or had any problems communicating with the mechanics controller, the PS2 would fail to boot to the OSD, getting stuck on a black screen...

 

I am looking to give this unit another go. The problem seems to be on the GM-038 DVD logic board. I pulled out the one in my PS2 Tool and tried that, the SCPH-10000 works normally. Obviously I refuse to scrap a perfectly good Tool or SCPH-10000. How can I fix this?

 

Scrap a PS2 TOOL to fix a "boring" and "common" SCPH-10000 ? That's something unthinkable, honestly ...

Well, if the SCPH-10000 is missing the thermal pad which is on top of the SONY RF frontend chip, the board could overheat and solders are likely to break causing malfunctions. Also it's aways possible that mechanical stress could cause the joints to break, even with the thermal pad in place.

I had such a fault on my original SCPH-30001 (the one I bought new) and it was cold joints on the RF frontend board.

While I never saw such fault on a 10k unit, it's a totally plausible fault.

My first suggestions are:

1st is look for corrosion on all parts. Finger grease, for example can cause corrosion on the edge of SMD chip resistors. That's why people should not touch the boards of their devices with bare hands.

2nd is re-work the solders on the GM-038 board.