| Both sides previous revision
Previous revision
Next revision
|
Previous revision
Next revision
Both sides next revision
|
submission:nintendo-carts [2021/10/11 19:45]
jonasrosland |
submission:nintendo-carts [2021/10/11 19:53]
jonasrosland [Detailed information] |
| |
| General Note: If you are submitting this info to a person/group in order for them to add it to a database, you can skip the transcription of some things, and leave it to them. But it can make the process smoother if you do the transcription yourself. | General Note: If you are submitting this info to a person/group in order for them to add it to a database, you can skip the transcription of some things, and leave it to them. But it can make the process smoother if you do the transcription yourself. |
| * Link(s): Link to release post/page, if applicable. | * **Link(s)**: Link to release post/page, if applicable. |
| * Languages/Language Select: Some games either show a language selection screen at startup or in the game options. Note that it is possible to submit a game without checking the languages, but this then needs to be stated in your submission. | * **Languages/Language Select**: Some games either show a language selection screen at startup or in the game options. Note that it is possible to submit a game without checking the languages, but this then needs to be stated in your submission. |
| * Cart Images: Back and front. | * Tip: Using an emulator like Desmume can speed up the language checking dramatically since you can switch the BIOS language in the emulator settings much faster than on a real DS. You can hold down the tab key to speed up emulation. |
| * Box Barcode: Keep the spaces. It could be verified against the barcode itself by using barcode scanning software and using the check digit. | * **Cart Images**: Back and front. |
| * ROM Region: The region found in the ROM data. (Can be extracted using [[https://www.romhacking.net/utilities/931/|GameHeader]]) | * **Box Barcode**: Keep the spaces. It could be verified against the barcode itself by using barcode scanning software and using the check digit. |
| * ROM Revision: The revision found in the ROM data. (Can be extracted using GameHeader) | * **ROM Region**: The region found in the ROM data. (Can be extracted using [[https://www.romhacking.net/utilities/931/|GameHeader]]) |
| * ROM Serial: The four-character serial found in the ROM data. (Can be extracted using GameHeader, if the header includes it) | * **ROM Revision**: The revision found in the ROM data. (Can be extracted using GameHeader) |
| * Size: The size of the ROM in bytes. | * **ROM Serial**: The four-character serial found in the ROM data. (Can be extracted using GameHeader, if the header includes it) |
| * CRC32: Generated from the ROM file using [[https://mh-nexus.de/en/hxd/|HxD]] or [[http://implbits.com/products/hashtab/|HashTab]] on windows, or by using crc32 in a terminal emulator for linux/mac. | * **Size**: The size of the ROM in bytes. |
| * MD5: As above, or by using md5 in a terminal emulator for linux/mac. | * **CRC32**: Generated from the ROM file using [[https://mh-nexus.de/en/hxd/|HxD]] or [[http://implbits.com/products/hashtab/|HashTab]] on windows, or by using crc32 in a terminal emulator for linux/mac. |
| * SHA-1: As above, or by using shasum -a 1 in a terminal emulator for linux/mac. | * **MD5**: As above, or by using md5 in a terminal emulator for linux/mac. |
| * SHA-256: As above, or by using shasum -a 256 in a terminal emulator for linux/mac. | * **SHA-1**: As above, or by using shasum -a 1 in a terminal emulator for linux/mac. |
| | * **SHA-256**: As above, or by using shasum -a 256 in a terminal emulator for linux/mac. |
| |
| === N64 specific === | === GBA/N64 specific === |
| |
| <code> | <code> |
| </code> | </code> |
| |
| * Physical media stamp: Two numbers imprinted on the back label, possibly followed by an A or B. May need to view under a light source. | * **Physical media stamp**: Two numbers imprinted on the back label, possibly followed by an A or B. May need to view under a light source. |
| |
| === NDS/3DS specific === | === NDS/3DS specific === |
| SHA-256: | SHA-256: |
| </code> | </code> |
| * Decrypted ROM file info: To encrypt a copy of the ROM in order to get the encrypted hashes, use [[https://github.com/SabreTools/NDecrypt|NDecrypt]], [[https://archive.org/details/3dsEncryptV4|3ds_encrypt_v4.py]] or GodMode9 itself (use "NCSD image options">"Decrypt file" on the copy) | |
| * Serial. You can find this at 0x1150 in the ROM. | * **Decrypted ROM file info**: To encrypt a copy of the ROM in order to get the encrypted hashes, use [[https://github.com/SabreTools/NDecrypt|NDecrypt]], [[https://archive.org/details/3dsEncryptV4|3ds_encrypt_v4.py]] or GodMode9 itself (use "NCSD image options">"Decrypt file" on the copy) |
| * Revision. You can find this at 0x312 in the ROM. | * **ROM Serial**: You can find this at 0x1150 in the ROM. |
| * Cart ID: Included in the txt file beside the ROM in the virtual drive called “GAMECART”. | * **ROM Revision**: You can find this at 0x312 in the ROM. |
| | * **Cart ID**: Included in the txt file beside the ROM in the virtual drive called “GAMECART”. |
| * Technical note - GodMode9 displays these in the little endian byte order (i.e. first byte is the chip manufacture byte), which makes sense as the 3DS CPU is little endian (as are the DS and DSi's CPUs). But the gbatek documentation of the [[https://problemkaputt.de/gbatek.htm#dscartridgeprotocol|cart protocol]] displays these in big endian byte order (i.e. last byte is the chip manufacture byte). | * Technical note - GodMode9 displays these in the little endian byte order (i.e. first byte is the chip manufacture byte), which makes sense as the 3DS CPU is little endian (as are the DS and DSi's CPUs). But the gbatek documentation of the [[https://problemkaputt.de/gbatek.htm#dscartridgeprotocol|cart protocol]] displays these in big endian byte order (i.e. last byte is the chip manufacture byte). |
| * Save Chip ID: Found in the same file as the Cart ID. | * **Save Chip ID**: Found in the same file as the Cart ID. |
| * PCB Serial: Use for ''▼'' for the triangle character, one space character ('' '') for each empty "slot" and ''•'' for the small circle characters (which don't always appear). | * **PCB Serial**: Use for ''▼'' for the triangle character, one space character ('' '') for each empty "slot" and ''•'' for the small circle characters (which don't always appear). |
| |