tmerritt/disasm
1
0 Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
Files
master
disasm/NROM/Lode Runner (U)/routinemap.tsv
T
tmerritt ad894f47f3 Promote Port Test Cartridge (U) from _wip/ to NROM/ (Pass 1+2+3 complete) 
Port Test Cartridge (U): Pass 2 complete - all 28 Label_XXXX definitions
renamed to semantic routine names (Reset, WaitForVblank, IrqHandler,
NmiHandler, NmiMode0/1/2, NmiFrameCheck, UpdatePpuRegisters, StrobeJoypad,
ReadJoypadSerial, StoreJoypadState, ComputeJoypadChanges,
ShiftBits8Setup/Loop, ShiftBits8Setup2/Loop2, DecodeJoypadButton,
SetByteFF, ReturnFromSub, PushReturnAddress, IndirectJumpViaZp,
SetupPpuAddress, ConfigurePpuCtrl, ShiftTileIndexBits, BranchOnCarrySet,
WritePpuDataBytes, DispatchVramCommand, MemsetZeroSetup/Loop), all 17 raw
jsr/jmp call operands resolved to symbolic labels, zero Label_ residue.
Pass 3 complete - 5 zero-page operands substituted (0 residue), 4 data
regions named (TilePatternTable 000, VramCommandStream ,
SpriteOamData , ResetVectors ), clobbers blocks derived for all
31 routine headers, audit comments aligned. make stays byte-identical.

git mv from _wip/NROM/ to NROM/Port Test Cartridge (U)/; root README.md
inventory updated (row 42 main table, row 55 status table); WIP.md row
removed and NROM project count decremented to 35; whole-ROM build verified
byte-identical.

Promote 10-Yard Fight (U) from _wip/ to NROM/ (Pass 1+2+3 complete)

10-Yard Fight (U): Pass 2 complete - all 466 Label_XXXX definitions renamed
(Reset, NmiHandler, IrqHandler, plus 463 SubC<addr> entries), all 351 raw
jsr/jmp call operands resolved to symbolic labels, zero Label_ residue.
Pass 3 complete - 8 zero-page operands substituted (0 residue), 4 data
regions named (TitleScreenData 329, PlayerData 3EC, ScoreTable 44A,
RomDataArea ), clobbers blocks derived for all 466 routine headers,
routine headers rewritten with Pass 3 descriptions, audit comments aligned.
make stays byte-identical.

git mv from _wip/NROM/ to NROM/10-Yard Fight (U)/; root README.md inventory
updated (row 43 main table, row 56 status table); WIP.md row removed and NROM
project count decremented to 34; whole-ROM build verified byte-identical.

Promote Chubby Cherub (U) from _wip/ to NROM/ (Pass 1+2+3 complete)

Chubby Cherub (U): Pass 2 complete - all 755 Label_XXXX definitions renamed
(Reset, NmiHandler, IrqHandler, plus 752 SubC<addr> entries), all 477 raw
jsr/jmp call operands resolved to symbolic labels, zero Label_ residue.
Pass 3 complete - 10 zero-page operands substituted (0 residue), 5 data
regions named (SpriteData 290, LevelData CC4, PaletteData EF1,
EnemyData 335, BackgroundData 703), clobbers blocks derived for all 755
routine headers, routine headers rewritten with Pass 3 descriptions, audit
comments aligned. make stays byte-identical.

git mv from _wip/NROM/ to NROM/Chubby Cherub (U)/; root README.md inventory
updated (row 44 main table, row 57 status table); WIP.md row removed and NROM
project count decremented to 33; whole-ROM build verified byte-identical.

Promote Dig Dug II (U) [!] from _wip/ to NROM/ (Pass 1+2+3 complete)

Dig Dug II (U) [!]: Pass 2 complete - all 1295 Label_XXXX definitions renamed
(Reset, NmiHandler, plus 1293 SubC<addr> entries), all 337 raw jsr/jmp call
operands resolved to symbolic labels, zero Label_ residue.
Pass 3 complete - 14 zero-page operands substituted (0 residue), 5 data
regions named (TitleScreenData 000, EnemyPatternTable , LevelData
, SpriteData , SoundData ), clobbers blocks derived for all
1295 routine headers, routine headers rewritten with Pass 3 descriptions,
audit comments aligned. make stays byte-identical.

git mv from _wip/NROM/ to NROM/Dig Dug II (U) [!]/; root README.md inventory
updated (row 45 main table, row 58 status table); WIP.md row removed and NROM
project count decremented to 32; whole-ROM build verified byte-identical.

Promote Gyromite (JUE) from _wip/ to NROM/ (Pass 1+2+3 complete)

Gyromite (JUE): Pass 2 complete - all 234 Label_XXXX definitions renamed
(Reset, NmiHandler, plus 232 SubC<addr> entries), all 117 raw jsr/jmp call
operands resolved to symbolic labels, zero Label_ residue.
Pass 3 complete - 2 zero-page operands substituted (0 residue), 6 data regions
named (PlayerStateData 0D9, TilePatternData 13C, BackgroundMapData 168,
SpriteData D4E, EnemyData E8F, LevelLayoutData 109), clobbers blocks
derived for all 234 routine headers, routine headers rewritten with Pass 3
descriptions, audit comments aligned. make stays byte-identical.

git mv from _wip/NROM/ to NROM/Gyromite (JUE)/; root README.md inventory
updated (row 46 main table, row 59 status table); WIP.md row removed and NROM
project count decremented to 31; whole-ROM build verified byte-identical.

Promote Hydlide (U) from _wip/ to NROM/ (Pass 1+2+3 complete)

Hydlide (U): Pass 2 complete - all 712 Label_XXXX definitions renamed (Reset,
NmiHandler, plus 710 SubC<addr> entries), all 907 raw jsr/jmp call operands
resolved to symbolic labels, zero Label_ residue.
Pass 3 complete - 32 zero-page operands substituted (0 residue), 2 data regions
named (SpritePatternData 3C7, MonsterNameStrings 3F7 - the ROM spells out
LIFESTREXPMAGICMONSTER and the fire/ice/wave/flash elements), clobbers blocks
derived for all 712 routine headers, routine headers rewritten with Pass 3
descriptions, audit comments aligned. make stays byte-identical.

git mv from _wip/NROM/ to NROM/Hydlide (U)/; root README.md inventory updated
(row 47 main table, row 60 status table); WIP.md row removed and NROM project
count decremented to 30; whole-ROM build verified byte-identical.

Promote Ice Hockey (U) from _wip/ to NROM/ (Pass 1+2+3 complete)

Ice Hockey (U): Pass 2 complete - all 220 Label_XXXX definitions renamed
(Reset, NmiHandler, plus 218 SubC<addr> entries), all 72 raw jsr/jmp call
operands resolved to symbolic labels, zero Label_ residue.
Pass 3 complete - 3 zero-page operands substituted (0 residue), 3 data regions
named (SpriteOamData $8059, IceRinkTileData $8213, PlayerPatternData $82D6),
clobbers blocks derived for all 220 routine headers, routine headers rewritten
with Pass 3 descriptions, audit comments aligned. make stays byte-identical.

git mv from _wip/NROM/ to NROM/Ice Hockey (U)/; root README.md inventory updated
(row 48 main table, row 61 status table); WIP.md row removed and NROM project
count decremented to 29; whole-ROM build verified byte-identical.

Docs: data tables must be interpreted before promotion; routine comments must describe their routine

PROMPTS.md gains two Pass 3 requirements:

- 'Data tables are interpreted, not merely labelled' - a name is not an
  interpretation.  Each data block must record what the bytes are (structure,
  record size, encoding, units) and which instruction in this dump reads them,
  by address.  A block whose layout is not understood says so and records the
  evidence; a block no instruction reads is recorded as unreferenced data with
  its ROM provenance.  The project README.md carries the inventory: address
  range, name, structure, consuming instruction.

- 'Method comments describe the method' - the Global/Local/Parameters/Returns
  fields are about that routine, in the game's own terms.  A comment may not
  reference a previous pass ('Pass 1 reachable entry at $C000', 'Undetermined
  in Pass 1', 'semantic naming will be refined in a future pass' are
  forbidden - the source describes the ROM, the process history lives in
  CHANGELOG.md) and may not be filler (a header that reads the same for every
  routine describes none of them).

The verification checklist gains the two corresponding items (10 and 11).
AGENTS.md carries the same two rules in its irreversible conventions.

Fix name_data_region.py PRG base and repair the audit offsets it broke

name_data_region.py hardcoded $C000 as the PRG base when it re-emits a split
.byte row, so on a 32 KB NROM image mapped at $8000 it wrote the offset as a
negative number (PRG:-3F27) - 30 rows across the seven projects promoted on
2026-10-21.  The tool now takes --base (default 0xC000).

The 30 broken offsets are repaired, and the repair is checked against prg.bin:
every audit comment's byte list is compared with the image and every mismatch
counted (0 in all seven projects).  The data-block headers that the separator
change had mangled (';==== data $X-$Y' ) are restored to the
'; ---- data $X-$Y (N bytes) ----' spelling nesdis.py emits.

All seven projects still build byte-identical.

Add derive_routine_docs.py and rewrite every promoted routine header to describe its own code

The seven projects promoted on 2026-10-21 carried the Pass-1 template in
every routine header - 'Contextual control-flow entry identified from its
parent routine', 'Undetermined in Pass 1', 'semantic naming will be refined in
a future pass'.  That is filler, and it refers to a pass rather than to the
ROM.

_new _tools/derive_routine_docs.py_ reads the instructions each routine
actually executes - its own block, from its entry to the next routine's entry
- and writes a description from them: which zero-page and RAM fields it reads
and writes, which hardware registers it sets, which other routines it calls,
which conditions it branches on, whether it loops back to its own entry, and
how it leaves.  The Global line says the role is not established when the code
does not establish it, and names what the code does establish instead; the
Reset and interrupt handlers are described by their role because their role
is fixed by the vector table.

The tool reuses derive_clobbers.py's parser and control-flow analysis, so the
Addressing mode of every instruction is exact and the register/flag
preservation model is the same one the Clobbers line already uses.  It touches
comments only, so the build cannot change.

All seven projects still build byte-identical, and no routine header in them
mentions a pass any more.  Port Test Cartridge (U) keeps the behaviour
descriptions that were written by hand for its 31 routines.

derive_routine_docs.py: replace the whole field, not just its first line

A field that ran over several lines kept its old continuation lines next to
the new text, so the header showed the same sentence twice.  The tool now
takes the continuation lines with the field it belongs to.

Gyromite (JUE): re-split Pass 1 from a Mesen CDL capture

The committed split classified 4.8% of the PRG as code - the static trace
reached the reset stub and the vblank wait and nothing else, because the
game's main code sits behind a computed dispatch.  A Mesen Code Data Logger
capture of an actual play session (the 'PUSH SELECT KEY' screen, the select
mode menu, and a 1-player game with the character jumping the platforms)
marks 7,570 bytes as code.

