Forums for Conway's Game of Life
https://conwaylife.com/forums/
Thank you for the corrections. At some point whilst I was working on the 323, I swapped the mnemonics for jf and jnf around, and when I wrote the opcode table I referenced an old file that hadn't been updated. I have attached a fixed version of the main.html file below (I don't think the changes are enough to warrant re-doing the whole tar-ball). I suppose trying to use documentation to implement something is the ultimate test of its correctness; any mistakes will inevitably (probably) be caught.Rei wrote: January 19th, 2025, 12:01 pm I found some issues in the documentation. The opcode for st xX,xY should be aYX0. Also the opcodes for jf and jnf are swapped. The last byte of jf should be 2 and jnf should be 1.
This made my day! This is the first time someone other than me has written an emulator for a CPU I designed. It even has breakpoints.Rei wrote: January 19th, 2025, 12:01 pm I created an emulator that can be used in a browser.
https://rei1024.github.io/323-web-emulator/
Code: Select all
/* Save-state (.3ss) format:
3 BYTES: ASCII '323'.
BYTE: 23.
BYTE: Flag (only LSB is used; all other bits are cleared).
WORD: Program counter.
15 WORDS: Registers (x1 first, xF last; value in xF is as read, not as
written; i.e. if the last instruction was "xor x0,x0,xF", xF
will be -1).
4 TIMES:
16 WORDS: Cache line; hwords are converted to words in little-
endian style.
4 WORDS: Addresses that those cache lines correspond to; lower 5 bits
cleared. They indicate the lowest address in the cache line.
BYTE: Cache order. Consists of 4 groups of 2 bits which refer to a
cache line. The rightmost group indicates the most recently used
one, and the leftmost is the LRU. The cache lines are numbered in
the order in which they appear in the save-state.
WORD: Amount of RAM words saved in this save-state. If 0, this is the
end of the save-state.
AMOUNT OF WORDS SPECIFIED BY PREVIOUS: RAM.
Overall, the non-RAM section is 346 bytes.
*/Anivec wrote: January 19th, 2025, 12:23 pm I think the next computer up is a 64-86x architecture computer (that’s what I want to see at least).
You don't need to do anything special; it's just cells. You just need to pan/zoom Golly's view to fit it in the window with the right zoom level. At the left of the machine is a component that repeats 16 times going in a line downwards; this is the I/O system. On the left of that line are some peripherals, surrounded by eaters to make it clear where they begin and end. The largest peripheral is the display; on the left-middle of it is the 32x32 screen itself. At the right zoom level, each pixel of the display is a 2x2 of pixels on your actual screen.Yoel wrote: April 10th, 2025, 4:15 am Extremely impressive!
How do you make the display visible in Golly though?