AMiRo-OS: Issueshttps://opendata.cit-ec.de/https://opendata.cit-ec.de/favicon.ico?14265323552019-03-14T10:06:12ZResearch for Cognitive Interaction
Redmine Feature #594 (Resolved): Revise periphALhttps://opendata.cit-ec.de/issues/5942019-03-14T10:06:12ZThomas Schöppingtschoepp@techfak.uni-bielefeld.de
<p>The periphery abstraction layer (periphAL) should be revised and optimized:</p>
<ul>
<li>All <code>enum</code> should be replaced by a combination of <code>#define</code> and optimal fundamental types (e.g. <code>typedef uint16_t apalExitStatus_t</code>) for best code efficiency.</li>
<li><code>apalGpioActive_t</code> should be extended by two further states: <code>APAL_GPIO_ACTIVE_NONE</code> and <code>APAL_GPIO_ACTIVE_ANY</code></li>
<li><code>apalGpioEdge_t</code> documentation s´must clearly state that values refer to physical (not logical!) signal edges.</li>
<li><code>apalGpioMeta_t</code> needs to be updated accordingly (i.e. two bits for the <code>apalGpioActive_t</code> member).</li>
<li>The <code>edge</code> member of <code>apalGpioMeta_t</code> can also apply to output signals, so wherever this struct is used, comments must be updated accordingly (right now the definitions in all <code>module.c</code> files state it as "interrupt edge", which just one of many ways how the edge information can be interpreted).</li>
</ul> Feature #592 (Resolved): AMiRo-LLD configuration via Makefilehttps://opendata.cit-ec.de/issues/5922019-03-08T12:24:17ZThomas Schöppingtschoepp@techfak.uni-bielefeld.de
<p>Currently AMiRo-LLD drivers are activated via the alldconf.h file, which results in numerous files being compiled without providing any functionality. Furthermore, those useless files will be included in the QtCreator projects, since GCC evaluates them.<br />To tackle this issue, drivers should be enabled via the module Makefile, so only the required files and paths are included to the build process. The alldconf.h file can still be used to configure the drivers if they provide further settings.</p> Feature #590 (Resolved): System (de)initialization with disabled bootloaderhttps://opendata.cit-ec.de/issues/5902019-03-08T12:16:04ZThomas Schöppingtschoepp@techfak.uni-bielefeld.de
<p>Introduce a possibility to configure AMiRo-OS to not use a bootloader, so that the OS will fully initialize the hardware, including SSSP related signal handling and synchronization (if SSSP is enabled).</p> Feature #585 (Resolved): Investigate whether CAN can be an optional feature of AMiRo-OShttps://opendata.cit-ec.de/issues/5852019-02-25T15:50:11ZThomas Schöppingtschoepp@techfak.uni-bielefeld.de
<p>So far, having a CAN bus enabled is mandatory for AMiRo-OS to work.<br />The necessity for this should be investigated again and - if possible - this requirement should be removed.</p>