Talk:Eboot.PBP

From PS3 Developer wiki
Revision as of 02:18, 11 December 2012 by Euss (talk | contribs) (note: make sure to set contrasting foreground colour when selecting a background colour)
Jump to navigation Jump to search

Structure folder/files around EBOOT.PBP

Dev_HDD0/game/NPXX.12345/

|-ICON0.PNG (ICON on PS3 XMB)
|
|-PARAM.SFO (SFO used by PS3: CATEGORY_For_HDD_contents)
|
|-PIC0.PNG
|
|-PIC1.PNG
|
|-PIC2.PNG
|
|-PS3LOGO.DAT 
|
|- USRDIR:
      |
      |-CONTENT (dir): (this folder is sent when using export)
      |     |
      |     |-DOCUMENT.DAT (software manual)
      |     |-EBOOT.PBP (more infos on main page)---SFO inside used by PSP
      |     |-PBOOT.PBP (udpate game. SFO category is PG, used with main SFO as PP)      
      |     |-KEYS.BIN (see above)
      |     |-other possible files related to the game when it s update PBOOT.PBP
      |
      |
      |- SAVEDATA (dir):about minis/ ps1 classic save  and Memory card adapter
      |     | 
      |     |-ICON0.PNG   (used for PSP save data)
      |     |-PARAM.SFO   (Category: MS, used for PSP save data)
      |     |-SCEVMC0.VMP (memory card save in PSP format for slot 1)
      |     |-SCEVMC1.VMP (memory card save in PSP format for slot 2)
      |     |-CONFIG.BIN  (probably generated by the PSP)
      |
      |-CONFIG (generated after first boot)
      |
      |-ISO.BIN.EDAT: Iso.bin.edat (1Ko file when update PBOOT.PBP) see also EDAT files
      |    
      |-MINIS.EDAT (used on MINIS game)
      |
      |-MINIS2.EDAT (used on PSP remaster)
      |
      |-load_tmp: (dir only on MINIS after first boot?) 
      |      | 
      |      |-ICON0.PNG
      |      |-PARAM.SFO (Category: MS)
      |      |-PIC1.PNG
      |      |-SECURE.BIN
      |      |-SND0.AT3
      |
      |-save.tmp (empty dir only on MINIS after first save?)



(Might not be complete structure tree/)

About NPDRM and PSP

Files related to EBOOT.PBP

DOCUMENT.DAT

Software manual of games (minis, PSP remaster and ps1 classic).

By pressing home button during the game, ICON of software manual will appear near the game icon to of the ps3 (as option when it s PS1 classic)

Can be replaced by other DOCUMENT.DAT of others same game category (Minis and PSP remaster can be interchanged).

DOCUMENT.DAT on PS3

  • PARAM.SFO:
 for DG game:  The icon of software game can appear on PS3 games but 
 not loading the manual.
(edited SFO category as MN instead, the utility icon don t appear with HG)

DOCUMENT.DAT on PSP

3 different version supported? ( ps1 classic-MINIS-old format used on homebrew) Can be loaded from psp XMB (if it is from MINIS, not from PS1 classic) without having to boot the game or even a working game.

Create your homebrew manual or walktrough by using PSP DocMaker GUI:

