When using the ChipScope Core Inserter flow within the ISE Design Suite Project Navigator or Standalone, the Core Inserter freezes after going to ILA parameters page.
And, messages similar to the following are printed in the ISE Console window or in the shell/terminal.
"Exception in thread "AWT-EventQueue-0" java.lang.OutOfMemoryError: GC overhead limit exceeded
at java.lang.String.toUpperCase(Unknown Source)
at java.lang.String.toUpperCase(Unknown Source)
at com.xilinx.chipscope.inserter.DesignNodeBase.<init>(DesignNodeBase.java:37)
at com.xilinx.chipscope.inserter.DesignSignalNode.<init>(DesignSignalNode.java:24)
at com.xilinx.chipscope.inserter.DesignComponentNode.loadChildren(DesignComponentNode.java:88)
......"
"Exception in thread "AWT-EventQueue-0" java.lang.OutOfMemoryError: Java heap space
at java.lang.String.toUpperCase(Unknown Source)
Exception in thread "Timer-0" java.lang.OutOfMemoryError: Java heap space
at java.lang.StringBuilder.toString(Unknown Source)
at com.xilinx.chipscope.inserter.ILAModelBase.getCoregenParams(ILAModelBase.java:963)
at com.xilinx.chipscope.inserter.ILAProModel.getCoregenParams(ILAProModel.java:197)
......"
How can I resolve this problem?
This error can occur when the ChipScope Inserter tool workswith large netlists.Some large netlists cause the tool to run out of memory and this error can occur.Towork aroundthis problem, set the following environment variable:
XIL_CS_JVMARGS
Set the value for this environment variable to -Xmx1024M. This increases the maximum amount of memory dedicated to the inserter tool to 1024 MB. In Linux, you can set this environment variable by typing the following command:
setenv XIL_CS_JVMARGS "-Xmx1024M"
For Windows, set the environment variable by right clicking on "My Computer", click on "Advanced System settings" and then click on the "Environment Variables..." button. You can now create a new variable called "XIL_CS_JVMARGS" and set the value to "-Xmx1024M".
Remember that after setting the environment variable, you need to close all open Xilinx ISE windows and reopen the tools for the new environment variables to be enabled.
Alternatively, use the PlanAhead software flow to insert the ChipScope Cores into your design, which also works around this issue because the PlanAhead tool can handle large netlists.