...
KAL is not as a full-featured kernel abstraction layer and only aims to provide minimal kernel services for usage in Micriµm's products and thus its functions should not be called by your application(s), except for an optional call to KAL_Init().
The KAL implementation code for µC/OS-II and µC/OS-III is available. Users of third party kernel will need to provide their own KAL implement using the provided template file,.
...
If KAL resources are allocated from the heap (no specific memory segment is used, as specified through KAL_Init()), LIB_MEM_CFG_HEAP_SIZE (in lib_cfg.h) must provide enough memory for allocation of these resources.
...
If no specific memory needs to be used for KAL resources, the products using KAL (µC/FS, µC/TPC, etc.) will call KAL_Init() themselves without specifying a memory segment. In that case, KAL will allocate its resources in the heap and LIB_MEM_CFG_HEAP_SIZE may need to be adjusted to provide enough memory for allocating these resources.
...
This initialization example shows how KAL can be initialized and configured to use a specific memory location to allocate everything it needs.
| Insert excerpt | ||||||
|---|---|---|---|---|---|---|
|