Commit 652c5eba authored by Christian Fibich's avatar Christian Fibich Committed by Stefan Tauner
Browse files

Spellcheck

parent b3f55d63
...@@ -3,7 +3,7 @@ ...@@ -3,7 +3,7 @@
This chapter sums up some concepts of the Perl classes used in the \ac{FIJI} framework. This chapter sums up some concepts of the Perl classes used in the \ac{FIJI} framework.
Their use in the complete tool flow and the respective interfaces to the vendor tools are described in detail in \hyperref[UG:sec:flow]{the \ac*{UG}}. Their use in the complete tool flow and the respective interfaces to the vendor tools are described in detail in \hyperref[UG:sec:flow]{the \ac*{UG}}.
You should consult the Doxygen documentation and source files for the details beyong the overview given below. You should consult the Doxygen documentation and source files for the details beyond the overview given below.
\subsection{FIJI Settings} \subsection{FIJI Settings}
...@@ -94,7 +94,7 @@ The two major differences are: ...@@ -94,7 +94,7 @@ The two major differences are:
\item The rules and data used for validation in the Tests is generated from a \ac{FIJI} Settings instance. \item The rules and data used for validation in the Tests is generated from a \ac{FIJI} Settings instance.
This allows for validation against the actual design settings instead of some coarse generic rules. This allows for validation against the actual design settings instead of some coarse generic rules.
\item The utility functions differ greatly.\\ \item The utility functions differ greatly.\\
E.g., instead of calculation FPGA resources like in \texttt{FIJI::Settings::estimate\_resources} the functions in \texttt{Tests.pm} are concerned with generating code related to simluations. E.g., instead of calculation FPGA resources like in \texttt{FIJI::Settings::estimate\_resources} the functions in \texttt{Tests.pm} are concerned with generating code related to simulations.
\end{itemize} \end{itemize}
\subsubsection{FIJI Setup Tool} \subsubsection{FIJI Setup Tool}
...@@ -116,7 +116,7 @@ The dependency graph of \texttt{Tk::FIJISettingsViewer} is depicted in \Cref{fig ...@@ -116,7 +116,7 @@ The dependency graph of \texttt{Tk::FIJISettingsViewer} is depicted in \Cref{fig
All settings of type \texttt{net} (representing a net in the Verilog netlist) can be set by a distinct dialog that is represented by \texttt{Tk::FIJINetSelection}. All settings of type \texttt{net} (representing a net in the Verilog netlist) can be set by a distinct dialog that is represented by \texttt{Tk::FIJINetSelection}.
Another dialog that is not exclusive to \texttt{fiji\_setup.pl} is \texttt{Tk::FIJIModalDialog} that is a simple implementation of a modal dialog that conveniencetly handles buttons and supports images and markup text (used in the about dialog) as well. Another dialog that is not exclusive to \texttt{fiji\_setup.pl} is \texttt{Tk::FIJIModalDialog} that is a simple implementation of a modal dialog that conveniently handles buttons and supports images and markup text (used in the about dialog) as well.
\subsection{Instrumentation} \subsection{Instrumentation}
\label{sec:instrumentation} \label{sec:instrumentation}
...@@ -129,7 +129,7 @@ The general idea of the instrumentation process (cf.\ \texttt{FIJI::Netlist::ins ...@@ -129,7 +129,7 @@ The general idea of the instrumentation process (cf.\ \texttt{FIJI::Netlist::ins
\begin{enumerate} \begin{enumerate}
\item Retrieve all signals connected to the respective net (\texttt{FIJI::Netlist::\_get\_net\_connections}) including its driver. \item Retrieve all signals connected to the respective net (\texttt{FIJI::Netlist::\_get\_net\_connections}) including its driver.
\item Create unique, sane identifieres\footnotemark{} for the various new objects to create (e.g., ports to forward \ac{DUT}-internal signals). \item Create unique, sane identifiers\footnotemark{} for the various new objects to create (e.g., ports to forward \ac{DUT}-internal signals).
\item Forward the original and instrumented signals up/down the hierarchy respectively via newly created ports. \item Forward the original and instrumented signals up/down the hierarchy respectively via newly created ports.
\item Determine the name for an intermediate net to ease splicing of the instrumented signal (e.g., into single bits of busses). \item Determine the name for an intermediate net to ease splicing of the instrumented signal (e.g., into single bits of busses).
\item Split up the instrumented net depending on its driver. \item Split up the instrumented net depending on its driver.
...@@ -187,7 +187,7 @@ The dependency graph of \texttt{FIJI::Downloader} is depicted in \Cref{fig:Downl ...@@ -187,7 +187,7 @@ The dependency graph of \texttt{FIJI::Downloader} is depicted in \Cref{fig:Downl
The two available user interfaces of \texttt{fiji\_ee.pl} and \texttt{fiji\_ee\_gui.pl} merely prepare data structures representing test patterns and pass them to the classes mentioned above. The two available user interfaces of \texttt{fiji\_ee.pl} and \texttt{fiji\_ee\_gui.pl} merely prepare data structures representing test patterns and pass them to the classes mentioned above.
The GUI application is the only truely\footnote{As far as Perl threads are \textit{real} anyway,\\cf.\ \url{http://perldoc.perl.org/perlthrtut.html\#What-kind-of-threads-are-Perl-threads\%3f}} multithreaded application in the framework. The GUI application is the only truly\footnote{As far as Perl threads are \textit{real} anyway,\\cf.\ \url{http://perldoc.perl.org/perlthrtut.html\#What-kind-of-threads-are-Perl-threads\%3f}} multi-threaded application in the framework.
Its \texttt{download\_worker} function is executed in parallel and triggers the actual communication. Its \texttt{download\_worker} function is executed in parallel and triggers the actual communication.
It gets its commands from the \texttt{Tk}/main thread via a \texttt{Thread::Queue} and returns its result and log message via the same mechanism as well. It gets its commands from the \texttt{Tk}/main thread via a \texttt{Thread::Queue} and returns its result and log message via the same mechanism as well.
......
...@@ -148,7 +148,7 @@ Simply checking out the source code repository and loading the respective script ...@@ -148,7 +148,7 @@ Simply checking out the source code repository and loading the respective script
To help you navigate within the repository the directory structure is shown in \Cref{fig:fijidir} and explained below. To help you navigate within the repository the directory structure is shown in \Cref{fig:fijidir} and explained below.
All source code to be executed by the user on a host PC including customized Perl libraries resides in \texttt{bin}. All source code to be executed by the user on a host PC including customized Perl libraries resides in \texttt{bin}.
This includes also the 4 main scripts already mentioned needed in the \textit{setup}, \textit{instrumentation} and \textit{execution} steps of the workfow. This includes also the 4 main scripts already mentioned needed in the \textit{setup}, \textit{instrumentation} and \textit{execution} steps of the workflow.
Documentation including demo projects, the technical reference manual and this very document can be found in \texttt{docs}. Documentation including demo projects, the technical reference manual and this very document can be found in \texttt{docs}.
......
...@@ -22,7 +22,7 @@ following \emph{optional} command-line arguments: ...@@ -22,7 +22,7 @@ following \emph{optional} command-line arguments:
\item \texttt{-v, {-}{-}verbose} \item \texttt{-v, {-}{-}verbose}
Increase verbosity on the terminal. Each occurence of \texttt{-v} or Increase verbosity on the terminal. Each occurrence of \texttt{-v} or
\texttt{{-}{-}verbose} further increases verbosity. \texttt{{-}{-}verbose} further increases verbosity.
\item \texttt{-h, {-}{-}help} \item \texttt{-h, {-}{-}help}
......
...@@ -52,7 +52,7 @@ the following parameters and switches: ...@@ -52,7 +52,7 @@ the following parameters and switches:
\item \texttt{-v, {-}{-}verbose} \item \texttt{-v, {-}{-}verbose}
Increase verbosity on the terminal. Each occurence of \texttt{-v} or Increase verbosity on the terminal. Each occurrence of \texttt{-v} or
\texttt{{-}{-}verbose} further increases verbosity. \texttt{{-}{-}verbose} further increases verbosity.
\item \texttt{-h, --help} \item \texttt{-h, --help}
......
...@@ -44,8 +44,8 @@ Synopsys' \textit{Synplify Pro} offers the possibility to define \textit{Compile ...@@ -44,8 +44,8 @@ Synopsys' \textit{Synplify Pro} offers the possibility to define \textit{Compile
Points} which correspond to modules in a HDL design \cite{synpmanual}. At the start of the Points} which correspond to modules in a HDL design \cite{synpmanual}. At the start of the
compilation process, Synplify checks if the source for each compile point compilation process, Synplify checks if the source for each compile point
has changed since the last compilation. Only compile points whose source has changed since the last compilation. Only compile points whose source
has changed are resynthesized. has changed are re-synthesized.
Thus, to prevent cross-boundary optimization and resynthesis of the \ac{DUT} netlist, Thus, to prevent cross-boundary optimization and re-synthesis of the \ac{DUT} netlist,
a compile point has to be defined for the instantiated \ac{DUT}. a compile point has to be defined for the instantiated \ac{DUT}.
To do this via the Synplify GUI, the following steps have to be executed: To do this via the Synplify GUI, the following steps have to be executed:
......
...@@ -114,7 +114,7 @@ The script also accepts the following \emph{optional} command-line arguments: ...@@ -114,7 +114,7 @@ The script also accepts the following \emph{optional} command-line arguments:
\item \texttt{-v, {-}{-}verbose} \item \texttt{-v, {-}{-}verbose}
Increase verbosity on the terminal. Each occurence of \texttt{-v} or Increase verbosity on the terminal. Each occurrence of \texttt{-v} or
\texttt{{-}{-}verbose} further increases verbosity. \texttt{{-}{-}verbose} further increases verbosity.
\item \texttt{-h, {-}{-}help} \item \texttt{-h, {-}{-}help}
...@@ -175,7 +175,7 @@ When choosing the \texttt{manual} mode, \textit{\ac{FIJIEE}} prompts ...@@ -175,7 +175,7 @@ When choosing the \texttt{manual} mode, \textit{\ac{FIJIEE}} prompts
the user for fault configurations before they are downloaded as shown the user for fault configurations before they are downloaded as shown
in \Cref{lst:manualprompt}. in \Cref{lst:manualprompt}.
To choosen between the various fault models one has to enter its index. To choose between the various fault models one has to enter its index.
The mapping between these fault indices and the respective fault models is shown in \Cref{tab:faultmap}. The mapping between these fault indices and the respective fault models is shown in \Cref{tab:faultmap}.
\begin{figure} \begin{figure}
...@@ -225,7 +225,7 @@ external trigger (\texttt{1}) shall be used. ...@@ -225,7 +225,7 @@ external trigger (\texttt{1}) shall be used.
Finally, the user has to enter if the fault injection logic shall apply Finally, the user has to enter if the fault injection logic shall apply
a reset to the \ac{DUT} before applying this fault injection pattern. a reset to the \ac{DUT} before applying this fault injection pattern.
Informations other than the fault patterns (e.g., the serial port, Information other than the fault patterns (e.g., the serial port,
baud rate, or \texttt{HOLD\_ON\_FAULT\_DETECT} information) are read from baud rate, or \texttt{HOLD\_ON\_FAULT\_DETECT} information) are read from
the \textit{\ac{FIJI} Settings} and \textit{\ac{FIJI} Tests} files. the \textit{\ac{FIJI} Settings} and \textit{\ac{FIJI} Tests} files.
...@@ -249,7 +249,7 @@ following \emph{optional} command-line arguments: ...@@ -249,7 +249,7 @@ following \emph{optional} command-line arguments:
\item \texttt{-v, {-}{-}verbose} \item \texttt{-v, {-}{-}verbose}
Increase verbosity on the terminal. Each occurence of \texttt{-v} or Increase verbosity on the terminal. Each occurrence of \texttt{-v} or
\texttt{{-}{-}verbose} further increases verbosity. \texttt{{-}{-}verbose} further increases verbosity.
\item \texttt{-h, {-}{-}help} \item \texttt{-h, {-}{-}help}
......
...@@ -70,7 +70,7 @@ In a real-world design the states of the redundant units would usually be determ ...@@ -70,7 +70,7 @@ In a real-world design the states of the redundant units would usually be determ
\item Leave \textit{\#RTS} unconnected. \item Leave \textit{\#RTS} unconnected.
\item Connect \textit{\#CTS} to GND (or leave unconnected if your cable pulls it down). \item Connect \textit{\#CTS} to GND (or leave unconnected if your cable pulls it down).
\item If your cable requires an I/O voltage input (e.g., FTDI TTL-232R-VIP), \item If your cable requires an I/O voltage input (e.g., FTDI TTL-232R-VIP),
connect the correspondig wire to PMOD JE6. connect the corresponding wire to PMOD JE6.
\end{itemize} \end{itemize}
\begin{figure}[H] \begin{figure}[H]
\centering \centering
...@@ -106,7 +106,7 @@ In a real-world design the states of the redundant units would usually be determ ...@@ -106,7 +106,7 @@ In a real-world design the states of the redundant units would usually be determ
\item Leave \textit{\#RTS} unconnected. \item Leave \textit{\#RTS} unconnected.
\item Connect \textit{\#CTS} to GND (or leave unconnected if your cable pulls it down). \item Connect \textit{\#CTS} to GND (or leave unconnected if your cable pulls it down).
\item If your cable requires an I/O voltage input (e.g., FTDI TTL-232R-VIP), \item If your cable requires an I/O voltage input (e.g., FTDI TTL-232R-VIP),
connect the correspondig wire to any 3V3 pin on GPIO1 (e.g., J5.29). connect the corresponding wire to any 3V3 pin on GPIO1 (e.g., J5.29).
\end{itemize} \end{itemize}
\end{minipage} \end{minipage}
\hspace{0.05\linewidth} \hspace{0.05\linewidth}
...@@ -149,8 +149,8 @@ Due to the various supported boards there are some important points to consider ...@@ -149,8 +149,8 @@ Due to the various supported boards there are some important points to consider
To reconstruct the execution of the flow to configure, instrument and synthesize the design with injection logic, the following steps have to be executed. To reconstruct the execution of the flow to configure, instrument and synthesize the design with injection logic, the following steps have to be executed.
The makefile found in \texttt{<FIJI ROOT>/docs/demos/tmr\_vga} optionally guides the user through the \ac{FIJI} flow, executing the following steps The Makefile found in \texttt{<FIJI ROOT>/docs/demos/tmr\_vga} optionally guides the user through the \ac{FIJI} flow, executing the following steps
in a partly automatized manner, providing information about each step. To use this makefile, execute \texttt{make} in the demo directory. in a partly automatized manner, providing information about each step. To use this makefile, execute \texttt{make} in the respective directory.
\subsubsection{Input Netlist} \subsubsection{Input Netlist}
......
...@@ -52,7 +52,7 @@ executed in that order): ...@@ -52,7 +52,7 @@ executed in that order):
\begin{enumerate} \begin{enumerate}
\item The initial synthesis step as well as the \ac{FIJI} Setup and the \item The initial synthesis step as well as the \ac{FIJI} Setup and the
\ac{FIJI} Instrument tool are executed by the Makfile found in \ac{FIJI} Instrument tool are executed by the Makefile found in
\texttt{docs/demos/hx8k\_demo/impl/original/}. Run \texttt{docs/demos/hx8k\_demo/impl/original/}. Run
\begin{lstlisting}[style=shell,gobble=12] \begin{lstlisting}[style=shell,gobble=12]
$ make fiji-instrument $ make fiji-instrument
......
...@@ -72,7 +72,7 @@ NET_NAME=i2c_master_top|G_18_i_a3_8 ...@@ -72,7 +72,7 @@ NET_NAME=i2c_master_top|G_18_i_a3_8
\end{lstlisting} \end{lstlisting}
\begin{table}[H] \begin{table}[H]
\caption{Absoulte resource usage of FIJI logic for different FPGA families} \caption{Absolute resource usage of FIJI logic for different FPGA families}
\label{tab:resources} \label{tab:resources}
\centering \centering
\begin{tabular}{ l l l l l } \begin{tabular}{ l l l l l }
...@@ -86,7 +86,7 @@ NET_NAME=i2c_master_top|G_18_i_a3_8 ...@@ -86,7 +86,7 @@ NET_NAME=i2c_master_top|G_18_i_a3_8
Altera & Stratix V & 5SGTMC5K3 & 253 & 232 \\ Altera & Stratix V & 5SGTMC5K3 & 253 & 232 \\
\midrule \midrule
Xilinx & Virtex 5 & XC5VLX20T & 219 & 229 \\ Xilinx & Virtex 5 & XC5VLX20T & 219 & 229 \\
Xilinx & Zync & XC7Z020 & 214 & 229 \\ Xilinx & Zynq & XC7Z020 & 214 & 229 \\
Xilinx & Spartan 6 & XC6SLX9 & 237 & 229 \\ Xilinx & Spartan 6 & XC6SLX9 & 237 & 229 \\
Xilinx & Kintex 7 & XC7K70T & 219 & 229 \\ Xilinx & Kintex 7 & XC7K70T & 219 & 229 \\
Xilinx & Artix 7 & XC7A100T & 218 & 229 \\ Xilinx & Artix 7 & XC7A100T & 218 & 229 \\
......
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment