Quartus

Expansion Bus Interface zero memory region at address [0x<number>, 0x<number>] does not have enough space for 0x<number> bytes of boot data generated


CAUSE:

You attempted to generate a flash programming file. As part of this process, the makeprogfile utility that you or the Software Builder is using generated the specified amount of boot data from the initialization data in one or more Hexadecimal (Intel-Format) Files (.hex). However, the amount of boot data generated does not fit into the Expansion Bus Interface zero (EBI0) memory region at the specified address, which you mapped by editing the System Build Descriptor File (.sbd) for the current project.

The makeprogfile utility placed all the boot data it generated in a boot data file. You can use this boot data file to generate a flash programming file; however, you may experience problems with the boot data and the EBI0 memory region when you try to use the flash programming file to configure an ARM-based Excalibur device.

ACTION:

Perform one of the following actions:

  • Edit the SBD File to map the EBI0 memory region so it has enough space for the boot data.

  • Specify HEX Files for the makeprogfile utility to use to generate less boot data for the EBI0 memory region. If necessary, generate new HEX Files using the Software Builder or a code converter, and use these new HEX Files when generating the flash programming file.

See also:

Alternative Procedure for Generating a Flash Programming File
Generating a Flash Programming File
Generating Binary Files, Hexadecimal (Intel-Format) Files, Library Files & Motorola S-Record Files
Overview: Using the MegaWizard Plug-In Manager

- PLDWorld -

 

Created by chm2web html help conversion utility.