So I just setup the core and was playing around with it, when I found out that the JP boot rom is an overdump.
Its identical to the US boot.rom
These are the sha1sums for the files:
Code: Select all
$ sha1sum *.rom
a749c815e858a2487f4105022d23e7001ee6f0ec br.rom
15c23c3b671a8828302603f30c81d464b24a7fb1 eu.rom
9174eadc0f0ea2654c95fd941406ab46b9dc9bdd jp.rom
b7a0070cbe4b9bcaa08ec0b76b8c4955b2ae535a us.rom
These are the sizes:
Code: Select all
$ ls -l *.rom
-rwxr-xr-x 1 test test 1984 Jan 1 2000 br.rom
-rwxr-xr-x 1 test test 1984 Jan 1 2000 eu.rom
-rwxr-xr-x 1 test test 2048 Jan 1 2000 jp.rom
-rwxr-xr-x 1 test test 1984 Jan 1 2000 us.rom
As you can see the jp.rom is 2048 bytes long instead of 1984 bytes.
Examining those last bytes they do not contain any relevant data.
Code: Select all
hexdump -vC jp.rom
Code: Select all
000007d0 00 00 00 00 ff ff ff ff ff ff ff ff ff ff ff ff |................|
000007e0 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff |................|
000007f0 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff |................|
00000800
Stripping the bytes from the jp.rom into jp_fixed.rom
Code: Select all
$ head -c1984 jp.rom >jp_fixed.rom
Gives us the sizes:
Code: Select all
$ ls -l *.rom
-rwxr-xr-x 1 test test 1984 Jan 1 2000 br.rom
-rwxr-xr-x 1 test test 1984 Jan 1 2000 eu.rom
-rw-r--r-- 1 test test 1984 Oct 6 20:19 jp_fixed.rom
-rwxr-xr-x 1 test test 2048 Jan 1 2000 jp.rom
-rwxr-xr-x 1 test test 1984 Jan 1 2000 us.rom
These are the sha1sums for the files, sorted by hash:
Code: Select all
$ sha1sum *.rom | sort
15c23c3b671a8828302603f30c81d464b24a7fb1 eu.rom
9174eadc0f0ea2654c95fd941406ab46b9dc9bdd jp.rom
a749c815e858a2487f4105022d23e7001ee6f0ec br.rom
b7a0070cbe4b9bcaa08ec0b76b8c4955b2ae535a jp_fixed.rom
b7a0070cbe4b9bcaa08ec0b76b8c4955b2ae535a us.rom
You can clearly see the jp_fixed.rom is identical to the us.rom