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.

mig switch not working/updating??

stickybit · 2024-03-28T19:59:51+00:00

just got my mig switch and followed instructions to the T to update it and all im getting is a red light and then a message saying cart not recognised, all im trying to do is update it to the latest firmware, it says it should flash blue when...

ROM Hack Question Doom and sys-clk

Thread starter jeka467
Start date Jul 6, 2020
Views 1,020
Replies 3

jeka467

Active Member

Newcomer

Level 3

Jul 6, 2020

So I noticed that doom 2016 drops clocks when using sys-clk (I used status monitor to check it). I set it to 614 gpu, but it drops it to 304, 384, 460. And fps jumps too much. Also I noticed when using overlay it lags even more, dropping around 3-5 frames. Anyone else have same problem?

Retic1337

Member

Newcomer

Level 1

Jul 7, 2020

Not sure if you are docked or charging, but you need to be to get the gpu clock over 460. just tested this myself. i cant post links but if you visit the projects github it gives a overview of this information.

Last edited by Retic1337, Jul 7, 2020

jeka467

Active Member

Newcomer

Level 3

Jul 7, 2020

Retic1337 said:
Not sure if you are docked or charging, but you need to be to get the gpu clock over 460. just tested this myself. i cant post links but if you visit the projects github it gives a overview of this information.

I am charging, but clocks still drop

masagrator

The patches guy

Developer

Level 22

Jul 7, 2020

If you mean that clock drops and goes back to 614, then this is normal, because sys-clk only overwrites clocks, doesn't lock them. So if game will change clocks, sys-clk changes clocks in next loop.