This is a fork of this project: https://sites.google.com/view/ysai187/home/projects/ps2ident

PlayStation 2 Identification tool (PS2Ident)

v0.850

Introduction

PS2Ident is an identification tool that allows dumps of a PlayStation 2 console's ROM chips and MECHACON NVRAM to be made. It will also gather data from the console, for research purposes.

It has the following features:

• Dumps ROM chips (BOOT and DVD ROM) as a whole, not according to their contents (rom0, rom1, rom2 and erom)
• Displays the actual addresses for DEV1 (rom1, rom2 and erom) that are set by the ROM filesystem drivers.
• Coloured user interface that is easy to use.
• Supports dumping to memory cards and USB mass storage devices.
• Supports multi-languages, which include the 8 supported languages by the PS2
• Gathers data of all known parts of the PS2.
• Attempts to automatically match the chip/part name with the version number of the part.

Note: on some DTL-H***** consoles it can fail to retreive MECHACON chip version. Note: some values are retreived incorrectly from PS3 BC consoles. Note: it can fail on PS3 semi-BC, PS3 non-BC and PS4 in PS2 emulation mode.

Its database, which contains the parts and mainboard data, is managed and updated with the PlayStation 2 Ident DataBase Management System (PS2IDBMS) tool. It wasn't possible to get a complete list of all PlayStation 2 models in existence. With PS2IDBMS, a spreadsheet containing all recorded models can be generated automatically.

How to use this software:

Extract the whole archive (do not delete any files or folders) onto a location on a supported device. The only supported devices are the Memory Card and USB mass storage device.

After dumping recheck if there is some "Missing" values in *_specs.txt If you see Missing value after some chip name you can make a photo of each chip that is marked as Missing. If you see Missing (sticker) you should provide photo of your sticker.

When the console's mainboard cannot be identified, the mainboard model will be "Missing". Open your console, and take note of the mainboard model number. A database record file (*_database.bin) will be generated when a dump is made. No personal information is recorded in database file. When making a submission, please provide the database record file, sticker photo and any valuable information about console.

When recording down the model of the MECHACON chip, please take note that the model number should include its firmware version as well (e.g. CXP103049-401GG instead of just CXP1013049).

Please specify the chassis model, the true model number (i.e. SCPH-39006a) and the colour of the console (if not the standard black version).

If possible, please help to complete the chip ID list as well, for any part that is not identified ("Missing") or is incorrectly identified. When doing so, please provide the full model of the part, especially for the MECHACON chip (e.g. CXP103049-401GG).

As for the chassis and EMCS ID (For Dragon-series units): At the lower right-hand corner of the product information sticker that is either on the bottom or back of the unit, there will be something like "H FOXC". In this example, the letter 'H' is the chassis model, while "FOXC" stands for FOXConn (the EMCS that made the console).

Notes:

• Sometimes, Sony makes hardware revisions without changing the chip implementation numbers as well, hence why chip identification may be inaccurate. The chip and version IDs are, however, accurate since they are taken directly from the hardware.
• Slimline consoles that had the SSBUS I/F Controllers integrated into the IOP will report them as version 0x31.
• Due to some SSBUS I/F controllers reporting the same version number (0x31), those will be all generalized and reported as "CXD9611". All of them are supposed to be fully compatible anyway.

Mainboards are uniquely identified by:

ROMVER string                   - ROM version string
Model name                      - The "name" of the console's model.
EE revision
FPU revision                    - Revision of the EE chip's FPU.
IOP revision
GS revision
MECHACON revision and region    - Revision and MagicGate region of the MECHACON
SPU2 revision                   - Revision of the sound processor.
SSBUS I/F Controller revision
Model ID                        - Uniquely identifies the console's model. Even more accurately than the model name.
Console model ID                - Another (2-byte) version of the model ID. Obtained from the i.Link ID data.
EMCS ID                         - Uniquely identifies the Engineering, Manufacturing and Customer Services (EMCS) system that made the console.
M Renewal Date                  - What this represents is unclear. It's something related to the MECHACON (date of firmware build or EEPROM settings update?)
ADD0x010                        - An ID that is used by the SONY service tools to identify major revisions (which historically existed at word offset 0x10).
BOOT + DVD ROM Checksum

If your console is not recognized, its mainboard model will appear as "Missing". While it is true that Sony consoles might be physically similar across releases from different territories, I've decided to treat each region's release as being different because I would also want to have a complete list of existing PlayStation 2 models. With such data it is possible to determine what models Sony has released in every terrirory, and at which series did they start at.

Glossary/terms:

