how to test programs

[log in]

Im totaly lost now

have read some many files/docs,with my poor english and made it this far.
But now im stuck in a real strange way

now about number systems

I now how the nes console and cart look like inside and how the work to gether

I even now how to make basic nes programs. The beginning that is
.inesprg etc and even now what it means.

Never even thought i would make it this far


But now im stuck in a strange way

i thought i would try making some programs what i did.
By writting them on paper.

But i dont now what to do next? Icant find noob friendly info/docs or im looking wrong

How do i test my codes?

Write them in notepad or wordpad,run them threw ah nes assembler and put the outcome into a emulator right?

[Celius]

Write them in notepad or wordpad,run them threw ah nes assembler and put the outcome into a emulator right?

Yes, but make sure it's an accurate emulator like Nintendulator. FCEUXD is a great emulator for debugging, and it's fairly accurate (I'm pretty sure). Nintendulator is more accurate, but it's not as easy to debug with.

EDIT: Actually, if you want, I've written a simple NROM setup for WLA-DX:
http://www.freewebs.com/the_bott/test.rar

Just put your code under the "Reset" label or the NMI label, and just double-click the .bat file included, and it'll compile your ROM for you provided you didn't make any typos.

[log in]

what are the best assemblers by the way?

keep reading that nes asm is bad

[Celius]

There is much controversy over such topics... It is generally agreed that NESASM is limited in lots of ways, but it is good for starting out because it's easy to set up a file to code right away. The most commonly used assembler around here is CC65 (CA65? I don't know the difference), I think, but I don't know too much about it. I use WLA-DX, but there are some things that I find annoying about it like having to put a ".w" after every "ldy 16-bit address". WLA is good, and it has lots of features, but I don't know, CC65 may have them + more.