You generated a flash programming file. As part of this process, you specified, or the Software Builder generated, a Hexadecimal (Intel-Format) File (.hex) that contains initialization data for the memory region at the specified address. Also, when editing the System Build Descriptor File (.sbd) for the current project, you mapped the memory region as the Expansion Bus Interface zero (EBI0) memory region for the current ARM-based Excalibur device.

The makeprogfile utility that you or the Software Builder is using generated the boot data file necessary for generating a flash programming file. However, if the current ARM-based Excalibur device has a read-only EBI0 memory region, the makeprogfile utility does not use the initialization data for the EBI0 memory region when generating the boot data file.

If the current ARM-based Excalibur device does not have a read-only EBI0 memory region, or you do not want the makeprogfile utility to use the initialization data for the EBI0 memory region, no action is required. Otherwise, perform one of the following actions:

• Edit the SBD to map the EBI0 memory region to a location for which the HEX File does not contain initialization data.

• If you are using the Software Builder to generate the flash programming file, specify linker settings to make sure the Software Builder generates a HEX File that does not contain initialization data for the EBI0 memory region.

• If you specified the file, specify a different HEX File that does not contain initialization data for the EBI0 memory region. If necessary, generate a new HEX File using the Software Builder or a code converter, and use this new HEX File when generating the flash programming file.