Hello guys, this is my first post here! I just got a MIG Switch card out of curiosity and I was tinkering with it. For those who don't know, it's used by placing XCI dumps as well as other game specific bin files in the sd card of the MIG Switch, and are obtained from the original cartridge by using an app like nxdumptool. Two of these bin files are mandatory to get the game to boot: Initial Data.bin and Certificate.bin. They stay the same for every cartridge of a specific game. Now, if you want to use an XCI dump from a shady website it's impossible to get it to work without those files. By using the Certificate.bin from another game it has no problem, but this does not count for the Initial Data.bin. So I looked for a way to obtain this Initial Data from an XCI file and read a bit of the XCI file documentation from switchbrew dot org. Here's what I understood so far: The Switch checks if the cartridge is valid by doing a challenge–response authentication on the Initial Data. The Package ID is contained both on the XCI and the Initial Data, on positions 0x110 and 0x0 respectively. The Initial Data hash is on the XCI at position 0x160. It is calculated by doing a SHA-256 hash on the full Initial Data content. So I was wondering, is there a way to to construct a functional Initial Data file starting from an XCI dump? I also tried a reverse approach by editing the Package ID in the Initial Data from another game, generating the Initial Data hash and putting it in the XCI file but is not enough to get the Switch believe it's a real game. Sorry if this may seem stupid but let me know what you think.

duckstation for Switch

catlover007 · 2024-04-22T04:06:40+00:00

duckstation is an excellent Playstation 1 emulator by Stenzek. It has a very good compabiility and it is quite performant. It also supports all kinds of enhancements such as high resolution rendering and PGXP which can lessen the "wobble" and...

Homebrew Tutorial Updated

Install MSYS Environment

One of the most used developer environment on Windows is MSYS, MSYS's MINGW is a Cygwin environment working on Windows, is very easy to setup and as it is an enclosed environment is not affected by other software on your computer.

The most recent information about MSYS is on the official webpage: https://www.msys2.org/ and latest installation instructions are on the site: https://www.msys2.org/wiki/MSYS2-installation/, there you can find lot of information.

The MinGW32 & MinGW64 environments can be used to compile Native Windows binaries using a linux toolchain (gcc, bash, etc.)

In order to install MSYS on your system, you need few steps:

Download the latest version from: https://github.com/msys2/msys2-installer/releases, there you will find several packages, the most easy to use is msys2-x86_64-YYYYMMDD.exe
Execute the msys2-x86_64-YYYYMMDD.exe file

And accept the default options:

On the last window, deselect the «Run MSYS2 now» option and and the installation pressing the «Finish» button.
Run the MINGW64 environment from the Start Menu
Once you open the console execute the command pacman -Syuu --needed --noconfirm several times until you get the message: there is nothing to do, is possible what the window close, if is the case, open again the environment and run the command again.
When you end this step you have a full working MSYS environment