Source files include the driver implementation and related header files. These include multiple files separated into the interface exposed for the user of the driver and private source that is closer to a particular target hardware MCU as well as interrupt sources.

Header (.h) and Source (.c) files for a particular driver were named starting with <Mip> for Module Implementation Prefix in Pascal_Snake_Case (that is, a combination of PascalCase and snake_case) to comply with the AUTOSAR specification for naming and directory structure. <Mip> named files are those having Public Interface contents including Macros, Data Types, and APIs that are exposed to use from a device driver. This source is kept as generic and compliant with the module SRS and SWS specifications. APIs have a fixed, well-defined interface for any given functionality expected by this layer, making the APIs reliable for use with the source library. APIs remain backward compatible; therefore, no cleanup or version migration changes are ever necessary.

Use of highly hardware-specific source named <Mip>_Priv (containing the Private implementation) in the driver application is not recommended. The <Mip>_Priv identifiers and symbols can be updated anytime a hardware design is migrated and need not provide a backward compatibility upon the existing source implementation easily on account of any feature support and bug fixes.

Files named <Mip>_Irq contain the IRQ and Interrupt handling source that is used to service interrupt routine (ISR) which is set using the ARM Nested Vectored Interrupt Controller implementation with TI Vectored Interrupt Module (VIM). Any files included other than just the <Mip> named files are considered as a private driver source whose content is not recommended for direct consideration as an interface usable from the built driver library, even if the files or symbols remain exposed to any part of source or the bundled library.

Example application source can be taken as a go-to reference when setting up the dependencies by initialization for any module in the package and can even work as a starter application for your own custom driver-based program. The example source is available as an exemplary demonstration and holds as no application dependency for any driver library, except for the configuration file header generated for examples that is also used for building driver source library when no different generated configuration header file is used.