Game Boy

[Helius]

Very nice djh, keep us informed!

I didn't even try the bootrom myself. Not many people making Game Boy emulators these days.

I'm trying to port my emulator to Raspberry Pi so I will be monitoring the thread if I can be of any help. Feel free to ask.

[hackiosa]

Hey guys!
I'm writing a GameBoy Emulator in .net, that will be open source. But I got the following problem.
I've already written the code for memory managment (including code for the most MBCs), for register managment, for mapping file ecettera.
But now I'm on adding all the about 400(?) opcodes, but I don't exactly know what the following opcodes do.

• RL
  RLA
  RLC
  RLCA
  RLD
  RR
  RRA
  RRC
  RRCA
  RRD

Note: These are for the Z80 Cpu. I know , they got something to do with bit shifting.

Greetz hackiosa

[Helius]

Those are rotations, you know, rotate left (RL), rotate right (RR)...

These two documents will help with the opcodes.

Good luck with your emu and keep us updated

[Mepsi]

Hey, newbie to these forums here.

I am rather interested in making a GB emulator for myself, as far as my coding experience goes, I can program just not to a massively advanced level.
I had a go at doing a Chip8 emulator in C# using XNA last night and managed to complete it in about 12 hours and I must say it was the most fun I've had programming in a long time.

Anyway I'm trying to get my head around this GB emulation and I just cant get my head around it quite yet, one of the big things for me is how do I go about implementing the interrupts and timings properly, any help will be much appreciated, or any recomendations on easier emulators past the Chip8 I can work on first.

[Helius]

Going from chip-8 to Game Boy is a massive step forward. Be prepared for 50x the complexity and size of chip-8.

Space Invaders is easier than Game Boy but not very rewarding as you will end up playing only one game :-P

I recommend you not bothering with interrupts for now. Start by implementing all the opcodes and basic background rendering, this way you'll see your results pretty quickly and improve from there.

For the timing just execute the opcodes and save their cycle counts to a variable. Use that to update the graphics state accordingly.