PlayStation 2 GH-004 problem

I got this unit a few months ago and it wasn't putting out video and acted like there was a disc inside even when there wasn't. I got it mostly working for a few weeks but now it is dead again. This time though the tray pops out like a rocket and then screeches, no video either. Help...

 

What model is it?
e.g. SCPH-xxxxx

 

It's a test DTL-H30001, otherwise I wouldn't waste my time, internally similar to v1/2, Btw I tried swapping the clock sub board and drive logic board, no change.

 

I did not realize that the MECHACON is not on the main part of this model's main board. But if you can actually change that with one from a CEX, you may not actually want to because it would no longer function as a DEX and the drive will probably not be boot certified correctly.

 

Which board is the mechacon on in this one?

 

I thought you knew, since you wrote that you swapped the "drive logic board".
The MECHACON should be a CXP102064. According to @l_oliveira, they also have a DSP chip with slightly different markings.

I don't know how to really help you, so you may want to wait for someone who knows to chime in. Particularly in the name of conservation.

 

You can't mix a dex mechacon with a cex dsp. Doesn't work at all.

If you do that, the PS2 will stop powering on... Well, it will power on but it will shut down once the mechacon figures out it has a wrong DSP attached to it. It will send syscon a power off request through the I2C bus.

 

I think we might be getting mixed up the mechacon is on the motherboard. I think it was the later version with the single drive ribbon that did that. That's why I was confused.

 

if that's the case that isn't the problem.

 

@ the OP: The EEPROM has information about the tray motor speed, default position for the tilt adjust motor and a lot of other things. It is on the smaller board along with the real time clock and the battery.
There might be a problem with the attachment between the two boards that form the console mainboard. Have that checked.

 

Possible but I doubt it this the drive at one point I had it 99% working. It would work perfectly running games however pressing the reset/power button would sometimes cause it hang it with a black screen. It would continue accessing the disc almost as if it were working normally. Any good technical information on the reset and bios boot process. I did a temporary swap of the clock board that is how I know the GH-004 part is the problem. Btw this unit was in good condition with an intact warranty seal and no roach/water damage.
Which components are non swappable from cex to dex besides the Mechacon, BIOS and DSP chips I have the technical ability to swap anything on the board except for the EE and GS chips and possibly the rdram

 

It's the boot ROM, DSP and mechacon. EEPROM there's no need to physically swap as long you have a copy of it's contents and can transfer it with software.

But before you perform a swap, try to reflow the DSP solders as that might be the fault. GH-004 units have a pad on top of the DSP chip (it doesn't really heat that much to need a thermal pad, mind you) and that crushes it against the mainboard. In the long term connections between the board and the IC pins crack. The circuit board is too thin.

The PS2 ROM need proper communication to the DSP for booting up properly. So if the DSP is malfunctioning you can get all sort of problems, including the console staying into a black screen.

 

Seems plausible, a quick google search for gh 004 pulled up a few motherboard requests and dead system reports, now which chip is the dsp?

 

CXD1869AQ is the DSP. (the 208 pin QFP IC)

archivos.diagramas.mx/otros/PlayStation2-SCPH30000%20Series.PDF <- service manual that regards B(004), B' (005), C (006), C' (007) for USA and PAL regions. At the end of the PDF there's block diagrams for each of the ICs. Apparently this is the unedited version of the PDF (I.E.: complete)

Just mentioning, I've already successfully revived many units reflowing the DSP chip solder.

 

Reflow didn't fix it. Seems though the video out was working after all, just not in component, the eeprom is definitely corrupt I had forgotten about that. One of the last times I started it up it went to the first boot screen like a new console. Component not working and the rocket tray should also be eeprom related. How would I go about fixing the eeprom? Fmcb is out due to
Magicgate being crippled and both title.db and master discs are out due to the drive freak out. What would be lost if I use a retail eprom to get it working. Also where is the chip located.

 

Well, you can connect the small board to a retail GH-004 unit and see if it boots. If it boots you can backup the eeprom with lenschanger.

I believe the only way to repair the eeprom without magic gate is using the RS232 method with the testpoints.

Bad solder joints on the DSP could be how the eeprom got corrupted, actually.

Edit: Swapping out the eeprom will cause the DTL-xxxxx string to change into SCPH-xxxxx at the console version screen. Not really desirable, eh?

 

When it first did the initial setup screen I didn't not check the drive, seems the video out problem is due to the setting being missing, thus defaulting to rgb. That and the tray problem. I have to assume that the entire chip was wiped. I'm thinking put in a retail chip to restore the drive to a functional state then exploit with title.db. Unfortunately I have never gotten lenschanger to boot and I don't know much about how to work with eeprom dumps. Any documentation of the chip's contents?

 

Not really besides my own notes, some notes from Dampro (author from lenschanger) and a truckload of eeprom dumps.

Having your original dump could help preserving at least things like the ilink mac and console serial number. All other stuff can be re-generated at least.

 

Assuming that is actually there, can the serial number be edited with a hex or binary editor? And what is the ilink mac used for besides FireWire functions that aren't very useful

 

ilink mac is generated based on the serial number and board id. algorithm vary depending on console version but it can also be re-generated. But we don't know the formula for the later consoles. I think it could be possible to fully recreate the eeprom of a GH-004 console but it would be cool to see what is in your eeprom, I mean, how it got corrupted.