Exploring the visualization of 6502 opcodes
Go to file
2020-08-26 02:24:09 -04:00
project add support for bit fields and enums 2020-08-15 17:04:16 -04:00
src more definitions 2020-08-26 02:24:09 -04:00
.gitignore just checking in 2018-05-05 14:23:21 -04:00
.scalafix.conf scalafix 2020-08-15 02:04:28 -04:00
.scalafmt.conf fmt 2020-08-15 03:52:11 -04:00
build.sbt add support for bit fields and enums 2020-08-15 17:04:16 -04:00
Jenkinsfile add jenkinsfile 2019-11-30 01:52:25 -05:00
LICENSE Create LICENSE 2018-05-11 18:03:32 -04:00
README.md add next todo 2020-08-21 05:12:26 -04:00

6502-opcodes

Addressing modes

  • Immediate: a value literal
  • ZeroPage: argument is an 8-bit address to the zero page
  • ZeroPageX: argument is an 8-bit address to the zero page, incremented by X without carry
  • ZeroPageY: argument is an 8-bit address to the zero page, incremented by Y without carry
  • Absolute: argument is an 16-bit address
  • AbsoluteX: argument is an 16-bit address, incremented by X with carry
  • AbsoluteY: argument is an 16-bit address, incremented by Y with carry
  • Indirect: argument an address (A); the effective value is an address (B) stored at that address (A); used only by Jump
  • IndirectX: argument is an 8-bit address; find a value at this address incremented by the value X
  • IndirectY: argument is an 8-bit address; find a value at this address; increment the value by Y

TODO

  1. operand support should be derived from enum support
  • postfix operations to accumulator values
  • maybe implement define registry
  • register locking (i.e. disallow X writes during indexed traversal that uses X)
  • compiler optimization
    • when writing multiple, 16-bit address literals to memory, they may share the same high byte. if all writes are done by bouncing off the accumulator, you can save instructions by using the accumulator for the high byte once and writing multiple times
  • articulate AST as different from ASM stream
  • register locking (transactions) via phantom types