399
edits
Changes
Jump to navigation
Jump to search
Line 77:
Line 77: − + Line 97:
Line 97: − + − + − + − + + + + + + + + + + + + + + + + + + + + + Line 120:
Line 140: + − +
→Partitions: more on DISA
| 0x04
| 0x04
| 4
| 4
| Unknown
| Unknown (maybe magic, the same in all the save files so far)
|-
|-
| 0x08
| 0x08
| 0x28
| 0x28
| 8
| 8
| Unknown (padding?)
| SAVE Partition entry offset in the partition table
|-
|-
| 0x30
| 0x30
| 8
| 8
| Size of data from the active table to be hashed
| SAVE Partition entry length in the partition table
|-
|-
| 0x38
| 0x38
| 8*6
| 8
| Unknown
| DATA Partition entry offset in the partition table
|-
| 0x40
| 8
| DATA Partition entry length in the partition table
|-
| 0x48
| 8
| SAVE Partition offset
|-
| 0x50
| 8
| SAVE Partition length
|-
| 0x58
| 8
| DATA Partition offset
|-
| 0x60
| 8
| DATA Partition length
|-
|-
| 0x68
| 0x68
|}
|}
* The hash in the DISA blob hashes the SAVE entry of the 'active_table' in 1 partition files.
* The hash in the DISA blob hashes 'hash_size' bytes of the 'active_table'.
* The partitions offsets points to a 0x1000 long block which isn't understood yet. The actual information starts after that block.
The DIFIs table @ 0x200 (into the image) is written twice, (Meaning, if there's 4 DIFI blobs then the table is 2 DIFIs long).
The DIFIs table @ 0x200 (into the image) is written twice, (Meaning, if there's 4 DIFI blobs then the table is 2 DIFIs long).