\section*{Revision history}
+{\small
\noindent\begin{tabularx}{\linewidth}{|l|l|l|X|}
\rowcolor[gray]{0.9}\hline
Revision & Date & Author(s) & Comments \\ \hline
part of Eaton distribution.
\\\hline
- 0.7 & 2015-10-04 & Sojka & Simulink GIO blocks
+ 0.7 & 2015-10-05 & Sojka & Simulink GIO blocks
(sec.
\ref{sec:block:sfunction_gio_in.c},
\ref{sec:block:sfunction_gio_out.c})
initialization demo''.
\\\hline
\end{tabularx}
-
+}
\tableofcontents
\newpage
low-level run-time C library and a tool for interactive testing of
hardware and software functionality.
-Originally, the RPP project was created for a custom TMS570-based board
-and the port to other platforms such as RM48 HDK and TMS570 HDK
-development kits. Porting to other platforms was done under a contract
-from Eaton Corporation.
+Originally, the RPP project was created for a custom TMS570-based
+board. Subsequently, it was ported to other board such as RM48 HDK and
+TMS570 HDK development kits under a contract from Eaton Corporation.
The document contains step-by-step instructions for installation of
development tools, information about Simulink Coder configuration,
% exclusively on the bottom layer, not on any lower level layer (except for a
% couple of exceptions).
\item Each layer should provide a unified layer interface
- (\texttt{rpp.h}, \texttt{drv.h}, \texttt {hal.h}, \texttt{sys.h} and
+ (\texttt{rpp.h}, \texttt{drv.h}, \texttt{sys.h} and
\texttt{os.h}), so that higher layers depend on the lower layer's interface
and not on individual elements from that layer.
\end{compactitem}
As a consequence of this division the source code files and interface files are
placed in private directories like \texttt{drv/din.h}. With this organization
user applications only needs to include the top layer interface files (for
-example \texttt{rpp/rpp\_can.h}) to be able to use the selected library API.
+example \texttt{rpp/rpp.h}) to be able to use the selected library API.
The rest of the section provides basic description of each layer.
\clearpage
\input{block_desc.tex}
+\newpage
\section{Compilation}
\label{sec-simulink-compilation}
The first step, before any attempt to compile demo or other models, is to compile the S-Functions of the RPP blocks. The S-Functions are compiled during the Configuring Simulink for RPP, described in Section \ref{sec-configuration-simulink-for-rpp}. If you want to recompile the S-Functions without reconfiguring the Simulink, open the Matlab and run those commands in the Matlab commad line:
\textbf{115200-8-N-1}. When the software starts, the received welcome message
and prompt should look like:
-
+\bigskip
\ifx\tgtId\tgtIdTMSRPP
-\begin{verbatim}
-Rapid Prototyping Platform v00.01-001
-Test Software version v0.2-261-gb6361ca
-CTU in Prague 2014
--->
-\end{verbatim}
+\noindent\texttt{Rapid Prototyping Platform v00.01-001\\
+Test Software version \input{version.tex}\\
+CTU in Prague 2014\\
+-->
+}
\else
-\begin{verbatim}
-Ti HDK \mcuname, FreeRTOS 7.0.2
-Test Software version eaton-0.1-beta-8-g91419f5
-CTU in Prague 10/2014
--->
-\end{verbatim}
+\noindent\texttt{Ti HDK \mcuname, FreeRTOS 7.0.2\\
+Test Software version \input{version.tex}\\
+CTU in Prague 10/2014\\
+-->
+}
\fi
+\bigskip
+
Type in command help for a complete list of available command, or help command
for a description of concrete command.