Commit 6562f1da authored by Cesar Prados's avatar Cesar Prados Committed by Benoit Rat

last changes

parent 0567a175
......@@ -94,7 +94,7 @@ Switch.
{WR Switch Production Tests}
\begin{itemize}
\item Manufacturing quality control of the WR Switch
\item Avoid that hardware problems manifest themselves as software issues.
\item Avoid that hardware problems manifest themselves as software issues
\end{itemize}
\end{block}
......@@ -109,9 +109,8 @@ Switch.
\begin{block}
{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.
\item Based on the project "Production Test Suite"
\item Software that automatizes the production test procedure
\end{itemize}
\end{block}
......@@ -133,6 +132,7 @@ $\Rightarrow$ {\bfseries Goal:} detection of soldering/mouting problems
\item Electrical inspection of the PCBs
\end{itemize}
<<<<<<< HEAD
% CAN NOT ADD the FIGURE???
%
......@@ -142,6 +142,12 @@ $\Rightarrow$ {\bfseries Goal:} detection of soldering/mouting problems
% SCB-electrical_test.png: 1783x868 pixel, 72dpi, 62.89x30.62 cm, bb=0 0 1783 868
\end{center}
=======
%\centering
%\begin{tabular}{c}
%\includegraphics[scale=0.70]{SCB-electrical_test.eps}
%\end{tabular}
>>>>>>> 272ef6c... last changes
\end{frame}
......@@ -259,22 +265,53 @@ Fri Oct 12 13:46:14 CET 2012
\frametitle{White Rabbit Compliance and Performance Tests}
\section{White Rabbit Compliance and Performance Tests}
Integrasys has done the following compliance tests:
\begin{itemize}
\item VLAN support
\item MRP and MVRP
\item Remote Management Interface
\end{itemize}
CERN (Maciej Limpinsky) has "tortured" the switch and measured the
synchronization performance between 0 and 50 degrees.
\begin{block}
{Do we need it?}
{Missing Tests}
\begin{itemize}
\item Throughput
\item Latency
\item Frame Loss Rate
\item System Recovery
\item Synchronization performance with multicast traffic
\item etc...
\end{itemize}
\end{block}
\begin{block}
{Do we need this tests?}
\begin{itemize}
\item Would commercial solutions fulfil our tests?
\item Could community afford to buy/rent commercial solutions?
\item Do we need a way of verifying that a combination hw+firmware achieves
the White Rabbit features?
\item This test could detect new issues in the v3
gateware/firmware/design
\item Do we need a standardized way of verifying that a combination hw+firmware achieves the White Rabbit features?
\end{itemize}
\end{block}
\begin{block}
{Do we need special hw and which one?}
\begin{itemize}
\item Commercial solutions cover partly our tests
\item The community could hardly afford to buy/rent a commercial
solutions. For the manufacture it could be seen as an investment.
\end{itemize}
\end{block}
\begin{block}
{Proposal}
\begin{itemize}
\item Use the WR Switch hw platform for developing a compliance and performance
tester.
\item We could reuse part of the current gateware/firmware, but that
tester. It could be also used as a network debugger in production
systems.
\item We could reuse part of the current gateware/firmware of the switch, but that
wouldn't be enough,it is a new development...
\end{itemize}
......@@ -287,7 +324,7 @@ Fri Oct 12 13:46:14 CET 2012
\section{Hardware Testing Framework}
\begin{block}
{Architecture}
Client/Server model, the server steers the tests and gather the log information
Client/Server model, the server steers the tests and gathers the log information
of one or several DUT clients.
\end{block}
......@@ -297,7 +334,7 @@ of one or several DUT clients.
\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
\item Flexible order of the execution of the tests
\end{itemize}
\end{block}
......@@ -317,8 +354,8 @@ for all the WR Node form factors.
{WR Production Test}
\begin{itemize}
\item Cosmetic changes
\item Integration with Hw Testing Framework
\item Development of more test??
\item Integration with hw Testing Framework
\item Development of more tests?
\end{itemize}
\end{block}
......@@ -343,13 +380,19 @@ for all the WR Node form factors.
\begin{frame}
\frametitle{Wiki of the Project}
\section{Wiki of the Project}
\begin{block}
{Information about this Project in the OHWR Wiki, so far there is:}
\begin{itemize}
\item WR Production Tests and How To
\item WR.v2 802.1Q Functional Test Cases Report (Integrasys)
\item Torture Report (Maciej Lipinsky)
\item Testing Hardware Framework
\item Test Methodology and Proposal for the Test-Bencher
\item WR.v2 802.1Q Functional Test Cases Report
\item Torture Report
\item Testing Hardware Framework, not released yet
\item Test Methodology Doc
\item Proposal for the WR tester.
\end{itemize}
\end{block}
\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