Boot methods - Team-Neptune/DeepSea GitHub Wiki

Fusee-Primary vs FSS0/Hekate

Boot using fusée-primary This is the primary method of booting atmosphere supported by the developers.
Example1: You send Atmosphère fusée-primary payload directly to the console in RCM.
Example2: You send Hekate_CTR payload to the console in RCM, which boots Atmosphère using “payload=fusée-primary” functionality.
The scenario in example 2 is the same way of launching Atmosphère as in Example1, except it's chain-loaded by Hekate.

Using Hekate to boot fusée-secondary Hekate can boot Atmosphère by extracting Atmosphere modules directly from fusée-secondary.bin, which can then be loaded or replaced independently.
Example3: You send Hekate_CTR payload to the console in RCM, which boots Atmosphère using “fss0=fusée-secondary” functionality.

So the three can be resumed like this:

Send Payload “Fusee-primary.bin” > boot Atmosphere (fusée-secondary)
Send Payload “Hekate” > chain-boot fusee-primary.bin > boot Atmosphere (payload=)
Send Payload “Hekate” > Hekate uses fusee-secondary to boot Atmosphere (fss0=)

A Special Note About EmuMMC and Hekate/DeepSea: Hekate (and Nyx interface of Hekate) set by DeepSea ready-to-use package lets you choose how you want to boot your console (Stock, SysMMC or emuMMC) directly from its menu. But this choice can only be applied if you launch Atmosphère with fusée-secondary (“fss0=”).

If you have an emuMMC folder or partition and use fusée-primary (“payload=”) method to boot your console, Atmosphère will always follow its own setting to determine whether to use sysMMC or emuMMC regardless of the user choice in Hekate. While an alternative may be to edit Atmosphere config files to force disable emuMMC and reboot the console, the typical method is to edit “emummc/emummc.ini” and set emummc!enabled=0 or 1. 0 means disabled. 1 Means enabled. You can edit the file yourself, or use existing homebrew directly from your Homebrew Launcher menu, such as emuMMC Toggler or EmuMmcConfig and reboot the payload (fusée-primary).

This loss of flexibility and user unfriendliness from Hekate boot menu when using fusee-primary.bin to launch AMS is why DeepSea uses the “fss0=” booting style for syntax. Using fss0= with fusée-secondary potentially allows for the following boot modes directly from Hekate:

  • Stock-like sysMMC
  • sysCFW
  • emuCFW

This increased flexibility, all in one menu would not be possible if booting using fusée-primary.bin

Add a custom footer
⚠️ **GitHub.com Fallback** ⚠️