That's true for all units manufacturated before 2006. Since the 7700x series Sony started to ship a single version of bios and mechanics controller which contains all regions. The region is then set at factory by writing a value on the mechacon chip EEPROM (which is internal to the said chip and has tight security). This is also why around that time most modchips stoped working with the newer PS2s and needed their CPLD microcodes to be updated.Originally Posted by SilverBull
Or if there's any, even (DVD-R/CD-R). I couldn't have it explained better :)Originally Posted by SilverBull
Like I said on the previous post, faulty EE RAM can (and will on most cases) cause the RDRAM init to fail or even if the PS2 get to boot, cause random crashes, garbage on the screen and bad sound.Originally Posted by SilverBull
In the case of PS2 units that can't init the GS chip (TV stays on it's blue screen) or black screen with no boot the only diagnosis one can do is hook the EE SIO cable and set up it properly then wait for the DECI2 error messages. If RDRAM is faulty you will see something like this:
# Initialize memory (rev:3.17, ctm:393Mhz, cpuclk:295Mhz )
# RDRAM INIT returned error: -1
The error code varies depending on the kind of error... And sadly I don't know what each value means. And the unit hangs at that.
On early units (pre 7700x), because the Mechacon is completely independent from the IOP, it will work even if the ROM bios chip is removed, which prevents the IOP from booting for obvious reasons. I don't know how it is for the current production batches though.Originally Posted by SilverBull
For the IOP, the mechacon is seen as part of the DVD drive DSP registers as it's the DVD DSP chip that interfaces with the IOP. If the DVD drive hardware was faulty, you would get a normal boot log on EE SIO but still a black screen and the disc would not spin, I believe.
Hardware vs software behavior is such a wonderful topic for discussion, isn't it ? :thumbsup: