Initial Program Loader: Difference between revisions
CelesteBlue (talk | contribs) No edit summary |
|||
| (4 intermediate revisions by 4 users not shown) | |||
| Line 1: | Line 1: | ||
Initial Program Loader, abbreviated as IPL, is a PSP program that runs on boot and loads Kernel. IPL is loaded by [[ | Initial Program Loader, abbreviated as IPL, is a PSP program that runs on boot and loads Kernel. IPL is loaded by [[iplloader]]. IPL can be stored either on the NAND or on a [[Magic Memory Stick]], depending on the iplloader code and if a [[JigKick Battery]] is inserted or not. | ||
On DevKits, the file is embedded after the iplloader, named [[Kbooti.bin]]. | |||
= Tools = | = Tools = | ||
| Line 22: | Line 24: | ||
= Location = | = Location = | ||
Offset 0x40000 in the NAND (or NAND dump without ECC). | |||
= Structure = | = Structure = | ||
| Line 31: | Line 34: | ||
== Decrypted form == | == Decrypted form == | ||
The decrypted IPL is composed of 3 parts: Part1 - the 'loader', Part2 - 'main.bin', and Part3 - the 'payload'. | === Retail === | ||
The decrypted IPL is composed of 3 parts: Part1 - the 'loader', Part2 - 'main.bin', and Part3 - the 'payload', aka 'kbooti_for_ipl'. | |||
Part1 is plaintext MIPS code, Part2 is gzip compressed, and Part3 is again encrypted (from 2.60 onwards, parts 2 & 3 are further encrypted again). | Part1 is plaintext MIPS code, Part2 is gzip compressed, and Part3 is again encrypted (from 2.60 onwards, parts 2 & 3 are further encrypted again). Part3 is what actually loads the kernel modules from flash and begins the kernel boot process. | ||
== Prototype 0.4.0-0.6.0 (23-07-2004 or older) == | === Prototype 0.4.0-0.6.0 (23-07-2004 or older) === | ||
The decrypted IPL only contains the 'payload' | The decrypted IPL only contains the 'payload' | ||
| Line 45: | Line 50: | ||
One of the first things Part1 IPL does is reset the main CPU. | One of the first things Part1 IPL does is reset the main CPU. | ||
After reset the | After reset the iplloader mask ROM device is no longer mapped to memory at all (the 0x1FC00000 address range is then remapped to the 4KB RAM mentioned above to be used for the ME reset vector). This is why the iplloader is no longer accessible once the IPL has booted. | ||
Part1 IPL does some very basic hardware inits and decompresses the gzipped Part2 IPL (main.bin) to address 0x04000000 (still in EDRAM). | Part1 IPL does some very basic hardware inits and decompresses the gzipped Part2 IPL (main.bin) to address 0x04000000 (still in EDRAM). | ||
| Line 63: | Line 68: | ||
== Part3 IPL (the payload) == | == Part3 IPL (the payload) == | ||
Part 3 is really the IPL equivalent of reboot.bin. Since part2 kindly initialized main DDR memory, part3 is the first to actually run inside DDR. On most modern firmwares this will load to 0x88600000. | |||
After some initial clean up of the co-processsors, this begins by loading /kd/sysmem.prx and /kd/loadcore.prx from flash0. Part3 contains a kernel version of the main prx decrypt routines as well as the keys for decrypting the prx tags for this version of the kernel. This is very similar to what you would find in mesg_led.prx. | |||
At the conclusion of the load, part3 sets a series of useful function pointers for loadcore.prx and transfers control to loadcore for the rest of the kernel load process. | |||
= Custom IPL = | = Custom IPL = | ||
It is possible to load a custom IPL by either: | It is possible to load a custom IPL by either: | ||
* exploiting | * exploiting iplloader to run unsigned IPL (never done) | ||
* crafting a fake IPL using bruteforce (since 2007 thanks to [[Prometheus Project]]) | * crafting a fake IPL using bruteforce (since 2007 thanks to [[Prometheus Project]]) | ||
* crafting a valid encrypted and signed IPL using recovered keys (since 2018 thanks to PS3 hacks and mathieulh) | * crafting a valid encrypted and signed IPL using recovered keys (since 2018 thanks to PS3 hacks and mathieulh) | ||
See [[ | See [[iplloader]] and [[Pandora]]. | ||
= See also = | = See also = | ||
Latest revision as of 21:28, 17 June 2024
Initial Program Loader, abbreviated as IPL, is a PSP program that runs on boot and loads Kernel. IPL is loaded by iplloader. IPL can be stored either on the NAND or on a Magic Memory Stick, depending on the iplloader code and if a JigKick Battery is inserted or not.
On DevKits, the file is embedded after the iplloader, named Kbooti.bin.
Tools[edit | edit source]
Dumper[edit | edit source]
NAND-IPL-DUMPER by KanadeEngel
Decrypter / Encrypter[edit | edit source]
IPL SDK[edit | edit source]
Bruteforce forger[edit | edit source]
Location[edit | edit source]
Offset 0x40000 in the NAND (or NAND dump without ECC).
Structure[edit | edit source]
Encrypted form[edit | edit source]
IPL is divided into chunks of 0x1000 bytes, the size of the buffer used at address 0xBFD00000 where they are decrypted. The IPL blocks are standard KIRK cmd 1 blocks and passed directly to KIRK Crypto Engine for decryption.
Decrypted form[edit | edit source]
Retail[edit | edit source]
The decrypted IPL is composed of 3 parts: Part1 - the 'loader', Part2 - 'main.bin', and Part3 - the 'payload', aka 'kbooti_for_ipl'.
Part1 is plaintext MIPS code, Part2 is gzip compressed, and Part3 is again encrypted (from 2.60 onwards, parts 2 & 3 are further encrypted again). Part3 is what actually loads the kernel modules from flash and begins the kernel boot process.
Prototype 0.4.0-0.6.0 (23-07-2004 or older)[edit | edit source]
The decrypted IPL only contains the 'payload'
IPL Boot Sequence[edit | edit source]
Part1 IPL (the loader)[edit | edit source]
One of the first things Part1 IPL does is reset the main CPU.
After reset the iplloader mask ROM device is no longer mapped to memory at all (the 0x1FC00000 address range is then remapped to the 4KB RAM mentioned above to be used for the ME reset vector). This is why the iplloader is no longer accessible once the IPL has booted.
Part1 IPL does some very basic hardware inits and decompresses the gzipped Part2 IPL (main.bin) to address 0x04000000 (still in EDRAM).
Part1 IPL then jumps to the entry address of main.bin (0x04000000) to initialize the hardware.
Part2 IPL (main.bin)[edit | edit source]
Part2 IPL (main.bin) is responsible for initializing the PSP hardware.
It has copies of its own driver modules similar to the drivers found in the firmware (including: sceNAND_Driver, sceDDR_Driver, sceIdStorage_Service, sceSYSREG_Driver, sceSYSCON_Driver, sceGPIO_Driver, sceClockgen_Driver, & sceI2C_Driver). Some of the initialisation of the hardware depends on data stored in IDStorage leaves (for example leaves 4, 5, 6). Note this is where TA-082 / TA-086 motherboards 'brick' on 1.50 firmware. The clockgen hardware was changed on TA-082 / TA-086 motherboards so the functions used to initialize it does not recognise the new hardware. And because part of the initialization depends on data stored in leaf 5, simply by invalidating leaf 5 (by corrupting the header), the initialization is skipped allowing the firmware to continue to boot. See IdRepair by codes02.
After initializing the hardware (including the DDR RAM), Part2 IPL decrypts Part3 IPL (the payload) and loads it to address 0x08400000 (which is located in normal DDR RAM now that it has been initialised).
It then jumps to the entry address of the Part3 IPL (0x08400000) to boot the firmware.
Part3 IPL (the payload)[edit | edit source]
Part 3 is really the IPL equivalent of reboot.bin. Since part2 kindly initialized main DDR memory, part3 is the first to actually run inside DDR. On most modern firmwares this will load to 0x88600000.
After some initial clean up of the co-processsors, this begins by loading /kd/sysmem.prx and /kd/loadcore.prx from flash0. Part3 contains a kernel version of the main prx decrypt routines as well as the keys for decrypting the prx tags for this version of the kernel. This is very similar to what you would find in mesg_led.prx.
At the conclusion of the load, part3 sets a series of useful function pointers for loadcore.prx and transfers control to loadcore for the rest of the kernel load process.
Custom IPL[edit | edit source]
It is possible to load a custom IPL by either:
- exploiting iplloader to run unsigned IPL (never done)
- crafting a fake IPL using bruteforce (since 2007 thanks to Prometheus Project)
- crafting a valid encrypted and signed IPL using recovered keys (since 2018 thanks to PS3 hacks and mathieulh)