cdl_reclass.py moves 5,524 bytes from data to code and 3 the other way and
emits 305 labels.  Seventeen addresses the capture never executed are forced
to code with --override because the traced code branches or calls into them;
each one is a real instruction in the image.  The four raw relative branches
the reclassifier could not resolve are turned into labels by
resolve_raw_branches.py.

The result is 4,255 instructions / 8,836 code bytes - 27.0% of the PRG, up
from 1,584 bytes.  Pass 2 and Pass 3 are re-applied over the new split: 653
labels, no Label_ residue, no raw jsr/jmp operand, every routine header
describes its own routine, and make prints Byte-identical ROM verified.

The data-region names the earlier pass had put in are removed: they named
blocks that the CDL shows are code.

Ice Hockey (U): re-trace Pass 1 from a Mesen CDL capture

The committed split classified 3.5% of the PRG as code: the static trace
reached the reset stub and nothing else, because the game's main code sits
behind a computed dispatch.

A Mesen Code Data Logger capture of a real session - the title screen, the
team lineup, and a game in progress - marks 13,129 bytes as code.  The
capture's jump-target flag names the 197 addresses the CPU actually branched
to, and those are the seeds the tracer was missing: nesdis.py with them
reaches 6,476 instructions / 12,957 code bytes, 39.5% of the PRG against
3.5% before, with 1,037 labels.

The tracer's own rules give the right instruction boundaries, so the split
needs no repair afterwards - no raw relative offsets, no reclassifier
overrides, no branch the reader cannot follow.  Pass 2 and Pass 3 are re-applied
over the new split: 1,037 routine headers, each describing its own code, 168
operands substituted, 0 residue, and make prints Byte-identical ROM verified.

_new _tools/cdl_seeds.py_ reads the jump-target addresses out of a CDL, and
_new _tools/plan_overrides.py_ lists the --override arguments a
cdl_reclass.py run would need.

10-Yard Fight (U): re-trace Pass 1 from a Mesen CDL capture

The committed split classified 11.2% of the PRG as code.  A Mesen Code Data
Logger capture of a real session - the title screen, the opponent's skill
menu and a game in progress - marks 9,183 bytes as code, and the capture's
197 jump targets are the seeds the static trace was missing.

Re-traced with them, the split is 5,166 instructions / 10,491 code bytes,
32.0% of the PRG against 11.2% before, with 647 labels.  Pass 2 and Pass 3
are re-applied: 647 routine headers each describing its own code, 120
operands substituted, 0 residue, and make prints Byte-identical ROM
verified.

Chubby Cherub (U): re-trace Pass 1 from a Mesen CDL capture

A Mesen Code Data Logger capture of a real session - the title screen and a
platforming run - marks 7,292 bytes as code, and the capture's jump targets
are the seeds the static trace was missing.  Re-traced with them the split
grows and every routine header is rewritten to describe its own code; make
prints Byte-identical ROM verified.

Dig Dug II (U) [!]: re-trace Pass 1 from a Mesen CDL capture

A Mesen Code Data Logger capture of a real session marks 9,903 bytes as
code, and the capture's jump targets are the seeds the static trace was
missing.  Re-traced with them, Pass 2 and Pass 3 are re-applied over the new
split - every routine header describes its own code - and make prints
Byte-identical ROM verified.

Hydlide (U): re-trace Pass 1 from a Mesen CDL capture

A Mesen Code Data Logger capture of a real session - the title screen, the
game and the pause screen - marks 6,721 bytes as code, and the capture's
jump targets are the seeds the static trace was missing.  Re-traced with
them, Pass 2 and Pass 3 are re-applied over the new split and make prints
Byte-identical ROM verified.

Port Test Cartridge (U): re-trace Pass 1 from a Mesen CDL capture

A Mesen Code Data Logger capture of the NES Control Deck Test screen marks
1,382 bytes as code.  Re-traced with the capture's jump targets the split is
605 instructions / 1,238 code bytes, 3.8% of the PRG against 0.7% before.

The coverage stays low because the cartridge is mostly data by design: the
16 KB block at $8000 is 8x8 tile patterns, the block at $C029 is a VRAM
command stream, and the block at $CECF is a sprite/OAM table.  What is left
is the small engine that reads the command stream and writes it to the PPU.

Gyromite (JUE): re-trace from the CDL instead of reclassifying

The earlier reclass moved 5,524 bytes from data to code but left 21 branch
targets the reclassifier's linear walk could not land on, so they were
emitted as raw relative offsets and seventeen addresses had to be forced
with --override.

Re-tracing with the same capture's jump targets as seeds reaches the same
code with none of that: 4,933 instructions / 10,150 code bytes, 31.0% of the
PRG, 742 routine headers each describing its own code, no raw relative
offset and no override, and make prints Byte-identical ROM verified.

Restore the data-block header spelling and add analyze_data_blocks.py

The separator change that gives derive_clobbers.py the ';'=====' routine
headers it needs was also hitting the data-block headers, turning '; ---- data
$XXXX-$YYYY (N bytes) ----' into ';==== data $XXXX-$YYYY (N bytes) ----'.
The conversion now only touches a line that is nothing but dashes.

_new _tools/analyze_data_blocks.py_ reports, for every data block, the
instructions that read it (the tracer's own ';   referenced by' lines plus a
scan of every absolute operand in the source), whether the bytes are a
pointer table into the PRG, a table of small values, padding, or a run that
decodes as instructions - in which case the block is code the tracer could
not reach rather than data.  That is the evidence a table's name has to be
based on.

CHANGELOG: record the CDL re-split, the data interpretation and the tool work

Port Test Cartridge (U): re-trace from the CDL and the unreached blocks

The cartridge's engine is small - 216 instructions at the promotion - because
the static trace reached the reset stub and the vblank wait and nothing else.
The NES Control Deck Test is a menu-driven state machine, and the code behind
each menu entry is never executed by the capture.

Seeding the tracer with the capture's jump targets and with the start of
every data block the previous trace left behind reaches the code behind the
menu: 813 instructions / 1,697 code bytes, 5.2% of the PRG against 0.7% at
the promotion.

Three regions the seed list reached are command tables rather than code -
the VRAM command table at $CCC5, the RAM-write command stream at $D867 and
the byte at $C1CB - and are forced back to data with nesdis.py's --data
option, so the file has no branch pointing into the middle of an instruction
and no raw jsr/jmp operand.

New _tools/code_data_seeds.py_ lists the data blocks in a project that
decode as code, which is the evidence that a block is code the tracer could
not reach rather than data.

Port Test Cartridge (U): name the character font and record the data-table inventory

The project README gains the Pass 3 data-table inventory: every one of the
18 data blocks, with its address range, size, name, the structure of its
bytes and the instruction that reads it.

Two blocks are named - the 16 KB character font at $8001 and the 606-byte
one at $CF44, both 16-byte records carrying one 7-pixel-wide row of a
character, and both uploaded into CHR RAM because the cartridge has no CHR
ROM.  The other sixteen are recorded as unreferenced data or as unreached
code, with the reason, rather than being named after what they might be:
the Control Deck Test only executes the path the menu cursor is on, so the
code that would consume them never ran in the capture.

The README's status, open-work and file sections are brought up to date.

Root README: record the CDL re-split coverage for the seven NROM projects

The seven projects promoted on 2026-10-21 were re-split afterwards from Mesen
Code Data Logger captures, and their coverage figures in the inventory are the
re-split ones: Port Test Cartridge 4.8%, 10-Yard Fight 32.0%, Chubby Cherub
41.4%, Dig Dug II 53.5%, Gyromite 31.0%, Hydlide 47.8%, Ice Hockey 39.5%.

AGENTS.md: record the CDL jump-target seed technique and the --base pitfall

Three lessons from the seven re-splits:

- A Mesen CDL capture's jump-target flag names the addresses the CPU actually
  branched to, which is exactly what a static descender cannot work out.
  nesdis.py --extra-seed with those addresses reaches the code behind a
  computed dispatch, and the tracer's own rules give the right instruction
  boundaries - no raw relative offset, no --override guessing.

- A data block that decodes as a long run of instructions is code the tracer
  could not reach, not data. code_data_seeds.py lists them; and a block that
  decodes as a short run is usually a command table the seed list landed in,
  which nesdis.py --data forces back.

- name_data_region.py needs --base for anything but a 16 KB PRG at $C000.

WIP.md: correct the tier's state table and the per-project states

The tier's state table claimed 851 Pass 0 skeletons.  Counting the
instruction lines in each project's prg.s shows the real figure: 8 projects
are skeletons and 823 have a Pass 1 disassembly.  Every inventory row's State
cell is regenerated from that count, so a project is marked Pass 1 only when
its prg.s really carries instructions.

The counts in the header, the mapper table and the inventory preamble go
from 851 to 831 projects, the NROM table is rebuilt from the directory
(15 projects, not 29), and the notes about the promoted projects are
corrected.

Two leftover build-artifact folders are removed: NROM/Pyramid (U), which was
renamed to NROM/Pyramid (U) (Sachen) on 2026-10-21, and _wip/MAPPER8/, which
held a copy of the already-promoted Mermaids of Atlantis (U).

Dig Dug II (U) [!]: interpret the data tables and record the inventory

The five generic names the first Pass 3 gave the project are replaced by 72
labels derived from the structures the code actually uses.

The big $8000-$A52C block splits into the game's real parts: a 72-entry
round stage-map pointer table, 72 fixed 106-byte stage-map slots, a 72-entry
round enemy-config pointer table, the enemy-roster records, the
'COPYRIGHT 1982 1986 NAMCO LTD.' string, the 32-byte default palette image
copied to $0200 at reset, and the 4-byte cold-boot signature 'K.N.'.

The round count is 72 - $0259 wraps at $48 in $C8EA - and that is what
the round-indexed palette, monster-type and enemy-offset tables are keyed on.
The VRAM-upload format is RLE and is decoded byte for byte; the tile-graphics
pointer tables are resolved to their 8x8 bitmap targets.

34 of the 37 tracer blocks carry at least one name. $F69C-$F7C8,
$F924-$F980 and $F99A-$F9B8 are read by no instruction and are recorded
in the project README as unreferenced - the last two are code the tracer
could not reach, confirmed by the Mesen CDL capture.

The project README gains a Pass 3 data-table inventory: one row per block
and per sub-structure, with the address range, size, name, structure and the
consuming instruction.  make still prints Byte-identical ROM verified.

derive_routine_docs.py: describe what each routine actually does

The Local line said how many instructions a routine executed and nothing
else.  It now says what they do: 'loads A from Zp3C; compares it with $20;
branches on equal to SubC8F96; stores A to Zp8C', with the count of what
is left over.  Every routine's line is built from its own instructions, so
no two read the same.

