nesdev.org

You mean cc65 right? If so the cc65-nes-2 version or the dos32.

I think cc65 is the name of the whole package, and specifically the C compiler.

ca65 is the name of the assembler.

How is it run? Do i have to compile it?

You don't need to compile it if you use Windows and use the Windows binary.

You run ca65 and ld65 from the command prompt. If you have used GCC before, then it'll be familiar.

Same thing with NESASM to run it(cc65 file.asm)? Im kinda curious what are the include files for? It has everything from 6502 to Vic-20!!!!

Memblers wrote: The lazy way is to rip the first 16 bytes off an .NES file that has the same setup (size, mapper, etc), then do a "copy /b header+romname.bin romname.nes".

How do i do that? do i do it in x816? ive got my header from another file and my .bin.

A hex editor would probably help.

no i mean the "copy /b header+romname.bin romname.nes". but thats a good way too.

the "copy" instruction is a command line command (or whatever those are called). You input it at a command prompt and it does the work.

In a Windows environment, your best approach would probably be to create a batch file (an ordinary .txt file which has several instructions to give to the command prompt -- with the extention changed to .bat). When you execute the .bat file, the command prompt pops up and automatically runs everything in the .bat file in order. This makes assembling as simple as double-clicking a file.

If you want to assemble "demo.asm" into "demo.nes" with x816, here's an example of what your .bat file might look like when viewed in Notepad or some other hex editor:
I like to end with a 'pause' command so that the window will stay open until I press a key (so I can see any assembler errors that may have happened). You can omit the pause and the command prompt will open and shut almost instantaneously -- everything will assemble fine, but you won't be able to read any of the output.

What does mean?

Is the directive that .incbins the .chr to the source directory, in the header. For Example: What do i about compliing with the other files .nam, .spr, and .chr ?

nineTENdo wrote:What does

Code: Select all

.mem 8
.index 8

mean?

It tells the assembler that you're compiling for a 6502 (i.e. 8-bit registers, as opposed to the 65816 which can potentially do 16-bit registers).

nineTENdo wrote:Is the directive that .incbins the .chr to the source directory, in the header. For Example:

Code: Select all

        bank 2
	.org	$0000                        < is this in the header?  If not Where is it?
	.incbin "jumpy.chr"

If you're using x816, it does not create a header - you'll either have to create it with a hex-editor, or put a bunch of .byte/.db statements (whatever x816 uses for inline data blocks) to manually encode the iNES header. Personally, I prefer a 3rd method, which is to have a separate "makeiNES" program which produces the header from a human-readable text file and combines it with the PRG and CHR data (automatically filling in the PRG/CHR sizes in the header).

With MakeINES, What do i about compliing with the other files .nam, .spr, and .chr ?

What is PROG filename.obj?

hOW DO .CHR, .NAM, .INCBIN. get incorperated into the header in x816? Can Someone really help with setting up so i can assemble with the x816? Im still in the rut.

Thanks o wise ones,
EL


P.s. Does anyone have "makeines" i lost it and i cant seem to find the website to it.

http://www.qmtpro.com/~nes/tools/makeines10.zip

If you're using makeines, then you don't include any CHR data in your PRG file - you just use .incbin to include any nametable data and whatnot that needs to be directly accessed by the CPU.