Skip to content
Projects
Groups
Snippets
Help
Loading...
Sign in
Toggle navigation
W
White Rabbit Switch - Testing
Project
Project
Details
Activity
Cycle Analytics
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Charts
Issues
0
Issues
0
List
Board
Labels
Milestones
Merge Requests
0
Merge Requests
0
CI / CD
CI / CD
Pipelines
Jobs
Schedules
Charts
Wiki
Wiki
image/svg+xml
Discourse
Discourse
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Charts
Create a new issue
Jobs
Commits
Issue Boards
Open sidebar
Projects
White Rabbit Switch - Testing
Commits
0567a175
Commit
0567a175
authored
Nov 27, 2012
by
Benoit Rat
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
doc: last changes
parent
f0805ec5
Show whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
43 additions
and
27 deletions
+43
-27
presentation.tex
doc/presentations/workshop_madrid/presentation.tex
+43
-27
No files found.
doc/presentations/workshop_madrid/presentation.tex
View file @
0567a175
...
...
@@ -42,7 +42,7 @@
\author
{
B.Rat, C.Prados
}
\institute
[Seven Solutions, GSI]
{
GSI
\\
Seven Solutions,
GSI
\\
\medskip
{
\emph
{
benoit@sevensols.com, c.prados@gsi.de
}}}
\date
{
\today
}
...
...
@@ -119,9 +119,13 @@ Switch.
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
\section
{
White Rabbit Switch Tests
}
\subsection
{
Pre-Test
}
\subsection
{
Pre-Test
: Basic visual and electrical tests.
}
\begin{frame}
{
\insertsubsectionhead
}
The first steps for production test are:
\begin{block}
{}
Quality procedures already done and documented.
\\
$
\Rightarrow
$
{
\bfseries
Goal:
}
detection of soldering/mouting problems
\end{block}
\begin{itemize}
\item
FlyingProve done at the assembly company
...
...
@@ -131,12 +135,13 @@ The first steps for production test are:
% CAN NOT ADD the FIGURE???
%
\centering
\begin{tabular}
{
c
}
\includegraphics
[scale=0.70]
{
SCB-electrical
_
test.eps
}
%%SCB-electrical_test.png: 1783x868 pixel, 72dpi, 62.89x30.62 cm, bb=0 0 1783 868
%\caption{Electrical Inspection}
\end{tabular}
\begin{center}
\includegraphics
[height=3cm,keepaspectratio=true]
{
SCB-electrical
_
test.eps
}
% SCB-electrical_test.png: 1783x868 pixel, 72dpi, 62.89x30.62 cm, bb=0 0 1783 868
\end{center}
\end{frame}
...
...
@@ -145,10 +150,10 @@ The first steps for production test are:
\begin{block}
{}
The test of the switch has been intended to be as flat as possible,
this mean that we intend to test a component with the less dependency possible of other
component.
component
s
.
\end{block}
However we need to have at least the following working:
However
, to test a component (FGPA, NAND, ...)
we need to have at least the following working:
\begin{itemize}
\item
ARM (detected during the flashing stage)
\item
DDR (test during the flashing stage)
...
...
@@ -159,24 +164,26 @@ However we need to have at least the following working:
\subsection
{
Actual Testing
}
\begin{frame}
[allowframebreaks]
{
\insertsubsectionhead
}
The testing procedure is a se
ries
of scripts:
The testing procedure is a se
t
of scripts:
\begin{itemize}
\item
001-MD5
Checking.sh: Check MD5 of needed files
\item
001-MD5
\_
Checking.sh: Check MD5 of needed files
\item
002-USB.sh: Check the USB (Not implemented)
\item
003-FPGA Bridge.sh: CPU (EB1) <-> FPGA (WB)
\item
004-LED Checking.sh: LED of CPU
\&
miniBP
\item
005-FAN Checking.sh: FAN on/off and PWM speed
\item
006-FPGA QDRIIStress.sh: Stress the QDDR test.
\item
007-NF MT29F4G16.sh: NAND flash read/write full on (About 15m )
\item
008-DF AT45DB642.sh: Dataflash all position (6m).
\item
009-FPGA TempRetrieving.sh: Retrieve the temperature
\item
010-Flashing.sh: Flash with the latest stable firmware
\item
003-FPGA
\_
Bridge.sh: CPU (EB1)
$
\leftrightarrow
$
FPGA (WB)
\item
004-LED
\_
Checking.sh: LED of CPU
$
\&
$
miniBP
\item
005-FAN
\_
Checking.sh: FAN on/off and PWM speed
\item
006-FPGA
\_
QDRIIStress.sh: Check
$
\&
$
Stress the QDRII.
\item
007-NF
\_
MT29F4G16.sh: NAND flash partial R/W (
$
\sim
$
20m )
\item
008-DF
\_
AT45DB642.sh: Dataflash all position (
$
\sim
$
6m).
\item
009-FPGA
\_
TempRetrieving.sh: Retrieve the temperature.
\item
010-WRS
\_
SFPs.sh: Use standard bitstream to check SFP transfers.
\item
011-Flashing.sh: Flash with the latest stable firmware
\end{itemize}
To perform these steps we have create some generic tools.
\begin{block}
{
testing.sh
}
Main script
s called to generate proper log
Main script
called to generate proper log information:
\begin{itemize}
\item
S/N of the board
\item
Timestamp of each steps
...
...
@@ -187,7 +194,7 @@ The testing procedure is a series of scripts:
\begin{block}
{
shw
\_
tool.c
}
Accessing to libswitchhw
to test
Accessing to libswitchhw
library to test various components:
\begin{itemize}
\item
LEDs (GPIO, wishbone I2C)
\item
FANs (PWN fan, GPIO)
...
...
@@ -218,7 +225,8 @@ Fri Oct 12 12:24:08 CET 2012
007 > ERROR ( Sub0:OK Sub1:OK Sub2:OK Sub3:OK Sub4:50
% Sub5:OK Sub6:OK) (22'40)
008 > OK (02'47)
009 > OK (00'14)
010 > OK (04'51)
010 > OK (01'20)
% 011 > OK (04'51)
-----------------------------------------------
Fri Oct 12 13:46:14 CET 2012
...
...
@@ -228,13 +236,21 @@ Fri Oct 12 13:46:14 CET 2012
\end{frame}
\begin{frame}
\begin{block}
{
Future Work
}
Create small HDL to check only a component, not a functionality.
\begin{itemize}
\item
I2C sensor
\item
SFP transfers
\item
PLL frequency
\end{itemize}
\end{block}
\begin{block}
{
Conclusion
}
By doing these tests we
improve the quality
of the product:
By doing these tests we
{
\bfseries
improve the quality
}
of the product:
\begin{itemize}
\item
Checking the components
\item
Checking the connection
\item
Debugging the code (API)
\item
Understanding better the sw/gw
\\
$
\Rightarrow
$
{
\bfseries
Improve
client support
}
\item
Improve development: Check if a bug occurs for new functionality or for a specific component.
\item
Understanding better the sw/gw
\\
$
\Rightarrow
$
{
\bfseries
Better
client support
}
\end{itemize}
\end{block}
\end{frame}
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment