Commit e60706a2 authored by Javier Serrano's avatar Javier Serrano

Initial check in with files from Patrick, Natasa and Cesar.

parent b880afab
\pdffalse % we are not running PDFLaTeX => normal DVI output
\pdfoutput=1 % we are running PDFLaTeX
{ /Title (Guidelines for VHDL Coding)
/Author (Patrick Loschmidt, Natasa Simanic, Cesar Prados)
/Subject (VHDL)}
% \documentclass[a4paper,12pt]{article}
% \usepackage[a4paper]{hyperref}
\usepackage{color,listings} % color code source code
\usepackage{svn-multi} % use SVN keyword replacements
\svnid{$Id: VHDLcoding.tex 327 2009-04-21 10:51:34Z loschmidt $} % if replacement does not work set property 'svn:keywords' to 'Id'
\definecolor{darkgreen}{rgb}{0,0.5,0} % define new color dark green (50% green)
\definecolor{darkred}{rgb}{0.5,0,0} % define new color dark red (50% red)
\lstset{ language=VHDL, % set coding style to VHDL syntax
flexiblecolumns=false, % set fixed column width
basicstyle=\ttfamily\footnotesize, % set fixed with font in small
emph={std_logic, std_logic_vector, integer},
\author{Patrick Loschmidt$^{1}$, Nata$\check{s}$a Simani\'{c}$^{1}$, C\'{e}sar Prados$^{2}$\\
$^{1}$Research Unit for Integrated Sensor Systems, Austrian Academy of Sciences}\\
{\footnotesize \{Patrick.Loschmidt, Natasa.Simanic\}}\\
$^{2}$Gesellschaft fr Schwerionenforschung mbH, GSI}\\
{\footnotesize \}}
\title{Guidelines for VHDL Coding}
This is a summary of coding style rules which is intended to be a guideline for writing portable and readable VHDL code. Following these rules should result in better code quality or, at least, should make finding errors easier.
This version was printed on \today.
\section*{Changelog for rev. \svnrev}
\item changed postfix for pulsed signals
\item Author info added
\item \emph{Doxygen} chapter modified
\item SVN revision number / date
\item \emph{Doxygen} and Changelog chapters added
\item Variables usage and placing component instantiation determined
\item Naming conventions extended
\item Combinational blocks template added
\item Minor text corrections
\item Upper case naming convention changed
\item Initial release
\bibitem[ESA94]{ESA94}\emph{R. Creasey, R. Coirault, P. Sinander}: VHDL Modelling Guidelines,
\url{}, September 1994
\bibitem[Cad00]{Cad00}\emph{Gerhard R. Cadek}: HDL Coding Style Rules,
\url{}, 10 September 2000
\bibitem[OC01]{OC01}\emph{Yair Amitay, Jamil Khatib, Damjan Lampret}: OpenCores Coding Guidelines,
\url{}, 24 October 2001
\bibitem[Kha00]{Kha00}\emph{Jamil Khatib}: VHDL Coding Style,
\url{}, 2000
\bibitem[VHDL01]{VHDL01}\emph{comp.lang.vhdl}: Frequently Asked Questions And Answers,
\url{}, 3 November 2001
\bibitem[COM10]{COM10}\emph{Peter Chambers}: The Ten Commandments of Excellent Design-VHDL Code
\bibitem[CERN]{CERN}\emph{Pablo Alvarez Sanchez}: VHDL guidelines,
\bibitem[DXGN]{DXGN}\emph{doxygen} website,
A lot of cross references are used because they make it easier to find other corresponding parts within the document. A link looks like ``($\rightarrow$ \ref{fonts})'' and always belongs to the word(s) right before it.
Further, this document distinguishes between different types of rules. An explanation of these types and the appropriate symbol is shown in table \ref{tab:ruleTypes}.\\
symbol & type & description\\
(*) & important & This rule should be followed in any case.\\
(x) & recommended & Coding and reading is a lot easier with this rule.\\
(o) & practical & Your code quality will improve using the rule.\\
none & hints & Just giving you an idea of how it could be.\\
\caption{Rule types}
\ No newline at end of file
This diff is collapsed.
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