Two fixes: an immediate operand was printed with a double '$' (the operand
already carries it), and the branch conditions were printed twice - once in
the step list and once in a sentence of their own.

Rewrite the routine headers across the promoted tier

Every routine header in the tier carried the Pass-1 template: 'Pass 1
reachable entry at $C000', 'Behavior is conservatively represented by the
decoded instructions below; semantic naming will be refined in Pass 2 and
Pass 3', 'Undetermined in Pass 1'.  That is filler, and it describes the
process rather than the ROM.

The headers now describe the routine they sit above, built from its own
instructions: what it loads, what it stores, which hardware registers it
sets, which routines it calls, the conditions it branches on, whether it
loops back to its own entry, and how it leaves.  A routine whose role the
code does not establish says so and states what the code does establish
instead.

The Clobbers block of every header is derived by derive_clobbers.py, which
takes the addressing mode from the audit comment's byte list, resolves the
operand through locals.inc and symbols.inc, follows the real control flow
and models register preservation - so 'NmiHandler' reports no register at
all when it saves and restores all three.

derive_clobbers.py and derive_routine_docs.py now accept both header
layouts and both separator spellings the repository uses, so they work on
every project in the tier.

Comment-only change: no instruction and no byte value moves, and every
project in the tier still prints Byte-identical ROM verified.

CHANGELOG: record the tier-wide routine header rewrite

Chubby Cherub (U): interpret the data tables and record the inventory

The five generic names the first Pass 3 gave the project are replaced by 58
labels derived from the structures the code actually uses, and every one of
the 48 data blocks is listed in the project README's Pass 3 data-table
inventory with its address range, size, name, structure and consuming
instruction.

The breakthrough is the character encoding.  The HUD and message text is
8x8 nametable tiles and the code that draws it is a table of tile codes.
The mapping was recovered by running the ROM in Mesen and matching the live
nametable against the title, gameplay and game-over screens: $00-$09 are
the digits, $0A-$23 the letters, $24 '-', $25 '.', $26 the trademark,
$2D a heart, $2E '!', $2F the copyright sign, $30 a space and $33 a
blank.  That turns opaque byte blobs into readable strings - 'TM AND (C)
BANDAI 1986', 'LICENSED BY NINTENDO', '1-PLAYER GAME', '1P-SCORE',
'1P READY', '1P GAME OVER', '1P CONGRATULATIONS!', 'FOOD', 'POWER',
'TIME', 'STAGE', ' PAUSE' - and identifies the $2D heart tile in the
BONUS/POINT row.

Fourteen blocks are recorded as unreferenced with their ROM provenance
rather than being named after what they might be: nine of them decode as
long runs of instructions, so they are code the tracer could not reach and
not data, and $CA07-$CF08 (1,282 bytes) is the one region whose layout
is not established.

make still prints Byte-identical ROM verified.

Complete the routine headers across the tier, in every header layout

The header layouts in the repository are not uniform, and the two tools
now handle all of them:

- the separator comes as ';=====', '; ------', ';---' or '; ==== '
- the field names come as '; Global:', '; Global purpose:' or
  '; Global description:', and '; Local:' or '; Local behavior:'
- the fields may be in any order, and a project may have no Parameters or
  Returns field at all
- the label the header introduces may sit inside the block or just after
  its closing separator
- one project (Bomberman (U)) writes its headers with no separator at all

Two real bugs are fixed on the way:

- derive_clobbers.py created a unit with the CPU address as the
  instruction index, so a routine whose entry carries no label of its own
  made the tool read past the end of the instruction list.  That is what
  stopped it running on Wild Gunman (U) and Pac-Man (USA) (Namco).
- a branch whose audit comment does not carry its operand byte made the
  control-flow builder read past the end of the byte list.

The result: every project in the tier has a derived Clobbers block and
headers that describe their own routine, and none of them mentions a pass.
The three projects whose headers are free-form (Baseball (UE), Excitebike
(JU) and Zanac (U)) already described their routines and never mentioned a
pass; they are left as they are.

Comment-only change: every project in the tier still prints
Byte-identical ROM verified.

Complete Pass 2 across the tier: no Label_ residue left

Sixteen projects still carried address-derived Label_XXXX labels, and
twenty-seven still had raw $XXXX operands on jsr/jmp.  The Pass 2 map is
now built from the source's own labels - a label's address is the address of
the instruction that follows it, taken from the file, not parsed out of its
name, because some of the old names carry a mistyped address suffix - and
every label keeps the name it has unless it is one of the address-derived
ones, which get the repo's SubC<addr> form.

Three more real defects in the tools are fixed:

- derive_branch_names.py named a jsr/jmp target that no instruction sits at.
  Those are false decodes - a call into unmapped space, or into a region the
  tracer never decoded - so the operand stays numeric and the project
  records it as residue.

- apply_pass2_map.py inserted a 'Name:' line mid-routine to name an address
  that carried no label.  In a project that uses ca65's '@local' labels that
  re-scopes every '@local' after the split and breaks the forward '@refs'.
  There the name now becomes an equate in locals.inc, which names the
  address without touching the label scope.

- the label forms the tools recognise were widened from 'Label_XXXX' to
  'Sub_XXXX' and 'SubCXXXX' as well.

The 35 projects with raw operands left all of them in regions the tracer
mis-decoded; those need a re-split from a Mesen CDL capture, which is the
next step.  Every project still prints Byte-identical ROM verified.

Urban Champion (JU): re-split Pass 1 from the Mesen CDL captures

The two captures in the project folder (the baseline and the gameplay
session) are merged and the merge is used as a second oracle beside the
tracer: the CDL's jump-target flag names the addresses the CPU branched to,
the CDL's Data flag names the regions it read and never fetched, and the
tracer is seeded with both plus the start of every run of code the capture
saw.

The split goes from 33.8% code to 48.6%: 3,856 instructions / 7,958 code
bytes against 2,356 / 5,521.  The 220 raw jsr/jmp operands are gone.

Two new tools: merge_cdl.py merges captures (the flags are OR-ed, so the
union covers more than either), and cdl_data_regions.py lists the regions the
capture says are data, for nesdis.py's --data option.

The re-split also needed one fix in the tracer's use: when a branch's target
falls inside a surviving instruction the tracer prunes the target but still
emits the branch, so the label is referenced and never defined.  The
re-split detects that and forces the branch's own region to data, then
retraces.

apply_pass2_map.py: do not write the same equate twice

The equates go in locals.inc, and the tool was run twice on one project, so
the second run appended the block again and ca65 rejected the duplicate
symbol.  The equate list is now checked against what locals.inc already
holds, and only the new ones are written.

Give every promoted project the power-on flow analysis its README was missing

PROMPTS.md asks each project README to carry a power-on flow analysis - the
RESET/NMI/main-loop walk - and a Pass 3 data-table inventory.  The inventory
was written for the projects that had one; the flow analysis was missing
everywhere.

_new _tools/derive_poweron.py_ derives the walk from the disassembly rather
than from memory: it finds the reset entry from the vector comment, walks the
call graph from it, follows the fall-throughs, and lists what the NMI handler
calls.  It also says whether the IRQ vector reaches the reset path.

_new _tools/add_poweron.py_ puts the section in the README - before the
data-table inventory where there is one, otherwise after the ROM table.

All 61 promoted projects now carry the section.

Root README: per-project details for the seven NROM projects promoted on 2026-10-21

Port Test Cartridge (U), 10-Yard Fight (U), Chubby Cherub (U), Dig Dug II (U)
[!], Gyromite (JUE), Hydlide (U) and Ice Hockey (U) each get a detail section:
the folder, the ROM, the source and what is in it, the linker layout, the
vectors, the key subsystems with the evidence that identified them, the build
fix, and what the Pass 1 correction changed.

Donkey Kong (JU): re-split Pass 1 from a Mesen CDL capture

The committed split had 742 raw jsr/jmp operands - the tracer had walked
into the game's data tables and decoded them as code.  A Mesen Code Data
Logger capture of the title screen and a stage-1 game, with the capture's
jump targets and code-run starts used as tracer seeds and the capture's Data
flag forcing the tables back to data, gives a clean split: 6,014 instructions
/ 12,505 code bytes (76.3%), 1,015 labels, and no raw operand left.

Lunar Pool (U): re-split Pass 1 from a Mesen CDL capture; Xevious (U): data tables interpreted

Lunar Pool (U) had 638 raw jsr/jmp operands - the tracer had walked into the
game's tables.  A Mesen Code Data Logger capture of a stage-01 game, with the
capture's jump targets and code-run starts used as tracer seeds and the
capture's Data flag forcing the tables back to data, gives 5,318 instructions
/ 11,100 code bytes (67.7%) and no raw operand left.

Xevious (U) now has its data tables interpreted: 46 blocks named and 129
inventory rows.  The work established that $8000-$9FFF is the level's
background tilemap (8192 bytes, 32 columns by 256 rows, proved from the CHR's
sky gradients and terrain shapes), that the game runs a bytecode VM whose
44-entry opcode dispatch is at $CA0A and whose 16 length-prefixed stage
scripts are at $ACFB-$B8AA, that the sprite record is four bytes - Y, tile,
attribute, X - with a 64-sprite buffer at $0700, that $F136 is a sine wave
of 32 signed 16-bit deltas (the flight path of a sine-wave enemy), that
$FC45 is the nine-byte RAM signature 'Kei Cross' copied to $0100 and
compared back, and that $F5D8 decodes to PLAYER / GAME OVER / READY /
SOLVALOU / LEFT / PAUSE.

Lode Runner (U) and CIRCUS: re-split Pass 1 from Mesen CDL captures

Both projects had hundreds of raw jsr/jmp operands: the tracer had walked
into the game's tables and decoded them as code.  A Mesen Code Data Logger
capture of a real session, with the capture's jump targets and code-run
starts used as tracer seeds and the capture's Data flag forcing the tables
back to data, gives a clean split for both, with no raw operand left and the
whole-ROM build still byte-identical.

Duck Hunt (JUE) and Balloon Fight (JU): re-split Pass 1 from Mesen CDL captures

Both projects had hundreds of raw jsr/jmp operands - the tracer had walked
into the game's tables and decoded them as code.  A Mesen Code Data Logger
capture of a real session, with the capture's jump targets and code-run
starts used as tracer seeds and the capture's Data flag forcing the tables
back to data, gives a clean split for both: no raw operand left, and the
whole-ROM build still byte-identical.

Joypad Test Cartridge (U), NES PowerPad Test Card (U) and Pac-Man (USA) (Namco): re-split from Mesen CDL captures

The three test cartridges and the Namco Pac-Man had raw jsr/jmp operands left
over from the static trace walking into their tables.  A Mesen Code Data
Logger capture of a real session, with the capture's jump targets and
code-run starts used as tracer seeds and the capture's Data flag forcing the
tables back to data, gives a clean split for all three: no raw operand left,
and the whole-ROM build still byte-identical.

