aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorcristian-grecu <cristian.grecu@gmail.com>2026-01-15 13:32:55 -0800
committerGitHub <noreply@github.com>2026-01-15 13:32:55 -0800
commita423326dce12b542afb319c37b90a0d6d1306ed7 (patch)
tree962b25f88665f676a0c6070c51db4b60188f0a8a
parentUpdate README.md (diff)
Update README.md
-rw-r--r--README.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/README.md b/README.md
index d56c6c0..9b7c152 100644
--- a/README.md
+++ b/README.md
@@ -221,7 +221,7 @@ The hardest part of this lab is getting the state machine right. We strongly urg
### Post-synthesis simulation
-Be sure to exhaustively test both the SystemVerilog RTL code you write and the post-synthesis netlist Verilog file produced by Quartus (see the Tutorial). It is entirely possible to write “unsynthesizable” RTL that works “in simulation” but either fails to synthesize or synthesizes into something that behaves differently. Optionally, you may include the post-synthesis netlist (.vo file) you generated from Quartus. We will not use it for marking, but it can provide evidence in the unlikely event that you need to appeal your marks.
+Be sure to exhaustively test both the SystemVerilog RTL code you write and the post-synthesis netlist Verilog file produced by Quartus (see the Tutorial). It is entirely possible to write “unsynthesizable” RTL that works “in simulation” but either fails to synthesize or synthesizes into something that behaves differently. Optionally, you may include in your submission the post-synthesis netlist (.vo file) you generated from Quartus. We will not use it for marking, but it can provide evidence in the unlikely event that you need to appeal your marks.
### Task 6: Verify your design on a DE1-SoC board