nesdev.org

That's what i meant, too. Some flags wrong in other opcodes, which are causing wrong program flow.

If all tests fail to execute successful, altough they are most likely correct, that means some flags are wrong? Running test 06-ld r,r outputs this: 06-ld r,r 40 41 42 43 44 45 46 47 48 49 4A 4B 4C 4D 4E 4F 50 51 52 53 54 55 56 57 58 59 5A 5B 5C 5D 5E 5F 60 61 62 63 64 65 66 67 68 69 6A 6B 6C 6D 6E ...

Found the bug in my generated code, the CP n opcode. /* CP n */ void Processor::CP_n() // 0xFE { SetFlag(FLAG_SUB); if (A < memory->ReadByte(PC++)) EnableFlag(FLAG_CARRY); if (A == memory->ReadByte(PC++)) EnableFlag(FLAG_ZERO); if (((A - memory->ReadByte(PC++)) & 0xF) > (A & 0xF)) EnableFlag...

I'll do, I just add passing the rom name from the commandline, so you can test.

[EDIT] Don't have time anymore today. Could you build it from my Github repository and change the rom name inside main.cpp

Thanks for the suggestion, I double checked the RET Z opcode and it seems correct. Also I tried running the individual tests and they give me no output at all. /* RET Z */ void Processor::RET_Z() // 0xC8 { if (IsFlagSet(FLAG_ZERO)) { condition = true; StackPop(PC); } } void Processor::StackPop(uint1...

Hello, I've just started writing my own gb emulator. After finishing implementing all opcodes, I wanted to see if it's actually working by running Blargg's cpu_instr rom. As I have no working lcd emulation atm I'm printing the output by reading from the SB port. Now running the rom I got some strang...