Unzip the background.zip file.
Open a DOS window.
change into that background folder

type the following:
dir


There should be 3 files
background.asm
background.bat
mario.chr

type:
background.bat

It should complain: 'NESASM3' is not recognized as an internal or external command

Update background.bat to include the entire path to nesasm (be aware that you may need quotes if there are spaces in the path).

Alternativly, add nesasm to your sytem "PATH" variable.
to do this:
Open your "Control Panel" and click on "System". to open "System Properties"
In "System Properties" find the "Advanced" tab. and click on the "Environment Variables" button.
Find an item entitled "PATH" and edit it to add the path to your nesasm (you probably should add this at the end, and remember to add a semi colon before you enter the path)

If this all works, and nesasm is working, you should see your background.nes file being created.
Double click the NES file and your emulator should load it.
Al

Finaly made nesasm work with the controller.zip file

thanks al.

it was great to see asm make controller.nes and when the fceuxd showed mario i jumped sky high!
i can finally test all my codes and work on them.

Hi all,

well you may have copied it wrong here, but it should be #%10000000 , not %10000000. # signs can screw a lot of things up lol.

you're palette initialization looks right to me, but you shouldn't even need a palette loaded to intensify color.

This is definitely a difference between FCEUXDSP and Nestopia.  I compiled FCEUX on OS X, and it did not need the palette initialized.  I'll leave it in is it doesn't change anything on FCEU*.

cool, I use NESASM3 and FCEU so, I couldn't be much help. I looked at your source and I didn't see any reason it shouldn't run. I thought maybe there might have been a difference between ca65 and NESASM, but nice to know it was just the emulator.

I've verified that the initial palette on Nestopia is not all zeros.  Take a look at the Nestopia source code in NstPpu.cpp:

Is there any reason, that bank 0 is at memory location $C000, instead of $8000, where the cartige ROM starts? $0000 is the internal RAM, but there is only 2KB of RAM, and bank 2 is 8KB. And what about the CHR RAM? The graphics shouldn't be there?

You can have 16k of ROM space starting at $C000 or 32k starting at $8000.

The bank 2 here is referring to CHR ROM starting at $0000 in the PPU (note that the PPU and CPU memory are in different address spaces).

Thank you, now I understand it.

Would anyone know the reason why, when I make a save state on fcgeux, that the colors turn from green, where I have it now;

LDA #%11000000 ;intensify blues
STA $2001

Back to a dull gray.
I don't yet know how to bring the new save state back into a format that I can analyze in a text document like the original asm to see what has changed either...

You guys rock the rocks, btw.
Cheers!

I'm not really sure how save states work. I assume it just picks up the code from wherever it left off when you saved it. Perhaps it's just waking up in the infinite loop and bypasses all the loading stuff? I have no idea.

Would there be a way to open it into the rom and the decompile it reanalyze the code in the save state to try to see exactly what changed where? Wouldn't Fceuxdsp be able to do this somehow?

P.S. I hope there's a tutorial coming up here on changing the palette more, cause I want to make my rom- yellow!

oh, the tutorials will do a lot more than that. I think week 4 does palettes, you'll probably never use the intensify line again. It's the most basic of things. Palettes are much more fun

How can I make a NES ROM to support right to left language?
I don't have any problem for translating fixed text on the screen but texts which gradually appear from left to right, are really hard to translate.
Captain Tsubasa Arabic translation is a good example for this matter.
I guess I have to do it in assembly 6502 but I don't have any idea how to do it?
I appreciate anyone who can help me.

Also some other nice people guide me but I really need some more help :

http://www.romhacking.net/forum/i...

Anyone know what the label NMI means for the vBlank section? Why NMI? Why not vBlank0 or something?

http://wiki.nesdev.com/w/index.php/NMI

i have a question to the BNE/BEQ command. How can i figure out which adress the code passages have?

Sorry for the necropost, but I'm having trouble understanding why the banks begin where they do. In the sample code from the download link .bank0 starts at .org $C000, .bank1 starts at .org $FFFA, and .bank2 starts at .org $0000. Is .org specifying where to put the code in reference to the system's memory map or the cart rom's? $FFFA is too big a number for the 32KB cart, so I have to assume we're dealing with the CPU's memory map. And why does .bank0 start at $C000? Does it need to go there or did you just put it there because you wanted to? Also, the 32KB cart rom on the memory map from week 2 doesn't include the 16KB chr rom, correct? I'm thinking the chr rom is outside the CPU's memory map and can only be accessed by the PPU. Is that why the chr rom can start at $0000, because it isn't really a part of the CPU's memory map?

Thanks for the tutorials. Anymore help you or anyone else can give is greatly appreciated.

Thanks for the reply. Is 16KB the maximum the prg rom can be? I was under the impression it could be a maximum of 32KB with 4 8K banks. Also why are things arranged in 8K banks? Is this just how NESASM likes to do it, or does the hardware need it that way for some reason.

Sorry for all the questions, but I would like to get this down before I move on. Thanks again.

NESASM just puts them in 8KB banks. You can put more data in it, but then you'll have to use a mapper, probably first off a logic mapper, then maybe MMC1 then if you get really good, MMC3.

Yes, 32KB is the maximum without mappers. Then the data will appear at $8000-FFFF, unmirrored, so you should use .org $8000 and put it in 4 NESASM banks.

Hello, I'm trying to get into assembly programming through NES development,
but I have some trouble understanding some stuff from your attached code. Please help me,
I really want to understand this before moving on.



01. RESET:
02. SEI ; disable IRQs
03. CLD ; disable decimal mode
04. LDX #$40
05. STX $4017 ; disable APU frame IRQ
06. LDX #$FF
07. TXS ; Set up stack
08. INX ; now X = 0
09. STX $2000 ; disable NMI
10. STX $2001 ; disable rendering
11. STX $4010 ; disable DMC IRQs
12. vblankwait1: ; First wait for vblank to make sure PPU is ready
13. BIT $2002
14. BPL vblankwait1



Line 02 - IRQ's have to be disabled if not used, but why?
Line 03 - Decimal mode not supported by the 2A03
Line 04.05 - Aren't address $4017 controller 2? How is that connected to the APU? What is so special
about the number $40?

Line 06.07 - $FF last memory location in stack, initialize stack to this value.
Line 08 - Increment $FF so it overflows and becomes 0.
Line 09.10.11 - Set all bits in address $2000, $2001 and $4010 to 0. The first two I understand
but what is a DMC IRQ, and why does it need to be disabled?

Line 12.13.14 - I know the PPU have to warm up before using it, but what exactly do these lines of code do?



Please someone, look through this and correct me where I'm wrong,
and help me understand this code. I'm new to the field of computer science,
but I got a book coming in the mail any day now that will introduce me to
boolean algebra and stuff like that, which, if I understand it correctly,
is essential to NES dev and ASM programming in general.
Sorry for the long post.