6502/n65
1
0
Fork 0
mirror of https://github.com/safiire/n65.git synced 2024-12-12 00:29:03 +00:00
Code Issues Projects Releases Wiki Activity
An assembler for the 6502 microprocessor written in Ruby
30 Commits 1 Branch 0 Tags 246 KiB
Ruby 100%
2dca12a519
Go to file
Safiire 2dca12a519 Updating the demo.asm
2015-03-02 21:27:53 -08:00
data Intermediate commit 2015-02-22 05:59:03 -08:00
lib Trying to re-organize my classes, and add a base class for objects which can emit_bytes to the ROM 2015-02-24 17:37:00 -08:00
test Trying to get the tests working again after some changes 2015-02-24 15:56:38 -08:00
utils Initial Commit 2015-02-17 19:05:37 -08:00
.gitignore Accidentally had the opcode for TXA be NOP, don't know how that happened. I ported background.asm from NESASM format to my format, it is veeeery similar so not much needed changing, and the resulting ROM worked fine :) 2015-02-18 03:56:39 -08:00
assembler_6502.rb Separated the frontend commandline stuff from the actual assembler 2015-02-24 16:43:50 -08:00
assembler_demo.png Updaing readme, adding an image 2015-02-18 18:44:17 -08:00
background.asm Initial Commit 2015-02-17 19:05:37 -08:00
beep.asm Updating some of the demo asm files 2015-02-28 17:43:43 -08:00
demo.asm Updating the demo.asm 2015-03-02 21:27:53 -08:00
LICENSE Initial commit 2015-02-17 18:26:26 -08:00
my_background.asm For some reason we can't make capital letters in labels now? 2015-02-22 06:38:14 -08:00
noise.asm Adding an example of making noise 2015-02-28 17:44:11 -08:00
README.md Can use lower case instruction names and hex now 2015-02-22 18:49:24 -08:00

README.md

assembler6502 0.3

An NES assembler for the 6502 microprocessor written in Ruby

Usage: ./assembler_6502.rb <infile.asm> -o outfile.nes

This is a pretty straightfoward assembler, that is currently set up to produce iNES ROM formatted binaries from simple assembly listings. It is good at knowing which addressing modes are and are not allowed for each instruction, and contains some examples of correct syntax.

This assembler does not understand banks or mappers yet, and so having more than one PROG section does not quite work yet. That is next in line to be fixed.

It handles labels, and does a two pass assembly, first assembling the byte codes, and then going back and filling in the proper addresses where labels were used.

I have used this to compile some code for the NES, and it ran correctly on FCEUX, got it to make some sounds, load tiles, sprites, and scrolling.

Scrolling NES Demo

Some Todos:

  • Understand how to deal with various mappers
  • Understand how to create multiple banks
  • Get an NSF file playing
  • More unit tests for each instruction
  • I may make this into a Rubygem
  • Maybe I can put some better error messages.
  • I would like to add some Macros to generate settings for the PPU and APU, (values for locations like $2000 and $2001, the $4000s, etc.)
  • Support binary literals ie %10101010
  • Anonymous Label support, (maybe, not sure if I like the idea)
  • Give this project a better name.
  • Create an interactive read eval compile loop?

Some new additions:

  • Lower case mnemonics and hex digits
  • Ported NES101 tutor to this assembler.
  • Added msb and lsb byte selectors on address labels
  • added .org directive
  • added .dw directive
  • added .bytes directive
  • added .incbin directive
  • added .ascii directive
  • Invented my own iNES header directive that is JSON
  • Split the project up into separate files per class
  • Wrote some more unit tests
  • Added OptionParser for commandline opts
  • Tested a ROM with Sound output
  • Tested a ROM that changes background color

I decided that during the first pass of assembly, I should just initialize an entire 65535 byte virtual memory images, and write the instructions to their correct places, and then after resolving symbols during the second pass, I just clip out the Cartridge ROM area and iNES header at the end, works great so far. Now that I know I will need to support various mappers, I still may use this method, but will need to create multiple 65535 memory segments and use banking to distinguish them before finally writing out the resulting ROM in the correct order.