summaryrefslogtreecommitdiff
path: root/docs
diff options
context:
space:
mode:
authorFrederick Yin <fkfd@fkfd.me>2022-08-24 14:13:00 +0800
committerFrederick Yin <fkfd@fkfd.me>2022-08-24 14:13:00 +0800
commit6e9509d1a8f71ba6b5bf96440e155d25dca731b6 (patch)
treee27854ad016d395aa880641f46fe42d5448f416a /docs
parent59c421aee70a6cafb8c79517f28d2d8923850d02 (diff)
projects/nand2tetris_1: rename img dir to nand2tetris_1
Diffstat (limited to 'docs')
-rw-r--r--docs/projects/img/nand2tetris_1/6502.jpg (renamed from docs/projects/img/nand2tetris/6502.jpg)bin235588 -> 235588 bytes
-rw-r--r--docs/projects/img/nand2tetris_1/alu.kra (renamed from docs/projects/img/nand2tetris/alu.kra)bin507037 -> 507037 bytes
-rw-r--r--docs/projects/img/nand2tetris_1/alu.png (renamed from docs/projects/img/nand2tetris/alu.png)bin122130 -> 122130 bytes
-rw-r--r--docs/projects/img/nand2tetris_1/alu_highlighted.png (renamed from docs/projects/img/nand2tetris/alu_highlighted.png)bin93144 -> 93144 bytes
-rw-r--r--docs/projects/img/nand2tetris_1/and_gate.png (renamed from docs/projects/img/nand2tetris/and_gate.png)bin11081 -> 11081 bytes
-rw-r--r--docs/projects/img/nand2tetris_1/and_gate_nand.png (renamed from docs/projects/img/nand2tetris/and_gate_nand.png)bin17995 -> 17995 bytes
-rw-r--r--docs/projects/img/nand2tetris_1/and_gate_nand_not.png (renamed from docs/projects/img/nand2tetris/and_gate_nand_not.png)bin16708 -> 16708 bytes
-rw-r--r--docs/projects/img/nand2tetris_1/computer.kra (renamed from docs/projects/img/nand2tetris/computer.kra)bin460149 -> 460149 bytes
-rw-r--r--docs/projects/img/nand2tetris_1/computer_registers.png (renamed from docs/projects/img/nand2tetris/computer_registers.png)bin143235 -> 143235 bytes
-rw-r--r--docs/projects/img/nand2tetris_1/cpu.kra (renamed from docs/projects/img/nand2tetris/cpu.kra)bin841631 -> 841631 bytes
-rw-r--r--docs/projects/img/nand2tetris_1/cpu.png (renamed from docs/projects/img/nand2tetris/cpu.png)bin222785 -> 222785 bytes
-rw-r--r--docs/projects/img/nand2tetris_1/cpu_book.png (renamed from docs/projects/img/nand2tetris/cpu_book.png)bin170476 -> 170476 bytes
-rw-r--r--docs/projects/img/nand2tetris_1/cpu_controls.png (renamed from docs/projects/img/nand2tetris/cpu_controls.png)bin196576 -> 196576 bytes
-rw-r--r--docs/projects/img/nand2tetris_1/cpu_emulator_pong.png (renamed from docs/projects/img/nand2tetris/cpu_emulator_pong.png)bin49719 -> 49719 bytes
-rw-r--r--docs/projects/img/nand2tetris_1/cpu_hunch.png (renamed from docs/projects/img/nand2tetris/cpu_hunch.png)bin177527 -> 177527 bytes
-rw-r--r--docs/projects/img/nand2tetris_1/cpu_mysterious_jump_logic.png (renamed from docs/projects/img/nand2tetris/cpu_mysterious_jump_logic.png)bin227952 -> 227952 bytes
-rw-r--r--docs/projects/img/nand2tetris_1/mux.png (renamed from docs/projects/img/nand2tetris/mux.png)bin27133 -> 27133 bytes
-rw-r--r--docs/projects/img/nand2tetris_1/pc.png (renamed from docs/projects/img/nand2tetris/pc.png)bin84490 -> 84490 bytes
-rw-r--r--docs/projects/img/nand2tetris_1/pc_incorrect.png (renamed from docs/projects/img/nand2tetris/pc_incorrect.png)bin83727 -> 83727 bytes
-rw-r--r--docs/projects/img/nand2tetris_1/register.png (renamed from docs/projects/img/nand2tetris/register.png)bin15090 -> 15090 bytes
-rw-r--r--docs/projects/img/nand2tetris_1/register_internal.png (renamed from docs/projects/img/nand2tetris/register_internal.png)bin26004 -> 26004 bytes
-rw-r--r--docs/projects/img/nand2tetris_1/zx_nx.png (renamed from docs/projects/img/nand2tetris/zx_nx.png)bin26921 -> 26921 bytes
-rw-r--r--docs/projects/nand2tetris_1.md38
23 files changed, 19 insertions, 19 deletions
diff --git a/docs/projects/img/nand2tetris/6502.jpg b/docs/projects/img/nand2tetris_1/6502.jpg
index 06c6e7f..06c6e7f 100644
--- a/docs/projects/img/nand2tetris/6502.jpg
+++ b/docs/projects/img/nand2tetris_1/6502.jpg
Binary files differ
diff --git a/docs/projects/img/nand2tetris/alu.kra b/docs/projects/img/nand2tetris_1/alu.kra
index a86fafa..a86fafa 100644
--- a/docs/projects/img/nand2tetris/alu.kra
+++ b/docs/projects/img/nand2tetris_1/alu.kra
Binary files differ
diff --git a/docs/projects/img/nand2tetris/alu.png b/docs/projects/img/nand2tetris_1/alu.png
index 64bed05..64bed05 100644
--- a/docs/projects/img/nand2tetris/alu.png
+++ b/docs/projects/img/nand2tetris_1/alu.png
Binary files differ
diff --git a/docs/projects/img/nand2tetris/alu_highlighted.png b/docs/projects/img/nand2tetris_1/alu_highlighted.png
index 3290f07..3290f07 100644
--- a/docs/projects/img/nand2tetris/alu_highlighted.png
+++ b/docs/projects/img/nand2tetris_1/alu_highlighted.png
Binary files differ
diff --git a/docs/projects/img/nand2tetris/and_gate.png b/docs/projects/img/nand2tetris_1/and_gate.png
index 95a8ec6..95a8ec6 100644
--- a/docs/projects/img/nand2tetris/and_gate.png
+++ b/docs/projects/img/nand2tetris_1/and_gate.png
Binary files differ
diff --git a/docs/projects/img/nand2tetris/and_gate_nand.png b/docs/projects/img/nand2tetris_1/and_gate_nand.png
index 9af285a..9af285a 100644
--- a/docs/projects/img/nand2tetris/and_gate_nand.png
+++ b/docs/projects/img/nand2tetris_1/and_gate_nand.png
Binary files differ
diff --git a/docs/projects/img/nand2tetris/and_gate_nand_not.png b/docs/projects/img/nand2tetris_1/and_gate_nand_not.png
index e230230..e230230 100644
--- a/docs/projects/img/nand2tetris/and_gate_nand_not.png
+++ b/docs/projects/img/nand2tetris_1/and_gate_nand_not.png
Binary files differ
diff --git a/docs/projects/img/nand2tetris/computer.kra b/docs/projects/img/nand2tetris_1/computer.kra
index 72cab90..72cab90 100644
--- a/docs/projects/img/nand2tetris/computer.kra
+++ b/docs/projects/img/nand2tetris_1/computer.kra
Binary files differ
diff --git a/docs/projects/img/nand2tetris/computer_registers.png b/docs/projects/img/nand2tetris_1/computer_registers.png
index 4999988..4999988 100644
--- a/docs/projects/img/nand2tetris/computer_registers.png
+++ b/docs/projects/img/nand2tetris_1/computer_registers.png
Binary files differ
diff --git a/docs/projects/img/nand2tetris/cpu.kra b/docs/projects/img/nand2tetris_1/cpu.kra
index 2022f55..2022f55 100644
--- a/docs/projects/img/nand2tetris/cpu.kra
+++ b/docs/projects/img/nand2tetris_1/cpu.kra
Binary files differ
diff --git a/docs/projects/img/nand2tetris/cpu.png b/docs/projects/img/nand2tetris_1/cpu.png
index c29068f..c29068f 100644
--- a/docs/projects/img/nand2tetris/cpu.png
+++ b/docs/projects/img/nand2tetris_1/cpu.png
Binary files differ
diff --git a/docs/projects/img/nand2tetris/cpu_book.png b/docs/projects/img/nand2tetris_1/cpu_book.png
index 2611a06..2611a06 100644
--- a/docs/projects/img/nand2tetris/cpu_book.png
+++ b/docs/projects/img/nand2tetris_1/cpu_book.png
Binary files differ
diff --git a/docs/projects/img/nand2tetris/cpu_controls.png b/docs/projects/img/nand2tetris_1/cpu_controls.png
index 77c034a..77c034a 100644
--- a/docs/projects/img/nand2tetris/cpu_controls.png
+++ b/docs/projects/img/nand2tetris_1/cpu_controls.png
Binary files differ
diff --git a/docs/projects/img/nand2tetris/cpu_emulator_pong.png b/docs/projects/img/nand2tetris_1/cpu_emulator_pong.png
index 5dd9a75..5dd9a75 100644
--- a/docs/projects/img/nand2tetris/cpu_emulator_pong.png
+++ b/docs/projects/img/nand2tetris_1/cpu_emulator_pong.png
Binary files differ
diff --git a/docs/projects/img/nand2tetris/cpu_hunch.png b/docs/projects/img/nand2tetris_1/cpu_hunch.png
index 5c12596..5c12596 100644
--- a/docs/projects/img/nand2tetris/cpu_hunch.png
+++ b/docs/projects/img/nand2tetris_1/cpu_hunch.png
Binary files differ
diff --git a/docs/projects/img/nand2tetris/cpu_mysterious_jump_logic.png b/docs/projects/img/nand2tetris_1/cpu_mysterious_jump_logic.png
index a460fcd..a460fcd 100644
--- a/docs/projects/img/nand2tetris/cpu_mysterious_jump_logic.png
+++ b/docs/projects/img/nand2tetris_1/cpu_mysterious_jump_logic.png
Binary files differ
diff --git a/docs/projects/img/nand2tetris/mux.png b/docs/projects/img/nand2tetris_1/mux.png
index da7f3d2..da7f3d2 100644
--- a/docs/projects/img/nand2tetris/mux.png
+++ b/docs/projects/img/nand2tetris_1/mux.png
Binary files differ
diff --git a/docs/projects/img/nand2tetris/pc.png b/docs/projects/img/nand2tetris_1/pc.png
index 0cbbd20..0cbbd20 100644
--- a/docs/projects/img/nand2tetris/pc.png
+++ b/docs/projects/img/nand2tetris_1/pc.png
Binary files differ
diff --git a/docs/projects/img/nand2tetris/pc_incorrect.png b/docs/projects/img/nand2tetris_1/pc_incorrect.png
index 2ac3ae8..2ac3ae8 100644
--- a/docs/projects/img/nand2tetris/pc_incorrect.png
+++ b/docs/projects/img/nand2tetris_1/pc_incorrect.png
Binary files differ
diff --git a/docs/projects/img/nand2tetris/register.png b/docs/projects/img/nand2tetris_1/register.png
index ff32d3c..ff32d3c 100644
--- a/docs/projects/img/nand2tetris/register.png
+++ b/docs/projects/img/nand2tetris_1/register.png
Binary files differ
diff --git a/docs/projects/img/nand2tetris/register_internal.png b/docs/projects/img/nand2tetris_1/register_internal.png
index f9ef91e..f9ef91e 100644
--- a/docs/projects/img/nand2tetris/register_internal.png
+++ b/docs/projects/img/nand2tetris_1/register_internal.png
Binary files differ
diff --git a/docs/projects/img/nand2tetris/zx_nx.png b/docs/projects/img/nand2tetris_1/zx_nx.png
index 14330a2..14330a2 100644
--- a/docs/projects/img/nand2tetris/zx_nx.png
+++ b/docs/projects/img/nand2tetris_1/zx_nx.png
Binary files differ
diff --git a/docs/projects/nand2tetris_1.md b/docs/projects/nand2tetris_1.md
index 865595d..42337f3 100644
--- a/docs/projects/nand2tetris_1.md
+++ b/docs/projects/nand2tetris_1.md
@@ -44,18 +44,18 @@ CHIP And {
Graphically, the HDL describes the following schematic:
-![A NAND connected to a NOT](img/nand2tetris/and_gate_nand_not.png)
+![A NAND connected to a NOT](img/nand2tetris_1/and_gate_nand_not.png)
Here `a`, `b` and `out` are hardcoded, but `nout` is an arbitrary name
I gave to the internal pin. If we further substitute the implementation of
`Not` in `Nand`, this is what _actually_ lives on the silicon:
-![Two NANDs](img/nand2tetris/and_gate_nand.png)
+![Two NANDs](img/nand2tetris_1/and_gate_nand.png)
Once we have written this HDL code, we can encapsulate the AND gate in the
following symbol, which is in essence two NAND gates in a trenchcoat:
-![One AND](img/nand2tetris/and_gate.png)
+![One AND](img/nand2tetris_1/and_gate.png)
And this is one of the few chips that have so few pins exposed (hence
"elementary") that you can craft a truth table for it, and thus can test
@@ -182,7 +182,7 @@ this call for an `if` statement? Well, in project 01 I made a chip named
`Mux16` and it is _tremendously_ helpful. It's the hardware embodiment of
`if () ... else ...`.
-![Schematic of a mux](img/nand2tetris/mux.png)
+![Schematic of a mux](img/nand2tetris_1/mux.png)
(In reality we are using the 16-bit version, but in principle they're the
same.)
@@ -200,7 +200,7 @@ Mux16(a=zdx, b=ndx, sel=nx, out=px);
Graphically:
-![Two muxes in series outputting "px"](img/nand2tetris/zx_nx.png)
+![Two muxes in series outputting "px"](img/nand2tetris_1/zx_nx.png)
(The order of the muxes matters, because when `zx = nx = 1`, this logic
configuration yields `~0 = -1` while the other way gives you 0.)
@@ -254,7 +254,7 @@ set iff every bit in `out` is zero.
That's it, we have completed the ALU! I know y'all are anticipating the
schematics; how can I let you down?
-![Schematic of ALU](img/nand2tetris/alu.png)
+![Schematic of ALU](img/nand2tetris_1/alu.png)
For some reason nand2tetris only provided me with `Or8Way`, which OR's
together 8 bits, so I had to use two of them to do all 16. I tried writing
@@ -363,7 +363,7 @@ boolean AND and binary addition. It is the Mux's job to select which
branch to pass downstream, and which one to discard. This is, in
a stretch, called [speculative execution](https://en.wikipedia.org/wiki/Speculative_execution)
-![Schematic of ALU. The AND, Adder, and "f" mux are highlighted](../img/nand2tetris/alu_highlighted.png)
+![Schematic of ALU. The AND, Adder, and "f" mux are highlighted](img/nand2tetris_1/alu_highlighted.png)
As you see in the highlighted area, _both_ of these gates are
switching internally, and both of them consume power, even when one of
@@ -400,7 +400,7 @@ can build registers from 1 bit to 16K words.
Here's how a register works from the user's point of view:
-![Schematic of chip with in, load, and out pins](img/nand2tetris/register.png)
+![Schematic of chip with in, load, and out pins](img/nand2tetris_1/register.png)
If you give it some data via `in` and pull `load` to logic one, the data
will show up in `out` at the next clock cycle. However as long as `load`
@@ -413,7 +413,7 @@ into the DFF again, creating an eternal feedback loop, but this time the
simulator handles it with no problem, because the loop is delayed by one
clock cycle each step.
-![Schematic of Mux and DFF in register](img/nand2tetris/register_internal.png)
+![Schematic of Mux and DFF in register](img/nand2tetris_1/register_internal.png)
The RAM I proceeded to build is just an array of arrays of arrays of … of
arrays of registers. Just copy and paste; no thinking required.
@@ -430,7 +430,7 @@ zero.
It's not hard to think of using the Register for storage and Inc16 (16-bit
incrementer) to do the math. The rest is Muxes, just like this:
-![PC with "out" wired to output of the final "reset" mux](img/nand2tetris/pc_incorrect.png)
+![PC with "out" wired to output of the final "reset" mux](img/nand2tetris_1/pc_incorrect.png)
There is a problem with this solution. Do you see it? Let's read the chip
specs again carefully:
@@ -450,7 +450,7 @@ We just need a way to delay `out` by one clock cycle. The only sequential
chip here is the Register, so let's try hooking `out` onto its output
instead:
-![PC with "out" wired to output of Register](img/nand2tetris/pc.png)
+![PC with "out" wired to output of Register](img/nand2tetris_1/pc.png)
Simulation tells me that this works perfectly, but deep inside I feel I'm
still extremely sloppy at clocked logic.
@@ -464,7 +464,7 @@ instructions. But first, we need to imagine we have a computer.
![Incomplete schematic of computer. Inside blue rectangle: ROM, CPU, RAM.
Inside the CPU is a blob labeled "ALU and stuff", A Register, and D Register.
-Outside: Reset button, screen, keyboard.](img/nand2tetris/computer_registers.png)
+Outside: Reset button, screen, keyboard.](img/nand2tetris_1/computer_registers.png)
Here you see three devices inside the blue rectangle: ROM, CPU, and RAM.
@@ -599,7 +599,7 @@ which is 24576. If you write the highest bit to one in RAM[16384], you
paint the top left pixel black. If you press space, it sets RAM[24576] to
32 (0x20). You can interact with them in the CPU emulator.
-!["Pong" running in the CPU emulator](img/nand2tetris/cpu_emulator_pong.png)
+!["Pong" running in the CPU emulator](img/nand2tetris_1/cpu_emulator_pong.png)
▲ CPU Emulator running Pong
@@ -658,7 +658,7 @@ The instant I read the requirements, I knew there will be a ton of
internal wires. Fortunately, the authors provided a block diagram similar
to this one:
-![Incomplete diagram of CPU. Many labels are question marks](img/nand2tetris/cpu_book.png)
+![Incomplete diagram of CPU. Many labels are question marks](img/nand2tetris_1/cpu_book.png)
Yikes! What's with the question marks? Apparently it's the authors' own
version of spoiler alerts. I had to figure out what they are by myself,
@@ -707,7 +707,7 @@ four groups of control bits:
In a hunch, it seems we have the answer to most of the question marks.
-![CPU but some question marks are replaced with bit names](img/nand2tetris/cpu_hunch.png)
+![CPU but some question marks are replaced with bit names](img/nand2tetris_1/cpu_hunch.png)
This is simple but wrong. Let's take a close look at the `load` pin
labeled `d1` on the A register. If we try to load address 1 into it, using
@@ -727,7 +727,7 @@ The mux on the left will let the instruction through because `opcode` is
load, because `instruction[5]` is zero. Something similar will also happen
to `d2` and `d3`, so we add a little logic:
-![CPU with correct logic controls at d1, d2, and d3](img/nand2tetris/cpu_controls.png)
+![CPU with correct logic controls at d1, d2, and d3](img/nand2tetris_1/cpu_controls.png)
This ensures that A, D and M load data if and only if we explicitly tell
them to. Now we shift our attention to the only two question marks left:
@@ -738,12 +738,12 @@ that we can set the PC to its input if we pull `load` to high, and this
way we can jump to ROM[A]. But how?
![CPU with a blob labeled "mysterious logic that decides whether we jump
-or not"](img/nand2tetris/cpu_mysterious_jump_logic.png)
+or not"](img/nand2tetris_1/cpu_mysterious_jump_logic.png)
It's actually very straightforward! Apparently the authors thought it
through when specifying the ALU.
-![Complete diagram of CPU](img/nand2tetris/cpu.png)
+![Complete diagram of CPU](img/nand2tetris_1/cpu.png)
(Actual gates may differ)
@@ -920,7 +920,7 @@ this deep-rooted fear that one loose jumper wire on the breadboard can
knock your Ben Eater-style computer completely off the rail?
![DIP chips and LCD connected with numerous jumper wires on three
-breadboards; the LCD reads "6502 Computer kit"](img/nand2tetris/6502.jpg)
+breadboards; the LCD reads "6502 Computer kit"](img/nand2tetris_1/6502.jpg)
▲ Image credit: [Ben Eater, "Build a 6502 computer"](https://eater.net/6502)