# mima-tools
A set of tools and specifications related to the MiMa
(Minimalmaschine).
* [Tools](#tools)
* [mima-run](#mima-run)
* [mima-asm](#mima-asm)
* [Specification](#specification)
* [Instructions](#instructions)
* [Registers](#registers)
* [Opcodes](#opcodes)
* [Memory dump file format: `.mima`](#memory-dump-file-format-mima)
* [Conventions](#conventions)
For example MiMa programs, see the [examples folder](examples/).
## Tools
### mima-run
This program can load and run `.mima` files.
```
$ mima-run --help
Usage: mima-run INFILE [-n|--steps N] [-d|--dump OUTFILE] [-q|--quiet]
[-s|--sparse] [-r|--norun]
Available options:
-h,--help Show this help text
INFILE The binary memory dump to load and execute
-n,--steps N How many instructions to execute (if not specified,
runs until HALT or execution exception)
-d,--dump OUTFILE If specified, write the MiMa's binary memory dump to
this file after execution is finished
-q,--quiet Don't print the memory dump
-s,--sparse Don't print memory locations containing only 0x000000
in the memory dump
-r,--norun Don't run the MiMa. Use the initial state for all
further actions. Roughly equivalent to -n 0
```
### mima-asm
This program can parse `.mimasm` files and convert them to `.mima`
files. More information and a specification of the `.mimasm` format
may be coming soon. For example programs, look in the `examples/`
folder.
```
$ mima-asm --help
Usage: mima-asm INFILE [-o|--out OUTFILE]
Available options:
-h,--help Show this help text
INFILE The .mimasm file to assemble
-o,--out OUTFILE The .mima file to write the assembled result
to (default: "out.mima")
```
## Specification
In the following sections, `` means "the value at the address
`a`". In the case of `<>`, bits 19-0 of `` are interpreted as
the address.
The MiMa uses words of 24 bits and addresses of 20 bits.
Each step, the MiMa fetches the value at the address stored in the
`IAR`, interprets it as an instruction and executes it. If the
instruction does not explicitly modify the `IAR`, the `IAR` it is
incremented by one automatically.
During execution, the following situations can be encountered where
execution should not be continued:
* The `HALT` instruction was executed
* The value at `` cannot be decoded to a valid instruction
* The `IAR` is `0xFFFFF` and an instruction was executed that did not
modify the `IAR`
In these cases, a MiMa emulator should stop execution and show a
suitable error message explaining why execution could not continue.
### Instructions
An instruction has one of the following forms:
```
Small opcode:
+----+ +-----------------------+
| SO | | Value/Address |
+----+ +-----------------------+
23 20 19 0
Large opcode:
+----+ +----+ +----------------+
| F | | LO | | Value |
+----+ +----+ +----------------+
23 20 19 16 15 0
```
Small opcodes can range from `0` to `E` and have an address or 20-bit
value as argument. Large opcodes can range from `F0` to `FF` and have,
if at all, a 16-bit value as argument.
For large opcodes without an argument, the 16 value bits are
ignored. They don't have to be set to 0.
### Registers
| Name | Size (bits) | Function |
|-------|-------------|------------------------------|
| `IAR` | 20 | Instruction Address Register |
| `ACC` | 24 | Accumulator |
| `RA` | 20 | Return Address |
| `SP` | 20 | Stack Pointer |
| `FP` | 20 | Frame Pointer |
### Opcodes
| Opcode | Name | Function |
|--------|---------------------------------|--------------------------------|
| `0` | `LDC c` (load constant) | `c -> ACC` |
| `1` | `LDV a` (load value) | ` -> ACC` |
| `2` | `STV a` (store value) | `ACC -> ` |
| `3` | `ADD a` | `ACC + -> ACC` |
| `4` | `AND a` | `ACC and -> ACC` |
| `5` | `OR a` | `ACC or -> ACC` |
| `6` | `XOR a` | `ACC xor -> ACC` |
| `7` | `EQL a` (equal) | `(ACC == ? -1 : 0) -> ACC` |
| `8` | `JMP a` (jump) | `a -> IAR` |
| `9` | `JMN a` (jump if negative) | `if (ACC < 0) {a -> IAR}` |
| `A` | `LDIV a` (load indirect value) | `<> -> ACC` |
| `B` | `STIV a` (store indirect value) | `ACC -> <>` |
| `C` | `CALL a` | `IAR -> RA; JMP a` |
| `D` | `ADC c` (add constant) | `ACC + c -> ACC` |
| `F0` | `HALT` | Halt execution |
| `F1` | `NOT` | `not ACC -> ACC` |
| `F2` | `RAR` (rotate ACC right) | `ACC >> 1 -> ACC` |
| `F3` | `RET` (return) | `RA -> IAR` |
| `F4` | `LDRA` (load from RA) | `RA -> ACC` |
| `F5` | `STRA` (store to RA) | `ACC -> RA` |
| `F6` | `LDSP` (load from SP) | `SP -> ACC` |
| `F7` | `STSP` (store to SP) | `ACC -> SP` |
| `F8` | `LDFP` (load from FP) | `FP -> ACC` |
| `F9` | `STFP` (store to FP) | `ACC -> FP` |
| `FA` | `LDRS o` (load relative to SP) | ` -> ACC` |
| `FB` | `STRS o` (store relative to SP) | `ACC -> ` |
| `FC` | `LDRF o` (load relative to FP) | ` -> ACC` |
| `FD` | `STRF o` (store relative to FP) | `ACC -> ` |
* `LDC c` sets bits 23-20 of `ACC` to 0.
* `ADD a`, `AND a`, `OR a`, `XOR a` and `NOT` are bitwise operations
* `ADC c` interprets its 20-bit value as a signed integer, whose value
is then added to the `ACC`'s current value.
* `RAR` shifts all bits in the `ACC` right by one. The rightmost bit
wraps around to the leftmost position.
* `LDRS`, `STRS`, `LDRF` and `STRF` interpret their 16-bit value as a
signed integer, whose value is then added to the address in the
respective register.
## Memory dump file format: `.mima`
All tools share a common memory dump file format with extension
`.mima`. It contains the whole execution state of a MiMa, meaning the
contents of its memory and all its registers. It also doubles as "MiMa
excutable" format.
The file is split up into blocks of 3 bytes, which form MiMa
words. The bytes within a word are ordered from most to least
significant.
The values of registers which are only 20 bits long are stored in the
lower 20 bits of a MiMa word, and the remaining bits 23-20 are filled
with zeroes, like so:
```
+----+ +-----------------------+
| 0 | | 20-bit register value |
+----+ +-----------------------+
23 20 19 0
```
The registers and memory are stored as follows:
| Word | Content |
|--------------:|:------------|
| 0 | `IAR` |
| 1 | `ACC` |
| 2 | `RA` |
| 3 | `SP` |
| 4 | `FP` |
| starting at 6 | Memory dump |
The memory dump contains the words of the MiMa's memory, written in
increasing order directly one after the other with nothing
in-between. The dump always starts at address `0x00000`, but may end
before it reaches address `0xFFFFF`. When reading a dump, all
unspecified values are to be intialized as `0x000000`.
A `.mima` file must always be a multiple of 3 bytes long. It must
always be at least 15 bytes long (contains all register values).
## Conventions
In the source code, the name MiMa is spelled `Mima`. When displayed,
it is spelled `MiMa`.
Executable names are all lowercase, and words are separated by a `-`.