-
The currently released OSAL unit tests may not fully run with OSAL 4.1.1.
JSC has made updates so that they run with Linux and ARINC653 OSAL 4.1.1.
JSC is currently updating to work with VxWor…
-
There are two issues that cause a build failure when using a recent RTEMS toolchain/library:
* {{{MSG_DONTWAIT}}} now //is// defined by the library headers. This is re-defined in {{{fsw/cfe-core/s…
-
JSC has developed a known and understood version of printf that has been code reviewed and unit tested. It can be used on platforms that do not provide a printf (such as ARCIN653) or as a known, trus…
-
The version of the unit tests currently included with cFE 6.4.1 were developed and tested against cFE 6.3.2. Due to cFE changes, all of the tests no longer pass.
Also, the tests have only been tes…
-
Hi,
I'm trying to use Ocarina on the ADIRU example but I get the following errors:
`Frontends : error : partitions.aadl:304:55: parsing Error_Condition, token ')' is expected, found token 'and'
…
-
This project has no unit tests that can be run as part of an automatic build-and-test cycle to assure that a change has not broken fundamental behaviors.
We need central portable unit tests that ca…
-
OSAL returns object identifiers which are defined as uint32 values. In the current implementation of OSAL they happen to be zero-based but this should not be a requirement; in fact there are several …
-
**Is your feature request related to a problem? Please describe.**
Resolve the follow cppcheck.
```
[osal/src/bsp/mcf5235-rtems/src/bsp_start.c:136] -> [osal/src/bsp/mcf5235-rtems/src/bsp_start.…
-
Some platforms (RTEMS, for example) do not natively support the concept of dynamic module loading. Even on platforms that do offer this feature, it is sometimes beneficial to statically link anyway, …
-
With trac ticket #29 (and related #30) now implemented, the OSAL tests can be used as one piece of a build verification tool suite.
However, the implementation is currently very basic - it does not…