Projekt

Allgemein

Profil

Bringup » Historie » Revision 3

Revision 2 (Maximilian Seesslen, 11.07.2022 16:21) → Revision 3/7 (Maximilian Seesslen, 18.08.2022 15:01)

h1. Bringup

There has to be a bringup application which uses the bringup class from campo.
At least the bringup application is able to write the hwinfo via gdb scripts.

* The result is an protocol that should be added to the hw repository. "doc/bringup_0.1.x.txt".
The bringup class shall dump the protocoll after the interactive communication.

* Defects are created

* The readme is enhanced by possible erratas with defect id when the reason is clear. (meanwhile fixed biwak problem)

h2. Architecture

<pre><code class="cpp">

class CBringup
{
CList<CResult> results;
}

int CBringup::testAssert(const char *test)
{
CResult &result=( results << CResult(test) );
result.setGroup(getGroup());
}

int CBringup::testRtc(CRtc &rtc)
{
setGroup("RTC");
testAssert("plausibility", rtc.getDate() > 2010, rtc.getDate() );
return(sta);
}

</code></pre>