N64FlashcartMenu
|
An open source menu for N64 flashcarts.
Ensure the cart is running the latest firmware Download the sc64menu.n64
ROM from the latest action run assets. Add it to the root folder on your SD card.
Currently not supported, but there is an aim to do so. The aim is to replace Altra64 and ED64-UnofficialOS.
To use boxart, you need to place png files of size 158x112 in the folder sd://menu/boxart/
Each file must be named according to the 2 letter ROM ID. e.g. for goldeneye, this would be GE.png
A known set of PNG files can be downloaded from https://mega.nz/file/6cNGwSqI#8X5ukb65n3YMlGaUtSOGXkKo9HxVnnMOgqn94Epcr7w
Emulators should be added to the sd:/emulators/
folder
The menu currently supports the following emulators and associated ROM's:
Work in progress!
You can use a dev container in VSCode to ease development.
sc64deployer.exe
in the tools/sc64
directory.Make sure that your firmware is compatible (currently v2.16.0+) See: https://github.com/Polprzewodnikowy/SummerCart64/blob/v2.16.0/docs/00_quick_startup_guide.md#firmware-backupupdate
It is not currently possible to directly communicate with USB devices. BUT, as a work around you can use a proxy TCP/IP connection Set up a proxy: open a terminal window, cd ./tools/sc64
and then ./sc64deployer.exe server
Then in the dev container, use make run
or make run-debug
./localdeploy.bat
from the terminalToggle the N64 power switch to load the ROM.
ms-vscode.makefile-tools
will help (installed automatically in dev container). TODO: it does not yet work with F5
: see https://devblogs.microsoft.com/cppblog/now-announcing-makefile-support-in-visual-studio-code/ WORKAROUND: in the dev container terminal, use make directly, i.e.: make
The ROM can be found in the output
directory.
NOTE: a "release" version of the SC64 menu is called sc64menu.n64
and can be created for when you want to add it directly to the SDCard. This is generated by running make all
or running make sc64
.
This repo currently uses the unstable
branch as a submodule at a specific commit. To update to the latest version, use git submodule update --remote
from the terminal.
Run doxygen
from the dev container terminal. Make sure you fix the warnings before creating a PR! Generated documentation is located in output/docs
folder.