- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi,
I am trying to run minimal flow for the hello sample:
$ cd $OPAE_PLATFORM_ROOT/hw/samples/hello_afu
$ afu_synth_setup --source hw/rtl/filelist.txt build_synth
$ cd build_synth
$ $OPAE_PLATFORM_ROOT/bin/run.sh
from:
to generate an AFU.
Synthesis fails with the following error. I googled it, but nothing comes up.
Error (19877): Partial reconfiguration no longer supports synthesis revisions
Error: Flow failed:
Error: Quartus Prime Synthesis was unsuccessful. 2 errors, 9 warnings
Error: Peak virtual memory: 1279 megabytes
Error: Processing ended: Wed Oct 10 14:45:57 2018
Error: Elapsed time: 00:00:08
Error (23035): Tcl error: ERROR: Error(s) found while running an executable. See report file(s) for error message(s). Message log indicates which executable was run last.
while executing
"execute_module -dont_export_assignments -tool syn"
(procedure "synthesize_persona_impl" line 14)
invoked from within
"synthesize_persona_impl $synth_rev"
(procedure "compile_pr_revision" line 18)
invoked from within
"compile_pr_revision $options(impl)"
(procedure "main" line 110)
invoked from within
"main"
invoked from within
"if {($::quartus(nameofexecutable) == "quartus") || ($::quartus(nameofexecutable) == "quartus_pro") || ($::quartus(nameofexecutable) == "qpro")} {
#..."
(file "./a10_partial_reconfig/flow.tcl" line 1039)
Do you know what may be causing it? Thanks in advance.
1 Solution
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Yes, thank you. Downgrading to 17.1 and installing the patches provided with the acceleration stack solved the error.
Link Copied
2 Replies
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi,
From my understanding, you are using Quartus 18.0 or later version which is causing the issue. I would recommend you to use Quartus 17.1 Pro edition in order to compile your design.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Yes, thank you. Downgrading to 17.1 and installing the patches provided with the acceleration stack solved the error.
Reply
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page