Quartus

Hexadecimal (Intel-Format) File(s) do not specify entry point--entry point 0x<number> is being used


CAUSE:

You generated a flash programming file or or one or more passive programming files. As part of this process, you specified, or the Software Builder automatically generated, one or more Hexadecimal (Intel-Format) Files (.hex) that are necessary for generating the flash or passive programming files. However, the HEX File(s) do not specify an entry point. As a result, the Compiler, or the makeprogfile utility that you or the Software Builder is using, is using the specified entry point.

ACTION: If you want the Compiler or makeprogfile utility to use the default entry point, no action is required. Otherwise, specify different HEX File(s) that specify an entry point. If necessary, generate new HEX Files using the Software Builder or a code converter, and use these new HEX Files when generating the flash or passive programming files.

See also:

Alternative Procedure for Generating a Flash Programming File
Alternative Procedure for Generating Passive Programming Files
Generating a Flash Programming File
Generating Optional Programming Files for Programmer Object Files
Generating Optional Programming Files for SRAM Object Files
Generating Passive Programming Files

- PLDWorld -

 

Created by chm2web html help conversion utility.