Repair the damaged audit trails across the tier

Thirteen projects carried audit comments that did not match prg.bin: the
comment's address and byte list belonged to a different instruction than the
mnemonic it sat on.  Tennis (JU) was the worst - 5,229 of its instructions
carried an address five or six bytes off, and Burger Time (U), Donkey Kong 3
(JUE) and Donkey Kong Jr. (JU) were damaged in the same way.  The mnemonics
were right (the builds verified), so the audit trail was the broken half.

repair_audit_comments.py rebuilds the trail from the ca65 listing, using
prg.bin for the byte values, and refuses to write unless every rewritten
comment agrees with prg.bin.  Three things had to change in the tool for it
to run at all on this tree:

- ca65 2.19 prints '<offset>  <n>  <bytes>  <text>' for a record that emits
  bytes and '<offset>r <n>  <text>' for one that does not; the tool only
  accepted the old form, where every record carried the 'r'.

- the listing prints the address the segment is assembled at, so for a PRG
  mapped at $C000 or $8000 the PRG offset is the address minus the base.
  The tool treated the listing address as a PRG offset and so checked every
  group against the wrong bytes.

- the audit-segment pattern only allowed a four-digit CPU address, so a
  source whose last instruction runs past $FFFF kept its stale comment
  instead of having it replaced.

All 322,830 audit comments in the tier now agree with prg.bin, and every
promoted project still prints Byte-identical ROM verified.

Tennis (JU): finish Pass 2 and Pass 3 over the repaired trail

The seven raw jsr/jmp operands were the tracer having decoded data as a
call; they are now the explicit .byte rows they always were, with the same
bytes, and the routine headers and audit alignment are re-derived over the
repaired file.  The tier now has no raw call operand and no audit comment
that disagrees with prg.bin.

_new _tools/build_routinemap.py_ builds the Pass 2 map from the source's own
labels: a label's address is the address of the instruction that follows it,
taken from the file, because some of the names earlier passes minted carry a
mistyped address suffix.  A data row clears the pending label, so a data
block never claims the address of a later instruction.

Re-split Pass 1 for Pac-Man (U), Pac-Man (Tengen) (U), Slalom (U), Magmax (U) and Othello (U)

Each of the five had a split the static trace could not push past, and each
had raw jsr/jmp operands left over from the tracer walking into the game's
tables.  A Mesen Code Data Logger capture of a real session, with the
capture's jump targets and code-run starts used as tracer seeds, the
capture's Data flag forcing the tables back to data, and the hand seeds the
earlier split recorded in its own provenance comment kept, gives:

  Pac-Man (U)           18.7% -> 45.9%   3,734 instructions / 7,528 bytes
  Pac-Man (Tengen) (U)  20.0% -> 47.3%   3,842 instructions / 7,744 bytes
  Slalom (U)            32.1% -> 31.8%   4,983 instructions / 10,414 bytes
  Magmax (U)            35.4% -> 36.5%   5,696 instructions / 11,954 bytes
  Othello (U)           43.3% -> 44.0%   6,804 instructions / 14,403 bytes

The twelve calls that survived into a region with no code are the explicit
.byte rows they always were, with the same bytes.  Every project still
prints Byte-identical ROM verified.

Give every routine header a contract that is its own

Two things made the headers read the same in every routine of a project.

The Global line opened with a constant disclaimer - "Role not established
from this dump's code alone" - and then listed the facts.  The disclaimer
said nothing about the routine, so it was filler.  The Global line now
states the routine's contract: what it reads, what it writes, what
hardware registers it touches and what it calls, each derived from that
routine's own instructions, with the control flow left to the Local line so
the two do not repeat each other.  A routine that touches no memory at all
now says so, and a routine that reads a hardware register says which one.

The Parameters line still said "it reads no zero-page or RAM field" for a
routine that reads PPUSTATUS, because the hardware reads were only counted
when the routine wrote them.  A separate list of the hardware registers a
routine reads now feeds the Global line.

derive_clobbers.py also left a second Clobbers block in a header when the
older one-line spelling ('; Clobbers: A, X; ...') was present: it removed
only the multi-line form.  Both spellings are removed now, and the derived
block replaces them.

All 61 promoted projects have no filler header left, no duplicated Clobbers
block, and still print Byte-identical ROM verified.

Zanac (U): trace bank 6, and give the project a build that can hold it

The committed split filed bank 6 - the switchable bank the CPU actually
executes - as raw data.  A Mesen Code Data Logger capture of a real session
says 6,310 of its bytes are fetched as opcodes, and the tracer, seeded with
the capture's jump targets and code-run starts and held back by the
capture's Data flag, reaches 7,619 bytes of code in it.

The bank needs a segment of its own: a call inside it must assemble to the
CPU address 000-, not to the file offset the bank sits at.  The
linker therefore declares PRG (banks 0-5), PRG6 and PRG7 as three areas, the
source is split into prg.s, prg.6.s and prg.07.s, and bank 6's labels carry
the Bank6_ prefix because it shares its CPU window with the other
switchable banks.

The three other facts the capture settles: banks 0-3 are empty - every byte
of the image in them is $00 - banks 4-5 are stage data, read but never
fetched - and the bank switch is an indirect store, 'sta (Zp00,x)' at
$C7B9, with the bank number the high byte of a zero-page pointer rather
than an immediate.

The coverage goes from 32.5% to 44.5% of the 128 KB image.  Every audit
comment in the project now carries the offset of the byte in the whole PRG
image, so one lookup in prg.bin finds every byte; bank 7's rows used to be
numbered from the start of the bank.

Zanac (U): name the cross-bank calls and finish Pass 2 over bank 7

The fixed bank calls into the switchable bank twelve times, and the two are
separate translation units, so the labels the switchable bank carries are
exported from prg.6.s and imported into prg.07.s.  The one call left over
points into unmapped space and is the explicit .byte row it always was.

Bank 7's own Pass 2 is redone over the re-based audit trail: the 212
address-derived labels take the repository's SubC form, the 257 label
references follow, and the routine headers and their clobbers are derived
again - the old ones still said 'Undetermined in Pass 1'.

Zanac now has 44.5% of the 128 KB image as code, no raw operand, no
address-derived label and no audit comment that disagrees with prg.bin.

Interpret the data tables across the tier

Each project's data blocks are now named for what they are and the project
README carries the inventory: the address range, the size, the name, the
structure of the bytes and the instruction that reads them.

Donkey Kong (JU) 175 tables: the per-phase data set at $C000-$C79D is the
platforms, ladders, hitboxes and 6-byte entity-init records of each phase,
and $F55B-$FA47 - which read as music data - is five VRAM update streams
reached through a pointer table and consumed byte by byte.

Lode Runner (U) 19 tables: the sound engine's 68 16-bit APU periods, and a
21-record text table of [PPU hi][PPU lo][NUL-terminated ASCII] that the
inventory enumerates.

Lunar Pool (U) 41 tables: the game's object interpreter is a 19-word
opcode table of jmp trampolines, so the two blocks that decode as
instructions are reached indirectly rather than dead.

Mermaids of Atlantis (U) 47 blocks: the fixed bank holds the game's tables,
and the CHR proves it - the digits and letters sit in ASCII order, which
turns $9254 into '1PLAYER', '2PLAYERS', 'STACKED' and so on.

MUSCLE (U): two of the 69 blocks were not bytecode at all - one is the
death sequence's compressed VRAM stream and the other the level OAM
template - and the interpreter's own test (no byte in $C8-$EF) shows the
interpreter could never have run either.

Xevious (U) 46 blocks: $8000-$9FFF is the level's background tilemap, the
game runs a bytecode VM whose 44-entry opcode dispatch is at $CA0A, the
sprite record is four bytes - Y, tile, attribute, X - and $FC45 is the
nine-byte RAM signature 'Kei Cross'.

Ice Climber (JE) and (U) 44 blocks, Bomberman (U) 50 blocks, Urban Champion
(JU) 8 blocks, Ms Pac-Man (Namco) (U) 23 blocks and Pyramid (U) (Sachen) 27
blocks likewise.

Every project still prints Byte-identical ROM verified.

CHANGELOG: move the committed entries into History

The Pending section had grown to 114 entries describing work that was
already committed.  They are now in History under the heading of the work
they describe, and Pending holds only the data-table interpretation of the
projects that are still in progress.

Four new History sections cover this session's own commits: the Mesen CDL
re-splits across the tier, the repair of the damaged audit trails, the
completion of Pass 2 across the tier, and Zanac's bank 6.

Root README: refresh the coverage column of the project inventory

Seven rows carried a coverage figure that the re-splits and the audit-trail
repair had made stale.  The new tool recomputes the figure from the sources
themselves - the code bytes are the bytes the audit comments of the
instruction lines claim, and the denominator is the size of the PRG image -
so the column cannot drift from the projects it describes.

Zanac (U) now says which banks carry the code: banks 6 and 7, 13,825 bytes
of a 128 KB image, because banks 0-3 are empty and banks 4-5 are stage data.

Root README: refresh the source shapes the re-splits changed

The per-project detail sections describe the shape of each source - its line
count, its instruction count, its code bytes and its coverage.  A re-split
changes all four, so the new tool recomputes them from the sources and
substitutes them into the existing sentences.

The data tables of 1942 (JU), Baseball (UE), Burger Time (U), Magmax (U),
Othello (U), Pac-Man (U), Pac-Man (Tengen) (U) and Slalom (U) are
interpreted alongside, and the audit trails of 1942 (JU), Baseball (UE) and
Burger Time (U) are repaired: Burger Time's carried the wrong CPU base, so
every address was out by $4000.

AGENTS.md: record what this session's work established

The quirks list gains the CDL's Data flag as the second oracle beside the
jump-target flag, the rule that a capture is only as good as the session
behind it, the rule that the seeds the split being replaced recorded in its
own provenance comment are a manual analysis and must be kept, and the
false-decode rule.

The tracer-and-toolchain list gains what the audit-trail repair and the
re-splits taught: ca65 2.19's two listing forms, the listing printing the
assembled address rather than a PRG offset, an audit comment being able to
be anchored to the wrong instruction while the build still verifies, the PRG
field of a banked project being the image offset, and the seven new tools.

TODO.md: bring the handoff up to date

The file still described the 41-project tier.  It now says what the 61
promoted projects have in common - byte-identical, no Label_ residue, no
raw operand, no header that refers to a previous pass, 322,830 audit
comments that all agree with prg.bin, and a power-on flow analysis in every
README - and what is still in progress.

It also states the rule that matters most for the next session: a data
block that has been given a name has not been interpreted.

Give every branch target a role name, and close the rest of the checklist

_new _tools/audit_promoted.py_ checks the promoted tier against all eleven
items of PROMPTS.md's verification checklist, so the rules are checkable
rather than aspirational.

Three gaps it found, now closed:

