You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the terminal, use make directly, i.e.: `make all`.
16
+
The ROMs can be found in the `output` directory.
17
+
18
+
For the future:
19
+
`ms-vscode.makefile-tools` will hopefully help (installed automatically in dev container).
20
+
NOTE: it does not yet work with `F5`: see [this blog post](https://devblogs.microsoft.com/cppblog/now-announcing-makefile-support-in-visual-studio-code/).
13
21
14
-
### How to deploy
15
-
#### SC64
16
-
* Download the deployer [here](https://github.com/Polprzewodnikowy/SummerCart64/releases/download/v2.20.2/sc64-deployer-windows-v2.20.2.zip).
17
-
* Extract and place `sc64deployer.exe` in the `tools/sc64` directory.
18
22
23
+
## How to deploy and/or debug to the SC64
19
24
Make sure that your firmware is compatible (currently v2.20.2+).
It is not currently possible to directly communicate with USB devices. BUT, you can use a proxy TCP/IP connection as a workaround.
24
-
To set up a proxy, open a terminal window, `cd ./tools/sc64` and then `./sc64deployer.exe server`.
27
+
You will need to download a copy of the `sc64deployer` from [here](https://github.com/Polprzewodnikowy/SummerCart64/releases/download/v2.20.2/) or build your own depending on the scenario.
28
+
29
+
> [!TIP]
30
+
> Toggle the N64 POWER switch to load and run the ROM.
31
+
32
+
### From within the devcontainer
33
+
#### To the native OS
34
+
It is not currently possible to directly communicate with USB devices from a devcontainer. BUT, you can use a proxy TCP/IP connection as a workaround.
35
+
To set up a "proxy", open a terminal window on the native OS, then `cd ./tools/sc64` and then `./sc64deployer.exe server`.
36
+
Keep this terminal window open.
25
37
26
38
Then, in the dev container, use `make run` or `make run-debug`.
27
39
40
+
#### To a remote LAN device
28
41
If you want to Deploy and debug to a fully remote target (over your LAN)
29
-
Make sure that the remote target has the server running:
42
+
Make sure that the remote target device (i.e. the one with the carts USB connected) has the server running (similar as specified in To the native OS, but):
30
43
31
44
> [!TIP]
32
45
> Make sure you specify its accessible IP and port.
@@ -38,35 +51,51 @@ Make sure that the remote target has the server running:
38
51
39
52
The following commands can then be run from the docker environment terminal:
40
53
54
+
To upload and run the ROM (requires power toggle):
* Download the deployer [here](https://github.com/Polprzewodnikowy/SummerCart64/releases/download/v2.20.2/sc64-deployer-windows-v2.20.2.zip).
66
+
* Extract and place `sc64deployer.exe` in the `tools/sc64` directory.
67
+
* Then use `make run` or `make run-debug` in the terminal.
52
68
53
-
`ms-vscode.makefile-tools` will help (installed automatically in dev container).
54
-
NOTE: it does not yet work with `F5`: see [this blog post](https://devblogs.microsoft.com/cppblog/now-announcing-makefile-support-in-visual-studio-code/).
55
-
WORKAROUND: in the dev container terminal, use make directly, i.e.: `make`.
56
-
The ROM can be found in the `output` directory.
57
69
70
+
### To an SD Card
58
71
NOTE: A "release" version of the SC64 menu is called `sc64menu.n64` and can be generated by running `make all` or running `make sc64`. You can then copy the resulting `sc64menu.n64` file to your SD card.
59
72
60
-
#### Ares Emulator
73
+
74
+
## How to deploy and/or debug to other flashcarts/emulators
75
+
### Ares Emulator
61
76
For ease of development and debugging, the N64FlashcartMenu ROM can run in the [Ares emulator](https://ares-emu.net/) (without most flashcart features).
62
77
63
78
* Ensure you have the Ares emulator on your computer.
64
79
* Load the `N64FlashcartMenu.n64` ROM.
65
80
66
-
####Others
81
+
### Others
67
82
* Add the required file to the correct folder on your SD card.
68
83
69
84
85
+
## How to add debug code
86
+
Within the code, use the `debugf` command, and then deploy using a debug build e.g. `make run-debug`.
0 commit comments