12-16-2009 02:04 PM
I'm receiving this error when I try and generate a Divider with the Divider Generator 3.0. I'll post some of my log output, and attach the rest. I am stumped. I've updated to the latest 11.4 and everything.
ERROR:coreutil:576 - An error occurred while running Java. Please examine the
console or coregen log file for a specific IP related error.
For more information please search the Xilinx Answers Database for this
ERROR:coreutil - XST has returned an error: ERROR:Xst:2996 - XST patch Expired.
ERROR:coreutil:308 - If the error occurred during generation, the problem may be
due to a failure occurring in xst. Please check the xst log file - available
in the working directory.
12-17-2009 07:44 AM
12-17-2009 11:51 AM
12-17-2009 11:54 AM
12-17-2009 12:22 PM
12-18-2009 06:48 AM
I'm getting these errors from ISE/Core Generator 11.3 also. I'm trying to modify an old core, and upgrade it at the same time. First I observed ERROR:sim - Upgrade Aborted. So I did what I always do, manually capture all the significant parameters and options, start a new core, and configure it to be the same in every way possible to the old one, except for the changes I want. This gives me ERROR:coreutil - An error occurred while running Java. Also, ERROR:Xst:2996 - XST patch Expired.
I'll try to roll the clock back 20 years so I can keep track of date and time for version control. October won't work, since some of my files were actually generated then.
12-18-2009 09:28 AM
12-18-2009 12:37 PM
This worked for me on 11.3.
I thought I'd download the 11.4 upgrade at the same time, but that's taking a long time for my web browsing PC to get, and will clearly threaten the limits of my memory stick.
When I use "ERROR:Xst:2996" or "2996" in the Xilinx web page search engine box for the Answer Browser, I get:
Your search - ERROR:Xst:2996 - did not match any documents.
No pages were found containing "ERROR:Xst:2996".
When I use "ERROR:Xst:2996" in the Xilinx web page search engine box for Forum Message Search, I get:
Sorry, your search yielded no matching results.
Please revise your search query
This would explain why we cannot find answer record 33993. Any idea why words in the title and the keyword list don't get a hit from the search engine? Perhaps this topic is too new.
12-19-2009 05:16 AM
Yes, AR33993 was too new yesterday. Anyway, it's searchable now.
12-20-2009 01:53 PM
Thx for the #AR33993
It worked for me under 11.3.