Hi all!
I'm yet another person writing yet another NES emulator. My reason is mostly for self enrichment, not so much to replace any thing that is out there already. I've called it ALIAneS and am building it on OS X in C++. I have CPU emulation nearly complete, with only a handful of opcodes left to write. I do not have any PPU or controller emulation.
For fun I loaded up nestest.nes and ran it in ALIAneS, starting execution at 0xc000. I spent half an hour comparing line by line output with the Nintendulator log... before realizing it was 8000 lines long...
Without any visual or sound output other than an execution log, is there any good way to test opcodes without comparing line by line? Would just comparing the execution addresses be sufficient?
Thanks!
I'm yet another person writing yet another NES emulator. My reason is mostly for self enrichment, not so much to replace any thing that is out there already. I've called it ALIAneS and am building it on OS X in C++. I have CPU emulation nearly complete, with only a handful of opcodes left to write. I do not have any PPU or controller emulation.
For fun I loaded up nestest.nes and ran it in ALIAneS, starting execution at 0xc000. I spent half an hour comparing line by line output with the Nintendulator log... before realizing it was 8000 lines long...
Without any visual or sound output other than an execution log, is there any good way to test opcodes without comparing line by line? Would just comparing the execution addresses be sufficient?
Thanks!