0% found this document useful (0 votes)
17 views8 pages

Embedded Programming: The Task Model

The document discusses the elements that define a task in embedded programming, including a name, unique ID, priority, task control block, stack, and task routine. It notes the key criteria for structuring a program using tasks are parallelism, timing, priority, structure, and periodicity. Effective task design involves balancing a small number of loosely coupled tasks to reduce overhead with a larger number to minimize risk from changes.

Uploaded by

Cristian Ceruţa
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
17 views8 pages

Embedded Programming: The Task Model

The document discusses the elements that define a task in embedded programming, including a name, unique ID, priority, task control block, stack, and task routine. It notes the key criteria for structuring a program using tasks are parallelism, timing, priority, structure, and periodicity. Effective task design involves balancing a small number of loosely coupled tasks to reduce overhead with a larger number to minimize risk from changes.

Uploaded by

Cristian Ceruţa
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
You are on page 1/ 8

EMBEDDED PROGRAMMING

The Task Model

Student: Cristian Ceruta (crcer18)


Task Definition

Elements of a task:
 A name
 Unique ID
 Priority
 Task control block
 Stack
 Task routine
Task Definition

Elements of a task:
 A name
 Unique ID
 Priority
Task vs Function!
 Task control block
 Stack
 Task routine
Task Definition

Criteria for structuring the program by tasks:


 The parallel Criteria
 The timing Criteria
 The priority Criteria
 The structural Criteria
 The periodical Criteria

Note:
Few divided tasks – less loose coupling, bigger risk when changes occur.
Many tasks – may cost overhead
Task Diagrams
Loosely coupling tasks
Inter-task communication
State Machine Diagram

You might also like