diff options
| author | cristian-grecu <cristian.grecu@gmail.com> | 2026-01-15 13:32:55 -0800 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2026-01-15 13:32:55 -0800 |
| commit | a423326dce12b542afb319c37b90a0d6d1306ed7 (patch) | |
| tree | 962b25f88665f676a0c6070c51db4b60188f0a8a | |
| parent | Update README.md (diff) | |
Update README.md
| -rw-r--r-- | README.md | 2 |
1 files changed, 1 insertions, 1 deletions
@@ -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 |