trunk/c_ber0/c_ber0.tex

%$Header: /home/dashley/cvsrep/e3ft_gpl01/e3ft_gpl01/dtaipubs/esrgubka/c_ber0/c_ber0.tex,v 1.2 2001/07/01 20:32:16 dtashley Exp $

\chapter{\cberzerolongtitle{}}

\label{cber0}

\section{Corrupted Software Build Output}

A recent article in \emph{Scientific American}
highlighted that data transfers and RAM contents in computers
were vulnerable to errors.  During the single build of
an embedded software load, how large is the probability
that the build output will be corrupted, and does this
probability justify any special build procedures, especially when
MROM is involved?


%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%

\noindent\begin{figure}[!b]
\noindent\rule[-0.25in]{\textwidth}{1pt}
\begin{tiny}
\begin{verbatim}
$RCSfile: c_ber0.tex,v $
$Source: /home/dashley/cvsrep/e3ft_gpl01/e3ft_gpl01/dtaipubs/esrgubka/c_ber0/c_ber0.tex,v $
$Revision: 1.2 $
$Author: dtashley $
$Date: 2001/07/01 20:32:16 $
\end{verbatim}
\end{tiny}
\noindent\rule[0.25in]{\textwidth}{1pt}
\end{figure}

%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
% $Log: c_ber0.tex,v $
% Revision 1.2  2001/07/01 20:32:16  dtashley
% Move out of binary mode for use with CVS.
%
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
% $History: c_ber0.tex $
% 
% *****************  Version 2  *****************
% User: Dashley1     Date: 12/22/00   Time: 12:53a
% Updated in $/uC Software Multi-Volume Book (A)/Chapter, BER0, Build Environment Research Questions
% Tcl build is up and running.  Result is near-perfect.
% 
% *****************  Version 1  *****************
% User: David T. Ashley Date: 7/19/00    Time: 12:22a
% Created in $/uC Software Multi-Volume Book (A)/Chapter, BER0, Build Environment Research Questions
% Initial check-in.
%
%End of file C_BER0.TEX
1	%$Header: /home/dashley/cvsrep/e3ft_gpl01/e3ft_gpl01/dtaipubs/esrgubka/c_ber0/c_ber0.tex,v 1.2 2001/07/01 20:32:16 dtashley Exp $
2
3	\chapter{\cberzerolongtitle{}}
4
5	\label{cber0}
6
7	\section{Corrupted Software Build Output}
8
9	A recent article in \emph{Scientific American}
10	highlighted that data transfers and RAM contents in computers
11	were vulnerable to errors. During the single build of
12	an embedded software load, how large is the probability
13	that the build output will be corrupted, and does this
14	probability justify any special build procedures, especially when
15	MROM is involved?
16
17
18	%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
19
20	\noindent\begin{figure}[!b]
21	\noindent\rule[-0.25in]{\textwidth}{1pt}
22	\begin{tiny}
23	\begin{verbatim}
24	$RCSfile: c_ber0.tex,v $
25	$Source: /home/dashley/cvsrep/e3ft_gpl01/e3ft_gpl01/dtaipubs/esrgubka/c_ber0/c_ber0.tex,v $
26	$Revision: 1.2 $
27	$Author: dtashley $
28	$Date: 2001/07/01 20:32:16 $
29	\end{verbatim}
30	\end{tiny}
31	\noindent\rule[0.25in]{\textwidth}{1pt}
32	\end{figure}
33
34	%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
35	% $Log: c_ber0.tex,v $
36	% Revision 1.2 2001/07/01 20:32:16 dtashley
37	% Move out of binary mode for use with CVS.
38	%
39	%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
40	% $History: c_ber0.tex $
41	%
42	% *************** Version 2 ***************
43	% User: Dashley1 Date: 12/22/00 Time: 12:53a
44	% Updated in $/uC Software Multi-Volume Book (A)/Chapter, BER0, Build Environment Research Questions
45	% Tcl build is up and running. Result is near-perfect.
46	%
47	% *************** Version 1 ***************
48	% User: David T. Ashley Date: 7/19/00 Time: 12:22a
49	% Created in $/uC Software Multi-Volume Book (A)/Chapter, BER0, Build Environment Research Questions
50	% Initial check-in.
51	%
52	%End of file C_BER0.TEX