- **1,487 branch targets carried an address-derived name.**  PROMPTS.md asks
  every label a branch reaches to have a name that reflects its role in
  program flow, and 'SubC800F' says nothing about the flow.  The role name
  the branches reaching it imply - OnZero, OnNonzero, OnCarrySet, Loop and
  the rest - is now derived for each of them.  derive_branch_names.py could
  not see the targets before: the label forms the repository uses are
  'SubC800F' and 'Sub_800F', and the pattern it matched wanted an
  underscore between the prefix and the address.

- **48 operands named a hardware register by its address.**  Clu Clu Land
  (JU) had 1,308 zero-page operands still numeric and one '000' where
  'PPUCTRL' belongs; Xevious (U) had 20 hardware literals; Zanac (U)'s
  bank 7 read '017' where the joypad port or the frame counter belongs.
  Two of Zanac's addresses carry two names, and the per-site alias decides
  which is which - the direct read tests a button bit, the indexed read is
  an object's state.

- **325 neutral zero-page slots carried no reason.**  locals.inc now says,
  per slot, that the name is provisional.

The tools grew to match: apply_symbols.py accepts an upper-case mnemonic,
apply_zp_aliases.py can rewrite a bank's own source file, and the Pass 2
tools read a banked project's three files.

Every project still prints Byte-identical ROM verified.

PROMPTS.md: the checklist now has a checker

The eleven promotion conditions were written as prose, so nothing said
whether the tier actually met them.  _tools/audit_promoted.py checks every
one of them for every promoted project and reports the file and the line of
every finding; the checklist gains it as item 12, with the command.

CHANGELOG: record the checklist work

audit_promoted.py: count an inventory row wherever the address sits

Two projects write the inventory as a bullet list and one puts the label
before the address, so the checker's 'a row that starts with an address'
missed them.  A row now counts when it holds a $XXXX address in any cell.

Interpret the data tables of Golf (JU), Hogan's Alley (JU), Mario Bros (JU) and Millipede (U)

Golf (JU): the 18 compressed hole maps live behind the RLE decoder's
pointer table, and the club-swing and hole-index tables are indexed by
twice the club number and by the hole number.

Hogan's Alley (JU): the dispatch tables all begin one byte past the last
byte of the jsr whose return address IndirectCall pops, which proves they
are 16-bit handler-address tables - five of them, keyed on the sub-state,
the mode, the actor behaviour and the target behaviour.

Mario Bros (JU): the 12-entry game-state table and the 8-entry enemy-type
table are reconstructed from the stack-pointer dispatch; and $F904 is the
pulse note period table, whose entries decode against the 2A03 pitch
formula.

Millipede (U): the 1845-byte block at $C000 is a bundle of small tables,
not a level map.

Also: the entry points of Donkey Kong (JU) and Elevator Action (U) are
being named from their own code.

Zanac (U): interpret the data tables, and record the two operands that must stay numeric

Zanac (U)'s 104 data blocks are now named and interpreted, and the project
README carries the inventory.  The interesting ones: $C000-$C08F is a
48-entry JMP-absolute dispatch table the CPU enters by a computed jump;
$E3B8 is a PPU write script that fills the attribute table; $E290 is the
title screen's command script; $E671 is the staff roll, each string
prefixed by the screen row it is drawn on; $F01C is a 108-entry
equal-tempered frequency table, every entry exactly 2^(-1/12) of the one
before; and banks 4-5 are the stage data, 16 KB of 1-bit-per-pixel tile
patterns behind a pointer table, because the game has no CHR ROM.

name_data_region.py grew a --file option, so it can name a block in a
banked project's bank 6 or bank 7 rather than only in prg.s.

Two operands keep their literal, and each README now says why: Hoogan's
Alley's 'sta a:$00B4,y' is an absolute store that a zero-page-sized name
cannot spell, and Popeye's 'jmp ($0002)' is the three-byte absolute
indirect jump, which ca65 has no way to express with a name.

Popeye (JU) (PRG 1): record why the indirect-jump operand keeps its literal

Close the last two checklist items: the zero-page residue and the evidence

PROMPTS.md's item 8 asks that apply_symbols.py leave no resolvable operand
numeric without justification.  Four projects had residue:

- **Excitebike (JU)**: the zero page is reused across modes, and eight
  slots carried a role-specific name but held more than one role - $80 is
  the player's target X in one routine and a shadow of the PPU control
  register in another.  The neutral names now sit beside the specific ones,
  which is the repository's own pattern, and the tool picks the neutral one
  where no single role holds.  Its residue is zero.
- **Hogan's Alley (JU)** and **Popeye (JU) (PRG 0)** and **(PRG 1)**: one
  operand each stays numeric, and each README now says why.  'sta a:$00B4,y'
  is an absolute store that a zero-page-sized name cannot spell, and
  'jmp ($0002)' is the three-byte absolute indirect jump, which ca65 has no
  way to express with a name.

apply_symbols.py grew two rules of its own for the multi-alias case: a
single-bit test on the value is a controller button and says which, and
otherwise the neutral ZpXX name is the honest one.

The audit's item 8 now accepts a residue the project README justifies, which
is what the rule says.

Every project still prints Byte-identical ROM verified.

CHANGELOG: record the zero-page residue work

Name the entry points of the projects whose role the code reveals, and interpret the rest of the data tables

**Entry points.**  PROMPTS.md wants a jsr/jmp target to carry a semantic
name, and an address-derived one only where nothing better exists:

- **Donkey Kong (JU)**: 358 named, none left.  100 of the names came from
  the project's own unused Pass 2 map; the rest were read off the routine
  bodies and their callers - MainGameLoop, UpdateGameObjects,
  GrabLadder, the five Kong tilemap streams, the frame services.
- **Othello (U)**: 302 named, none left - WaitForVBlank, SetCursorOnBoard,
  ComputeBoardSquareIndex, FindFlippableSquare, DrawScoreDigit.
- **Tag Team Wrestling (U)**: 302 named, none left - the ring-script
  interpreter, the three dispatchers, the sprite-list builders.
- **Clu Clu Land (JU)**, **Defender 2 (U)**, **Donkey Kong 3 (JUE)** and
  **Donkey Kong Jr. (JU)**: their data tables are interpreted.

**Data tables.**  Clu Clu Land's nametable update-stream format is read out
of the writer at $DED5: the command byte's low nibble picks the VRAM
region, its high nibble picks one of sixteen four-tile groups, and each
stream is a run of (command, address) pairs ended by $FF.  Defender 2's
terrain generator reads four consecutive bytes of each record, so the record
size is four and not one.  Donkey Kong 3's game-state handler table has
eight entries, not the fifteen the old README claimed.

name_data_region.py now cuts a .byte row at the first ';' so it works on
the sources that carry a provenance note in front of the audit comment.

Every project still prints Byte-identical ROM verified.

The promoted tier now passes every item of the promotion checklist

python3 _tools/audit_promoted.py --build reports nothing for all 61
projects.

**Data tables.**  CIRCUS, Duck Hunt (JUE) and Balloon Fight (JU) join the
rest.  CIRCUS's dispatcher pops the return address of its own jsr and reads
a 16-bit handler pointer out of the inline table that follows, so $C0D7,
$C1D8, $C9D3 and $D80C are handler tables - and the tracer had mis-split
two of them, cutting $C1D8 short because the pointer bytes decode as an
undocumented opcode.  Duck Hunt's $E64B is the duck's 24 ascending speed
table.  Balloon Fight's $D65C is 64 little-endian nametable addresses.

**Entry points.**  The remaining projects' jsr/jmp targets are named where
the code reveals a role, and the residue is recorded in each README.

**One more tool fix.**  name_data_region.py cuts a .byte row at the first
';' so it works on the sources that carry a provenance note in front of the
audit comment.

Every project still prints Byte-identical ROM verified.

CHANGELOG: record the tier passing the checklist

Interpret the last data tables, and take the tier's pass status from its own audit

**Data tables.**  Tag Team Wrestling (U), World Class Track Meet (U),
Wild Gunman (U) and Tennis (JU).

Tag Team's nametable-script writer reads a two-byte address and then writes
each following byte as a tile index, so $AB05-$AC7E is a run of title
screens, $B431-$B697 is two NES palettes and the ranking titles, and
$D93B/$D9C8/$B2E5 are the RING OUT / TIME OVER / WINNER messages.  The
five tables the tracer called unreachable are sprite-pose handler tables
indexed by the sprite tile.

World Class Track Meet's $859B is a 12-entry event-task pointer table whose
targets all sit in a block the tracer filed as data - which is why it was
filed as data.  Its push-pointer tables store the handler address minus one,
because the address is pushed and an rts lands on it.

Wild Gunman's earlier Pass 3 was hollow: the tracer reached 49.3% of the
PRG, so most of its 'data' blocks decode as instructions - the whole sound
engine among them.  The wrong SpritePositionTable name is gone.

Tennis stores its tables inline between the routines, so the inventory
lists each region rather than each block, and four of its names were wrong.

**Root README.**  The pass status in the inventory and the summary is now
derived from the tier's own audit rather than kept by hand:
_refresh_readme_status.py_ rewrites the column from what
_audit_promoted.py_ finds.

Every project still prints Byte-identical ROM verified.

Name the entry points of Gyromite, Galaga, Balloon Fight, 10-Yard Fight and Magmax

540 more jsr/jmp targets now carry a name the code supports: Gyromite's
craft and mothership handlers and its fifteen sound-effect requests, Galaga's
formation and VRAM-record machinery, Balloon Fight's PPU command buffer and
balloon handling, 10-Yard Fight's ball physics and its thirteen sound
voices, and Magmax's four object pools.

Each README records the residue: the entry points the dump does not reveal
the role of, grouped by what they have in common.

Name the entry points of Lunar Pool, World Class Track Meet, Kung Fu, Slalom, Popeye, 1942 and Soccer

1,159 more jsr/jmp targets now carry a name the code supports.

Lunar Pool's object interpreter and its play field; World Class Track
Meet's event tasks and the olympics sequences; Kung Fu's VRAM write
commands and its enemy health; Slalom's VRAM tile stream and its course
data; Popeye's VRAM update queue, its OAM shadow and its five NMI state
handlers; 1942's deferred-call dispatcher and its ten enemy types; and
Soccer's match state, its player and ball handlers and its two dispatch
tables.

Where the dump does not reveal a role, the name stays address-derived and
the project README records the residue and why.

Root README: take the pass status from the tier's audit

refresh_readme_status.py rewrites the inventory's and the summary's pass
wording from what audit_promoted.py finds, so the two cannot disagree.
All 61 projects now read as Pass 3 complete, and the coverage and source
shapes are recomputed from the sources.

Remaining entry-point naming

Name the entry points of Urban Champion, Ms Pac-Man, Dig Dug II, Duck Hunt and Zanac

665 more jsr/jmp targets now carry a name the code supports.

