| Commit message (Collapse) | Author | Age | Files | Lines | |
|---|---|---|---|---|---|
| * | runrom: add the --until-address option | Miquel Sabaté Solà | 3 days | 1 | -6/+12 |
| | | | | | | | | | | This allows the user to run execution until a given address is reached. This can, like with the --start option, be coupled with the --nasm option in order to be able to provide an identifier instead of a regular hexadecimal value. Signed-off-by: Miquel Sabaté Solà <mssola@mssola.com> | ||||
| * | Allow the --start flag to accept identifiers | Miquel Sabaté Solà | 3 days | 1 | -8/+24 |
| | | | | | | | | This is coupled with the new -n/--nasm option, which works in the same way as in `readrom`. Signed-off-by: Miquel Sabaté Solà <mssola@mssola.com> | ||||
| * | Improve the description of runrom | Miquel Sabaté Solà | 4 days | 1 | -11/+29 |
| | | | | | Signed-off-by: Miquel Sabaté Solà <mssola@mssola.com> | ||||
| * | Add the runrom crate and the vnf library | Miquel Sabaté Solà | 10 days | 1 | -0/+32 |
| The vnf library supports the runrom crate and they both combined enable users to "run" a ROM file. This is basically an emulator, but with two key differences: 1. It is to be run programatically. That is, you are not expected to play games with this, but to run code by steps, start at a given address, run a function, etc. 2. It is headless: there are no graphics displayed on screen, nor sound being delivered. Thus, the target for both these things are developers, not players. This way developers can validate code paths without needing a full blown emulator. You can write tests with this and be able to run some checks as part of your testing infrastructure. Signed-off-by: Miquel Sabaté Solà <mssola@mssola.com> | |||||
 |
index : tools.nes | |
| Tools for NES/Famicom development. |
| aboutsummaryrefslogtreecommitdiff |