<li>Download the deployer <ahref="https://github.com/Polprzewodnikowy/SummerCart64/releases/download/v2.18.0/sc64-deployer-windows-v2.18.0.zip">here</a></li>
<li>Extract and place <code>sc64deployer.exe</code> in the <code>tools/sc64</code> directory.</li>
</ul>
<p>Make sure that your firmware is compatible (currently v2.18.0+) See: <ahref="https://github.com/Polprzewodnikowy/SummerCart64/blob/v2.18.0/docs/00_quick_startup_guide.md#firmware-backupupdate">here</a></p>
<p>It is not currently possible to directly communicate with USB devices. BUT, as a workaround you can use a proxy TCP/IP connection Set up a proxy: open a terminal window, <code>cd ./tools/sc64</code> and then <code>./sc64deployer.exe server</code></p>
<p>Then in the dev container, use <code>make run</code> or <code>make run-debug</code></p>
<li>Run <code>./localdeploy.bat</code> from the terminal</li>
</ul>
<p>Toggle the N64 power switch to load the ROM.</p>
<p><code>ms-vscode.makefile-tools</code> will help (installed automatically in dev container). NOTE: it does not yet work with <code>F5</code>: see <ahref="https://devblogs.microsoft.com/cppblog/now-announcing-makefile-support-in-visual-studio-code/">this blog post</a> WORKAROUND: in the dev container terminal, use make directly, i.e.: <code>make</code> The ROM can be found in the <code>output</code> directory.</p>
<p>NOTE: a "release" version of the SC64 menu is called <code>sc64menu.n64</code> and can be created for when you want to add it directly to the SDCard. This is generated by running <code>make all</code> or running <code>make sc64</code>.</p>
<p>For ease of development and debugging, the menu ROM can run in the <ahref="https://ares-emu.net/">Ares emulator</a> (without most flashcart features).</p>
<p>This repo currently uses the <code>preview</code> branch as a submodule at a specific commit. To update to the latest version, use <code>git submodule update --remote</code> from the terminal.</p>
<p>Run <code>doxygen</code> from the dev container terminal. Make sure you fix the warnings before creating a PR! Generated documentation is located in the <code>output/docs</code> folder and auto-published to the <code>gh-pages</code> branch when merged with <code>main</code>.</p>