tmerritt/disasm
1
0 Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
Files
691b2bc23ca267436de0dcc424e42f65d4b2f5d8
disasm/NROM/Duck Hunt (JUE)/duckhunt_label_map.tsv
T
tmerrittandClaude Opus 4.8 49e117bfcc Fix Pass 3 symbol application and add promotion criteria to PROMPTS.md 
- Apply symbols.inc hardware register names to Defender 2 (U) (51 operands)
- Apply symbols.inc hardware register names to Donkey Kong 3 (JUE) (36 operands)
- Add APU register symbols (-) to Defender 2 (U) and Donkey Kong 3 (JUE) symbols.inc
- Apply symbols to Donkey Kong Jr. Math (U) (80 operands: 11 single + 69 hardware)
- Apply symbols to Excitebike (JU) (786 operands: 785 single + 1 hardware)
- Add promotion criteria to PROMPTS.md: symbol/local substitution,
  ROM-specific semantic naming, and verification checklist

Add branch/jump target naming requirement to PROMPTS.md

All branches and jumps must target symbolic labels with descriptive names
derived from program flow role (e.g., _Loop, _Next, _Done, _Store, _Return),
never raw address literals. Adds criterion 8 to verification checklist.

Rename all OVERVIEW.md to README.md; add root README content to top-level

- Rename all OVERVIEW.md files to README.md throughout the repo (47 files)
- Prepend README.md content to top-level OVERVIEW.md before rename
- Fix apply_symbols.py NAME_RE regex to handle spaced assignments
- Apply symbols.inc to Defender 2 (U) (51 hardware operands)
- Apply symbols.inc to Donkey Kong 3 (JUE) (36 hardware operands)
- Apply symbols.inc to Donkey Kong Jr. Math (U) (80 operands: 11 single + 69 hardware)
- Apply symbols.inc to Excitebike (JU) (786 operands: 785 single + 1 hardware)
- Add missing Zp18/FrameCounter aliases to Excitebike prg.s
- Build all 27 top-level projects: byte-identical

Promote Donkey Kong Jr. Math back to _wip tier

Moves code from `copilot` folder and verifies each builds after

Add pre-commit hook for byte-identical verification

Add .git/hooks/pre-commit that runs 'make' then 'make clean' in each
project directory before committing. This ensures every project builds
byte-identical before any commit is accepted.

Also includes all file moves from the Donkey Kong Jr. Math (U) demotion
and other file restructuring from the session.

moves code out of copilot folder, its all AI generated.
Moves NROM games into NROM folder

removes copilot folder from Lunar Pool
Adds makefile to build all projects recursively

Updates docs to reflect changes in layout

Repromotes Donkey Kong Jr Math
Repromotes Excitebike
Promotes Popeye (JU) (PRG 1)
Updates Makefile to provide summary of build failure/success

Promote Raid on Bungeling Bay (U): Pass 2/3 partial, whole-ROM byte-identical

Move _wip/NROM/Raid on Bungeling Bay (U) to NROM/ and switch the build
from a PRG-only compare to a whole-ROM one:

  - header.s/chr.s added (one-line .incbin of header.bin / chr.bin)
  - linker.cfg gains HEADER ($0000, $0010) and CHR ($0000, $2000)
    areas ahead of PRG ($C000, $4000)
  - rom.nes symlink to the space-containing original ROM name
  - Makefile builds header.o/prg.o/chr.o into reconstructed.nes and
    compares it against rom.nes ('Byte-identical ROM verified.')
  - one leftover neutral indirect operand jmp (Zp01) at $E2EC becomes
    jmp (IndDispatch01); apply_symbols.py reports 0 substitutions pending

README.md / TODO.md / AGENTS.md updated: 29 promoted, 7 in _wip/.

Pac-Man (U): Pass 2 complete (label renaming) + Pass 3 partial (ZP aliases, table names)

Pass 2 — fresh map derived from the committed split, not from any drafted
map (the drafted maps in other projects were audited and found not
applicable):

  - all 194 address-derived Label_XXXX definitions renamed to semantic
    routine-entry names plus <Routine>_<Role>_<addr> internal branch
    targets; zero Label_ remains
  - all 49 jsr/jmp call sites resolved from raw $XXXX to labels; zero
    raw $XXXX call operands remain
  - routinemap.tsv / derived_names.tsv record the derivation

Pass 3 (partial):

  - 15 proven semantic zero-page aliases added to locals.inc
    (GameState, NmiFlag, ScrollX/Y, PpuCtrlShadow, OamDmaPage,
    CocktailModeFlag, ActivePlayerFlag, GameplaySuspended, FrameCounter,
    StateTimer, Player1/2Input, ActiveInput, CopyrightVerified)
  - 112 operands substituted into prg.s (11 single + 101 hardware)
  - key data tables named: ProgrammerSig ($C0EB), GameStateDispatchTable
    ($C253), TitleScreenData ($C2FD), EntityPtrTable ($D912),
    AudioCommandTable ($EFDD)

