mirror of https://github.com/ran-j/PS2Recomp.git synced 2026-09-26 08:51:05 -04:00

Files

T

Vova Vovchok 765cbcca0f Integrate ps2xStudio and improve elf_analyzer callback detection (#83 )

* Integrate ps2xStudio and improve elf_analyzer callback detection

* Update CMakeLists.txt for ImGui libraries

* CMakeLists Fixes Again

Updated dependencies and improved comments for clarity.

* Again CMakeLists. Now it definitely works

* again CMakeLists

* Update CMakeLists.txt ps2xStudio & ps2xTest

* Update CMakeLists.txt

* Update CMakeLists.txt

* Update StudioState.hpp

* Update CMakeLists.txt

2026-03-01 16:41:33 -03:00

include/ps2recomp

Integrate ps2xStudio and improve elf_analyzer callback detection (#83 )

2026-03-01 16:41:33 -03:00

src

Integrate ps2xStudio and improve elf_analyzer callback detection (#83 )

2026-03-01 16:41:33 -03:00

CMakeLists.txt

feat: refactor analyzer to not realy only on debug symbols (#53 )

2026-02-13 15:02:34 -03:00

Readme.md

Feature/better analyzer v1 (#39 )

2026-02-02 01:49:51 -03:00

Readme.md

PS2 ELF Analyzer Tool

The PS2 ELF Analyzer Tool automates the creation of TOML configuration files for the PS2Recomp static recompiler. It identifies function boundaries, library stubs, and problematic instructions.

Analysis Paths

The analyzer supports three distinct paths for discovering code within a PS2 binary:

1. DWARF Debug Information

If the ELF was compiled with debug symbols (-g), the analyzer uses libdwarf to extract perfect function names and exact start/end addresses. This is common in homebrew or early development builds.

2. Native Heuristic Scanner (Retail/Stripped)

For commercial games where symbols are stripped, the analyzer uses a "JAL Scanner":

It scans executable sections for JAL (Jump and Link) instructions.
It infers function start points based on jump targets.
It generates names like sub_XXXXXXXX.

3. Ghidra Integration (For Complex Games)

For the highest accuracy in stripped games, you can use Ghidra's superior analysis engine:

Use the provided script: ps2xRecomp/tools/ghidra/ExportPS2Functions.py or .java.
Run it in Ghidra to export a CSV map of all functions.
Add the CSV path to your TOML: ghidra_output = "path/to/map.csv".
The recompiler will prioritize Ghidra's boundaries over its own heuristics.

Key Features

Analyzes PS2 ELF binaries to extract symbols, functions, and structure
Identifies common library functions that should be stubbed
Flags system functions that should be skipped during recompilation
Detects potential instruction patterns that may need patching
Generates a ready-to-use TOML configuration file for PS2Recomp

Using the Analyzer

ps2_analyzer <input_elf> <output_toml>

Parameters:

input_elf: Path to the PS2 ELF file.
output_toml: Path where the generated TOML configuration will be saved.

Example Workflow

Run the analyzer on your game: ps2_analyzer game.elf config.toml
(Optional) Open game.elf in Ghidra, run the export script, and update config.toml with the CSV path.
Run the recompiler: ps2recomp config.toml

Generated Configuration

The tool creates a TOML file with the following sections:

[general]: Paths to ELF and Ghidra maps.
stubs: List of library functions to be replaced by C++ stubs.
skip: List of functions to be ignored (entry points, initialization).
[patches]: Individual instructions that need to be replaced (SYSCALLs, COP0, etc.).

Limitations

Heuristics may not catch all special cases in highly optimized code.
Self-modifying code is flagged but requires manual review.
Indirect jumps (jump tables) are detected but complex ones might need manual TOML entries.

For more details on the recompilation process, see the Main README.