Quartus

Initialization data in Hexadecimal (Intel-Format) File for memory region at address [0x<number>, 0x<number>] cannot be used because region is part of programmable logic device memory region of ARM-based Excalibur device


CAUSE: You generated one or more passive programming files. 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. However, when editing the System Build Descriptor File (.sbd) for the current project, you mapped the memory region as part of the programmable logic device (PLD) memory region of the current ARM-based Excalibur device. You cannot load initialization data to a PLD memory region, and therefore the Compiler, or the makeprogfile utility that you or the Software Builder is using, cannot use the initialization data when generating the passive programming files.
ACTION:

Perform one of the following actions:

  • Map the PLD memory region in the SBD File to a location for which the HEX File does not contain initialization data.

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

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

See also:

Alternative Procedure for Generating Passive Programming Files
Generating Optional Programming Files for Programmer Object Files
Generating Optional Programming Files for SRAM Object Files
Generating Passive Programming Files
Overview: Using the MegaWizard Plug-In Manager
Specifying Linker Settings

- PLDWorld -

 

Created by chm2web html help conversion utility.