Projekt

Allgemein

Profil

Bringup » Historie » Version 3

Maximilian Seesslen, 18.08.2022 15:01

1 1 Maximilian Seesslen
h1. Bringup
2
3
There has to be a bringup application which uses the bringup class from campo.
4
At least the bringup application is able to write the hwinfo via gdb scripts.
5
6
* The result is an protocol that should be added to the hw repository. "doc/bringup_0.1.x.txt". 
7
The bringup class shall dump the protocoll after the interactive communication.
8
9
* Defects are created
10
11 2 Maximilian Seesslen
* The readme is enhanced by possible erratas with defect id when the reason is clear. (meanwhile fixed biwak problem)
12 3 Maximilian Seesslen
13
h2. Architecture
14
15
<pre><code class="cpp">
16
17
class CBringup
18
{
19
   CList<CResult> results;
20
}
21
22
int CBringup::testAssert(const char *test)
23
{
24
   CResult &result=( results << CResult(test) );
25
   result.setGroup(getGroup());
26
}
27
28
int CBringup::testRtc(CRtc &rtc)
29
{
30
   setGroup("RTC");
31
   testAssert("plausibility", rtc.getDate() > 2010, rtc.getDate() );
32
   return(sta);
33
}
34
35
</code></pre>