Page 1 of 1

strange output on blargg tests

Posted: Sun May 31, 2015 3:56 pm
by theotherjim
Hi all,

I'm getting some bizarre output running the individual roms for blargg's cpu tests. At the end of the test run when (I assume) all the tests pass, I get output like:

Code: Select all

Failed #10L

Any ideas what might be causing it?

Also, running the full rom shows strange behavior:


Any feedback or things to check would be appreciated.

Re: strange output on blargg tests

Posted: Wed Jun 03, 2015 9:45 am
by Shonumi
Hard to say. Could be rendering issue, or something to do with your CPU emulation (...which in turn would cause a rendering issue). Have you tried running other test ROMs for basic graphical output (or for that matter, commercial ROMs?) I would suggest trying Imran Nazar's Opus 5 demo ( It's what I cut my teeth on way back when I started GB/GBC emulation. Try to at least get that displaying the BG correctly, then move on to several title screens for commercial games. Super Mario Land, Tetris are good ones to start with, since they don't really do anything fancy before displaying things on-screen.

Also, for individual tests, it should be easy enough to run it through a debugger (look into BGB) and see if you're doing everything correctly. If not, then you definitely have a CPU issue, and you should look into what behavior the test considers accurate. Of course, you should have a debugger in your own emulator. If not, code one right away! I can't stress enough how important this is ;)

Re: strange output on blargg tests

Posted: Thu Jun 04, 2015 8:40 am
by theotherjim
The Opus5 demo is definitely exposing some issues. It looks like I have some graphical issues to sort out first. (ship appears many times in the background) Then apparently quite a bit of other work too as the background is scrolling (oddly) non-stop. Definitely going to work on a debugger first though. I've just been using xcode as my primary debugger, but it clearly doesn't supply all the information I need to properly work through this. I'll take a look at bgb. Thanks!

Re: strange output on blargg tests

Posted: Thu Jun 04, 2015 9:01 pm
by Dwedit
Opus5 appears to be quite buggy. On VisualBoyAdvance you can see lots of discontinuities if you scroll diagonally.
It appears to look fine on NO$GMB though. In BGB, it crashes at an invalid opcode after jumping to ram or echo ram.

I can't recommend use of buggy test programs for testing emulators.

Re: strange output on blargg tests

Posted: Fri Jun 05, 2015 12:01 am
by Shonumi
Those discontinuities are present on real hardware. If it appears fine in NO$GMB, it's inaccurate emulation. BGB shouldn't crash if real hardware doesn't either. VBA-M gets it correct in this case (well, almost, the irregularities should have a staircase pattern on real hardware). I would imagine Gambatte works too, but I haven't built it in a while.

The purpose of Opus 5, for those beginning to write a GB emulator, is just to test fundamental BG rendering. Pop it open in your emulator; if you don't see asteroids, you know you have core issues with LCD emulation. Since it actually does have some unique scrolling quirks, it's probably a better judge of accurate LCD emulation than other "basic" demos.

Re: strange output on blargg tests

Posted: Sat Feb 09, 2019 11:46 pm
by telliott
I was seeing the same thing on my emulator project and in my case this was because I had the carry flag behavior reversed for the CP instruction (see this post on StackOverflow).

Because CP was setting the carry flag incorrectly, a JP C call following CP wasn't jumping as expected, and the flow dropped into failure output, so both "Passed" and "Failed" were being output during the exit routine.