alfonsohdez08 / nessharp Goto Github PK

Creates an iNES parser in order to parse a NES rom. It must follow the specifications of an INES file: http://fms.komkon.org/EMUL8/NES.html#LABA https://sadistech.com/nesromtool/romdoc.html

The memory layout should follow the NES memory layout: https://en.wikibooks.org/wiki/NES_Programming https://wiki.nesdev.com/w/index.php/CPU_memory_map
http://www.fceux.com/web/help/fceux.html?6502CPU.html

• Review how each instruction affects the CPU flags.
• Implement the arithmetic, logical and shift operations.
• Review the current design of how a cycle is executed (fetch -> decode -> execute).
• Abstract the addressing modes (there should be a single method per each instruction, not a method per instruction and its addressing mode). Addressing modes and instructions should be decoupled (addressing modes it's the approach for fetch from memory the instruction's operands).

Avoid using properties that are evaluated each time we call... I see we can use fields and just store their values when main value is written to - usually from the cpu. For instance, the Control Register might take help from this.

Just a basic assembler that would take the 6502 instructions (program) and dump it into hexadecimals. Its main use would be for test the CPU functionalities (tests automation).

• How can I make this project run in Mac?

• Would it be possible to migrate to .Net Core ?

Use the cpu nes rom in order to test my 6502 implementation. The expected log is this one: http://www.qmtpro.com/~nes/misc/nestest.log

The cpu nes rom follows the iNES format, so an iNES parser is required first. The PRG-ROM (the program itself) should be loaded in the NES memory locations where the PRG-ROM should reside ($8000–$FFFF); more information about this is here: http://forums.nesdev.com/viewtopic.php?f=10&t=14232