SWCU192 November 2021 CC1312R7 , CC1352P7 , CC2652P7 , CC2652R7
20.3.1.1 Programming Model
Sensor Controller Studio is project based. Each Sensor Controller project may contain up to eight Sensor Controller tasks. The output of a project is a set of C source files called the Sensor Controller Interface (SCIF) driver, which can easily be integrated into the System CPU application.
The Sensor Controller is user programmable. The Sensor Controller task code programming language uses a syntax that is similar to C, but has limited features compared to C since it specifically targets the Sensor Controller Engine’s instruction set and firmware framework. For example, there is only support for 16-bit variables, and there are predefined roles for each block of task code (initialization, scheduled execution, event handling and termination).
Figure 20-3 ADC Window Monitor - Execution Code
Hardware peripherals and software algorithms are available as resources. For each task, a set of resources must be selected and configured to enable different types of functionality, such as:
- Analog and digital peripheral modules (for example ADC)
- Analog and digital general-purpose I/O pins
- Simple and complex software algorithms
- Bit-banged serial interfaces
- Task scheduling and event handling
- Communication with the System CPU
Each task resource enables a set of procedures (equivalent to functions in C), with associated constants and global variables. The Sensor Controller calls these procedures from the task code, and can thereby combine use of multiple resources, and can also reuse resources (for example the ADC, Figure 20-4) across multiple tasks.
The Sensor Controller tasks and the System CPU application exchange data through data structure variables (located in the AUX RAM). Sensor Controller Studio generates type definitions and other needed definitions for easy access to these variables.
Figure 20-4 ADC Window Monitor