Hack images, store outputs in git again for now

Easier to track what each script change does if we keep the before and
after versions of the markdown in git too.  Clean this up eventually,
but simplifies development.

1 files changed, 15 insertions, 0 deletions

diff --git a/tracwiki/EDAToolchainSurvey%22.trac b/tracwiki/EDAToolchainSurvey%22.trac
new file mode 100644
index 0000000..f49c37c
--- /dev/null
+++ b/tracwiki/EDAToolchainSurvey%22.trac
@@ -0,0 +1,15 @@
+'''Note: this page has been replaced by wiki:EDAToolchainSurvey'''

+

+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:

+* Finding open EDA tools and assess their status

+* Settling for Closed

+* Strategy to Develop Trust in Tools

+* Validation Methods for Output

+

+Some tools and frameworks worth investigating are:

+* [http://www.optimsoc.org/index.html "OpTiMSoC"] - An open System on Chip (SoC) framework built around the OpenRISC CPU.

+* [http://iverilog.icarus.com/ "Icarus Verilog"] - An open Verilog event driven simulator that supports Verilog 2001, 2005 and SystemVerilog.

+* [http://www.geda-project.org/ "gEDA"] - A project that aims at developing GNU based EDA tools.

+* [http://www.gpleda.org/ "gplEDA"] - A collection of GPL licensed EDA tools. Points to gEDA.