AUTOSIZE (Windows CE 5.0)
When run-time images are located entirely in RAM, this configuration option allows all RAM not occupied by the run-time image itself to be used as system RAM and Object Store RAM without modifying the memory parameters set in the BIB files.
For example, if AUTOSIZE is not set and a 5 MB run-time image is installed on a target device with 20 MB of RAM, this could result in an assignment of 10 MB for the run-time image itself and 10 MB for system RAM. However, this means that 5 MB of RAM on the device remains unused.
In this situation, AUTOSIZE can be set to take advantage of the unused RAM. When it is set, Romimage treats all available sources of RAM on the device as though they are a single source of RAM. So after the run-time image in the example occupies 5 MB of the available RAM on the device, the remaining 15 MB can be pooled and used as system RAM and Object Store RAM.
This configuration option can also be used to take extra memory from system RAM and reassign it to run-time image RAM.
When building single region XIP images, use AUTOSIZE to control whether or not to move the RAM start address. This is typically only used when loading a run-time image entirely into RAM.
When building multi-region XIP images, use AUTOSIZE to globally enable or disable all xxx_autosize options.
To enable all multi-XIP AUTOSIZE flags, this configuration option must be set.
This configuration option uses the following syntax:
AUTOSIZE = OFF | ON
Parameters
- OFF
By default, Romimage.exe does not combine unused RAM. - ON
Romimage.exe combines the system RAM and run-time image memory regions into one region, with the run-time image filling this region from the lowest address to the highest. The RAM parameters in the table of contents are modified to allow the system to use all remaining RAM.
See Also
CONFIG Section | Binary Image Builder File
Last updated on Thursday, February 02, 2006
Send Feedback on this topic to the authors