EmuCR Feeds
Email Us

EmuCR: BizHawkBizHawk SVN r2574 is compiled. BizHawk is a A multi-system emulator written in C#. BizHawk provides nice features for casual gamers such as full screen, and joypad support in addition to full rerecording and debugging tools for all system cores.

BizHawk Supported Systems
- Nintendo Entertainment System (NES)
- Sega Master System
- SG-1000
- Game Gear
- PC-Engine (TurboGrafx-16) / CD-ROM
- SuperGrafx
- TI-83 Calculator

BizHawk Experimental
- Sega Genesis (low compatibility list)
- Gameboy (Debugger only)

BizHawk SVN Changelog:
r2570
-Finished the disassembler with the branches.
-Added bytesToAdvance assignments to the relevant opcodes I added yesterday.

TODO: Implement more stuff in Execute and use the Executive ROM as a test case.
r2571
NES - add mapper 61, chr mapping is off somehow
r2572
Implemented / tested MVI@ and AND@.
-They both seem to work, but the operands for AND@ are both 0, so this seems fishy.
-I don't know for sure if AND@ executes cycles in the same way that MVI@ as the documentation isn't clear on this, but I assumed it did.

According to my disassembler, the first 5 instructions run on the Executive ROM are:

JSRD R5, $1026
MVI@ R7, R6
ADD@ R6, R1
JSR R5, $1A83
HLT

Considering that I hit a HLT, I figure something is going terribly wrong. Perhaps it has to do with my lack of an interrupt system?
r2573
LuaWriter. Now colors Multi-Line Comments.
r2574
-Made MVI@ and ADD@ follow the stack and immediate mode rules for incrementing / decrementing the SP / PC.
-Disabled Intellicart hook for ReadMemory, which seemed to be interfering.
-Implemented MVO@.
-Several instructions are now executed in succession until it hits the unimplemented "XORR R5, R5".

I should probably refactor Disassemble and Execute to label registers as source / destination to avoid further confusion at some point. My disassembly might have the source / destination registers flipped as well.

Download: BizHawk SVN r2574
Source: Here



Random Related Topic Refresh Related Topic

Random Related Topic Loading...

0 Comments

Post a Comment

Can't post a comment? Try This!