Forum Discussion

corestar's avatar
corestar
Icon for Contributor rankContributor
2 months ago
Solved

Fitter stalls on "Advanced Physical Optimization" on Windows 10

We are reluctantly moving from Windows 7 to Windows 10. I have a project that compiles just fine on a Windows 7 Pro machine with an Intel Core i7-3930K CPU using Quartus 19.1 Lite.

I copied the project to a new Windows 10 Pro machine with a Ryzen Threadripper PRO 3995WX processor. Also copied the Quartus 19.1 install files and it installed with no problem.

But when I try to compile, it stalls during fitting at a line:

      Info (14951): The Fitter is using Advanced Physical Optimization.

On Windows 7, the whole compile takes 11 minutes. I let it run for two hours on Windows 10 and it just sits there. 

I limited the number of parallel cores to 6. That did not help. 

I upgraded to Quartus 24.1 Lite (the last one to support Windows 10) and that did not help.

If I disable "Advanced Physical Optimization" in the Advanced Fitter options, the compile completes. 

But this is bizarre. Why would the exact same project with the exact same version of Quartus compile fine on Windows 7 but not on Windows 10?

 

 

27 Replies

  • FvM's avatar
    FvM
    Icon for Super Contributor rankSuper Contributor

    Hi,

    does your PC provide sufficient RAM for utilized FPGA according to Quartus release notes? Otherwise different OS memory usage may make the difference.

    • corestar's avatar
      corestar
      Icon for Contributor rankContributor

      Hello,

      New system has 512 GB and 64 cores :-) . Old system 32GB and 6 cores. 

      I was trying to figure out what could possibly be different since project and Quartus are identical. The "use all available cores" options seemed like a possibility, but I limited it to 6 (also tried 1).

      • corestar's avatar
        corestar
        Icon for Contributor rankContributor

        When I say Quartus is identical, I had downloaded the full 5.8GB install on Windows 7:

            Quartus-lite-19.1.0.670-windows.tar    5,897, 490 KB

        and used it to install on both Windows 7 and Windows 10. The project itself was also just copied. Other than the old computer was an Intel processor and the new one is AMD Ryzen, seems like they should be the same. And other than this one option, it appears to work fine. 

  • sstrell's avatar
    sstrell
    Icon for Super Contributor rankSuper Contributor

    What's your targeted device and how full is the device with this design?

    • corestar's avatar
      corestar
      Icon for Contributor rankContributor

      Hello sstrell​ ,

      Below is the fitter report from the WIndows 7 machine. The logic usage is not very high.

       

       

    • ShengN_altera's avatar
      ShengN_altera
      Icon for Super Contributor rankSuper Contributor

      I had checked the previous internal message based on the KDB link. This is not a bug but configuration problem so wouldn't be fixed. Please follow the workaround stated in the KDB

      • corestar's avatar
        corestar
        Icon for Contributor rankContributor

        I'm afraid, as I mentioned, I already tried limiting the number of processors and it does not work.

        I'm sure alot of people use Quartus on Windows 10 Pro, but perhaps not so many have a 64 core processor. I assume it must have something to do with that. But it seems to me if Quartus cannot handle more than a certain number of processors, it should automatically limit itself as opposed to requiring the user to do so. 

  • I had another engineer try to compile this on his machine. It is the exact same version of Windows 10 Pro (10.0.19045 Build 19045), but has an AMD Ryzen 7 5800X 8-Core CPU. It compiles fine on his computer with Physical Optimization enabled and parallel compilation set to all available processors.

    So it does not appear to be a Windows 10 problem. Apparently, Quartus cannot handle a processor with more than a certain number of cores.