I'm trying to create an IPS file to change gameplay in a ROM.
The rom image is more than 16k and does not use mapper 1 so the NESREV disassembler won't work -- http://www.stud.ntnu.no/~kenth/nesrev/
Some of the features that would help:
- break on game controller reads/writes
- break on rom bank swaps (both data and code banks)
- turn on a flag that marks part of the rom as code for each instruction executed
- Memory reference map showing all locations read from, all locations written to, and all code executed. This would help me to quickly identify things such as title screen code/data, or the code/data used for a particular part of the rom.
I have been using these tools:
- fceu - ok but the debugger lacks functionality
- nesten
- hex editor
Some missing tools:
- call stack listing
- bank map breakpoints (when a new bank of code or data is mapped)
- indentation of code based on control flow instructions (BNE, JMP, BVC)
- ability to name blocks of code (such as 'get controller data')
The rom image is more than 16k and does not use mapper 1 so the NESREV disassembler won't work -- http://www.stud.ntnu.no/~kenth/nesrev/
Some of the features that would help:
- break on game controller reads/writes
- break on rom bank swaps (both data and code banks)
- turn on a flag that marks part of the rom as code for each instruction executed
- Memory reference map showing all locations read from, all locations written to, and all code executed. This would help me to quickly identify things such as title screen code/data, or the code/data used for a particular part of the rom.
I have been using these tools:
- fceu - ok but the debugger lacks functionality
- nesten
- hex editor
Some missing tools:
- call stack listing
- bank map breakpoints (when a new bank of code or data is mapped)
- indentation of code based on control flow instructions (BNE, JMP, BVC)
- ability to name blocks of code (such as 'get controller data')