aboutsummaryrefslogtreecommitdiff
path: root/content/EDAToolchainSurvey.md
diff options
context:
space:
mode:
authorRob Austein <sra@hactrn.net>2021-10-08 14:39:03 -0400
committerRob Austein <sra@hactrn.net>2021-10-08 14:39:03 -0400
commitb2f9504254a3d4894d4f9a8b13f4cdbcb26fa395 (patch)
tree73538e731d56f09fb6a49b742827a9e0b6ea0f7d /content/EDAToolchainSurvey.md
parent71487660812754e5f26f26595b6c3d456f9f6db8 (diff)
A lot of minor cleanup
Diffstat (limited to 'content/EDAToolchainSurvey.md')
-rw-r--r--content/EDAToolchainSurvey.md15
1 files changed, 12 insertions, 3 deletions
diff --git a/content/EDAToolchainSurvey.md b/content/EDAToolchainSurvey.md
index b8632a6..287d5af 100644
--- a/content/EDAToolchainSurvey.md
+++ b/content/EDAToolchainSurvey.md
@@ -1,8 +1,17 @@
-Title: EDAToolchainSurvey
-Author: trac
+Title: EDA Toolchain Survey
Date: 2016-12-15 22:43
-The major issue is finding tools that allows a designer, user to verify that the RTL source code (in Verilog or VHDL) matches what is generated at the physical level. As part of the project we need to investigate the current status of open tools in the toolchain for implementation and verification of hardware. This includes RTL simulation, synthesis, place & route, netlist verification, timing analysis and configuration file generation and analysis. (This implies that the target is an FPGA.). If there are no open tools we need to find ways of verifying pre- and post-functionality to check that the black box tool does not alter (subvert) the design in ways not intended.
+The major issue is finding tools that allows a designer, user to
+verify that the RTL source code (in Verilog or VHDL) matches what is
+generated at the physical level. As part of the project we need to
+investigate the current status of open tools in the toolchain for
+implementation and verification of hardware. This includes RTL
+simulation, synthesis, place & route, netlist verification, timing
+analysis and configuration file generation and analysis. (This implies
+that the target is an FPGA.). If there are no open tools we need to
+find ways of verifying pre- and post-functionality to check that the
+black box tool does not alter (subvert) the design in ways not
+intended.
The basic action flow is: