Forum Discussion

Altera_Forum's avatar
Altera_Forum
Icon for Honored Contributor rankHonored Contributor
9 years ago

Quartus Prime 16.0 stops compiling before fitter runs

So, I made the choice (mistake?) of upgrading my Quartus Prime Pro version 15.1 to Quartus Prime Pro version 16.0.

I ran the IP updater on my project that I am upgrading from 15.1 to 16.0 and everything seemed to update ok.

The problem is that now, whenever I run the compilation, the compiler completes the first two steps in the flow (IP Generation and Analysis & Synthesis) but then stops. It never runs the Fitter. When I specifically tell it to run the fitter, it sits at 0% for a few minutes then stops without generating any messages.

Has anyone else made the leap to 16.0 yet?

Why won't it finish compiling?

g

6 Replies

  • Altera_Forum's avatar
    Altera_Forum
    Icon for Honored Contributor rankHonored Contributor
    9 years ago

    I should mention that I am working with an Arria 10 SOC design.

  • Altera_Forum's avatar
    Altera_Forum
    Icon for Honored Contributor rankHonored Contributor
    9 years ago

    Did you pay attention to (and do anything about) any warnings that came up as part of the IP upgrade process? Frequently, following a major new Quartus release, minor changes are made to some IP blocks that require you to do something to your design to accommodate these changes. There will have been warnings drawing your attention to this.

    Why move to Q16? Are you hoping it will give you something Q15.1 didn't? As a rule of thumb, hold off upgrading to a major new release until the first service pack is available (unless you need it for the particular device you're using). Major new releases frequently 'feature' unwanted features (bugs).

    Cheers,

    Alex
  • Altera_Forum's avatar
    Altera_Forum
    Icon for Honored Contributor rankHonored Contributor
    9 years ago

    Quartus Prime 16.0 is an important update, especially for Arria 10. We just yesterday finally got a PCIe gen3 root port running under 16.0. And although I don't need it yet, 16.0 is the first release that officially supports Windows 10.

    g - We're running fine with 16.0 standard. We have no intention of upgrading to Pro. My guess for your problem would be a licensing issue. I did some testing a couple of months ago with QP Pro and the Blueprint tool would silently fail when I tried to open it. No warning messages of any kind, but it left a process running in windows. Ended up being a licensing issue. The pro version is clearly very different from standard under the covers.
  • Altera_Forum's avatar
    Altera_Forum
    Icon for Honored Contributor rankHonored Contributor
    9 years ago

    Thanks, it does appear to be a licensing issue. The compile just fails silently without any indication of what is wrong even with a simple program of just a few flip-flops (no IP). I am starting a new project using the Arria 10 with PCIe which is why I felt the timing to make the switch to 16.0 was prudent. Thanks for your help.

  • Altera_Forum's avatar
    Altera_Forum
    Icon for Honored Contributor rankHonored Contributor
    9 years ago

    I have exactly the same problem along with some other issues that popped up when I moved from 15.1.1 to 16.0.0... Analysis & Synthesis (and Analysis & Elaboration) run fine but after that the compile just stops... If I try to force a Fitter run, the spinner will spin for a minute or two (without incrementing the clock, bottom right) and then just stop.. No messages, not nothing...

    I have sent an email to my FAE's to see if it is possibly a licensing issue...

    I'm running an Arria 10AX048E3F29E2SG with two 32 bit banks of DDR3 and a couple of transceivers...

    The Quartus Prime experience for me so far has been a beating from the very start... Never could get a pinout unless I used the BluePrint tool...
  • Altera_Forum's avatar
    Altera_Forum
    Icon for Honored Contributor rankHonored Contributor
    9 years ago

    I got this response from tech support:

    "When the software team tested this particular error messaging, they only tested it via command line which does show that Quartus is needing a valid license. My team was able to confirm that that message does not appear when using the GUI. We have filed an internal Fogbugz case 371128. We will get this fixed."