( http://forums.qj.net/psp-development-forum/88463-release-update-psp-docmaker-gui.html / http://www.mediafire.com/?d2mobmwlrlw )

Others: Max 100 pages as display?

DOCUMENT.DAT on PSVITA

See game manual in png format

CONFIG

Infos about PS1 Emulation

Size:60 bytes, string in ASCII: "PS1EmuConfigFile", "disc_no"

Generated/overwrited at each boot of the game, configure the PS1 emulator for : ?

KEYS.BIN

16 bytes.

If you have this file, you can put it into the folder CONTENT to make your PS1 classic game working after being exported to the PSP (with CFW or LCFW).

On PSP scene: for the purpose of running ps1 iso, it seems the need of this keys.bin file was patched (to match the same game, attached to "PSP.base") and later no needed anymore.

For MINIS and export?

See here for some keys.bin examples

Others: PARAM.SFO attribut (PSP)

By group content format:

PSP™: X3,X5,X6,X7 (per default, used for unsupported/ Corrupted data as Unknown folder on PS3, X1 can be also in this folder and it is a bit different issue, in 2 case at least, but no matter)

minis: X1 (same on PS3)

Playstation® (for ps1 classic game) : Don t have attributes

PCENGINE : X0 (same for PS3)

NEOGEO : X2 (it s X4 on PS3, NEOGEO game don t have export so that can be the reason why Attribut are different)

Only X3 seems missing, X5,X6,X7 might not be used yet.

Decrypting Tools

  • PSARdumper

http://dl.qj.net/psp/homebrew-applications/psardumper-for-ofw-660.html

Note: This PSAR dumper is for firmware packages

  • PRXdecrypter

http://dl.qj.net/psp/homebrew-applications/prxdecrypter-v26b.html

Is a modification of psardumper that can decrypt other files as MODULES.PRX or EBOOT.BIN

  • PBP Unpacker

http://dl.qj.net/psp/tools-utilities-on-pc/pbp-unpacker-v094.html


PlayView

Description

Game used to advertise PlayView


PlayView can be described as Guide Book for games (...there are other type of content and not yet stand alone games).

Using "ultra-high resolution (4K) digital data" it can be compatible 3D (for some titles), PS Move+EYE Camera (for some titles) on PS3.

Demo video on PS3 (in English):

Transfer from PSP PlayView to PS VITA is possible for most of the PSP PlayView title with UMD passeport (?)

Speculation: export function, PS3 to PSP, for some titles but final release might have cancel it for commercial (and technical?) reasons.

Including possible extra content on PS3 (for example:themes)

Game List

Various kind of content, but it can be distinguish as for PS3 or PSP.

Note: some games titles are present in both category (e.g.PS3: NPJB-60006, PSP : NPJH-60004)

Game list in Japan for PS3,PSP&PS VITA

structure

Game Data structure on PSP

  • from only one example, so this might change up to each title (especially for other than guide book content). However, it might work on the same way (with specific encryption/security) on PS VITA since this is from PSP title with possible transfer. This example title is also present on PS3 with different ID but might as well work on the same way.

The video link show a little different structure on the PS3 (tile sizes only as 256x256, grid spacing).

It allow quick zoom, jump to other page and hyper link (images, video and music but the link video describe possible other sub element) and background music.

Global Embedded images structure example for one page

Each page contain 6 layers with the same graphical content, the layer display is according to the level you zoom. Visually, each page display is equivalent as 2 pages on art book/ game manual paper version. For this reason, added to the extra content, the size of game data can easily reach hundreds MB.


Level Layer visual Number Image Note Level Layer on file Grid (WxL)
Zoom in ∇
0 1 (180x101) Might not be display or used as "thumbnail" when slide 5 1x1
1 2 Left: 256x202 Right: 104x202 4 2x1
2 6 3 3x2
3 24 with visual arranged as "depth effect"(?) 2 6x4
4 84 1 12x7
5 299 Max_Zoom You reach the "deepest" into the page 0 23x12

gvd.dat.edat:

The file contain the image embedded as well as "database". Can be divide in 2 parts:

  • "TGDT0100"
  • "Image ID.gvd"

TGDT0100

Offset Length Value & Note
0000 8 TGDT0100
0008 4 version?
000C 4 size/start second part (first image id.gvd)
0010 4 Offset file name.gvd (without header TGDT0100)
0014 4 size file name.gvd
0018 4 Offset Data Base Viewer
001C 4 Length Data base Viewer file
0020 xx Repeat last 0x10 for page
0XXX 00 filled with zero until the first image ID.gvd start


Image ID.gvd:

Repeat for each page reference. Can be divide into 3 part: Name file referenced into XML, data base utility and the embedded images.


Name file.gvd
Offset Length Value & Note
0000 16 .name file.gvd
0010 00 filled with zero (variable per page):


DATA BASE Viewer
Offset Length Value Note
0000 16 47 56 45 57 30 31 30 30 4A 50 45 47 30 31 30 30 "GVEW0100JPEG0100"
0010 8 Similar
0018 4 42 4C 4B 5F BLK_
001C 4 00 00 xx xx Length Data Base (variable per game structure?)
0020 8 00 00 00 01 00 00 00 00 Similar
Data Base
0028 8 00 00 00 20 00 00 00 04 Similar
0030 4 00 00 00 xx Grid position Width (hex)
0034 4 00 00 00 xx Grid position Height (hex)
0038 4 00 00 00 0x Layer level
003C 4 00 00 xx xx Length of the image (hex)
0040 4 00 00 00 xx Length padding of the image (hex)
0044 4 00 00 00 00 Not used?
0048 4 00 00 0x xx Width image (hex)
004C 4 00 00 0x xx Height image (hex)
0050 ... ... Repeat last 0x20 for each image on the page
End Data Base
XXXX 4 42 4C 4B 5F BLK_
XXXX 4 xx xx xx xx Total length embedded images (with padding)
XXXX 8 00 00 00 02 00 00 00 00
XXXX xx xx image (first from level layer 5, top left)
Images JPG

Embedded image (JPEG JFIF) per page


The same for other page (without header "TGDT0100")


content.dat.edat

The file contain the XML structure to transport elements such music background etc...

Offset Length Value Note
0000 8 TGDT0100
0008 4 version?
000C 4 header size/start second part

Second part contain the XML Structure/Sub element

  • Image: JPEG (...)
  • Video: hyperlink Mp4 format 480x272 (...)
  • Music: background music + hyperlink : regular MP3 format ( 128 KBPS)