Share via


Boot Arguments Library (Windows CE 5.0)

Send Feedback

The boot arguments library passes parameters from the boot loader to the kernel in a uniform way on devices that use a boot loader. It does not export any function or variable to the kernel. The boot arguments library uses encapsulated data types for each component being initialized. This enables you to maintain component separation and still be able to add components in the future without affecting existing components. For more information, see %_WINCEROOT%\Platform\Common\Src\Inc\Oal_args.h.

The boot arguments library relies on image configuration parameters to locate the shared data area. If a component has specified a configuration data type, this data type might be simply included in the NKARGS type and then configured by the boot loader.

The NKARGS type is partitioned into the OAL and the OEM sections. The OAL section contains component data for OAL components. The OEM section should only contain OEM components. NKARGS relies on a standard header, located at the top of the shared NK/BOOTLOADER memory region to validate the data. In OEMInit, the signature is validated. If the signature is invalid, it might be assumed that the NKARGS parameters are not initialized. The memory region is located by constants defined in the Image_cfg.h file.

See Also

Production-Quality OAL Components | Boot Arguments Reference

Send Feedback on this topic to the authors

Feedback FAQs

© 2006 Microsoft Corporation. All rights reserved.