These settings control how images are combined with your System Builder project. For example,
you can control how the EFS is aligned, what format the resulting image is, the location of
the IPL, its image offset, and whether or not the IPL is padded to a certain size or not.
- The fully qualified name of a file that is concatenated to the front of an IFS image.
Pad IPL to
- The amount of padding that is required for the IPL file you want to append to the front
of an IFS image. If you need to accommodate an IPL file, the IPL plus the padding amount
will provide the start of the IFS image.
Align file system to
- Indicates the sector size that you want to align the file system to. Use this setting if
you want to combine an EFS image. This image must be aligned to a sector size for the
hardware (NOR flash).
- A hexadecimal amount that indicates the distance (displacement) from the beginning of
the image up until the IFS image starts.
- A numerical value for the size of the ROM. To determine the amount of ROM you'll
require, you can compile the code to create a hexadecimal file of the code, and then the
size of the hexadecimal file is the size of the ROM you require.
Combined image format
- Indicates the type of image format. If you want to download to the target, the resulting
file will be copied to the type specified here.
Images to combine with
- A list of the fully-qualified file names for the IFS and EFS images. The IFS and EFS
images are appended in the order specified in this comma-separated list.
Mount unbootable IFSs?
- Indicates whether you want any specified IFS images mounted when they are unbootable.
For advanced situations, if you might have multiple IFS filesystems, and because only the
ones with a startup are bootable, you might want any secondary IFSs mounted, regardless if
they are not bootable.