EDIT: not sure why the images didn't come through...ack!
It's been a while since essial or I posted anything about NESICIDE2. Lots has been going on!
I remember a while back there was discussion about code timing methods. A thought occurred to me on this, and I came up with the relatively simple but [I think powerful and useful] concept of the Execution Visualizer.
First, here it is being set up. The colored cells in the disassembly view are markers indicating code to be visualized. Markers can be anywhere and cover any code. [For example IRQ handling for MMC3].
Once you've set up your markers, opening the Execution Visualizer and running the emulator provides a colorized view of exactly where in the PPU cycle domain your marked code is executing.
It just so happens that I picked code that is in VBLANK. The dark-gray rectangle surrounding the emulator's screen is the PPU frame or 341x262 dots. If I had picked code that executes while the PPU is rendering it would show up on top of the screen [which will be hide-able in order to more clearly see the execution markers]. IRQ code [MMC3 for example] shows up in the right HBLANK area.
Execution Visualizer also works with source-code. You can set markers on your source, compile, and watch.
I intend to add more information to this such as SLOC, min/max cycles, etc.[/img]
It's been a while since essial or I posted anything about NESICIDE2. Lots has been going on!
I remember a while back there was discussion about code timing methods. A thought occurred to me on this, and I came up with the relatively simple but [I think powerful and useful] concept of the Execution Visualizer.
First, here it is being set up. The colored cells in the disassembly view are markers indicating code to be visualized. Markers can be anywhere and cover any code. [For example IRQ handling for MMC3].
Once you've set up your markers, opening the Execution Visualizer and running the emulator provides a colorized view of exactly where in the PPU cycle domain your marked code is executing.
It just so happens that I picked code that is in VBLANK. The dark-gray rectangle surrounding the emulator's screen is the PPU frame or 341x262 dots. If I had picked code that executes while the PPU is rendering it would show up on top of the screen [which will be hide-able in order to more clearly see the execution markers]. IRQ code [MMC3 for example] shows up in the right HBLANK area.
Execution Visualizer also works with source-code. You can set markers on your source, compile, and watch.
I intend to add more information to this such as SLOC, min/max cycles, etc.[/img]