DEBUGGING THE OS DESIGN
After compilation, a Compact 7 OS design contains a large collection of files from different OS, programming support library, device driver, networking, media Codec, file system, and other application components.
It’s common for a typical OS design project to cumulate in thousands of files that occupy well over 1 GB of storage during the build process to generate an OS run-time image. Without understanding how these files come together to form the final OS run-time image, searching for problems is often like looking for a needle in a haystack.
As part of the OS design development process, you are expected to carry out debugging tasks. Following are some examples:
- The OS design build process ended with an error and failed to generate an OS run-time image. You need to figure out what is causing the build error.
- The OS design build process completed successfully and generated an OS run-time image. However, the OS run-time image cannot boot. You need to figure out what is preventing the OS run-time image from completing the boot process.
- The OS design build process completed successfully and generated an OS run-time image. However, some of the features configured as part of the OS design cannot function. You need to figure out why these configured features failed to function as intended.
- The OS design build process completed successfully and generated an OS run-time image and included all the required files. However, the application configured to launch during ...
Get Professional Windows® Embedded Compact 7 now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.