1 |
dashley |
140 |
%$Header$ |
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 |
dashley |
275 |
$HeadURL$ |
25 |
|
|
$Revision$ |
26 |
|
|
$Date$ |
27 |
|
|
$Author$ |
28 |
dashley |
140 |
\end{verbatim} |
29 |
|
|
\end{tiny} |
30 |
|
|
\noindent\rule[0.25in]{\textwidth}{1pt} |
31 |
|
|
\end{figure} |
32 |
|
|
|
33 |
dashley |
275 |
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% |
34 |
dashley |
140 |
% |
35 |
|
|
%End of file C_BER0.TEX |