diff options
| author | Simon O'Shea <55282932+osheas1atwit@users.noreply.github.com> | 2020-04-21 00:29:57 -0400 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2020-04-21 00:29:57 -0400 |
| commit | ff446910d20c9720ee32baa38f16a874800ba643 (patch) | |
| tree | 30da5443d937c30264f7ac520946cf3af2e021b2 | |
| parent | c0163139d3ad8709575ca7fa4ab2107062de926b (diff) | |
quit edit
| -rw-r--r-- | README.txt | 5 |
1 files changed, 3 insertions, 2 deletions
@@ -27,8 +27,9 @@ less than the offset that would get to the address you want to store at. The ord change data causes the 'pcSelector' to receive an already-incremented PC value, so when the offset is
added during phase 3, the destination value is written one spot above the originally intended address.
Also, if the Logisim gives a 'label collision' error when loading the circuit, just rename any of the
-tunnels that output blue wires in the 'main' circuit to 'clock'. Otherwise, everything should work as
-intended.
+tunnels that output blue wires in the 'main' circuit to 'clock'. Lastly, this .circ was made with the
+.jar version of Logisim, not the Windows .exe version of the software. Otherwise, everything should work
+as intended.
All of the tests listed above were previously tested with various register values and proved to work
as intended. The AND and NOT operations were also tested early in the building process and once the
|