Iso module: Difference between revisions
Jump to navigation
Jump to search
| Line 12: | Line 12: | ||
! Module !! Usage !! Remarks | ! Module !! Usage !! Remarks | ||
|- | |- | ||
| AacsModule.spu.isoself || theoretically [[Flash#EID3_-_Section_3|EID3]] || | | AacsModule.spu.isoself || theoretically [[Flash#EID3_-_Section_3|EID3]] and [[Flash#FF_Filled_with_OCRL0200_section|OCRL]] || | ||
|- | |- | ||
| aim_spu_module || [[Flash#EID0_-_Section_0|EID0]] (section 0x00 and 0x0A) || | | aim_spu_module || [[Flash#EID0_-_Section_0|EID0]] (section 0x00 and 0x0A) || | ||
Revision as of 05:52, 23 March 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 and OCRL | |
| 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 \dev_flash\pspemu\release\emulator_drm.sprx mself (since FW 3.15). |
| 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 |