Also corrects the README's claim that the RESET vector points at padding:
$FF00 holds real boot code (sei/cld, PPU off, double vblank wait, then
jmp ColdStart at $C042).

.gitignore: ignore reconstructed_prg.bin (build artifact of the _wip
Makefiles; '**/reconstructed.*' does not match the underscore form).

Promote Pac-Man (U): Pass 2/3 complete, whole-ROM byte-identical

Move _wip/NROM/Pac-Man (U) to NROM/ and switch the build from a PRG-only
compare to a whole-ROM one:

  - header.s/chr.s added (one-line .incbin of header.bin / chr.bin)
  - linker.cfg gains HEADER ($0000, $0010) and CHR ($0000, $2000)
    areas ahead of PRG ($C000, $4000)
  - rom.nes symlink to 'Pac-Man (U) [!].nes' (the original ROM name
    contains a space and brackets)
  - Makefile builds header.o/prg.o/chr.o into reconstructed.nes and
    compares it against rom.nes
  - reconstructed.nes is 24,592 bytes, MD5 a69d310f8cae9397fbd39f204672b5c7
    - equal to the original ROM; the header/prg/chr splits were checked
    against the original before promotion and are byte-exact

Pass 3 residue closed.  The last 7 multi-alias zero-page operands are
resolved per site through a new sites.tsv, each proven from context
rather than guessed:

  - jmp ($0010) at $C250/$D3CA/$D90F/$D9B6 -> (DispatchPtrLo); each
    is immediately preceded by sta DispatchPtrLo/sta DispatchPtrHi
  - jmp ($00FE) at $EFDA -> (AudioHandlerPtrLo); preceded by
    sta AudioHandlerPtrLo/sta AudioHandlerPtrHi
  - sta a:$0000,y at $C048/$C089 -> a:Zp00,y; the literal zero-page
    base in the two ZP clear loops, so the neutral name is used rather
    than the semantic WorkPtrLo.  The 'a:' prefix survives the
    substitution, so the bytes stay 99 00 00 (sta abs,Y)

apply_symbols.py now reports 119 operands substituted (101 hardware,
11 single-name, 7 site) and 0 residue.

New tool _tools/align_audit_comments.py: re-aligns the audit comment to
column 35 after a substitution lengthens an operand (nesdis.py pads each
instruction to 31 characters).  Whitespace-only, so the byte identity
cannot change.  405 lines re-aligned in this project; all 2,387 audit
comments still match prg.bin at the stated PRG offset, 0 mismatches.

Docs: root README.md / TODO.md / AGENTS.md updated - 30 promoted, 6 in
_wip/; a per-project detail entry for Pac-Man (U) added; the stale
'Donkey Kong 3 (JUE) has no README.md' claim corrected (it has a
318-line one).

Promote Raid on Bungeling Bay (U) [a2]: Pass 3 complete, whole-ROM byte-identical

Move _wip/NROM/Raid on Bungeling Bay (U) [a2] to NROM/ and switch the build
from a PRG-only compare to a whole-ROM one:

  - header.s/chr.s added (one-line .incbin of header.bin / chr.bin)
  - linker.cfg gains HEADER ($0000, $0010) and CHR ($0000, $2000)
    areas ahead of PRG ($C000, $4000)
  - rom.nes symlink to 'Raid on Bungeling Bay (U) [a2].nes' (the original
    ROM name contains spaces and brackets)
  - reconstructed.nes is 24,592 bytes, MD5 659d340a1e9d420eee28df13319b0094
    - equal to the original ROM; the header/prg/chr splits were checked
    against the original before promotion and are byte-exact

Pass 3 - 15 semantic zero-page aliases, each applied only at the sites
where its role is proven:

  - PpuCtrlShadow ($C2), 15 sites: the reset entry primes it right after
    'sta PPUCTRL', and every other use is an ora/and/eor followed by
    'sta PPUCTRL'
  - NmiPathSelector ($C4), 5 sites: written 1 at $C3E9 and 0 at $C962
  - GameState ($D6), 6 sites: 'cmp #$02' and used as an index at $C4C7
  - FrameSubCounter ($55), 6 sites: set to $0A at $C520, decremented per
    NMI at $C07B
  - PrngPeriodCounter ($EA) / PrngSeedB ($EB) / PrngState ($EC), 13 sites:
    the PRNG state
  - PtrLo ($00) / PtrHi ($01), 8 sites: the 16-bit pair $1C13 and $1610
    compared at $E785/$E791
  - IndDispatch01 ($01) / IndDispatch02 ($02), 3 sites: the computed
    dispatch at $E2EC
  - IndDispatch1B ($1B) / IndDispatch1C ($1C), 6 sites: the dispatch at
    $E7A3
  - IndDispatch17 ($17) / IndDispatch19 ($19): the dispatches at $E79D
    and $E7A0

