Commit fbcbc470 authored by Cesar Prados's avatar Cesar Prados

mainly finished, only missing the WR Test Bencher section. Some fixes in Benoit section

parent 1d72648f
......@@ -85,25 +85,36 @@ morekeywords={>,__global__, __device__}, % CUDA specific keywords
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
\begin{frame}
\frametitle{Report Points}
\section{Status Report}
\frametitle{White Rabbit Switch Testing Project}
\section{White Rabbit Switch Testing Project}
The project gathers the methodology and methods for testing the White Rabbit
Switch.
\begin{block}
{White Rabbit Switch Tests}
The procedure used to detect failure in production.
{WR Switch Production Tests}
\begin{itemize}
\item Manufacturing quality control of the WR Switch
\item Avoid that hardware problems manifest themselves as software issues.
\end{itemize}
\end{block}
\begin{block}
{Testing Framework}
blabla
{Benchmark and Compliance Tests}
\begin{itemize}
\item Compliance with the protocol stack: GbE, PTP, WR PTP etc..
\item Assessment of the performance: throughput, frame latency etc..
\end{itemize}
\end{block}
\begin{block}
{White Rabbit Test-Bencher}
blabla
{Other Activities in the Project, Testing Hw Framework}
\begin{itemize}
\item Based on PTS
\item Automatization of the production test procedure task. The tests
are provided by the hw developers.
\end{itemize}
\end{block}
\end{frame}
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
\section{White Rabbit Switch Tests}
......@@ -176,7 +187,7 @@ The testing procedure is a series of scripts:
\end{block}
\begin{block}{shw_tool.c}
\begin{block}{shw\_tool.c}
Accessing to libswitchhw to test
\begin{itemize}
\item LEDs (GPIO, wishbone I2C)
......@@ -189,7 +200,8 @@ The testing procedure is a series of scripts:
\begin{frame}[fragile]{\insertsubsectionhead \ - Report}
The following is an example of the log history for board $014$ (v3.2)
%The following is an example of the log history for board $014$ (v3.2)
Below an example of the log history for the board $014$ (v3.2)
\begin{verbatim}
/tftpboot/rootfs/alpha-pts/logs/output-032014_history.log
\end{verbatim}
......@@ -231,17 +243,70 @@ Fri Oct 12 13:46:14 CET 2012
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
\begin{frame}[allowframebreaks]
\frametitle{Testing Framework}
\section{Testing Framework}
\frametitle{Hardware Testing Framework}
\section{Hardware Testing Framework}
\begin{block}
{Report}
{Architecture}
Client/Server model, the server steers the tests and gather the log information
of one or several DUT clients.
\end{block}
\begin{block}
{Feautures}
\begin{itemize}
\item Communication with freestanding or hosted hardware
\item One-time configuration
\item Guidance and test information during the procedure
\item Flexible order the execution of the tests
\end{itemize}
\end{block}
\begin{block}
{Goal}
Be able to provide a HW Testing Framework not only for the WR Switch, but also
for all the WR Node form factors.
\end{block}
\end{frame}
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
\begin{frame}[allowframebreaks]
\frametitle{White Rabbit Test-Bencher }
\section{White Rabbit Test-Bencher}
\frametitle{White Rabbit Compliance and Performance Tester}
\section{White Rabbit Compliance and Performance Tester}
\end{frame}
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
\begin{frame}
\frametitle{What's Next?}
\section{What's Next}
\begin{block}
{WR Production Test}
\begin{itemize}
\item Cosmetic changes
\item Integration with Hw Testing Framework
\item Development of more test??
\end{itemize}
\end{block}
\begin{block}
{WR Compliance and Test-Bencher}
\begin{itemize}
\item We should start working on it
\item Who wants to "chip in"?
\end{itemize}
\end{block}
\begin{block}
{Hw Testing Framework}
\begin{itemize}
\item Release by Februry a version for the WR Switch
\item Keep working!
\end{itemize}
\end{block}
\end{frame}
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
\begin{frame}[allowframebreaks]
\frametitle{More Information, in the Wiki}
\section{More Information, in the Wiki}
\end{frame}
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
\end{document}
......
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