SLAAEK8 August   2024 MSPM0G3507 , MSPM0L1306

 

  1.   1
  2. 1 Description
  3. 2 Required Peripherals
  4. 3 Compatible Devices
  5. 4 Design Steps
  6. 5 Design Considerations
  7. 6 Software Flow Chart
  8. 7 Application Code
    1. 7.1 Scheduler Code
    2. 7.2 Main Application Code
  9. 8 Additional Resources
  10. 9 E2E
  11. 10Trademarks

5 Design Considerations

When integrating tasks into the task scheduler subsystem, consider the following:

  1. If multiple interrupts or tasks are queued at the same time, the main scheduler loop services the tasks in the order the tasks appear in gTasksList. This can be considered a simple priority, although still not preemptive.
  2. All tasks are interrupt-driven in this architecture, meaning that the appropriate IRQ handler must set the pending flag associated with the task to be run. If only a single operation of an event makes sense in the system, only increment the gTasksPendingCounter if the flag was not already set. If multiple occurrences of an event need to be queued at the same time, use an integer value for the pending flag, rather than strictly a true or false Boolean value.