This directory contains the Baremetal-specific code, including drivers, platform abstraction and examples. This is in contrast to posix, which can only run on a POSIX or Windows OS, or ca821x-api and ca821x-utils, which can be used in both OS and embedded contexts. The baremetal code is used on Cascoda’s Chili platforms, and can easily be ported to different MCUs.
This folder contains example applications for:
ot-cli-*)ot-sed-*)ot-sed-sensorif)ot-cli-actuator)CASCODA_BM_INTERFACE CMake configuration variable)sensorif-bm)mikrosdk-bm).General baremetal drivers and API. This includes the EVBME (Evaluation Board Management Entity), which enables any host platform connected by USB/UART to control the device using EVBME commands.
Minimal baremetal driver. This contains the minimal functionality required to control a CA-821x via SPI without any of the extended EVBME functionality.
Port layer for the OpenThread stack. This enables using OpenThread on baremetal platforms with a CA-821x radio. The OpenThread API itself should be used for controlling the OpenThread stack.
Functions and examples specifically targeted for the Cascoda Development Board.
Set of MikroE CLICK boardTM drivers for extracting data from sensors and controlling actuators.
A mid-level adaptation layer between the driver API and hardware. It integrates the MikroElektronika library with the Cascoda libraries in the HAL (Hardware Abstraction Layer), allowing communication between MikroElektronika devices and Chili2 via I2C/SPI and GPIO.
Platform abstraction layers for different microcontrollers. These are split into seperate directories containing both vendor code from the MCU (Microcontroller Unit) vendor and port code written by Cascoda.
Set of specific (non-MikroE) drivers for extracting data from sensors and controlling actuators. This abstracts away the details of the underlying I2C/SPI communications.
Set of unit tests that are run at build time to verify common functionality.