How to Decrease Run-Time Image Size on a CEPC
Other versions of this page are also available for the following:
.gif "A hyphen indicates that the information in this topic is not relevant for this platform, or that the platform does not support the API that is listed.")
.gif "A checkmark indicates that the information in this topic is relevant for this platform, and that any API listed is also supported on this platform.")
8/27/2008
When you design and configure your run-time image, each module, component, and feature that you add or remove affects the size of the run-time image.
To meet the specific memory requirements of the target device, you can decrease the run-time image size by removing nonessential modules, compressing modules, and moving modules to different parts of the file system.
Hardware and Software Assumptions
- You have set up a Windows Embedded CE PC-based platform (CEPC).
For more information, see How to Set Up a CEPC. - You are familiar with how to use the IDE to modify your OS design.
For more information, see Catalog Overview. - You are familiar with how to the IDE to modify run-time image settings.
For more information, see OS Design Property Pages Dialog Box. - You are familiar with setting and clearing environment variables.
For more information, see Setting or Clearing an Environment Variable (Visual Studio). - You are familiar with editing, commenting, and correctly backing up the batch (.bat) files that determine what is included in your run-time image.
For more information about how to edit and commenting .bat files, see Command Processor Commands and see REM (Command Processor). - You are familiar with editing, commenting, and correctly backing up binary image builder (.bib) files.
To add a comment to a .bib file, use the ';' delimiter. For more information, see Binary Image Builder File.
Steps
| Step | Topic |
|---|---|
1. Configure and build your run-time image. The method for configuring your initial run-time image varies depending on the memory requirements of your target device. The following list shows different methods for configuring your initial run-time image:
|
|
2. After the build is complete, view your run-time image and check its size. Typically, the run-time image is named Nk.bin. You can check the run-time image size by doing one of the following:
|
Not applicable |
3. Create a new configuration and set it to the active configuration.
.gif "Cc440228.note(en-US,WinEmbedded.60).gif") Note:
Creating a new configuration does not automatically change the active configuration to the new configuration.
|
|
4. Remove nonessential features, modules, and components from your OS design by clearing the check box next to each nonessential feature, module, or component in the Catalog Items View. Note:
You might be unable to remove certain features, modules, or components because of dependencies on other features. To view dependencies, from Solution Explorer window in the IDE, choose Catalog Items View. Select a feature for which you want to check the dependencies, right-click it, and then choose Show Dependencies.
|
Not applicable |
5. If you do not need the VMINI Ethernet sharing library, remove support for it by setting the environment variables KERNELNOSHAREETH and the BSP_NOSHAREETH to 1. The VMINI Ethernet sharing library enables product, KITL, and debug Ethernet to run over a single Ethernet connection. |
|
6. If it is suitable for your target device, do not localize the run-time image. By not localizing your run-time image, you can decrease the run-time image size.
|
Not applicable |
7. Modify the .bib files for the run-time image by moving the entries for seldom-used, end-user modules to the FILES section of the .bib files. The module entries listed in the FILES section of a .bib file are compressed and take longer to load. This decreases your run-time image size, but might affect RAM usage and performance. Executable (.exe) files in the FILES section might take longer to load and might run slower.
|
|
8. Configure the Premakeimg.bat and MyPlatform_bib.cfg files to compress specified modules. |
|
9. Rebuild the run-time image to bring it up-to-date and save the changes that you made. |
|
10. After the build is complete, view the run-time image size again and compare it to the original run-time image to verify that the size decreased. You can check the run-time image size by doing one of the following:
If you want to verify that any file attributes that were assigned in step 8 persisted through the run-time image build and download, use the File Viewer. |
Not applicable |