Iso module: Difference between revisions

From PS3 Developer wiki
Jump to navigation Jump to search
mNo edit summary
Line 37: Line 37:
|-
|-
| sc_iso_factory.self || syscon || [[http://www.ps3devwiki.com/index.php?title=Playstation_Update_Package_%28PUP%29#2.43_RETAIL.2FCEX_JIG| 2.43 JIG PUP]]
| sc_iso_factory.self || syscon || [[http://www.ps3devwiki.com/index.php?title=Playstation_Update_Package_%28PUP%29#2.43_RETAIL.2FCEX_JIG| 2.43 JIG PUP]]
|-
| spu_handler.isoself || PSP || self inside emulator_drm.sprx mself.
|-
|-
| spu_mode_auth.self ||  || [[http://www.ps3devwiki.com/index.php?title=Playstation_Update_Package_%28PUP%29#2.43_RETAIL.2FCEX_JIG| 2.43 JIG PUP]]
| spu_mode_auth.self ||  || [[http://www.ps3devwiki.com/index.php?title=Playstation_Update_Package_%28PUP%29#2.43_RETAIL.2FCEX_JIG| 2.43 JIG PUP]]

Revision as of 18:00, 17 February 2012

Explaination

Isolated modules are used for de-/encryption, rehashing etc.

Commonly found in CoreOS, dev_flash, embedded sony selfs and service packages like Remarry Bluray Drive.

They are SPU .self binaries which can be called whenever needed: e.g. decrypting and hashcheck EID0 for Target ID inside IDPS when called upon by lv1 (HyperVisor) to set up restrictions for Retail/CEX or Debug/DEX etc.

Known isolated modules

Module Usage Remarks
AacsModule.spu.isoself theoretically EID3
aim_spu_module EID0 (section 0x00 and 0x0A)
CprmModule.spu.isoself theoretically EID3
CssModule.spu.isoself
fdm_spu_module EID2, Remarry Bluray Drive [2.43 JIG PUP]
manu_info_spu_module.self
mc_iso_spu_module PS2
me_iso_for_ps2emu.self PS2
me_iso_spu_module PS2
SacModule.spu.isoself
sb_iso_spu_module southbridge
sc_iso syscon
sc_iso_factory.self syscon [2.43 JIG PUP]
spu_handler.isoself PSP self inside emulator_drm.sprx mself.
spu_mode_auth.self [2.43 JIG PUP]
spu_pkg_rvk_verifier.self
spu_token_processor.self systemtokens, QA Flagging
spu_utoken_processor.self usertokens
ss_sc_init.self [2.43 JIG PUP]
sv_iso_for_ps2emu.self PS2
sv_iso_spu_module EID4, PS2, bluray