• EE - The Emotion Engine, which is a MIPS R5900. The "main CPU" of the PlayStation 2.
• FPU - The VU0, which also acts as the 2nd coprocessor to the EE.
• IOP - The I/O processor, which is a MIPS R3000A. The "sub-CPU" of the PlayStation 2. Although insignificant in power, it's actually in control of every part of the PS2, and provides access to the peripherals from the EE.
• GS - The Graphics Synthesizer (aka the "GPU" of the PS2).
• SPU2 - The Sound Processor.
• SSBUS I/F - The SS-BUS InterFace (I/F) Controller, provides an interface to the SS-BUS from the DEV9 expansion device. Also known as a "SSBUS buffer" on consoles sporting an expansion-bay. Connected to the PS2 as DEV9.
• MECHACON - The drive MECHAnics CONtroller. Connected to the PS2 as DEV5.
• DVP - I'm not sure about this one, but it's a very powerful and smart processor that is connected directly to the MECHACON.
• Boot ROM - The ROM chip containing the default IOP modules, the OSDSYS program, PlayStation driver and the self-test facility (On the SCPH-18000 and up). Connected to the PS2 as DEV2.
• DVD ROM - The ROM chip containing the DVD player, and the Chinese font on Chinese PlayStation 2 consoles. Newer consoles may have a single chip instead of a separate boot and DVD ROM chips. The SCPH-10000 and SCPH-15000, and all TEST, TOOL and PSX (DVR unit) units do not have a DVD ROM chip installed. Connected to the PS2 as DEV1. NVRAM/EEPROM - The Non-Volatile Memory storage that the MECHACON/DVP has, for storing settings (system, RTC and CD/DVD drive).
• SPEED - The expansion device that gets connected to the DEV9 expansion interface. May provide Ethernet support, a UART (for a dial-up modem), a DVRP, flash storage (For storing boot files), and an ATA interface.
• SMAP - The PlayStation 2 Ethernet interface. Connected to the SPEED device. Ethernet PHY - The PHYceiver device that is connected to the SMAP interface. The earliest models included a National Semiconductor DP83846A that has auto-negotiation issues with Gigabit Ethernet. Later models had a ST Microelectronics, while late slim PS2s come with a Broadcom.
• DVRP - Only found on PSX (DVR unit) consoles, the DVR Processor is a Fujitsu MB91302A that is connected to the SPEED device. It seems to be emulating the PS2's standard ATA interface and provides the DVR functionality. Contains its own firmware.
• i.Link and USB interfaces - The Firewire/IEEE1394/i.Link interface and USB interfaces. Their controllers are built into the IOP. Consoles that don't have an i.Link port still have the i.Link controller, but just have no physical connections to the outside world.
• AIF - On a DTL-T10000(H), the CXD9566R is connected through the AIF. The AIF also provides a RTC and IDE controller. MPU - See MRP.
• MRP (BoardInf) - The MRP is the interface between the PS2 and PC sides of a DTL-T10000(H). All DTL-T10000(H) units have a MPU 4.0 board as the MRP.
• EMCS ID - Contains the part of the IEEE1394 EUI-64 address that uniquely identifies the console, the model ID and EMCS ID.
• i.Link ID - Uniquely identifies the Engineering, Manufacturing and Customer Services (EMCS) system that made the console.
• Model ID - Uniquely identifies the console's model. Even more accurately than the model name.
• Console ID - Contains the EMCS ID, (another version of) model ID and serial number.
• M Renewal Date - What this represents is unclear. It's something related to the MECHACON (date of firmware build or EEPROM settings update?)
• ADD0x010 - An ID that is used by the SONY service tools to identify major revisions. Originally at word 0x010 of the EEPROM, it was moved to word 0x01 for the Dragon models. It does not always correspond with the chassis models (i.e. C and D-chassis have the same ID). It can also identify the loadout of the console, like its CEX/DEX status and the OP block installed (i.e. SANYO or SONY).
• PS1DRV Version - The version number of the PlayStation driver. The earliest ROMs do not have PS1VER in ROM. For Japan, only the SCPH-10000 and SCPH-15000 lack this file. "1.01" is hardcoded. For other territories (should be only the earliest SCPH-30001), "1.10" is hardcoded. The SCPH-75000 and later have a universal PS1DRV module, while earlier versions were tailored for the region of PS2 (Japan, USA, Europe, Asia or China).
• DVD Player Version The version number of the built-in DVD player, if applicable. Note: Slimline consoles that had the SSBUS I/F Controller integrated into the IOP will report their SSBUS I/F c