PlayStation 2 developer @sp193 did not just provide a recent update to the PS2 HDD Checker but also the PlayStation 2 Identification Tool (PS2Ident). This app works by dumping the PS2 ROM chips and MECHACON NVRAM and takes that data to identify different aspects about your console. Another great tool and update from the PS2 Community that is still very much active in 2017.
PlayStation 2 identification tool
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:
Note: Chip and mainboard identification is currently very incomplete and inaccurate, due to a lack of data. 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.
- Dumps ROM chips (BOOT and DVD ROM) as a whole, not according to their contents (rom0, rom1, rom2 and erom)
- 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.
- Supports all PlayStation 2 consoles, including the SCPH-10000 and SCPH-15000, and the PSX (DVR unit).
Its database, which contains the parts and mainboard data, is managed and updated with the PlayStation 2 Ident DataBase Management System (PS2IDBMS) tool.
I made such a change because 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.
Not to mention that the whole PS2Ident tool would have to be recompiled, whenever model data was added.
Changelog for v0.825:
Changelog for PS2IDBMS v1.05:
- Updated to have the fixed USBHDFSD module.
- Replaced the font-drawing system with a new design.
- Updated French localization.
- Fixed coordinate overflow in font-drawing.
- Rebuilt to not have the full kernel OSD patch (PS2SDK update).
(prevents users of SCPH-10000/SCPH-15000 from being blocked from changing the language setting)
- Added the "/modded" sub-option, so that modded consoles can be flagged as such.
Known parts of a PlayStation 2 console
Note: Slimline consoles that had the SSBUS I/F Controller integrated into the IOP will report their SSBUS I/F controllers as version 0x31 as well. Due to some controllers reporting the same version number (0x31), they will be all identified as a "CXD9611" since they are supposed to be fully compatible anyway.
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. Also known as DEV4. 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. MECHACON The drive MECHAnics CONtroller. DVP I'm not sure about this one, but it's a very powerful and smart processor that is connected directly to the MECHACON. Version data reported by the MECHACON includes data from the DVP as well. 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). 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. Also known 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. 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 DEV9 interface 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).
For more information on supported languages and how support for languages can be completed, click here. A template for translating this software is provided in the downloads section of this page.
Supported languages and their translation status
* Not updated for v0.824 and newer.
Language Status Japanese* Unassigned English (completed) Completed and built-in. French Translated by ShaolinAssassin. Spanish (completed) Translated by ElPatas German (completed) Translated by Delta_force. Italian* Translated by master991. Dutch* Translated by someone who wishes to remain anonymous. Portuguese (completed) Translated by Gillbert.
Download & Source (additional details):
Official Project Page
PS2 PS2ident v0.825 - New Improvements / Fixes by SP193
By STLcardsWS on Jan 19, 2017 at 11:31 PM
Developer @TheoryWrong talks about "OrbisSWU" - An interesting approach for Downgrading your PS4 ???Remember back in the old days when instead of installing an Kernel/Web-Exploit like nowadays, you asked "how I can install an Custom Firmware (CFW)" or something like "how I can Downgrade my Console"? Of course, todays attempts aren't that bad since you get a similar functionality in terms of running Homebrew for instance, but not quite for 100% compared to the old days. Especially not when we talk about the possibilities of modifying a PlayStation 3 compared to the PlayStation 4 today. In fact, there was a time where everyone wanted to "Downgrade" his/her PS3 from an higher System Firmware (OFW) to bring the functionality of Homebrew back to their PS3. Or can you remember when your Blu-ray Drive wasn't working anymore due to its age or because of an failed Downgrade process so everytime when you wanted to install a newer, higher CFW, it failed with displaying an error message and you had to install those "noBD" CFWs? While the latter one was already achieved for older Firmwares below <4.75 in the past, it will be still interesting to achieve both a Downgrading possibility and a "noBD" support for higher Firmwares on a PS4 as well. The good thing is, well-known Developer @TheoryWrong asked the same question to himself. And it gets even better; he is ready to show his progress so far So lets have a look at it. Continue reading
RetroArch (PS2 - v1.8.8) - Utilizing New PS2 SDK / Toolchain adds performance upgradesThere has been some great work being done in the PS2 community, First off i would like to give two PS2 developer a big shoutout and some recognition (I failed in doing so in my previous coverage back in April, thanks to @TnA for pointing that out ) with work done on the PS2 SDK / Toolchain as PS2 developer's @uyjulian and @Maximus32 have been working and progressing the toolchain and SDK for sometime as you can read about some of that progress and follow some of the development in this thread.
Developer @fjtrujy has also put in some great work to the project and has utilized and adopted the improved toolchain for the RetroArch PS2 port and can be seen with the release of RetroArch v1.8.8 and its been a good descion for the homebrew (multi-system emulator) as it has been getting significant performance increases, right now we only have one new core and its a classic from the 80's (theodore libretro core), but the existing cores have an incredible performance boost for instance the QuickNESContinue reading
The latest with RetroArch (PS4-Unofficial): PSP emulation in next update along with OOSDK conversionSince the release of unofficial version of RetroArch (PS4-R3) from developer @OsirisX and subsequently the source code release that came along with it, we surprisingly have not seen or heard much in regards to an official team adopting this release to make it official. We can however more then likely gather some clues and "connect some dots" from the OG port that started it all on the PS3 and has since been pulled in recent and replace with the still in development Psl1ght (Open Source) SDK port rather then the previous versions that used the official sony sdk. With the Open Orbis SDK (OoSDK) release recently for the PS4, this seems to be the approach for the PS4 to become official as well,
Recently developer OsirisX has stated that he wants to convert the project's to OoSDK before another release is made, but the developer has already made some progress and teases a bit of that progress in the video below showing a new core being supported in PPSSPP. When asked about potential PSP or PS2 Support the developer stated the plan is to include PSP support (via PPSSPP core) in the next release. The teaser video show's GTA Vice City Stories being quite playable (video shows FPS counter) so if this game looks this well, many others should play very well also. There is still alot of great development going on with this port by developer OsirisX. .Continue reading
Share This Page
- henkaku homebrew
- playstation 2
- playstation 2 resources
- playstation portable
- playstation portable cfw
- playstation portable resources
- playstation tv
- ps tv
- ps vita
- ps2 resources
- ps3 cfw
- ps3 homebrew
- ps4 homebrew
- psp cfw
- psp resources
- pstv homebrew
- vita homebrew
- webman mod
- User Record:
- Latest Member: