fusee_bct0_spec.txt

There'll be two stages in the core fusee payload, loading configuration from a shared ini file (https://en.wikipedia.org/wiki/INI_file).

- Stage 1 will be the actual exploit payload, and it will be fairly minimal:
    - It will initialize DRAM, and initialize the display.
    - It will load a filename and address for stage 2, loading stage 2 into DRAM and jumping to it.
    
- Stage 2 will be a "loader" -- it will be responsible for loading everything else into place prior to boot.
    - Stage 2 will be able to load arbitrarily many files to arbitrary load addresses off of the SD card.
        - Stage 2 will get a list of files to load from a "loadlist" key, with loadables delimited by "|" in the value.
        - For each loadable, a _path and _addr key will be used to identify a filename and where to load it to.
    - Stage 2 will also be responsible for displaying any "boot menu"-style things, for example menus to create/manage emunands, etc. 
    - Stage 2 will also be responsible for booting up Horizon (or chainloading to another payload).
        - Key derivation will happen here.
        - In general, this will mimic the funcionality of NX_BOOTLOADER -- it will launch Exosphere, etc.