Game-Decompilation/sotn-decomp
1
0
Fork 0
mirror of https://github.com/Xeeynamo/sotn-decomp.git synced 2024-11-23 13:09:44 +00:00
Code Issues Actions 5 Packages Projects Releases Wiki Activity
30274f0f0e
sotn-decomp/config/splat.pspeu.tt_000.yaml

50 lines
1.3 KiB
YAML
Raw Normal View History

Add TT_000 overlay from PSP (#1113) TT_000 is the first overlay from PlayStation 1 that we are now able to compile from the source and produce a 1:1 binary. This lead me to start exploring the same overlay from the game Castlevania: Dracula X Chronicles, which contains a PSP re-build of Symphony of the Night. This PR adds all the infrastructure to add the same flow for a PSP matching decomp. Use `export VERSION=pspeu` and then the usual `sotn` command to splat the overlay, build it and check if it matches. Running `make extract_disk` should not be necessary as the same ISO used from `VERSION=hd` is also used for `pspeu`, so you will probably have it extracted already. Some important notes about the PSP build: * The whole PSP build seems to be compiled with `-O0`, which makes it much easier to decompile * Having ŧhe PSX, PSP and Saturn builds will allow to easily cross-reference the code and reduce fake matches * `disks/pspeu/PSP_GAME/USRDIR/res/ps/hdbin/tt_000.bin` is the HD PSX build * `disks/pspeu/PSP_GAME/USRDIR/res/ps/PSPBIN/tt_000.bin` has the same code from the HD build, but for PSP * `disks/pspeu/PSP_GAME/USRDIR/res/ps/PACK_E/TP00.BIN` is the same as above, but it packs both overlay and graphics. This is the file the PSP game seems to actually use * The PSP build uses the Metrowerk CodeWarrior's C compiler, which is very different from the GCC one used on PSX. * Thanks to @mkst lead, we found a way to still use the GNU assembler and linker * MWCC uses [wibo](https://github.com/decompals/WiBo/), a think compatibility layer to run Windows CLI tools on Linux. It is much more lightweight than Wine. * MWCC does not support the `INCLUDE_ASM` dialect, so the custom pre-processor `tools/mwcpp` had to be created * The exact MWCC compiler version is unknown, but I suspect it is `build 147` * I am not yet sure of any implications for using GNU AS and GNU LD instead of the MW correspondent tools * Not all the functions can be correctly disassembled, spimdisasm will just produce a bunch of `.word 0x________` due to the in-progress effort of adding the Allegrex-specific opcodes support --- TO-DO list before marking the PR as ready: - [X] Add PSP build to the CI - [x] Add progress reporting to the PSP build - [x] Integrate source file from `src/servant/tt_000_psp` to `src/servant/tt_000` to promote the psp build as first-citizen --- TO-DO in a follow-up PR: * Figure out what `header` is: can we extract it as assembly code? or maybe as custom re-compilable asset via splat? Is it a MW stuff or a Castlevania-specific file? * Get rid of the last line in `Makefile.psp.mk`
2024-04-21 01:18:10 +00:00
options:
Use PSP platform to disassemble PSP overlays (#1118) Having `platform: psx` will not correctly disassemble PSP functions with opcodes that are not part of the R3000 (the PSX CPU) architecture. These functions would be disassembled by Splat as a bunch of `.word 0xBLAHBLAH`. Changing the platform to `psp` introduces all sort of new challenges. Function prototypes needs to be declared earlier. But also the MWCC compiler will not accept the `%lo` and `%hi` dialect from GNU AS. There were some patches on `mwcpp.py` to use `la SYMBOL_NAME` that would expand into a `lui / addiu` combo. But even though symbols needs to be declared like function prototypes at the top of the file. This is simply not feasible on bigger overlays. As a solution to the problem above, I replaced the existing patches by converting instructions into `.word`. The overlay cannot longer be relocated with this approach, but it is not an issue as the final goal is to decompile these functions any way. The labels in the jump table has the same problem, which forced me to change the segment type from `rodata` to `data. This is just another single step to create the conditions to start including bigger re-compilable PSP overlays. I am sure the `mwcpp.py` solution will be thrown into the bin at some point, but this PR improves our current situation.
2024-05-06 18:35:28 +00:00
platform: psp
Add TT_000 overlay from PSP (#1113) TT_000 is the first overlay from PlayStation 1 that we are now able to compile from the source and produce a 1:1 binary. This lead me to start exploring the same overlay from the game Castlevania: Dracula X Chronicles, which contains a PSP re-build of Symphony of the Night. This PR adds all the infrastructure to add the same flow for a PSP matching decomp. Use `export VERSION=pspeu` and then the usual `sotn` command to splat the overlay, build it and check if it matches. Running `make extract_disk` should not be necessary as the same ISO used from `VERSION=hd` is also used for `pspeu`, so you will probably have it extracted already. Some important notes about the PSP build: * The whole PSP build seems to be compiled with `-O0`, which makes it much easier to decompile * Having ŧhe PSX, PSP and Saturn builds will allow to easily cross-reference the code and reduce fake matches * `disks/pspeu/PSP_GAME/USRDIR/res/ps/hdbin/tt_000.bin` is the HD PSX build * `disks/pspeu/PSP_GAME/USRDIR/res/ps/PSPBIN/tt_000.bin` has the same code from the HD build, but for PSP * `disks/pspeu/PSP_GAME/USRDIR/res/ps/PACK_E/TP00.BIN` is the same as above, but it packs both overlay and graphics. This is the file the PSP game seems to actually use * The PSP build uses the Metrowerk CodeWarrior's C compiler, which is very different from the GCC one used on PSX. * Thanks to @mkst lead, we found a way to still use the GNU assembler and linker * MWCC uses [wibo](https://github.com/decompals/WiBo/), a think compatibility layer to run Windows CLI tools on Linux. It is much more lightweight than Wine. * MWCC does not support the `INCLUDE_ASM` dialect, so the custom pre-processor `tools/mwcpp` had to be created * The exact MWCC compiler version is unknown, but I suspect it is `build 147` * I am not yet sure of any implications for using GNU AS and GNU LD instead of the MW correspondent tools * Not all the functions can be correctly disassembled, spimdisasm will just produce a bunch of `.word 0x________` due to the in-progress effort of adding the Allegrex-specific opcodes support --- TO-DO list before marking the PR as ready: - [X] Add PSP build to the CI - [x] Add progress reporting to the PSP build - [x] Integrate source file from `src/servant/tt_000_psp` to `src/servant/tt_000` to promote the psp build as first-citizen --- TO-DO in a follow-up PR: * Figure out what `header` is: can we extract it as assembly code? or maybe as custom re-compilable asset via splat? Is it a MW stuff or a Castlevania-specific file? * Get rid of the last line in `Makefile.psp.mk`
2024-04-21 01:18:10 +00:00
basename: tt_000
base_path: ..
build_path: build/pspeu
target_path: disks/pspeu/PSP_GAME/USRDIR/res/ps/PSPBIN/tt_000.bin
asm_path: asm/pspeu/servant/tt_000
asset_path: assets/servant/tt_000
src_path: src/servant/tt_000
ld_script_path: build/pspeu/tt_000.ld
compiler: GCC
symbol_addrs_path:
- config/symbols.pspeu.txt
- config/symbols.pspeu.tt_000.txt
undefined_funcs_auto_path: config/undefined_funcs_auto.pspeu.tt_000.txt
undefined_syms_auto_path: config/undefined_syms_auto.pspeu.tt_000.txt
find_file_boundaries: yes
use_legacy_include_asm: no
Update mwccgap (basic rodata support) (#1276)
2024-06-07 17:14:08 +00:00
migrate_rodata_to_functions: yes
Add TT_000 overlay from PSP (#1113) TT_000 is the first overlay from PlayStation 1 that we are now able to compile from the source and produce a 1:1 binary. This lead me to start exploring the same overlay from the game Castlevania: Dracula X Chronicles, which contains a PSP re-build of Symphony of the Night. This PR adds all the infrastructure to add the same flow for a PSP matching decomp. Use `export VERSION=pspeu` and then the usual `sotn` command to splat the overlay, build it and check if it matches. Running `make extract_disk` should not be necessary as the same ISO used from `VERSION=hd` is also used for `pspeu`, so you will probably have it extracted already. Some important notes about the PSP build: * The whole PSP build seems to be compiled with `-O0`, which makes it much easier to decompile * Having ŧhe PSX, PSP and Saturn builds will allow to easily cross-reference the code and reduce fake matches * `disks/pspeu/PSP_GAME/USRDIR/res/ps/hdbin/tt_000.bin` is the HD PSX build * `disks/pspeu/PSP_GAME/USRDIR/res/ps/PSPBIN/tt_000.bin` has the same code from the HD build, but for PSP * `disks/pspeu/PSP_GAME/USRDIR/res/ps/PACK_E/TP00.BIN` is the same as above, but it packs both overlay and graphics. This is the file the PSP game seems to actually use * The PSP build uses the Metrowerk CodeWarrior's C compiler, which is very different from the GCC one used on PSX. * Thanks to @mkst lead, we found a way to still use the GNU assembler and linker * MWCC uses [wibo](https://github.com/decompals/WiBo/), a think compatibility layer to run Windows CLI tools on Linux. It is much more lightweight than Wine. * MWCC does not support the `INCLUDE_ASM` dialect, so the custom pre-processor `tools/mwcpp` had to be created * The exact MWCC compiler version is unknown, but I suspect it is `build 147` * I am not yet sure of any implications for using GNU AS and GNU LD instead of the MW correspondent tools * Not all the functions can be correctly disassembled, spimdisasm will just produce a bunch of `.word 0x________` due to the in-progress effort of adding the Allegrex-specific opcodes support --- TO-DO list before marking the PR as ready: - [X] Add PSP build to the CI - [x] Add progress reporting to the PSP build - [x] Integrate source file from `src/servant/tt_000_psp` to `src/servant/tt_000` to promote the psp build as first-citizen --- TO-DO in a follow-up PR: * Figure out what `header` is: can we extract it as assembly code? or maybe as custom re-compilable asset via splat? Is it a MW stuff or a Castlevania-specific file? * Get rid of the last line in `Makefile.psp.mk`
2024-04-21 01:18:10 +00:00
asm_jtbl_label_macro: jlabel
section_order:
- ".text"
- ".data"
- ".rodata"
PSP: func_80171ED4 (#1116) Co-authored-by: Luciano Ciccariello <Xeeynamo@users.noreply.github.com> Co-authored-by: Mc-muffin <Mc-muffin@users.noreply.github.com> Co-authored-by: 1superchip <1superchip@users.noreply.github.com>
2024-05-04 18:09:31 +00:00
- ".bss"
Add TT_000 overlay from PSP (#1113) TT_000 is the first overlay from PlayStation 1 that we are now able to compile from the source and produce a 1:1 binary. This lead me to start exploring the same overlay from the game Castlevania: Dracula X Chronicles, which contains a PSP re-build of Symphony of the Night. This PR adds all the infrastructure to add the same flow for a PSP matching decomp. Use `export VERSION=pspeu` and then the usual `sotn` command to splat the overlay, build it and check if it matches. Running `make extract_disk` should not be necessary as the same ISO used from `VERSION=hd` is also used for `pspeu`, so you will probably have it extracted already. Some important notes about the PSP build: * The whole PSP build seems to be compiled with `-O0`, which makes it much easier to decompile * Having ŧhe PSX, PSP and Saturn builds will allow to easily cross-reference the code and reduce fake matches * `disks/pspeu/PSP_GAME/USRDIR/res/ps/hdbin/tt_000.bin` is the HD PSX build * `disks/pspeu/PSP_GAME/USRDIR/res/ps/PSPBIN/tt_000.bin` has the same code from the HD build, but for PSP * `disks/pspeu/PSP_GAME/USRDIR/res/ps/PACK_E/TP00.BIN` is the same as above, but it packs both overlay and graphics. This is the file the PSP game seems to actually use * The PSP build uses the Metrowerk CodeWarrior's C compiler, which is very different from the GCC one used on PSX. * Thanks to @mkst lead, we found a way to still use the GNU assembler and linker * MWCC uses [wibo](https://github.com/decompals/WiBo/), a think compatibility layer to run Windows CLI tools on Linux. It is much more lightweight than Wine. * MWCC does not support the `INCLUDE_ASM` dialect, so the custom pre-processor `tools/mwcpp` had to be created * The exact MWCC compiler version is unknown, but I suspect it is `build 147` * I am not yet sure of any implications for using GNU AS and GNU LD instead of the MW correspondent tools * Not all the functions can be correctly disassembled, spimdisasm will just produce a bunch of `.word 0x________` due to the in-progress effort of adding the Allegrex-specific opcodes support --- TO-DO list before marking the PR as ready: - [X] Add PSP build to the CI - [x] Add progress reporting to the PSP build - [x] Integrate source file from `src/servant/tt_000_psp` to `src/servant/tt_000` to promote the psp build as first-citizen --- TO-DO in a follow-up PR: * Figure out what `header` is: can we extract it as assembly code? or maybe as custom re-compilable asset via splat? Is it a MW stuff or a Castlevania-specific file? * Get rid of the last line in `Makefile.psp.mk`
2024-04-21 01:18:10 +00:00
ld_bss_is_noload: True
Add mwccgap (#1131) OK. Here goes. Version 0.0.1 alpha of the MWCC Global Assembly Processor (mwccgap). It's currently very simple/limited, but it appears to work for `src/servant/tt_000/10E8.c`. There is lot more that can be done to improve mwccgap - i.e. supporting .rodata migration would be a good addition, but let's see how far we can get with it in it's current state. Note that the Makefile could do with some improvements - we don't nede to use mwccgap for any C file that *dont* have INCLUDE_ASM macros (it's a waste of time) so these could be ignored, i.e. for SSSV I do something like this to find the files that need fixing up: ``` GLOBAL_ASM_C_FILES := $(shell $(GREP) GLOBAL_ASM $(SRC_DIR) </dev/null 2>/dev/null) ``` .. although this is perhaps too simple given that SOTN has a mix of PSP and PSX functions (and therefore there may be INCLUDE_ASM for a PSX function but none for PSP functions...
2024-05-18 10:41:00 +00:00
disasm_unknown: True
asm_inc_header: |
.set noat /* allow manual use of $at */
.set noreorder /* don't insert nops after branches */
.include "macro.inc"
sha1: c8c34ac1d46b31e2e5336df271aa2409f44c9d01
Add TT_000 overlay from PSP (#1113) TT_000 is the first overlay from PlayStation 1 that we are now able to compile from the source and produce a 1:1 binary. This lead me to start exploring the same overlay from the game Castlevania: Dracula X Chronicles, which contains a PSP re-build of Symphony of the Night. This PR adds all the infrastructure to add the same flow for a PSP matching decomp. Use `export VERSION=pspeu` and then the usual `sotn` command to splat the overlay, build it and check if it matches. Running `make extract_disk` should not be necessary as the same ISO used from `VERSION=hd` is also used for `pspeu`, so you will probably have it extracted already. Some important notes about the PSP build: * The whole PSP build seems to be compiled with `-O0`, which makes it much easier to decompile * Having ŧhe PSX, PSP and Saturn builds will allow to easily cross-reference the code and reduce fake matches * `disks/pspeu/PSP_GAME/USRDIR/res/ps/hdbin/tt_000.bin` is the HD PSX build * `disks/pspeu/PSP_GAME/USRDIR/res/ps/PSPBIN/tt_000.bin` has the same code from the HD build, but for PSP * `disks/pspeu/PSP_GAME/USRDIR/res/ps/PACK_E/TP00.BIN` is the same as above, but it packs both overlay and graphics. This is the file the PSP game seems to actually use * The PSP build uses the Metrowerk CodeWarrior's C compiler, which is very different from the GCC one used on PSX. * Thanks to @mkst lead, we found a way to still use the GNU assembler and linker * MWCC uses [wibo](https://github.com/decompals/WiBo/), a think compatibility layer to run Windows CLI tools on Linux. It is much more lightweight than Wine. * MWCC does not support the `INCLUDE_ASM` dialect, so the custom pre-processor `tools/mwcpp` had to be created * The exact MWCC compiler version is unknown, but I suspect it is `build 147` * I am not yet sure of any implications for using GNU AS and GNU LD instead of the MW correspondent tools * Not all the functions can be correctly disassembled, spimdisasm will just produce a bunch of `.word 0x________` due to the in-progress effort of adding the Allegrex-specific opcodes support --- TO-DO list before marking the PR as ready: - [X] Add PSP build to the CI - [x] Add progress reporting to the PSP build - [x] Integrate source file from `src/servant/tt_000_psp` to `src/servant/tt_000` to promote the psp build as first-citizen --- TO-DO in a follow-up PR: * Figure out what `header` is: can we extract it as assembly code? or maybe as custom re-compilable asset via splat? Is it a MW stuff or a Castlevania-specific file? * Get rid of the last line in `Makefile.psp.mk`
2024-04-21 01:18:10 +00:00
segments:
Add ST/WRP from PSP (#1172) Extract ST/WRP out of #1119 . All the function symbols should have been cross-referenced. There as some PSX functions missing from PSP and some new functions from PSP that are not present on PSX (e.g. `st_init_wrp.c`). The files `st_debug.c` and `e_breakable.c` are shared between WRP PSX and WRP PSP. Everything else from PSP is isolated into its own folder. I had to do some tricks on the YAML config to allow shared code. `ST_WRP_MERGE = st_debug e_breakable` in the `Makefile` is a bit annoying as MWCC complains about every single minute detail from the C source that has been already decompiled for the PSX US build. `EntityWarpSmallRocks` is matching on PSP but I couldn't extract the rodata without having a bunch of linker errors. This might be a Splat issue. I need to investigate further. `func_psp_09244760` is soooo interesting. The values from `0x11` to `0x17` matches the Entity IDs that are unique to the WRP overlay. This aligns to what we have in `typedef enum EntityIDs`. Overall I am very excited to the recent discoveries from the PSP build!
2024-05-25 18:56:06 +00:00
- [0x0, bin, mwo_header]
Add TT_000 overlay from PSP (#1113) TT_000 is the first overlay from PlayStation 1 that we are now able to compile from the source and produce a 1:1 binary. This lead me to start exploring the same overlay from the game Castlevania: Dracula X Chronicles, which contains a PSP re-build of Symphony of the Night. This PR adds all the infrastructure to add the same flow for a PSP matching decomp. Use `export VERSION=pspeu` and then the usual `sotn` command to splat the overlay, build it and check if it matches. Running `make extract_disk` should not be necessary as the same ISO used from `VERSION=hd` is also used for `pspeu`, so you will probably have it extracted already. Some important notes about the PSP build: * The whole PSP build seems to be compiled with `-O0`, which makes it much easier to decompile * Having ŧhe PSX, PSP and Saturn builds will allow to easily cross-reference the code and reduce fake matches * `disks/pspeu/PSP_GAME/USRDIR/res/ps/hdbin/tt_000.bin` is the HD PSX build * `disks/pspeu/PSP_GAME/USRDIR/res/ps/PSPBIN/tt_000.bin` has the same code from the HD build, but for PSP * `disks/pspeu/PSP_GAME/USRDIR/res/ps/PACK_E/TP00.BIN` is the same as above, but it packs both overlay and graphics. This is the file the PSP game seems to actually use * The PSP build uses the Metrowerk CodeWarrior's C compiler, which is very different from the GCC one used on PSX. * Thanks to @mkst lead, we found a way to still use the GNU assembler and linker * MWCC uses [wibo](https://github.com/decompals/WiBo/), a think compatibility layer to run Windows CLI tools on Linux. It is much more lightweight than Wine. * MWCC does not support the `INCLUDE_ASM` dialect, so the custom pre-processor `tools/mwcpp` had to be created * The exact MWCC compiler version is unknown, but I suspect it is `build 147` * I am not yet sure of any implications for using GNU AS and GNU LD instead of the MW correspondent tools * Not all the functions can be correctly disassembled, spimdisasm will just produce a bunch of `.word 0x________` due to the in-progress effort of adding the Allegrex-specific opcodes support --- TO-DO list before marking the PR as ready: - [X] Add PSP build to the CI - [x] Add progress reporting to the PSP build - [x] Integrate source file from `src/servant/tt_000_psp` to `src/servant/tt_000` to promote the psp build as first-citizen --- TO-DO in a follow-up PR: * Figure out what `header` is: can we extract it as assembly code? or maybe as custom re-compilable asset via splat? Is it a MW stuff or a Castlevania-specific file? * Get rid of the last line in `Makefile.psp.mk`
2024-04-21 01:18:10 +00:00
- name: tt_000
type: code
start: 0x00000080
vram: 0x092E7680
PSP: func_80171ED4 (#1116) Co-authored-by: Luciano Ciccariello <Xeeynamo@users.noreply.github.com> Co-authored-by: Mc-muffin <Mc-muffin@users.noreply.github.com> Co-authored-by: 1superchip <1superchip@users.noreply.github.com>
2024-05-04 18:09:31 +00:00
bss_size: 0x500
Add TT_000 overlay from PSP (#1113) TT_000 is the first overlay from PlayStation 1 that we are now able to compile from the source and produce a 1:1 binary. This lead me to start exploring the same overlay from the game Castlevania: Dracula X Chronicles, which contains a PSP re-build of Symphony of the Night. This PR adds all the infrastructure to add the same flow for a PSP matching decomp. Use `export VERSION=pspeu` and then the usual `sotn` command to splat the overlay, build it and check if it matches. Running `make extract_disk` should not be necessary as the same ISO used from `VERSION=hd` is also used for `pspeu`, so you will probably have it extracted already. Some important notes about the PSP build: * The whole PSP build seems to be compiled with `-O0`, which makes it much easier to decompile * Having ŧhe PSX, PSP and Saturn builds will allow to easily cross-reference the code and reduce fake matches * `disks/pspeu/PSP_GAME/USRDIR/res/ps/hdbin/tt_000.bin` is the HD PSX build * `disks/pspeu/PSP_GAME/USRDIR/res/ps/PSPBIN/tt_000.bin` has the same code from the HD build, but for PSP * `disks/pspeu/PSP_GAME/USRDIR/res/ps/PACK_E/TP00.BIN` is the same as above, but it packs both overlay and graphics. This is the file the PSP game seems to actually use * The PSP build uses the Metrowerk CodeWarrior's C compiler, which is very different from the GCC one used on PSX. * Thanks to @mkst lead, we found a way to still use the GNU assembler and linker * MWCC uses [wibo](https://github.com/decompals/WiBo/), a think compatibility layer to run Windows CLI tools on Linux. It is much more lightweight than Wine. * MWCC does not support the `INCLUDE_ASM` dialect, so the custom pre-processor `tools/mwcpp` had to be created * The exact MWCC compiler version is unknown, but I suspect it is `build 147` * I am not yet sure of any implications for using GNU AS and GNU LD instead of the MW correspondent tools * Not all the functions can be correctly disassembled, spimdisasm will just produce a bunch of `.word 0x________` due to the in-progress effort of adding the Allegrex-specific opcodes support --- TO-DO list before marking the PR as ready: - [X] Add PSP build to the CI - [x] Add progress reporting to the PSP build - [x] Integrate source file from `src/servant/tt_000_psp` to `src/servant/tt_000` to promote the psp build as first-citizen --- TO-DO in a follow-up PR: * Figure out what `header` is: can we extract it as assembly code? or maybe as custom re-compilable asset via splat? Is it a MW stuff or a Castlevania-specific file? * Get rid of the last line in `Makefile.psp.mk`
2024-04-21 01:18:10 +00:00
align: 128
More TT_000 PSP functions matching (#1115)
2024-04-23 19:06:05 +00:00
subalign: 8
Add TT_000 overlay from PSP (#1113) TT_000 is the first overlay from PlayStation 1 that we are now able to compile from the source and produce a 1:1 binary. This lead me to start exploring the same overlay from the game Castlevania: Dracula X Chronicles, which contains a PSP re-build of Symphony of the Night. This PR adds all the infrastructure to add the same flow for a PSP matching decomp. Use `export VERSION=pspeu` and then the usual `sotn` command to splat the overlay, build it and check if it matches. Running `make extract_disk` should not be necessary as the same ISO used from `VERSION=hd` is also used for `pspeu`, so you will probably have it extracted already. Some important notes about the PSP build: * The whole PSP build seems to be compiled with `-O0`, which makes it much easier to decompile * Having ŧhe PSX, PSP and Saturn builds will allow to easily cross-reference the code and reduce fake matches * `disks/pspeu/PSP_GAME/USRDIR/res/ps/hdbin/tt_000.bin` is the HD PSX build * `disks/pspeu/PSP_GAME/USRDIR/res/ps/PSPBIN/tt_000.bin` has the same code from the HD build, but for PSP * `disks/pspeu/PSP_GAME/USRDIR/res/ps/PACK_E/TP00.BIN` is the same as above, but it packs both overlay and graphics. This is the file the PSP game seems to actually use * The PSP build uses the Metrowerk CodeWarrior's C compiler, which is very different from the GCC one used on PSX. * Thanks to @mkst lead, we found a way to still use the GNU assembler and linker * MWCC uses [wibo](https://github.com/decompals/WiBo/), a think compatibility layer to run Windows CLI tools on Linux. It is much more lightweight than Wine. * MWCC does not support the `INCLUDE_ASM` dialect, so the custom pre-processor `tools/mwcpp` had to be created * The exact MWCC compiler version is unknown, but I suspect it is `build 147` * I am not yet sure of any implications for using GNU AS and GNU LD instead of the MW correspondent tools * Not all the functions can be correctly disassembled, spimdisasm will just produce a bunch of `.word 0x________` due to the in-progress effort of adding the Allegrex-specific opcodes support --- TO-DO list before marking the PR as ready: - [X] Add PSP build to the CI - [x] Add progress reporting to the PSP build - [x] Integrate source file from `src/servant/tt_000_psp` to `src/servant/tt_000` to promote the psp build as first-citizen --- TO-DO in a follow-up PR: * Figure out what `header` is: can we extract it as assembly code? or maybe as custom re-compilable asset via splat? Is it a MW stuff or a Castlevania-specific file? * Get rid of the last line in `Makefile.psp.mk`
2024-04-21 01:18:10 +00:00
subsegments:
- [0x80, c, 10E8]
TT_000 PSP match more functions (#1150) Highlights: * `abs` is a real function the compiler can optimise and inline (thanks @Mc-muffin for the discovery) * `-Op` is required to avoid using `div` when dividing integer numbers * A file split in TT_000 is required to match on PSP * `UpdateAnim` had the wrong signature * Splatting the PSP build has been an excellent idea
2024-05-19 18:23:30 +00:00
- [0x48C8, c, 45E4]
Add TT_000 overlay from PSP (#1113) TT_000 is the first overlay from PlayStation 1 that we are now able to compile from the source and produce a 1:1 binary. This lead me to start exploring the same overlay from the game Castlevania: Dracula X Chronicles, which contains a PSP re-build of Symphony of the Night. This PR adds all the infrastructure to add the same flow for a PSP matching decomp. Use `export VERSION=pspeu` and then the usual `sotn` command to splat the overlay, build it and check if it matches. Running `make extract_disk` should not be necessary as the same ISO used from `VERSION=hd` is also used for `pspeu`, so you will probably have it extracted already. Some important notes about the PSP build: * The whole PSP build seems to be compiled with `-O0`, which makes it much easier to decompile * Having ŧhe PSX, PSP and Saturn builds will allow to easily cross-reference the code and reduce fake matches * `disks/pspeu/PSP_GAME/USRDIR/res/ps/hdbin/tt_000.bin` is the HD PSX build * `disks/pspeu/PSP_GAME/USRDIR/res/ps/PSPBIN/tt_000.bin` has the same code from the HD build, but for PSP * `disks/pspeu/PSP_GAME/USRDIR/res/ps/PACK_E/TP00.BIN` is the same as above, but it packs both overlay and graphics. This is the file the PSP game seems to actually use * The PSP build uses the Metrowerk CodeWarrior's C compiler, which is very different from the GCC one used on PSX. * Thanks to @mkst lead, we found a way to still use the GNU assembler and linker * MWCC uses [wibo](https://github.com/decompals/WiBo/), a think compatibility layer to run Windows CLI tools on Linux. It is much more lightweight than Wine. * MWCC does not support the `INCLUDE_ASM` dialect, so the custom pre-processor `tools/mwcpp` had to be created * The exact MWCC compiler version is unknown, but I suspect it is `build 147` * I am not yet sure of any implications for using GNU AS and GNU LD instead of the MW correspondent tools * Not all the functions can be correctly disassembled, spimdisasm will just produce a bunch of `.word 0x________` due to the in-progress effort of adding the Allegrex-specific opcodes support --- TO-DO list before marking the PR as ready: - [X] Add PSP build to the CI - [x] Add progress reporting to the PSP build - [x] Integrate source file from `src/servant/tt_000_psp` to `src/servant/tt_000` to promote the psp build as first-citizen --- TO-DO in a follow-up PR: * Figure out what `header` is: can we extract it as assembly code? or maybe as custom re-compilable asset via splat? Is it a MW stuff or a Castlevania-specific file? * Get rid of the last line in `Makefile.psp.mk`
2024-04-21 01:18:10 +00:00
- [0x4C80, data]
Update mwccgap (basic rodata support) (#1276)
2024-06-07 17:14:08 +00:00
- [0x5E00, .rodata, 10E8]
PSP: func_80171ED4 (#1116) Co-authored-by: Luciano Ciccariello <Xeeynamo@users.noreply.github.com> Co-authored-by: Mc-muffin <Mc-muffin@users.noreply.github.com> Co-authored-by: 1superchip <1superchip@users.noreply.github.com>
2024-05-04 18:09:31 +00:00
- {type: bss, vram: 0x092ed480}
Add TT_000 overlay from PSP (#1113) TT_000 is the first overlay from PlayStation 1 that we are now able to compile from the source and produce a 1:1 binary. This lead me to start exploring the same overlay from the game Castlevania: Dracula X Chronicles, which contains a PSP re-build of Symphony of the Night. This PR adds all the infrastructure to add the same flow for a PSP matching decomp. Use `export VERSION=pspeu` and then the usual `sotn` command to splat the overlay, build it and check if it matches. Running `make extract_disk` should not be necessary as the same ISO used from `VERSION=hd` is also used for `pspeu`, so you will probably have it extracted already. Some important notes about the PSP build: * The whole PSP build seems to be compiled with `-O0`, which makes it much easier to decompile * Having ŧhe PSX, PSP and Saturn builds will allow to easily cross-reference the code and reduce fake matches * `disks/pspeu/PSP_GAME/USRDIR/res/ps/hdbin/tt_000.bin` is the HD PSX build * `disks/pspeu/PSP_GAME/USRDIR/res/ps/PSPBIN/tt_000.bin` has the same code from the HD build, but for PSP * `disks/pspeu/PSP_GAME/USRDIR/res/ps/PACK_E/TP00.BIN` is the same as above, but it packs both overlay and graphics. This is the file the PSP game seems to actually use * The PSP build uses the Metrowerk CodeWarrior's C compiler, which is very different from the GCC one used on PSX. * Thanks to @mkst lead, we found a way to still use the GNU assembler and linker * MWCC uses [wibo](https://github.com/decompals/WiBo/), a think compatibility layer to run Windows CLI tools on Linux. It is much more lightweight than Wine. * MWCC does not support the `INCLUDE_ASM` dialect, so the custom pre-processor `tools/mwcpp` had to be created * The exact MWCC compiler version is unknown, but I suspect it is `build 147` * I am not yet sure of any implications for using GNU AS and GNU LD instead of the MW correspondent tools * Not all the functions can be correctly disassembled, spimdisasm will just produce a bunch of `.word 0x________` due to the in-progress effort of adding the Allegrex-specific opcodes support --- TO-DO list before marking the PR as ready: - [X] Add PSP build to the CI - [x] Add progress reporting to the PSP build - [x] Integrate source file from `src/servant/tt_000_psp` to `src/servant/tt_000` to promote the psp build as first-citizen --- TO-DO in a follow-up PR: * Figure out what `header` is: can we extract it as assembly code? or maybe as custom re-compilable asset via splat? Is it a MW stuff or a Castlevania-specific file? * Get rid of the last line in `Makefile.psp.mk`
2024-04-21 01:18:10 +00:00
- [0x5E80]
Reference in New Issue Copy Permalink