Iso module

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

sc_iso.self

sc_iso.self is used by the system to handle communications to/from syscon. Once debug printing is enabled after you load it, you can see some of the internal workings including error codes for when you are trying to use the module on your own.

Error Value	Meaning
0x81010101	sc_iso command failed
0x81010106	Bad input command value
0x81010B07	Bad parameter for Get SC Status (0xE)
0x81011e07	Bad parameter for encrypt (0x1) / decrypt (0x2)