Addresses that carry two names keep the neutral ZpXX name where the other
role applies - $01 is PtrHi at the 16-bit compare and IndDispatch01 at the
dispatch; $17 is IndDispatch17 at the dispatch and Zp17 for the absolute
RAM $0017 store in the copy loop at $E895/$E8D0.

New tool _tools/apply_zp_aliases.py does the per-site substitution:
apply_symbols.py only rewrites *numeric* operands, so it cannot rename an
operand that is already written as a neutral ZpXX name.  The tool keeps the
ca65 'a:' prefix (dropping it would turn 'sta a:Zp17,y' into a zero-page
store and change the bytes) and rewrites only the operand token, so the
audit comment survives byte for byte.

Naming correction in the promoted sibling.  Finishing this dump showed that
$EA was misnamed 'VBlankWaitCounter': the routine at $C412 is the game's
pseudo-random generator (the classic eor/asl/php/lsr/plp/rol scrambler,
called from thirteen gameplay sites, twice in a row at $CDF4/$CDF9 with the
second result masked #$07), so $EA is the scrambler's phase counter.
Renamed PrngPeriodCounter in both dumps and named $EB/$EC PrngSeedB /
PrngState.  The sibling's two 'sta a:IndDispatch17,y' operands were also
wrong - they are absolute stores to RAM $0017, not the dispatch pointer -
and are now 'a:Zp17,y', matching the file's 'a:' = absolute convention.

Audit-comment alignment re-done with _tools/align_audit_comments.py (1,040
lines here, 1,080 in the sibling).  Both files still match prg.bin at every
stated PRG offset: 5,467 and 5,483 audit comments, 0 mismatches.

Docs: root README.md / TODO.md / AGENTS.md updated - 31 promoted, 5 in
_wip/; per-project detail entries added for both Raid dumps.

Promote Pac-Man (Tengen) (U): Pass 2/3 from scratch, whole-ROM byte-identical

Move _wip/NROM/Pac-Man (Tengen) (U) to NROM/ and switch the build from a
PRG-only compare to a whole-ROM one:

  - header.s/chr.s added (one-line .incbin of header.bin / chr.bin)
  - linker.cfg gains HEADER ($0000, $0010) and CHR ($0000, $2000)
    areas ahead of PRG ($C000, $4000)
  - rom.nes symlink to 'Pac-Man (Tengen) (U) [!].nes'
  - reconstructed.nes is 24,592 bytes, MD5 d34e7a74d8d2c231b6cc601210e28ad0
    - equal to the original ROM; the header/prg/chr splits were checked
    against the original before promotion and are byte-exact

Disassembled from scratch.  No name, map or file was carried over from the
sibling 'Pac-Man (U)' dump; the map was derived from this dump's own
committed split and the two were only compared afterwards.

Pass 2 (new tool _tools/apply_pass2_map.py):
  - all 194 Label_XXXX definitions renamed to semantic routine entries plus
    <Routine>_<Role> branch targets; zero Label_ remains
  - all 48 raw $XXXX jsr/jmp operands resolved to labels; zero raw $XXXX
    call or branch operands remain
  - the map is in routinemap.tsv

Pass 3:
  - 30 semantic zero-page aliases, each applied only at the sites where its
    role is proven (per-site choice in sites.tsv; the addresses that carry
    two roles keep the neutral ZpXX name elsewhere).  _tools/
    derive_zp_aliases.py records how the set was derived, and locals.inc
    records the reason for every remaining neutral slot
  - 28 data tables named (new tool _tools/name_data_region.py), including
    CharacterDataTable ($C66A) and CharacterNameStrings ($C67E), where the
    ROM itself names Blinky, Pinky, Inky and Clyde - which is why the four
    indexed entities are called ghosts and not 'actors'
  - apply_symbols.py reports 0 substitutions pending and 0 residue
  - audit-comment alignment re-done with _tools/align_audit_comments.py;
    all 2,479 audit comments still match prg.bin at the stated PRG offset

Pass 1 correction - six command handlers recovered (new tool
_tools/recode_region.py).  ScriptCommandTable ($EFDD) is read by the traced
instruction at $EFCC, and six of its entries point at $F00A, $F022, $F03A,
$F052, $F062 and $F072 - all of which the tracer had left as data, and two
of which it had mis-split across the 'jmp $EF61' at $F01F and $F04F.
Those 120 bytes are code here, decoded straight from the ROM; the six
handlers tile $F00A-$F081 exactly.  The same gap exists in the promoted
'Pac-Man (U)' dump, which has not been corrected - recorded in both READMEs.

Residue (documented, not guessed): the unreached main game logic at
$C45A-$C55F is still .byte data.  It is code - the tracer's own decoder
walks it cleanly and the dispatch table at $C511 points into it - but
nothing reaches it, so it cannot be entered without a guess.  The same gap
exists in the promoted 'Pac-Man (U)' dump.  Re-deriving it is a Pass 1 job;
a Mesen Code Data Logger capture is the tool the repo uses for it.

Docs: root README.md / TODO.md / AGENTS.md updated - 32 promoted, 4 in
_wip/; a per-project detail entry added for the Tengen dump.

Promote Pyramid (U): Pass 1 corrected, Pass 2/3 complete, whole-ROM byte-identical

Move _wip/NROM/Pyramid (U) to NROM/ and switch the build from a PRG-only
compare to a whole-ROM one:

  - header.s/chr.s added (one-line .incbin of header.bin / chr.bin)
  - linker.cfg gains HEADER ($0000, $0010) and CHR ($0000, $2000)
    areas ahead of PRG ($C000, $4000)
  - rom.nes symlink to 'Pyramid (U) (Sachen).nes'
  - reconstructed.nes is 24,592 bytes, MD5 aa285ff17f25dd05da5996b7466c59e2
    - equal to the original ROM; the header/prg/chr splits were checked
    against the original before promotion and are byte-exact

Pass 1 correction - the committed split was a strict subset of the correct
one.  This game dispatches through 'jmp' trampoline tables that live
*inside* the data regions, and the tracer cannot follow a jmp there, so
828 bytes of code were still marked as data.  Four such tables were found
($C01E 3 entries, $C02A 6, $C042 2, $C054 5) plus ten more entries at
$C000-$C01B; all sixteen targets decode as valid instructions.  Seeding
them, the $C800 boot mainline and six further code starts recovers the
whole lot, plus a five-byte stub at $DF89 (lda $33 / jmp $DECB) that sat
in a hole between two routines.  The re-trace loses NO committed code byte
and takes the split from 34.5% to 39.6% (3,130 instructions / 6,493 code
bytes).  'make regen' reproduces it, so the split stays verifiable.

Pass 2 - a fresh map derived from this dump's own committed split:
  - 428 Label_XXXX definitions renamed; zero Label_ residue
  - 320 raw $XXXX jsr/jmp operands resolved; zero raw $XXXX branch
    operands remain
  - 431 routine entries and the 32 data blocks named from the code
  - the internal branch-target names are derived mechanically from the
    branch that reaches them by the new _tools/derive_branch_names.py
    (beq -> OnZero, bne -> OnNonzero, bcc/bcs -> the carry cases, a
    backwards branch -> Loop)
  - recorded in routinemap.tsv

Pass 3:
  - 24 semantic zero-page aliases, each applied only where its role is
    proven; the 57 slots that stay neutral are each listed with the reason
    in locals.inc (the neutral set lives in zp_aliases.inc so that
    'make regen' can rebuild locals.inc from prg.bin)
  - 32 data tables named - TaskVectorTable1/2, LevelScriptData,
    MusicPeriodTable, SoundEnvelopeTable, the actor tables - recorded in
    data_region_names.tsv
  - apply_symbols.py reports 0 substitutions pending and 0 residue; no
    hardware register is left as a raw literal
  - the audit comments are now canonical on every line, data included
    (the old file carried only 'PRG:$xxxx' on its 1,358 data lines);
    all 3,762 audit comments match prg.bin at their stated PRG offset

Kept as-is, not 'cleaned up':
  - sta $4100 stays a raw operand.  The iNES header claims mapper 0 but
    the boot code writes past the NES register space; the ROM does not
    explain it, so it is recorded rather than guessed
  - the 'A'/'V' check on RAM $0120/$0121 and its seed/clear routines
    are named for what they do, not for what they are for
  - the ninth entry of the $C3A6 task vector table ($D820) is a junk
    slot and stays data

Docs: root README.md / TODO.md / AGENTS.md updated - 33 promoted, 3 in
_wip/; a per-project detail entry added.

Hogan's Alley (JU): Pass 1 correction, Pass 2, Pass 3, promoted to NROM/

The light-gun game whose engine dispatches through *inline* tables:
`IndirectCall` at $C34D pops the return address of the `jsr` that called
it and reads a 16-bit handler pointer from the word that follows, so all
six handler tables ($C124 19 entries, $C219 4, $C89C 14, $CDD1 1, $D234 2,
$D3D6 14) live inside the code stream and the static tracer cannot follow
them.

Pass 1 correction.  The committed split was a strict subset of the correct
one -- 41.8% of the PRG was classified as code.  A fresh Mesen Code Data
Logger capture was merged with the four captures already in the folder
(hogans_merged.cdl, the OR of five per-byte flag arrays, 6,544 code bytes)
and _tools/cdl_reclass.py rewrote the split to match what the CPU actually
fetched: 1,216 bytes moved from data to code, five the other way, 59 labels
emitted.  The split is now 49.1% code (3,950 instructions, 8,041 bytes).
The four branch targets the reclassifier could not prove were turned into
labels by the new _tools/resolve_raw_branches.py.

Pass 2.  206 routine entries hand-named from this dump's own code and 413
internal branch targets derived mechanically by _tools/derive_branch_names.py:
630 Label_XXXX definitions gone, 484 raw $XXXX call operands resolved, 15
call targets the tracer had never labelled given a label.  Recorded in
routinemap.tsv.  No SubC<addr> residue was needed -- every entry the engine
reaches is named after what it does.

Pass 3.  60 semantic zero-page aliases, each applied only where its role is
proven (zp_aliases.inc, zp_alias_sites.tsv); the slots that stay neutral are
each listed with the reason.  All 34 data blocks named
(data_region_names.tsv).  apply_symbols.py reports 1 residue: `sta a:$00B4,y`
at $C203, the same address as Zp40/ActorPalette but forced to absolute
addressing, so it must stay numeric.

Promotion.  header.s, chr.s and a HEADER/PRG/CHR linker.cfg added, rom.nes
symlinked to the original ROM; the whole-ROM cmp passes on the first
promoted build.  There is deliberately no `make regen` target: the Pass 1
split here is the static trace corrected by a CDL capture, and the base the
correction was applied to is not what the current _tools/nesdis.py
produces, so prg.s is the maintained source of truth.

Tools changed:
  nesdis.py             --split/--note/--provenance options, so a data
                          region can carry its own name and explanation;
                          a forced-data address is no longer reported as a
                          recovered routine entry
  apply_pass2_map.py    can create the label for a call target the tracer
                          left unlabelled; no longer double-labels it
  apply_zp_aliases.py   --at-file, an address-based per-site list
  derive_branch_names.py keeps the map's own header instead of writing a
                          fixed one
  resolve_raw_branches.py  new: turns `bXX *+$NN` operands into labels
  build_hogans_map.py   new: the hand-written Pass 2 map builder

The existing regen pipelines (MUSCLE (U), Urban Champion (JU)) still
reproduce prg.s byte for byte.

Apply the symbols.inc register names at Pass 1; fix a dropped byte in cdl_reclass

nesdis.py now names the hardware registers as it renders the operands, so a
project's Pass 1 output already reads `lda PPUSTATUS` instead of `lda $2002`
and the Pass 3 apply_symbols.py step has nothing left to do for them.

  * nesdis.py --symbols FILE reads a symbols.inc-style file and substitutes
    the register names.  Only unambiguous entries in the $2000-$4017 window
    are used: $4017 is both JOY2 and APUFRAMECOUNTER, so it stays numeric
    and apply_symbols.py reports it as multi-alias residue, exactly as
    before.  The default is the symbols.inc next to --out, so a new project
    gets the names without asking; --no-symbols opts out.
  * The renderer records the operand's numeric value on the Insn, because
    operand_value() used to re-parse the operand text and could no longer
    read a name.
  * The controller bit masks in symbols.inc (PAD_A and friends) are
    constants, not addresses, and are still never substituted.

MUSCLE (U) and Urban Champion (JU) keep --no-symbols: their committed
prg.s was produced with the registers named by the Pass 3 apply_symbols.py
step, and the columns in those files reflect the in-place substitution.
Adding the missing apply_symbols.py step to both regen pipelines makes
them reproduce their committed prg.s byte for byte again - neither did
before this change (MUSCLE was 440 lines out, Urban Champion 772).

cdl_reclass.py had a bug that cost a byte: a region whose last source row
straddled the region's end was replaced by a regeneration of the region
only, so the tail of that row was dropped.  Mario Bros (JU) hit it at
$C595, where the rebuild came out one byte short and every label after it
shifted.  A region now covers the whole rows it replaces.

pass2.py reflow takes an optional column argument; the default is
unchanged (the ';' lands on the same column as before).

Mario Bros (JU): Pass 1 correction, Pass 2, Pass 3, promoted to NROM/

A two-player platformer whose handler tables are *inline*: the pointers sit
in the middle of the code stream, right after the `jsr` that reads them, so
the static tracer could never follow them.

Pass 1 correction.  The committed split was a strict subset of the correct
one -- only 72.0% of the PRG was classified as code.  A Mesen Code Data
Logger capture of this ROM (mario_mesen.cdl, 10,915 code bytes) showed
1,010 bytes the tracer had left as data were code; two branch targets the
capture never reached ($E4CB and $E639) were forced with --override for 57
more, so 1,067 bytes moved from data to code and 22 moved the other way.
The split is now 78.4% code (6,210 instructions, 12,847 bytes).  The three
branch targets the reclassifier could not prove were turned into labels by
_resolve_raw_branches.py, which now refuses to put a label on a `.byte` row.

Pass 2.  206 routine entries and 519 internal branch targets: 931
Label_XXXX definitions gone, 51 raw $XXXX call operands resolved and 12 call
targets the tracer had never labelled given a label.  Zero SubC residue --
the 185 entries a previous session had left as address-derived residue were
all named from this dump's own code.  Recorded in routinemap.tsv.

Pass 3.  25 semantic zero-page aliases, each applied only where its role is
proven (zp_aliases.inc); the slots that stay neutral are each listed with the
reason.  35 data tables named -- GameStateHandlerTable, EnemyBehaviourTable,
EnemyScriptTable, EnemyTypePointerTable, SoundRoutineTable,
NoteFrequencyTable and the rest -- and recorded in
data_region_names.tsv.  apply_symbols.py reports 0 residue.

Promotion.  header.s, chr.s and a HEADER/PRG/CHR linker.cfg added, rom.nes
symlinked to the original ROM; the whole-ROM cmp passes on the first
promoted build.  There is deliberately no `make regen` target: the Pass 1
split here is the static trace corrected by a CDL capture, and the base the
correction was applied to is not what the current _tools/nesdis.py
produces, so prg.s is the maintained source of truth.

Tools:
  apply_pass2_map.py     renames a label of any spelling -- SubC<addr> is
                          the honest residue form -- and its references
                          follow it; one combined pattern, so a 16,000-line
                          file does not need a substitution per label
  resolve_raw_branches.py refuses to label a data row
  build_mario_map.py      new: the hand-written Pass 2 map builder

Remove the old _wip/NROM/Mario Bros (JU) folder (promoted to NROM/)

Mario Bros (JU): add the promoted-tier header, CHR, rom.nes symlink and zero-page aliases

Moves _ROMS/<ROM> into _wip/<MAPPER>/<ROM>

Sync the docs and the skeleton tool with the 857-project _wip tier

The _wip/ tier now holds 857 projects across 30 mapper folders, all
building byte-identical for the whole ROM.  README.md, TODO.md and
AGENTS.md still described the old 39-project tier, so bring them in line
with WIP.md, which carries the tier's index.

The tier is no longer 39 projects of NROM-256 with a 16/32 KB PRG:
only two projects have a 16 KB PRG, 151 have 32 KB, 523 have 128 KB and
one has 1.5 MB, so most of it is a banked mapper whose image does not fit
the 6502's address space.  Those projects link their MEMORY areas at .nes
file offsets rather than CPU addresses, which is the only option and the
honest model; the 39 older projects keep the CPU-address layout because
their PRG really is one contiguous window.

make_skeleton.py gains the two layouts (--layout flat|cpu), the board
name for the mapper, and a fix for find_rom() mistaking the build
output reconstructed.nes for the source ROM.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-10-20 16:44:06 -04:00

273 lines
9.9 KiB
Plaintext
Raw Blame History

label Label_C000 Reset
label Label_C002 WaitVBlank
label Label_C01E ClearZeropage
label Label_C02C InitGameState
label Label_C035 WaitVBlank2
label Label_C046 InitPPU
label Label_C056 InitVariables
label Label_C061 MainGameLoop_1
label Label_C06B GameModeCheck_1
label Label_C06B GameModeCheck_3
label Label_C06E GameplayFrame
label Label_C07C MainGameLoopEntry
label Label_C07C MainGameLoop_3
label Label_C080 CallInitRound
label Label_C086 NmiHandler
label Label_C0A6 NmiFrameEnd
label Label_C0B3 GameModeDispatcher
label Label_C0BA TitleScreenMode
label Label_C0BA TitleScreenLoop
label Label_C0BC CheckZp16
label Label_C0BE CheckZp16_2
label Label_C0C0 CheckRoundIndex_1
label Label_C0C0 CheckRoundIndex_3
label Label_C0C5 CheckRoundIndex_4
label Label_C0C5 CheckRoundIndex_5
label Label_C0C5 CheckRoundIndex_6
label Label_C0CD CheckRoundIndex_7
label Label_C0CD CheckRoundIndex_8
label Label_C0CF CheckRoundIndex_9
label Label_C0CD CheckRoundIndex_10
label Label_C0CF CheckRoundIndex_11
label Label_C0CD CheckRoundIndex_12
label Label_C0CD CheckRoundIndex_13
label Label_C0CD CheckRoundIndex_14
label Label_C0CD CheckRoundIndex_15
label Label_C0CD CheckRoundIndex_16
label Label_C0CD CheckRoundIndex_17
label Label_C0CD CheckRoundIndex_18
label Label_C0CD CheckRoundIndex_19
label Label_C0DF InitializeRoundData
label Label_C0E1 InitializeDuckDataLoop
label Label_C0E9 UpdatePPUMask
label Label_C0ED UpdatePPUMask2
label Label_C0F0 UpdatePPUMask3
label Label_C0F2 UpdateZp25
label Label_C0F8 JumpToC112
label Label_C0FF UpdateZp09
label Label_C0FF UpdateZp09_2
label Label_C112 UpdateGameState
label Label_C11E UpdateGameState2
label Label_C123 UpdateGameState3_1
label Label_C14E UpdateGameState3_3
label Label_C154 UpdateGameState4_1
label Label_C16A UpdateGameState4_3
label Label_C18D UpdateGameState5
label Label_C1EA UpdateGameState6_1
label Label_C1FC UpdateGameState7
label Label_C22B UpdateSprites_1
label Label_C217 UpdateGameState6_3
label Label_C22B UpdateSprites_3
label Label_C22B UpdateSprites_4
label Label_C232 UpdateSprites2_1
label Label_C249 UpdateSprites2_3
label Label_C263 UpdateSprites3
label Label_C284 UpdateController
label Label_C291 UpdateController2
label Label_C2B9 UpdateController3
label Label_C2BF UpdateController4_1
label Label_C2BF UpdateController4_3
label Label_C2BF UpdateController4_4
label Label_C2BF UpdateController4_5
label Label_C2BF UpdateController4_6
label Label_C2BF UpdateController4_7
label Label_C2BF UpdateController4_8
label Label_C2BF UpdateController4_9
label Label_C2BF UpdateController4_10
label Label_C2BF UpdateController4_11
label Label_C2BF UpdateController4_12
label Label_C2BF UpdateController4_13
label Label_C2BF UpdateController4_14
label Label_C2BF UpdateController4_15
label Label_C2BF UpdateController4_16
label Label_C2BF UpdateController4_17
label Label_C2BF UpdateController4_18
label Label_C2BF UpdateController4_19
label Label_C2BF UpdateController4_20
label Label_C2BF UpdateController4_21
label Label_C2BF UpdateController4_22
label Label_C2BF UpdateController4_23
label Label_C2BF UpdateController4_24
label Label_C2BF UpdateController4_25
label Label_C2BF UpdateController4_26
label Label_C2BF UpdateController4_27
label Label_C2BF UpdateController4_28
label Label_C2BF UpdateController4_29
label Label_C2BF UpdateController4_30
label Label_C2BF UpdateController4_31
label Label_C2BF UpdateController4_32
label Label_C2BF UpdateController4_33
label Label_C2BF UpdateController4_34
label Label_C2BF UpdateController4_35
label Label_C2BF UpdateController4_36
label Label_C2BF UpdateController4_37
label Label_C2BF UpdateController4_38
label Label_C2BF UpdateController4_39
label Label_C2BF UpdateController4_40
label Label_C2BF UpdateController4_41
label Label_C2BF UpdateController4_42
label Label_C2BF UpdateController4_43
label Label_C2BF UpdateController4_44
label Label_C2BF UpdateController4_45
label Label_C2BF UpdateController4_46
label Label_C2BF UpdateController4_47
label Label_C2BF UpdateController4_48
label Label_C2BF UpdateController4_49
label Label_C2BF UpdateController4_50
label Label_C2BF UpdateController4_51
label Label_C2BF UpdateController4_52
label Label_C2BF UpdateController4_53
label Label_C2BF UpdateController4_54
label Label_C2BF UpdateController4_55
label Label_C2BF UpdateController4_56
label Label_C2BF UpdateController4_57
label Label_C2BF UpdateController4_58
label Label_C2BF UpdateController4_59
label Label_C2BF UpdateController4_60
label Label_C2BF UpdateController4_61
label Label_C2BF UpdateController4_62
label Label_C2BF UpdateController4_63
label Label_C2BF UpdateController4_64
label Label_C2BF UpdateController4_65
label Label_C2BF UpdateController4_66
label Label_C2BF UpdateController4_67
label Label_C2BF UpdateController4_68
label Label_C2BF UpdateController4_69
label Label_C2BF UpdateController4_70
label Label_C2BF UpdateController4_71
label Label_C2BF UpdateController4_72
label Label_C2BF UpdateController4_73
label Label_C2BF UpdateController4_74
label Label_C2BF UpdateController4_75
label Label_C2BF UpdateController4_76
label Label_C2BF UpdateController4_77
label Label_C2BF UpdateController4_78
label Label_C2BF UpdateController4_79
label Label_C2BF UpdateController4_80
label Label_C2BF UpdateController4_81
label Label_C2BF UpdateController4_82
label Label_C2BF UpdateController4_83
label Label_C2BF UpdateController4_84
label Label_C2BF UpdateController4_85
label Label_C2BF UpdateController4_86
label Label_C2BF UpdateController4_87
label Label_C2BF UpdateController4_88
label Label_C2BF UpdateController4_89
label Label_C2BF UpdateController4_90
label Label_C2BF UpdateController4_91
label Label_C2BF UpdateController4_92
label Label_C2BF UpdateController4_93
label Label_C2BF UpdateController4_94
label Label_C2BF UpdateController4_95
label Label_C2BF UpdateController4_96
label Label_C2BF UpdateController4_97
label Label_C2BF UpdateController4_98
label Label_C2BF UpdateController4_99
label Label_C2BF UpdateController4_100
label Label_C2BF UpdateController4_101
label Label_C2BF UpdateController4_102
label Label_C2BF UpdateController4_103
label Label_C2BF UpdateController4_104
label Label_C2BF UpdateController4_105
label Label_C2BF UpdateController4_106
label Label_C2BF UpdateController4_107
label Label_C2BF UpdateController4_108
label Label_C2BF UpdateController4_109
label Label_C2BF UpdateController4_110
label Label_C2BF UpdateController4_111
label Label_C2BF UpdateController4_112
label Label_C2BF UpdateController4_113
label Label_C2BF UpdateController4_114
label Label_C2BF UpdateController4_115
label Label_C2BF UpdateController4_116
label Label_C2BF UpdateController4_117
label Label_C2BF UpdateController4_118
label Label_C2BF UpdateController4_119
label Label_C2BF UpdateController4_120
label Label_C2BF UpdateController4_121
label Label_C2BF UpdateController4_122
label Label_C2BF UpdateController4_123
label Label_C2BF UpdateController4_124
label Label_C2BF UpdateController4_125
label Label_C2BF UpdateController4_126
label Label_C2BF UpdateController4_127
label Label_C2BF UpdateController4_128
label Label_C2BF UpdateController4_129
label Label_C2BF UpdateController4_130
label Label_C2BF UpdateController4_131
label Label_C2BF UpdateController4_132
label Label_C2BF UpdateController4_133
label Label_C2BF UpdateController4_134
label Label_C2BF UpdateController4_135
label Label_C2BF UpdateController4_136
label Label_C2BF UpdateController4_137
label Label_C2BF UpdateController4_138
label Label_C2BF UpdateController4_139
label Label_C2BF UpdateController4_140
label Label_C2BF UpdateController4_141
label Label_C2BF UpdateController4_142
label Label_C2BF UpdateController4_143
label Label_C2BF UpdateController4_144
label Label_C2BF UpdateController4_145
label Label_C2BF UpdateController4_146
label Label_C2BF UpdateController4_147
label Label_C2BF UpdateController4_148
label Label_C2BF UpdateController4_149
label Label_C2BF UpdateController4_150
label Label_C2BF UpdateController4_151
label Label_C2BF UpdateController4_152
label Label_C2BF UpdateController4_153
label Label_C2BF UpdateController4_154
label Label_C2BF UpdateController4_155
label Label_C2BF UpdateController4_156
label Label_C2BF UpdateController4_157
label Label_C2BF UpdateController4_158
label Label_C2BF UpdateController4_159
label Label_C2BF UpdateController4_160
label Label_C2BF UpdateController4_161
label Label_C2BF UpdateController4_162
label Label_C2BF UpdateController4_163
label Label_C2BF UpdateController4_164
label Label_C2BF UpdateController4_165
label Label_C2BF UpdateController4_166
label Label_C2BF UpdateController4_167
label Label_C2BF UpdateController4_168
label Label_C2BF UpdateController4_169
label Label_C2BF UpdateController4_170
label Label_C2BF UpdateController4_171
label Label_C2BF UpdateController4_172
label Label_C2BF UpdateController4_173
label Label_C2BF UpdateController4_174
label Label_C2BF UpdateController4_175
label Label_C2BF UpdateController4_176
label Label_C2BF UpdateController4_177
label Label_C2BF UpdateController4_178
label Label_C2BF UpdateController4_179
label Label_C2BF UpdateController4_180
label Label_C2BF UpdateController4_181
label Label_C2BF UpdateController4_182
label Label_C2BF UpdateController4_183
label Label_C2BF UpdateController4_184
label Label_C2BF UpdateController4_185
label Label_C2BF UpdateController4_186
label Label_C2BF UpdateController4_187
label Label_C2BF UpdateController4_188
label Label_C2BF UpdateController4_189
label Label_C2BF UpdateController4_190
label Label_C2BF UpdateController4_191
label Label_C2BF UpdateController4_192
label Label_C2BF UpdateController4_193
label Label_C2BF UpdateController4_194
label Label_C2BF UpdateController4_195
label Label_C2BF UpdateController4_196
label Label_C2BF UpdateController4_197
label Label_C2BF UpdateController4_198
label Label_C2BF UpdateController4_199
label Label_C2BF UpdateController4_200
label Label_C2BF UpdateController4_201
label Label_C2BF UpdateController4_202
label Label_C2BF UpdateController4_203
label Label_C2BF UpdateController4_204
label Label_C2BF UpdateController4_205
label Label_C2BF UpdateController4_206
label_Label_C2BF UpdateController4
Reference in new issue View Git Blame Copy Permalink