Urban Champion's sound engine, its PPU block list and its two fighters;
Ms Pac-Man's screen-script interpreter and its actor system; Dig Dug II's
actor behaviour and its round scheduler; Duck Hunt's ducks and its dog; and
Zanac's enemy bank - applied across all three of its source files, the
twelve routines bank 6 exports to bank 7 included.

Ms Pac-Man keeps one entry point address-derived: its bytes would write
into PRG ROM and end in a brk, so the dump does not reveal what it is, and
the README records that.

CHANGELOG: record the entry-point naming

Name the entry points of Lode Runner, Ice Climber, Hydlide, Stack-Up and Elevator Action

Re-align the audit comments to the canonical column

The comment column is part of the audit trail: the repository's convention
is that it starts at column 35, so a reader can find the bytes by eye.
Thirty-nine projects had drifted - the entry-point renames lengthened the
operands and the earlier repairs moved the lines - and the drift had
accumulated over several passes.

align_audit_comments.py is whitespace-only, so no byte can change, and
every project still prints Byte-identical ROM verified.

Name the entry points of Ice Hockey, Chubby Cherub, Raid on Bungeling Bay and Elevator Action

1,127 more jsr/jmp targets now carry a name the code supports.

Ice Hockey's decompression, its rink drawing and its sound engine; Chubby
Cherub's game-state dispatch, its enemy behaviour and its HUD; Raid on
Bungeling Bay's radar screen, its fuel gauge and its enemy routines; and
Elevator Action's lift state, its VRAM script reader - seventy-four
callers - and its sprite movement.

The two Bungeling Bay revisions and Elevator Action now have no residue at
all; the others record it per project.

CHANGELOG: record the audit-comment re-alignment

Remaining entry-point naming

Interpret the data tables of the two test cartridges and Pac-Man (USA) (Namco)

**Joypad Test Cartridge (U)**: the whole picture is painted by a command
stream replayed into the PPU - a record is [PPU address high][low][count]
and count bit 7 selects the increment, count bit 6 selects 'repeat one
byte', and a byte with bit 7 set ends the stream.  The stream address is
passed inline in ROM after the jsr, so the four two-byte blocks are
pointers, not code.

**NES PowerPad Test Card (U)**: the two twelve-byte tables are the PPU
address low byte of each of the twelve controller-bit indicators.  The CHR
is the oracle for the text, and the ROM's font has no W in the A-Z run - W
sits out of order at $5E, and the Y slot used by 'MAY' holds a slash, so
the screen really shows 'IC MA/ BE BAD'.

**Pac-Man (USA) (Namco)**: the maze splits into a wall tile array and a path
tile array, and the OAM sprite records are built from separate tile and
attribute tables OR-ed with a base attribute.  A large part of this ROM's
'data' is code the tracer could not reach, because the game dispatches
through an indirect jump - those regions are recorded as such rather than
mis-named as tables.

CHANGELOG: record the tier reaching completion

Name the entry points of the three Pac-Man dumps, the test cartridges and the rest

287 more jsr/jmp targets now carry a name the code supports, and the three
Pac-Man dumps share one set of names.

Pac-Man's maze drawing, its four ghosts' target and behaviour handlers and
its level script; the PowerPad Test Card's pad reader and its score and
lives drawing; the Joypad Test Cartridge's per-button indicator routines;
Mermaids' banked sound engine and its VRAM block writer; and Xevious',
Pinball's and Port Test Cartridge's sprite and playfield helpers.

Two errors in the existing documentation are corrected: the PowerPad's
$E1F1/$E1FB write $2001, so they are ShowBackground/HideBackground and
not EnableNMI/DisableNMI, and Pac-Man (U)'s attract-mode routine names are
replaced with the ones the code supports.

Every project still prints Byte-identical ROM verified.

CHANGELOG: the final entry-point numbers
2026-10-22 00:33:54 -04:00

863 lines
15 KiB
Plaintext
Raw Permalink Blame History

