OAL Code Overview (Compact 7)
3/12/2014
In this section, for ease of discussion, we divide the OEM adaptation layer (OAL) code into the following categories: startup, memory layout, real-time clock (RTC), cache, timer, power management, serial debugging, interrupts, and module inclusion. Each category of code is described separately.
Important
Not all functions, configurations, or other supporting files that Windows Embedded Compact requires are listed in this guide. If a function is listed, you may still have to customize the code to your particular implementation, and you will often need to explore lower-level methods that are called by the functions. For a detailed description of each function and configuration file, see Board Support Package (BSP).
Note
The OAL library is typically named oal.lib. However, you may name it anything you like.
In This Section
- Startup (OAL)
Provides the location of the OAL startup code, lists the main OAL startup functions, and includes a figure that shows the OAL function calls in the startup process.
- Memory Layout (OAL)
Specifies the configuration file that you need to modify to define the memory layout of the run-time image.
- Real-Time Clock (OAL)
Provides the location of the RTC code and lists the main functions.
- Cache (OAL)
Provides the location of the cache code and lists the main functions.
- Timer (OAL)
Provides the location of the timer code and lists the main functions.
- Power Management (OAL)
Provides the location of the power management code, lists the main functions, and includes a figure that shows the function calls that suspend and wake the CPU.
- Serial Debugging (OAL)
Points you to the boot loader serial debugging code, which you can often use with minor modifications for the OAL.
- Interrupts (OAL)
Provides the location of the interrupt code and lists the main functions.
- Module Inclusion (OAL)
Specifies the configuration files that tell the build system which modules and files to include in the run-time image.