PlayStation 2 developer @sp193 is back with a new update to the PS2 Identification Tool or better wise known as simply PS2Ident, This update pushes the utility to version 0.823 and in this update the developer is supporting the latest PS2SDK revisions, button hints, and improved model detection has been added. View complete changelog and details about his tool in the tabs below:
- About: PS2Ident
- Latest Changelog
- Date Recorded
- Making Submissions
- Glossary / Ps2 Terms
- Known limitations / bugs
- Supported Languages
This PlayStation 2 Utility by developer SP193 is an identification tool that allows a user to dump the PS2 Console ROM chip 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.823:
- Model identification now factors in the CRC16 of the ROMs.
- Added a field for the contributor's name.
- Updated to support the latest PS2SDK revision.
- Added button hints.
Data recorded : If the database has your console's data in it, PS2Ident will attempt to determine its mainboard model based on:
If your console is not recognized, its mainboard model will appear as "unknown". 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.
ROMVER string ROM version string Model name The "name" of the console's model. EE revision Revision of the EE chip. FPU revision Revision of the EE chip's FPU. IOP revision Revision of the IOP chip. GS revision Revision of the GS chip. MECHACON revision and region Revision and MagicGate region of the MECHACON SPU2 revision Revision of the sound processor. SSBUS I/F revision Revision of the SS-BUS I/F Controller. 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.
How to submit new model data, starting from this release:
Please understand that the database record file alone is useless to me, since I need the mainboard model name to update the database with PS2IDBMS.
- If your console model is not recognized, its mainboard will appear as "unknown" and a new database record file in this naming convention will be generated among the dumped files: __database.bin (e.g. SCPH-10000_0500044_database.bin).
- Open your console, and take note of the mainboard model number. Take note of the models of all chips that were unrecognized by PS2Ident, so that we can get an updated chip model list for all components.
- Submit this file to me, along with the mainboard model and other missing chip models via e-mail.
- 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).
The model database file will be updated every week, or whenever I can commit to do so.
If your model is already recognized, the database record file will not be generated.
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). Please contribute this information if necessary.
Glossary/terms: 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).
- Chip and mainboard names/numbers are very limited. Please help by contributing data!
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.822 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.
PS2 PS2Indent - A PS2 model detection Tool by SP193
By STLcardsWS on May 22, 2016 at 3:36 PM
BGFTP v1.0 (by GrapheneCt): Background FTP server for transfering file to your VitaDeveloper GrapheneCt has released BGFTP, a new FTP server that works in the background. It does not matter if your in-game or sleep mode or hanging around the Live Area, The FTP transfers are always working while the developer says this will not impact any performance of the running task, but does add a warning that transfer can be slowed down since they are running on Reserved System Cores and will be knocked to low priority on those reserves, but nonetheless a great way to transfer files from your PC (or other devices servicing as a FTP server) to either your homebrew enabled PS Vita or the PlayStation TV (aka vita tv)..Continue reading
The Power Supply (Vol. 02) - Our Guest Today: "PS4 Developer @m0rph3us1987"With the very first introduction of our new Series of Developer Interviews - as known by "The Power Supply" - you were already allowed to dabble a little bit with Volume 01 of the series, where you got a deep look into the work from well-known Developer @deank he did for this scene. While he worked mainly for the PS3 Community, we thought it would be only fair to bring you a PS4 Developer with Volume 02 of this Interview Series today. This Developer maybe don't have the same long reputation as deank have since he began to tinker with the PS4 as his very first Sony Console. But this doesn't mean that he isn't worth to ask some questions. We covered his Achievements already in the past here in this Forum, especially when we provided you our yearly Overview about the CCC Events held in Germany. In fact, you should be familiar with him and his Lecture he held back at 35C3. So please give an warm welcome to m0rph3us1987, while in his Interview, we will talk about his Lecture he held, we will learn how he sees the current situation in "PS4 Development and Hacking" and we will get an deep insight how he began to learn writing some code in his young age. So allow us to introduce him further.Continue reading
RetroArch (PS4) R3 Released: New libretro Cores Added (Dramcaset / Jaguar / ScummVM /) + Source CodeFollowing the initial release of R1 and the followup of R2, developer @OsirisX has just released R3 for the PS4 Port of RetroArch with new core being added, various bug fixes to go along and also a release of the promised source code is included as well.. The new update provides ps4 support for Flycast (Sega Dreamcast), Bettle PSX, Virtual Jaguar, ScummVM, Stella-2014 (Atari 2600), Vectrex and SameBoy are the new cores included (emulation like dreamcast is experimental and many games have speed issues) in this release This update is based on RetroArch v1.8.4 and the Core Updater has been enabled, multi-controller Support has been added (up to 4 can be used), previous R1/R2 only one controller was supported. Also some cores that need have added support for keyboard and mouse controls. This port has evolve quite nicely and should be even better with now the source code release and likely will becomes part of the official release as this is still considered an "unofficial" port, but likely to become the official port.
Also the developer has created a Core Updater, which provides another method to update the cores. It help keeps the main pkg lite and you can also download indvidual cores via RetroArch itself as that bug of downloading cores has been fixed. See all the latest details below pertaining to the R3 release.Continue reading
Share This Page
- henkaku homebrew
- playstation 2
- playstation 2 resources
- playstation portable
- playstation portable cfw
- playstation portable resources
- playstation 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: