diff options
| author | Miquel Sabaté Solà <msabate@suse.com> | 2023-11-07 14:14:55 +0100 |
|---|---|---|
| committer | Miquel Sabaté Solà <mikisabate@gmail.com> | 2025-02-04 21:02:07 +0100 |
| commit | cb854722b9890c171f7d0600812a7e9a3a2a25c9 (patch) | |
| tree | 1d9bce62db538471b1c98970115999b8ff93b43e /README.md | |
| parent | 988332816972638adfa8000dd7e1a474c5fea424 (diff) | |
| download | code.nes-cb854722b9890c171f7d0600812a7e9a3a2a25c9.tar.gz code.nes-cb854722b9890c171f7d0600812a7e9a3a2a25c9.zip | |
basics: Add an example on UNROM
Signed-off-by: Miquel Sabaté Solà <msabate@suse.com>
Diffstat (limited to 'README.md')
| -rw-r--r-- | README.md | 11 |
1 files changed, 11 insertions, 0 deletions
@@ -20,6 +20,17 @@ NES memory. A safe bet is to go with either [Mesen](https://github.com/SourMesen/Mesen2/), which provide tools like RAM watchers or a full debugger. +Notice that I will use some terms without actually introducing them. That is, I +expect you to go over the [NES Dev +wiki](https://www.nesdev.org/wiki/Nesdev_Wiki) for glossary or for full +documentation on the stuff being shown here. For example, if I am writing an +example code using the UNROM or the MMC1 chips, I assume that you will go over +the [NES Dev wiki](https://www.nesdev.org/wiki/Nesdev_Wiki) for details on what +these chips actually are or how they were used. That is, if you find that on a +bunch of comments I write stuff like "memory mapper", "MMC3 chip", "OAM" or +stuff like that, just go to the [NES Dev +wiki](https://www.nesdev.org/wiki/Nesdev_Wiki) to get a better picture. + The examples are distributed like this: - `basics`: simple examples which cover basic stuff for NES development. These |
