Request for Help: Configuring Safe Atmosphere SYSNAND Functioning + Payloads Creation

[Willsito_GG]

Thanks to the help of my brother we achieved compiling a fusee.bin including the sigpatches signature but we are still struggling with making the fusee.bin load SYSNAND with Atmosphere instead of EMUNAND with Atmosphere, in terms of code before the compilation.

Could someone help in this please?

Many thanks in advance,

Best regards

 

[Hayato213]

Thanks to the help of my brother we achieved compiling a fusee.bin including the sigpatches signature but we are still struggling with making the fusee.bin load SYSNAND with Atmosphere instead of EMUNAND with Atmosphere, in terms of code before the compilation.

Could someone help in this please?

Many thanks in advance,

Best regards

Fusee will always load Emunand if there is an emunand in use, you have to use the fss0 method.

 

[Willsito_GG]

Hello again, Team,

Just wanted to share with you a small achievement regarding this topic. To switch between SYSNAND and EMUNAND without going through Hekate (and without getting up from the sofa, since I mainly use the Switch in the dock), here’s what I did:

• Created 2 different emummc.ini files:
  • With this setup, if I rename one of them to .ini using Sphaira and then launch fusee.bin, it will boot either EMUNAND or SYSNAND.
  • /sdmc:/emuMMC/emummc.ini:
    • [emummc]
      enabled=1
      sector=0x738d0000
      path=emuMMC/RAW1
      id=0x*******
      nintendo_path=emuMMC/RAW1/Nintendo
  • /sdmc:/emuMMC/emummc.sys:
    • [emummc]
      enabled=0
      sector=0x738d0000
      path=emuMMC/RAW1
      id=0x*******
      nintendo_path=emuMMC/RAW1/Nintendo
      

This way, I just rename the one I want to use with for example, Sphaira, launch fusee.bin from the Payload Launcher, and I can switch between SYSNAND and EMUNAND without even getting off the couch.

If anyone has a better, cleaner, or more efficient idea, I’d really appreciate it if you could share it!

Thank you very much in advance,

Best regards

Willsito