Recommendations for testing 6502 core?

[mreiland]

So I finally got a chance to pick up the 6502 project again (very intermittent unfortunately) and I've finished the initial implementation of all the documented opcodes. I'm sure there's a dozen things wrong them due to mistakes made by me and also misreading of the documentation. Since I'm so new to 6502 I'd prefer to run tests written by someone with more experience to help suss out the issues.

I came across the following page: http://visual6502.org/wiki/index.php?ti ... stPrograms

and in particular I downloaded the klaus test suite.

But here's my conundrum. Until now I've been mostly just grabbing the binary hexdump on http://skilldrick.github.io/easy6502/ and saving it to binary files and loading it up @ memory location $0600 and executing from there (because that's how the site itself does it). I've written a few small tests of my own and kept doing it with an assumption of loading in @ $0600.

But I have no clue how to load the klaus examples in a reliable manner. I'm also unsure of which test suite is best suited for my needs (NES emulation, fairly ignorant of the CPU in general).

Does anyone have any recommendations of test suites that would be good for me? I did come across a thread on here for nestest.asm I think, but I got the feeling it was NES specific rather than just 6502. In a perfect world I would find something that's geared towards NES emulation, but only tests the 6502 core itself.

I apologize if this seems redundant, in this I'm so ignorant I'm unsure where to even start looking. That coupled with there being so many different things out there and I'm just not sure what the most productive way to start testing the 6502 core is.

[tepples]

Despite the name, "nestest" really is just for the 6502.

[Movax12]

nestest.asm I think, but I got the feeling it was NES specific rather than just 6502. In a perfect world I would find something that's geared towards NES emulation, but only tests the 6502 core itself.

From the documentation:

This test program, when run on "automation", (i.e. set your program counter
to 0c000h) will perform all tests in sequence and shove the results of
the tests into locations 02h and 03h.

No need for anything to be emulated other than the 6502 if you start executing at C000.

And see this post: viewtopic.php?p=6307#p6307

[mreiland]

Alright, thanks guys