SWRU439M October   2015  – April 2022

 

  1.   Trademarks
  2. 1Introduction
  3. 2Overview
    1. 2.1 Sensor Controller and AUX Domain Hardware Overview
      1. 2.1.1 Hardware Functionality
      2. 2.1.2 Power and Clock Management
        1. 2.1.2.1 CC13x0 and CC26x0 Operation Modes
        2. 2.1.2.2 CC13x2 and CC26x2 Operation Modes
        3. 2.1.2.3 Communication With the System CPU Application
    2. 2.2 Sensor Controller Interface Driver
      1. 2.2.1 Tailored How-To-Use Guide
      2. 2.2.2 Doxygen Documentation
    3. 2.3 Sensor Controller Programming Model
    4. 2.4 Sensor Controller Tasks
      1. 2.4.1 Data Structures
      2. 2.4.2 Task Code Blocks
      3. 2.4.3 High-Level Program Flow
    5. 2.5 Task Testing and Debugging
    6. 2.6 Run-Time Logging
  4. 3Prerequisites
    1. 3.1 Driver
    2. 3.2 Examples
  5. 4Installation
    1. 4.1 Sensor Controller Studio for Windows
      1. 4.1.1 Update Service
    2. 4.2 Sensor Controller Studio CLI for Linux (64-Bit)
  6. 5Sensor Controller Studio Tutorials
  7. 6Sensor Controller Studio Walkthrough
    1. 6.1  Start Page and Navigation
    2. 6.2  Documentation
    3. 6.3  Open the Example
    4. 6.4  Project Panel
    5. 6.5  Task Panel Settings
    6. 6.6  Constants and Data Structures Panel
    7. 6.7  Task Code Editor Panels
    8. 6.8  I/O Mapping Panel
    9. 6.9  Code Generator Panel
    10. 6.10 Compiling Example Applications in IAR or CCS
    11. 6.11 Task Testing Panel
      1. 6.11.1 Task Testing Setup
      2. 6.11.2 Task Testing Session
      3. 6.11.3 Data Handling
      4. 6.11.4 Task Debugging Panel
    12. 6.12 Run-Time Logging Panel
      1. 6.12.1 Run-Time Logging Setup
      2. 6.12.2 Run-Time Logging Session
  8. 7References
  9. 8Revision History

6.5 Task Panel Settings

The task panel contains settings that apply to one task, including resource selection and configuration (see the example in Figure 6-5).

GUID-23889949-4408-42F3-AE95-1684EC5F8389-low.png Figure 6-5 Task Panel

The task name is used in the generated SCIF driver code to identify the task and must be unique per project.

The task description (also included in the generated driver) can be used to explain the task purpose, usage, electrical connections, and so forth.

Task resources are selected to enable access to hardware modules, firmware framework functionality and various software algorithms. Some resources have configuration settings. For the "General Purpose I/O" resources, multiple usages with different name and configuration can be specified. Press the help buttons [?] to view resource documentation, including associated procedures, constants and variables.

For the ADC Window Monitor task, the following resources are selected:

  • ADC: to measure the output of the light sensor
  • Analog Pins (one instance): to connect the analog sensor output to the ADC
  • System CPU Alert: to wake up and generate interrupts in the System CPU application
  • RTC-Based Execution Scheduling: to trigger periodical execution of the task