diff options
| author | alekseiplusplus <alekseijeaves@protonmail.com> | 2023-12-07 02:19:48 +1100 |
|---|---|---|
| committer | alekseiplusplus <alekseijeaves@protonmail.com> | 2023-12-07 02:19:48 +1100 |
| commit | 98dd41e2ce7dedb81ab91342eed29da017006ea4 (patch) | |
| tree | de5efd1f899815dcad218accda405873687cbaf1 /docs | |
| parent | 5bb10fc4121a8c8434dcd367f2e611599a11e12e (diff) | |
about to rip apart my code, so saving progress
Diffstat (limited to 'docs')
| -rw-r--r-- | docs/interpreter.md | 64 | ||||
| -rw-r--r-- | docs/opcodes-reference.pdf | bin | 20266 -> 0 bytes |
2 files changed, 0 insertions, 64 deletions
diff --git a/docs/interpreter.md b/docs/interpreter.md deleted file mode 100644 index 85ab792..0000000 --- a/docs/interpreter.md +++ /dev/null @@ -1,64 +0,0 @@ -# interpreter - -This is a small program intended to help with testing the 6502 CPU, or running programs on it. - -The expected input is machine code written in plaintext. - -The program assumes you will write statements correctly so it doesn't waste time checking that you put four digits in instead of three. If you are using this I assume you know what you are doing. - -The program accepts stdin, so it can be used in two ways. -- Typing instructions inline. -- Piping a file in with cat. - -## Instructions - -To express the syntax of instructions, here are some valid examples to express LDA $01: - - a901 - A901 - A9 01 - -If you downloaded my project on Github, I have included a PDF called `opcodes_reference.pdf` which has a table with every legal opcode in it. - -Statements can be seperated or on a single line. For instance, - - a901 - p - q - -Can be written as - - a901pq - -The only case in which this should be avoided is after an M/m command. - -## Debug Commands - -The interpreter comes with multiple statements for the purpose of debugging the emulator. - -`Q/q` Quits the program. - -`R/r` Resets the virtual computer. - -`P/p` Dumps processor state. - -`M/m` Prints out memory. -There are two forms which memory can be printed. -The first is `sXX` where `XX` is a memory page. The whole page of memory is printed onto the screen. -The second is `sXXXX` where `XXXX` is a specific address. This prints out the value of the 1 byte requested. -Be aware that unallocated memory will be dumped if it happens to be accessed with this command. - -`S/s` Directly set a piece of memory. -Syntax is strictly of form `sXXXX.xx` where `XXXX` is the address and `xx` is the value. - -`/` Prints until newline. - -`#` Ignores until newline. - -## Anomalies - -I don't care a whole lot about making this interpreter foolproof since its mostly for my personal debugging use. There are a couple anomalies to look out for if you intend to write programs with it. - -1. After M/m command, a newline is *necessary* or it will have unexpected behavior. -2. Two newlines are necessary after single byte-length instructions or it will segfault. -3. If Q/q is not used at the end of a program, it will segfault. It's inconsequential if it does, but it's important to know.
\ No newline at end of file diff --git a/docs/opcodes-reference.pdf b/docs/opcodes-reference.pdf Binary files differdeleted file mode 100644 index ecff92b..0000000 --- a/docs/opcodes-reference.pdf +++ /dev/null |