Anatomy of component

A component is an object (software entity) that exposes a specific set of methods, properties, and events providing an abstraction for peripheral I/O and CPUs; a component can also be used to encapsulate software stacks or algorithms.

Types of components:

• Pure software algorithm
  • No hardware dependency
• Functionality extension
  • Delivers additional functionality
  • Inherits and extends the embedded component interface
  • Does not access hardware directly; therefore, there is no hardware dependency
• Peripheral driver
  • Uses initialization (init) components for peripheral initialization
  • Defines and implements peripheral functionality
  • Functions to access hardware
  • Hardware dependent; therefore, it defines HAL

A component can be accessed using properties, methods, and events.

Properties represent settings of the component during the design-time. Properties define:

• Component initialization state
• Component settings and features supported in runtime
• Component connection to the CPU (only for LDD components)

Methods are functions exposed by the component, available at runtime, and are used to set the component state and read the component results.

Events are callback functions exposed by the component to attend to asynchronous events such as Interrupts.

If you select any event in the component, you must specify the name of the procedure like event handler. This procedure will be called by a component driver when an associated asynchronous event takes place (for example, hardware interrupt or some error).