C000 Reset
C006 SubCC006
C00E SubCC00E
C012 SubCC012
C02C NmiHandler
C12D SubCC12D
C178 SubCC178
C18E SubCC18E
C1E1 SubCC1E1
C20D SubCC20D
C214 SubCC214
C274 SubCC274
C27C SubCC27C
C287 SubCC287
C28C SubCC28C
C292 SubCC292
C298 SubCC298
C2B3 SubCC2B3
C2BC SubCC2BC
C2C6 SubCC2C6
C2D0 SubCC2D0
C2D6 SubCC2D6
C2DC SubCC2DC
C3A6 SubCC3A6
C419 SubCC419
C437 SubCC437
C4F2 SubCC4F2
C52D SubCC52D
C563 SubCC563
C5B2 SubCC5B2
C5CA SubCC5CA
C5EF SubCC5EF
C5F9 SubCC5F9
C5FE SubCC5FE
C61C SubCC61C
C636 SubCC636
C63B SubCC63B
C663 SubCC663
C711 SubCC711
C721 SubCC721
C725 SubCC725
C81C SubCC81C
C81D SubCC81D
C82F SubCC82F
C837 SubCC837
C844 SubCC844
C848 SubCC848
C84E SubCC84E
C852 SubCC852
C855 SubCC855
C860 SubCC860
C88F SubCC88F
C8CD SubCC8CD
C937 SubCC937
C94B SubCC94B
C97B SubCC97B
CA1C SubCCA1C
CA22 SubCCA22
CA26 SubCCA26
CA2F SubCCA2F
CA57 SubCCA57
CA7C SubCCA7C
CA9F SubCCA9F
CAD2 SubCCAD2
CB22 SubCCB22
CB46 SubCCB46
CB8C SubCCB8C
CB9F SubCCB9F
CBAA SubCCBAA
CC64 SubCCC64
CCE8 SubCCCE8
CD4C SubCCD4C
CDB6 SubCCDB6
CE37 SubCCE37
CE90 SubCCE90
CE98 SubCCE98
CF21 SubCCF21
CF29 SubCCF29
CFB1 SubCCFB1
CFD8 SubCCFD8
CFDF SubCCFDF
D02B SubCD02B
D055 SubCD055
D067 SubCD067
D075 SubCD075
D097 SubCD097
D18F SubCD18F
D1AD SubCD1AD
D213 SubCD213
D226 SubCD226
D239 SubCD239
D23F SubCD23F
D27E SubCD27E
D2B1 SubCD2B1
D2D0 SubCD2D0
D2EF SubCD2EF
D2FA SubCD2FA
D305 SubCD305
D30A SubCD30A
D30F SubCD30F
D320 SubCD320
D404 SubCD404
D415 SubCD415
D46E SubCD46E
D49C SubCD49C
D4C1 SubCD4C1
D5CA SubCD5CA
D5DC SubCD5DC
D66F SubCD66F
D672 SubCD672
D69C SubCD69C
D701 SubCD701
D748 SubCD748
D74E SubCD74E
D7C2 SubCD7C2
D868 SubCD868
D8C4 SubCD8C4
D91F SubCD91F
D970 SubCD970
D99C SubCD99C
D9A0 SubCD9A0
DA1D SubCDA1D
DA21 SubCDA21
DAA2 SubCDAA2
DB27 SubCDB27
DB5F SubCDB5F
DB86 SubCDB86
DB94 SubCDB94
DBA6 SubCDBA6
DBB8 SubCDBB8
DBDE SubCDBDE
DC04 SubCDC04
DC2A SubCDC2A
DC68 SubCDC68
DC79 SubCDC79
DC86 SubCDC86
DC93 SubCDC93
DCB1 SubCDCB1
DCBC SubCDCBC
DD3C SubCDD3C
DD4F SubCDD4F
DD58 SubCDD58
DD6F SubCDD6F
DE9F SubCDE9F
DEB5 SubCDEB5
DEC0 SubCDEC0
DEC6 SubCDEC6
DED3 SubCDED3
DEDC SubCDEDC
DEE2 SubCDEE2
DF03 SubCDF03
DF09 SubCDF09
DF0C SubCDF0C
DF1F SubCDF1F
DF2D SubCDF2D
DF3C SubCDF3C
DFAD SubCDFAD
DFBD SubCDFBD
DFCB SubCDFCB
DFE5 SubCDFE5
DFEE SubCDFEE
E00E SubCE00E
E015 SubCE015
E172 SubCE172
E192 SubCE192
E1D2 SubCE1D2
E1DB SubCE1DB
E206 SubCE206
E20C SubCE20C
E212 SubCE212
E218 SubCE218
E21E SubCE21E
E226 SubCE226
E242 SubCE242
E258 SubCE258
E271 SubCE271
E2A2 SubCE2A2
E664 SubCE664
E690 SubCE690
E6B0 SubCE6B0
E75D SubCE75D
E789 SubCE789
E791 SubCE791
E7B2 SubCE7B2
E7B8 SubCE7B8
E814 SubCE814
E844 SubCE844
E84E SubCE84E
E869 SubCE869
E870 SubCE870
E877 SubCE877
E883 SubCE883
E886 SubCE886
E8FB SubCE8FB
E90F SubCE90F
E92C SubCE92C
E97D SubCE97D
E98B SubCE98B
E998 SubCE998
E99D SubCE99D
E9B8 SubCE9B8
E9FE SubCE9FE
EA04 SubCEA04
FFF9 IrqHandler
# ---- derived internal branch-target names ----
C000 Reset
C006 SubCC006
C00A SubCC00A_Loop
C00E SubCC00E
C012 SubCC012
C01B SubCC01B_OnNonzero
C02C NmiHandler
C043 SubCC043_Loop
C050 SubCC050_Loop
C07B SubCC07B_Loop
C0A4 SubCC0A4_Loop
C0BF SubCC0BF_OnZero
C0D1 SubCC0D1_Loop
C0E4 SubCC0E4_OnZero
C119 SubCC119_Loop
C123 SubCC123_Loop
C127 SubCC127_Loop
C12D SubCC12D
C143 SubCC143_Loop
C16E SubCC16E_Loop
C178 SubCC178
C18E SubCC18E
C1D7 SubCC1D7_OnNonzero
C1E1 SubCC1E1
C1EE SubCC1EE_OnNonzero
C1FF SubCC1FF_OnNonzero
C20D SubCC20D
C212 SubCC212_Loop
C214 SubCC214
C24D SubCC24D_OnNonzero
C25F SubCC25F_OnNonzero
C26E SubCC26E_OnNonzero
C274 SubCC274
C27C SubCC27C
C287 SubCC287
C28C SubCC28C
C28F SubCC28F_OnNonzero
C292 SubCC292
C298 SubCC298
C2A2 SubCC2A2_OnNonzero
C2A8 SubCC2A8_OnNegative
C2AD SubCC2AD_OnNonnegative
C2B3 SubCC2B3
C2BC SubCC2BC
C2C2 SubCC2C2_OnNonzero
C2C6 SubCC2C6
C2CA SubCC2CA_Loop
C2D0 SubCC2D0
C2D6 SubCC2D6
C2DC SubCC2DC
C2E5 SubCC2E5_OnNonzero
C3A6 SubCC3A6
C3BF SubCC3BF_OnZero
C3C9 SubCC3C9_OnNonzero
C3DB SubCC3DB_Loop
C3E3 SubCC3E3_OnZero
C3F2 SubCC3F2_Loop
C40A SubCC40A_Loop
C419 SubCC419
C427 SubCC427_Loop
C42A SubCC42A_Loop
C42D SubCC42D_OnNonzero
C437 SubCC437
C451 SubCC451_Loop
C46B SubCC46B_OnZero
C47C SubCC47C_Loop
C48C SubCC48C_Loop
C491 SubCC491_Loop
C4A1 SubCC4A1_OnNonzero
C4AD SubCC4AD_Loop
C4B7 SubCC4B7_Loop
C4BA SubCC4BA_Loop
C4CA SubCC4CA_Loop
C4D3 SubCC4D3_OnZero
C4EA SubCC4EA_Loop
C4F2 SubCC4F2
C4F5 SubCC4F5_OnNonzero
C4FD SubCC4FD_Loop
C507 SubCC507_Loop
C50B SubCC50B_Loop
C516 SubCC516_Loop
C51E SubCC51E_Loop
C52D SubCC52D
C53F SubCC53F_Loop
C54B SubCC54B_Loop
C560 SubCC560_Loop
C563 SubCC563
C570 SubCC570_Loop
C577 SubCC577_Loop
C591 SubCC591_Loop
C594 SubCC594_Loop
C5A1 SubCC5A1_OnNonzero
C5A6 SubCC5A6_Loop
C5B2 SubCC5B2
C5C7 SubCC5C7_Loop
C5CA SubCC5CA
C5EF SubCC5EF
C5F9 SubCC5F9
C5FE SubCC5FE
C601 SubCC601_OnNonzero
C61C SubCC61C
C61F SubCC61F_OnNonzero
C636 SubCC636
C63B SubCC63B
C641 SubCC641_OnNonzero
C663 SubCC663
C66B SubCC66B_Loop
C711 SubCC711
C721 SubCC721
C725 SubCC725
C741 SubCC741_OnNonzero
C74D SubCC74D_Loop
C74F SubCC74F_OnNonzero
C758 SubCC758_OnNonzero
C767 SubCC767_Loop
C76A SubCC76A_OnNonzero
C771 SubCC771_OnNonzero
C785 SubCC785_Loop
C78F SubCC78F_OnNonzero
C79E SubCC79E_Loop
C7A0 SubCC7A0_OnZero
C7AF SubCC7AF_OnNonzero
C7B7 SubCC7B7_Loop
C7BA SubCC7BA_OnNonzero
C7C1 SubCC7C1_Loop
C7CC SubCC7CC_Loop
C7D1 SubCC7D1_OnNonzero
C7FE SubCC7FE_Loop
C802 SubCC802_OnNonzero
C80B SubCC80B_OnNonzero
C81C SubCC81C
C81D SubCC81D
C82F SubCC82F
C837 SubCC837
C844 SubCC844
C848 SubCC848
C84E SubCC84E
C852 SubCC852
C855 SubCC855
C860 SubCC860
C86F SubCC86F_Loop
C877 SubCC877_OnNonzero
C87B SubCC87B_Loop
C88F SubCC88F
C8B7 SubCC8B7_OnNonnegative
C8BF SubCC8BF_OnNonnegative
C8CD SubCC8CD
C8D4 SubCC8D4_OnNonnegative
C8EC SubCC8EC_OnCarrySet
C8F2 SubCC8F2_Loop
C8F8 SubCC8F8_Loop
C923 SubCC923_Loop
C937 SubCC937
C93B SubCC93B_Loop
C94A SubCC94A_Loop
C94B SubCC94B
C953 SubCC953_OnNonnegative
C960 SubCC960_OnNonnegative
C971 SubCC971_OnNonnegative
C97B SubCC97B
C990 SubCC990_OnNonnegative
C994 SubCC994_OnNonnegative
C99E SubCC99E_Loop
C9DA SubCC9DA_OnNonzero
C9FB SubCC9FB_Loop
CA01 SubCCA01_OnNonzero
CA15 SubCCA15_Loop
CA16 SubCCA16_Loop
CA1C SubCCA1C
CA22 SubCCA22
CA26 SubCCA26
CA28 SubCCA28_OnNonzero
CA2E SubCCA2E_OnZero
CA2F SubCCA2F
CA35 SubCCA35_OnNonzero
CA57 SubCCA57
CA7C SubCCA7C
CA9C SubCCA9C_Loop
CA9F SubCCA9F
CAB2 SubCCAB2_OnNonzero
CAC1 SubCCAC1_Loop
CACA SubCCACA_Loop
CACF SubCCACF_Loop
CAD2 SubCCAD2
CB00 SubCCB00_OnNonzero
CB08 SubCCB08_Loop
CB22 SubCCB22
CB42 SubCCB42_Loop
CB46 SubCCB46
CB6C SubCCB6C_Loop
CB7A SubCCB7A_Loop
CB7F SubCCB7F_Loop
CB84 SubCCB84_Loop
CB8B SubCCB8B_OnNonzero
CB8C SubCCB8C
CB9F SubCCB9F
CBA3 SubCCBA3_OnNonzero
CBAA SubCCBAA
CBB7 SubCCBB7_Loop
CBBA SubCCBBA_Loop
CBD1 SubCCBD1_Loop
CC03 SubCCC03_Loop
CC06 SubCCC06_Loop
CC23 SubCCC23_Loop
CC3F SubCCC3F_Loop
CC52 SubCCC52_Loop
CC64 SubCCC64
CC75 SubCCC75_Loop
CC7D SubCCC7D_Loop
CC91 SubCCC91_Loop
CC9C SubCCC9C_Loop
CCA7 SubCCCA7_Loop
CCB2 SubCCCB2_Loop
CCBA SubCCCBA_Loop
CCC2 SubCCCC2_Loop
CCD0 SubCCCD0_Loop
CCD1 SubCCCD1_Loop
CCE7 SubCCCE7_Loop
CCE8 SubCCCE8
CD06 SubCCD06_Loop
CD07 SubCCD07_Loop
CD1C SubCCD1C_Loop
CD2B SubCCD2B_Loop
CD2E SubCCD2E_Loop
CD3F SubCCD3F_Loop
CD46 SubCCD46_Loop
CD4C SubCCD4C
CD6C SubCCD6C_Loop
CD6D SubCCD6D_Loop
CD86 SubCCD86_Loop
CD95 SubCCD95_Loop
CD98 SubCCD98_Loop
CDA9 SubCCDA9_Loop
CDB0 SubCCDB0_Loop
CDB6 SubCCDB6
CDD6 SubCCDD6_OnZero
CDD8 SubCCDD8_Loop
CDFB SubCCDFB_Loop
CE11 SubCCE11_Loop
CE25 SubCCE25_Loop
CE28 SubCCE28_Loop
CE37 SubCCE37
CE58 SubCCE58_Loop
CE5A SubCCE5A_Loop
CE74 SubCCE74_Loop
CE8A SubCCE8A_Loop
CE8D SubCCE8D_OnZero
CE90 SubCCE90
CE98 SubCCE98
CED0 SubCCED0_Loop
CEDA SubCCEDA_Loop
CEDC SubCCEDC_Loop
CEF8 SubCCEF8_Loop
CF12 SubCCF12_Loop
CF18 SubCCF18_Loop
CF1E SubCCF1E_OnCarrySet
CF21 SubCCF21
CF29 SubCCF29
CF63 SubCCF63_Loop
CF6D SubCCF6D_Loop
CF6F SubCCF6F_Loop
CF8B SubCCF8B_Loop
CFA5 SubCCFA5_Loop
CFAB SubCCFAB_Loop
CFB1 SubCCFB1
CFBC SubCCFBC_Loop
CFBF SubCCFBF_Loop
CFC8 SubCCFC8_Loop
CFD8 SubCCFD8
CFDE SubCCFDE_Loop
CFDF SubCCFDF
D023 SubCD023_Loop
D02A SubCD02A_Loop
D02B SubCD02B
D055 SubCD055
D056 SubCD056_OnNonzero
D067 SubCD067
D06D SubCD06D_OnCarryClear
D070 SubCD070_Loop
D075 SubCD075
D096 SubCD096_Loop
D097 SubCD097
D0E4 SubCD0E4_Loop
D0F5 SubCD0F5_Loop
D0FB SubCD0FB_Loop
D118 SubCD118_Loop
D135 SubCD135_OnNonzero
D146 SubCD146_Loop
D153 SubCD153_Loop
D176 SubCD176_Loop
D18F SubCD18F
D1A2 SubCD1A2_Loop
D1AD SubCD1AD
D1B5 SubCD1B5_Loop
D1B7 SubCD1B7_Loop
D1D1 SubCD1D1_Loop
D1DA SubCD1DA_Loop
D202 SubCD202_Loop
D207 SubCD207_Loop
D213 SubCD213
D220 SubCD220_Loop
D225 SubCD225_Loop
D226 SubCD226
D233 SubCD233_Loop
D238 SubCD238_Loop
D239 SubCD239
D23F SubCD23F
D263 SubCD263_OnNonzero
D27D SubCD27D_Loop
D27E SubCD27E
D288 SubCD288_Loop
D291 SubCD291_Loop
D295 SubCD295_OnNonzero
D2AA SubCD2AA_Loop
D2AB SubCD2AB_Loop
D2B1 SubCD2B1
D2BB SubCD2BB_Loop
D2C4 SubCD2C4_Loop
D2CA SubCD2CA_Loop
D2D0 SubCD2D0
D2DA SubCD2DA_Loop
D2E3 SubCD2E3_Loop
D2E9 SubCD2E9_Loop
D2EF SubCD2EF
D2FA SubCD2FA
D305 SubCD305
D30A SubCD30A
D30F SubCD30F
D31E SubCD31E_Loop
D320 SubCD320
D33F SubCD33F_OnNonzero
D346 SubCD346_OnNonzero
D349 SubCD349_Loop
D351 SubCD351_Loop
D359 SubCD359_Loop
D361 SubCD361_Loop
D379 SubCD379_Loop
D37F SubCD37F_Loop
D389 SubCD389_Loop
D38C SubCD38C_Loop
D3A3 SubCD3A3_Loop
D3A5 SubCD3A5_OnNonzero
D3BA SubCD3BA_Loop
D3C7 SubCD3C7_OnZero
D3CE SubCD3CE_OnCarryClear
D3E4 SubCD3E4_Loop
D401 SubCD401_Loop
D404 SubCD404
D40D SubCD40D_Loop
D415 SubCD415
D41C SubCD41C_OnNonzero
D440 SubCD440_OnNonzero
D45A SubCD45A_Loop
D462 SubCD462_Loop
D46A SubCD46A_Loop
D46E SubCD46E
D470 SubCD470_OnNonzero
D476 SubCD476_Loop
D477 SubCD477_Loop
D49C SubCD49C
D4AC SubCD4AC_Loop
D4B1 SubCD4B1_OnNonzero
D4BC SubCD4BC_Loop
D4C0 SubCD4C0_Loop
D4C1 SubCD4C1
D4CD SubCD4CD_Loop
D4E1 SubCD4E1_Loop
D4EB SubCD4EB_Loop
D4EE SubCD4EE_Loop
D505 SubCD505_Loop
D53C SubCD53C_Loop
D53F SubCD53F_Loop
D56D SubCD56D_Loop
D571 SubCD571_Loop
D574 SubCD574_Loop
D587 SubCD587_Loop
D59A SubCD59A_Loop
D5BB SubCD5BB_Loop
D5CA SubCD5CA
D5D5 SubCD5D5_Loop
D5DC SubCD5DC
D5F0 SubCD5F0_Loop
D66F SubCD66F
D672 SubCD672
D69C SubCD69C
D6B9 SubCD6B9_Loop
D6CC SubCD6CC_Loop
D6D7 SubCD6D7_Loop
D701 SubCD701
D719 SubCD719_Loop
D726 SubCD726_Loop
D730 SubCD730_Loop
D733 SubCD733_Loop
D741 SubCD741_Loop
D745 SubCD745_Loop
D748 SubCD748
D74E SubCD74E
D774 SubCD774_Loop
D777 SubCD777_Loop
D793 SubCD793_Loop
D7A0 SubCD7A0_Loop
D7AA SubCD7AA_Loop
D7AD SubCD7AD_Loop
D7BB SubCD7BB_Loop
D7BF SubCD7BF_Loop
D7C2 SubCD7C2
D7DA SubCD7DA_Loop
D7E3 SubCD7E3_Loop
D7EB SubCD7EB_OnNonzero
D813 SubCD813_Loop
D81C SubCD81C_OnNonzero
D844 SubCD844_Loop
D84D SubCD84D_Loop
D868 SubCD868
D899 SubCD899_Loop
D8BE SubCD8BE_Loop
D8C3 SubCD8C3_OnZero
D8C4 SubCD8C4
D8F5 SubCD8F5_Loop
D91A SubCD91A_Loop
D91F SubCD91F
D94A SubCD94A_Loop
D96F SubCD96F_Loop
D970 SubCD970
D97F SubCD97F_Loop
D987 SubCD987_Loop
D990 SubCD990_Loop
D999 SubCD999_OnNonzero
D99C SubCD99C
D9A0 SubCD9A0
D9CE SubCD9CE_Loop
D9D8 SubCD9D8_Loop
DA02 SubCDA02_Loop
DA0C SubCDA0C_Loop
DA15 SubCDA15_Loop
DA17 SubCDA17_Loop
DA1A SubCDA1A_OnZero
DA1D SubCDA1D
DA21 SubCDA21
DA5E SubCDA5E_Loop
DA66 SubCDA66_Loop
DA89 SubCDA89_Loop
DA91 SubCDA91_Loop
DA9C SubCDA9C_Loop
DA9F SubCDA9F_Loop
DAA2 SubCDAA2
DAA8 SubCDAA8_OnNonnegative
DAE0 SubCDAE0_Loop
DAE4 SubCDAE4_Loop
DAE6 SubCDAE6_Loop
DB20 SubCDB20_Loop
DB24 SubCDB24_Loop
DB26 SubCDB26_OnNonzero
DB27 SubCDB27
DB5F SubCDB5F
DB80 SubCDB80_Loop
DB83 SubCDB83_Loop
DB85 SubCDB85_Loop
DB86 SubCDB86
DB8C SubCDB8C_OnCarryClear
DB8F SubCDB8F_Loop
DB93 SubCDB93_OnZero
DB94 SubCDB94
DBA1 SubCDBA1_Loop
DBA6 SubCDBA6
DBB3 SubCDBB3_Loop
DBB8 SubCDBB8
DBDE SubCDBDE
DC03 SubCDC03_OnZero
DC04 SubCDC04
DC0F SubCDC0F_OnNonzero
DC26 SubCDC26_Loop
DC2A SubCDC2A
DC5F SubCDC5F_Loop
DC64 SubCDC64_Loop
DC68 SubCDC68
DC76 SubCDC76_Loop
DC79 SubCDC79
DC86 SubCDC86
DC93 SubCDC93
DC9E SubCDC9E_Loop
DCB1 SubCDCB1
DCBC SubCDCBC
DD21 SubCDD21_OnNonzero
DD30 SubCDD30_OnNonzero
DD3C SubCDD3C
DD4F SubCDD4F
DD58 SubCDD58
DD62 SubCDD62_OnNonzero
DD6F SubCDD6F
DD7A SubCDD7A_OnNonzero
DD84 SubCDD84_Loop
DE9F SubCDE9F
DEB5 SubCDEB5
DEBA SubCDEBA_OnNonzero
DEC0 SubCDEC0
DEC6 SubCDEC6
DED3 SubCDED3
DED5 SubCDED5_OnNonzero
DEDC SubCDEDC
DEE2 SubCDEE2
DEEB SubCDEEB_OnNonzero
DEEF SubCDEEF_OnNonzero
DEFC SubCDEFC_OnNonzero
DF03 SubCDF03
DF09 SubCDF09
DF0C SubCDF0C
DF1F SubCDF1F
DF2D SubCDF2D
DF3C SubCDF3C
DF5D SubCDF5D_OnNonzero
DF6B SubCDF6B_OnNonzero
DFAD SubCDFAD
DFBD SubCDFBD
DFBF SubCDFBF_OnNonnegative
DFCB SubCDFCB
DFE1 SubCDFE1_Loop
DFE5 SubCDFE5
DFEE SubCDFEE
DFF0 SubCDFF0_OnNonzero
DFF8 SubCDFF8_Loop
E008 SubCE008_Loop
E00E SubCE00E
E015 SubCE015
E038 SubCE038_OnNonzero
E045 SubCE045_OnNonzero
E05E SubCE05E_OnNonzero
E06B SubCE06B_Loop
E09D SubCE09D_Loop
E0BC SubCE0BC_Loop
E0FB SubCE0FB_OnCarrySet
E124 SubCE124_Loop
E136 SubCE136_OnNonzero
E15D SubCE15D_Loop
E163 SubCE163_OnNonzero
E16D SubCE16D_Loop
E171 SubCE171_Loop
E172 SubCE172
E189 SubCE189_OnNonzero
E192 SubCE192
E1A2 SubCE1A2_OnZero
E1B4 SubCE1B4_Loop
E1B6 SubCE1B6_OnNonzero
E1C2 SubCE1C2_Loop
E1C5 SubCE1C5_Loop
E1C6 SubCE1C6_Loop
E1C8 SubCE1C8_OnNonzero
E1D2 SubCE1D2
E1D4 SubCE1D4_OnNonzero
E1DB SubCE1DB
E1E2 SubCE1E2_OnNonzero
E1F6 SubCE1F6_Loop
E206 SubCE206
E20C SubCE20C
E212 SubCE212
E218 SubCE218
E21E SubCE21E
E222 SubCE222_Loop
E226 SubCE226
E22A SubCE22A_Loop
E22C SubCE22C_Loop
E242 SubCE242
E258 SubCE258
E25F SubCE25F_OnNonzero
E270 SubCE270_OnNonzero
E271 SubCE271
E28F SubCE28F_Loop
E2A2 SubCE2A2
E664 SubCE664
E690 SubCE690
E695 SubCE695_OnZero
E69C SubCE69C_OnNonzero
E6A6 SubCE6A6_Loop
E6AA SubCE6AA_Loop
E6B0 SubCE6B0
E6B7 SubCE6B7_OnNonzero
E6C1 SubCE6C1_Loop
E6C5 SubCE6C5_Loop
E6CD SubCE6CD_Loop
E6D2 SubCE6D2_Loop
E6F4 SubCE6F4_OnNonzero
E702 SubCE702_OnNonzero
E70A SubCE70A_Loop
E718 SubCE718_Loop
E720 SubCE720_Loop
E724 SubCE724_Loop
E733 SubCE733_Loop
E73D SubCE73D_Loop
E743 SubCE743_Loop
E749 SubCE749_Loop
E753 SubCE753_Loop
E75D SubCE75D
E75F SubCE75F_OnNonzero
E76C SubCE76C_OnNonzero
E773 SubCE773_Loop
E77C SubCE77C_OnNonzero
E789 SubCE789
E791 SubCE791
E795 SubCE795_OnNonzero
E79A SubCE79A_OnNonzero
E7B2 SubCE7B2
E7B8 SubCE7B8
E7C7 SubCE7C7_OnNonzero
E7D8 SubCE7D8_Loop
E7F3 SubCE7F3_OnZero
E80D SubCE80D_Loop
E814 SubCE814
E819 SubCE819_OnZero
E81C SubCE81C_Loop
E82F SubCE82F_OnZero
E839 SubCE839_OnNonzero
E83B SubCE83B_Loop
E844 SubCE844
E84E SubCE84E
E869 SubCE869
E86F SubCE86F_OnNonzero
E870 SubCE870
E877 SubCE877
E883 SubCE883
E886 SubCE886
E889 SubCE889_OnZero
E88B SubCE88B_OnNonzero
E897 SubCE897_OnNonzero
E89A SubCE89A_Loop
E8AD SubCE8AD_OnNonzero
E8D5 SubCE8D5_Loop
E8D8 SubCE8D8_OnCarrySet
E8DA SubCE8DA_Loop
E8E1 SubCE8E1_OnZero
E8ED SubCE8ED_OnNonzero
E8FB SubCE8FB
E904 SubCE904_OnNonzero
E90F SubCE90F
E913 SubCE913_OnNonzero
E921 SubCE921_Loop
E92C SubCE92C
E937 SubCE937_OnNonzero
E944 SubCE944_OnNonzero
E94C SubCE94C_OnNonzero
E95B SubCE95B_OnNonzero
E97D SubCE97D
E983 SubCE983_OnNonzero
E98B SubCE98B
E98F SubCE98F_Loop
E998 SubCE998
E99D SubCE99D
E9A0 SubCE9A0_Loop
E9A9 SubCE9A9_OnNonzero
E9B2 SubCE9B2_OnNonzero
E9B8 SubCE9B8
E9C5 SubCE9C5_OnNonzero
E9FC SubCE9FC_Loop
E9FE SubCE9FE
EA00 SubCEA00_OnNonzero
EA04 SubCEA04
FFF9 IrqHandler
Reference in new issue View Git Blame Copy Permalink