We have detected your current browser version is not the latest one. Xilinx.com uses the latest web technologies to bring you the best online experience possible. Please upgrade to a Xilinx.com supported browser:Chrome, Firefox, Internet Explorer 11, Safari. Thank you!

AR# 3325

V1.5.0, V1.4.0 CORE Generator - Error: java.lang.OutOfMemoryError


Keywords: CORE Generator, OutOfMemory, out of memory, COREGen, Solaris, swap, RAM,
PDA FIR, square root, constant coefficient multiplier

Urgency: Standard

General Description:
Out of memory errors similar to the following may be issued
by CORE Generator when generating very large versions of some of
the more complex modules:

"Exception occurred during event dispatching:



In many cases, these errors may be due to the fact that
Java is being invoked by COREGEN with an option that restricts
its memory usage to a default level of 64MB in COREGEN v1.4,
or 128MB in COREGEN v1.5, which is less than what is required
to generate the module. If your machine has more memory than
this the problem may be corrected by increasing this setting.

The option that specifies the maximum amount of memory
that Java is allowed to access is "-mx", and the default
setting in the v1.4 release is 64MB (-mx64m). For some
larger functions, such as large PDA FIR filters, COREGen
requires 128MB of RAM.

To change the setting in your coregen script (UNIX) or
coregen.bat file (Windows), navigate to

<install_dir>/coregen/bin/unix (UNIX)
<install_dir>\coregen\bin\win (Windows NT or 95)

and edit the java command line in the coregen script or
coregen.bat file:

----- vvvvvvv
$JAVA/bin/java -mx64m -classpath $COREGEN/lib:$COREGEN/ip:$JAVA/lib/classes.zip xilinx.xworks.builder.Xworks $COREGEN $1

-------- vvvvvvv
%JAVA%\bin\java.exe -mx64m -classpath .;%COREGEN%\lib;%COREGEN%\ip;%JAVA%\lib\classes.zip xilinx.xworks.builder.Xworks %COREGEN% %1

In the v1.5 release, the default setting has been changed
to -mx128m to make up to 128MB of RAM available to COREGen.


Other out of memory errors in CORE Generator on Solaris may be due to
the fact that after it generates a core, COREGen cannot
release the swap space it used to generate the core until you
exit the program. This may also prevent you from using other
programs while COREGen is running.

This problem is due to the way Solaris operating systems
handle memory. There is no work-around other than to quit
CORE Generator before trying to generate the next core.
AR# 3325
Date 02/08/2001
Status Archive
Type ??????