Different ways to organize main.c and other application-level files.

The characteristics of MCC Melody API, including Blocking vs. Non-blocking, ISRs, Callbacks and Task routines.

This sequential form of control flow, waits for each task to be complete, before moving onto the next. Polled or blocking control flow involves continuously checking a for tasks to complete and waiting (blocking) until a specific condition is met.

A structured and flexible approach to manage events without continuous CPU involvement is facilitated by interrupts immediately diverting processor attention to urgent tasks. Callbacks define specific actions to be executed in response.

Each application task is given its own control loop, consisting of a series of states. Transitions between these states are based on internal or external events, providing a clear, organized structure to handle foreseeable application logic.

Low-power consumption may be an important application requirement. Here, we recommend an interrupt/callback or state machine-based design pattern.

This section introduces Example Components and introduces important foundational examples for configuring MCC Melody components.