game.s<\/code> and save it in a folder. It now needs to be compiled with ca65<\/code> and linked with ld65<\/code>. Let’s see what happens.<\/p>\nIf you don’t know what ca65<\/code> and ld65<\/code> are, check out Part 0: Tools needed<\/a>.<\/p>\nStart with compiling the source file into an object file.<\/p>\n
ca65 game.s<\/code><\/p>\nNo error and a 251 byte game.o<\/code> was created. Good so far! Now link the object file.<\/p>\nld65 game.o
\nld65: Error: Memory configuration missing<\/code><\/p>\nSo, the cc65<\/code>\u00a0tools can build binaries for a bunch of different 6502 based systems with different memory layouts, the NES being just one of them.<\/p>\nUsually you’d now need to write a detailed memory map configuration file. Luckily we don’t have to do any of that, since there is already one for the NES bundled with the compiler.<\/p>\n
I’ll go into more technical details later on, for now let’s postpone learning about the memory layout and just get this thing working.<\/p>\n
To use the bundled config file just specify nes<\/code> as the system type. And let’s also name our output file.<\/p>\nld65 -t nes game.o -o game.nes<\/code>
\nld65: Warning: (...)\/nes.cfg(63): Segment `HEADER' does not exist
\nld65: Warning: (...)\/nes.cfg(63): Segment `STARTUP' does not exist
\nld65: Warning: (...)\/nes.cfg(63): Segment `VECTORS' does not exist
\nld65: Warning: (...)\/nes.cfg(63): Segment `CHARS' does not exist<\/code><\/p>\nA few warnings, but no errors, and a 40976 byte game.nes containing all zeroes was created.<\/p>\n
Let’s try running it in the emualtor<\/p>\n
fceux.exe game.nes<\/code><\/p>\n![\"\"](\"https:\/\/www.betelge.com\/blog\/wp-content\/uploads\/2018\/03\/fceux_error-300x278.png\")
<\/p>\n
Alright, so we’re missing something. Not surprising since the ROM contains all zeroes.<\/p>\n
ROMs need to start with the NES header. And the NES header starts with 4 specific bytes, the ASCII characters NES and the hexadecimal value 1A.<\/p>\n
Add the following to game.s<\/code><\/p>\n.byte \"NES\"\r\n.byte $1A<\/pre>\nAnd try again<\/p>\n
ca65 game.s
\nld65 -t nes game.o -o game.nes
\nld65: Warning: (...)\/nes.cfg(63): Segment `HEADER' does not exist
\nld65: Warning: (...)\/nes.cfg(63): Segment `STARTUP' does not exist
\nld65: Warning: (...)\/nes.cfg(63): Segment `VECTORS' does not exist
\nld65: Warning: (...)\/nes.cfg(63): Segment `CHARS' does not exist
\nfceux.exe game.nes<\/code><\/p>\n<\/p>\n
Same warnings and same error.<\/p>\n
Something is wrong. Examining game.nes<\/code> in a hex editor we see this:
\n00000000 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
\n00000010 4E 45 53 1A 00 00 00 00 00 00 00 00 00 00 00 00 NES.............
\n<\/code><\/p>\nThat’s strange! Our header is in there, but not at the start of the file. Instead it somehow ended up at offset $10, after 16 bytes of zeroes.<\/p>\n
To investigate I opened up nes.cfg<\/code>, the NES memory map configuration that came with cc65 and found this.<\/p>\n # INES Cartridge Header
\nHEADER: file = %O, start = $0000, size = $0010, fill = yes;
\n<\/code><\/p>\nSo the first 16 bytes are reserved for the header, and to use them we have to put our assembly into the HEADER segment. Should have known not to ignore those warnings.<\/p>\n
Segments are parts of the code and data that end up in different specific areas of RAM and ROM. In the source file they are specified as .segment \"SEGMEMT_NAME\"<\/code>.<\/p>\nThis is our new game.s<\/code> that specifies that our 4 bytes go into the HEADER segment.<\/p>\n.segment \"HEADER\"\r\n .byte \"NES\"\r\n .byte $1A\r\n<\/pre>\nTry this again now.<\/p>\n
ca65 game.s
\nld65 -t nes game.o -o game.nes
\nld65: Warning: (...)\/nes.cfg(63): Segment `STARTUP' does not exist
\nld65: Warning: (...)\/nes.cfg(63): Segment `VECTORS' does not exist
\nld65: Warning: (...)\/nes.cfg(63): Segment `CHARS' does not exist<\/code><\/p>\nOoh! One less warning this time.<\/p>\n
And this is what game.nes<\/code> looks like in the hex editor.<\/p>\n00000000 4E 45 53 1A 00 00 00 00 00 00 00 00 00 00 00 00 NES.............
\n00000010 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................<\/code><\/p>\nNice, the header is in the right place. The rest of the file is all zeroes.<\/p>\n
Let’s run it in the emulator<\/p>\n
fceux.exe game.nes<\/code><\/p>\n![\"\"](\"https:\/\/www.betelge.com\/blog\/wp-content\/uploads\/2018\/03\/fceux-grey-300x278.png\")
<\/p>\n
It works!<\/p>\n
I realise this is a post about a making a ROM that doesn’t even contain any code and just draws a gray background.<\/p>\n
It’s not useless though. This is now a ready template to fill with code and we know how to compile it.<\/p>\n
Finally let’s just add those missing segments to get rid of the remaining warnings.<\/p>\n
This is what game.s<\/code> looks like in the end<\/p>\n.segment \"HEADER\"\r\n .byte \"NES\"\r\n .byte $1A\r\n\r\n.segment \"STARTUP\"\r\n\r\n.segment \"VECTORS\"\r\n\r\n.segment \"CHARS\"<\/pre>\nIn the next part we’ll actually be putting something on the screen and we’ll have to talk about the different segments.<\/p>\n","protected":false},"excerpt":{"rendered":"
Can we start with a completely empty source file, compile it to a NES ROM and run it in an emulator? Let’s try! Create an empty plain text file game.s and save it in a folder. It now needs to … Continue reading