Forum Discussion

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

Can't fit design in device after upgrade from 13.0SP1 to 13.1

Hi,

I have a project for the MAX V "5M240ZM100C5" CPLD, almost at the max capacity of the device.

Previously I was using 32bit PC, Windows 7 and Quartus II 13.0 SP1 Web Edition, and was able to successfully compile and fit the design on the device.

Here is a piece of the log from the Fitter:


Info: Running Quartus II 32-bit Fitter    Info: Version 13.0.1 Build 232 06/12/2013 Service Pack 1 SJ Web Edition
...
Info: Command: quartus_fit --read_settings_files=off --write_settings_files=off InterfaceLogic -c InterfaceLogic
Info: qfit2_default_script.tcl version:# 1
...
Info (171003): Fitter is performing an Auto Fit compilation, which may decrease Fitter effort to reduce compilation time
...
Info (332144): No user constrained base clocks found in the design
Info (332128): Timing requirements not specified -- optimizing circuit to achieve the following default global requirements
    Info (332127): Assuming a default timing requirement
Info (332111): Found 5 clocks
...
Info (186079): Completed User Assigned Global Signals Promotion Operation
...
Info (186079): Completed Auto Global Promotion Operation
Info (176234): Starting register packing
Info (186391): Fitter is using Normal packing mode for logic elements with Auto setting for Auto Packed Registers logic option
Info (186468): Started processing fast register assignments
Info (186469): Finished processing fast register assignments
Info (176235): Finished register packing
Info (171121): Fitter preparation operations ending: elapsed time is 00:00:01
Info (170189): Fitter placement preparation operations beginning
Info (170190): Fitter placement preparation operations ending: elapsed time is 00:00:00
Info (11888): Total time spent on timing analysis during the Fitter is 0.02 seconds.
Info (170216): Fitter cannot place all nodes on current device -- Fitter will automatically make another fitting attempt and tightly pack logic elements
Info (176234): Starting register packing
Info (186391): Fitter is using Minimize Area packing mode for logic elements with Auto setting for Auto Packed Registers logic option
Info (186468): Started processing fast register assignments
Info (186469): Finished processing fast register assignments
Info (176235): Finished register packing
Info (171121): Fitter preparation operations ending: elapsed time is 00:00:00
Info (170189): Fitter placement preparation operations beginning
Info (170190): Fitter placement preparation operations ending: elapsed time is 00:00:00
Info (11888): Total time spent on timing analysis during the Fitter is 0.02 seconds.
Info (170216): Fitter cannot place all nodes on current device -- Fitter will automatically make another fitting attempt and tightly pack logic elements
Info (176234): Starting register packing
Info (186391): Fitter is using Minimize Area with Chains packing mode for logic elements with Auto setting for Auto Packed Registers logic option
Info (186468): Started processing fast register assignments
Info (186469): Finished processing fast register assignments
Info (176235): Finished register packing
Info (171121): Fitter preparation operations ending: elapsed time is 00:00:01
Info (170189): Fitter placement preparation operations beginning
Info (170190): Fitter placement preparation operations ending: elapsed time is 00:00:00
Info (170191): Fitter placement operations beginning
Info (170137): Fitter placement was successful
Info (170192): Fitter placement operations ending: elapsed time is 00:00:01
Info (170193): Fitter routing operations beginning
Info (170195): Router estimated average interconnect usage is 28% of the available device resources
    Info (170196): Router estimated peak interconnect usage is 28% of the available device resources in the region that extends from location X0_Y0 to location X8_Y5
Info (170194): Fitter routing operations ending: elapsed time is 00:00:01
Info (170202): The Fitter performed an Auto Fit compilation.  No optimizations were skipped because the design's timing and routability requirements required full optimization.
Info (11888): Total time spent on timing analysis during the Fitter is 0.55 seconds.
Info (11218): Fitter post-fit operations ending: elapsed time is 00:00:00
...
Info: Quartus II 32-bit Fitter was successful. 0 errors, 3 warnings

On the report I have a total of logic elements of 150 / 160 ( 94 % ).

Now I bought a new PC i7 64bit, Windows 8.1 64bit and installed the Quartus II 13.1 Web Edition.

And now the compilation fails at the Fitter, for the log it seems that no optimization is atempted:


Info: Running Quartus II 64-Bit Fitter
    Info: Version 13.1.0 Build 162 10/23/2013 SJ Web Edition
...
Info: Command: quartus_fit --read_settings_files=off --write_settings_files=off InterfaceLogic -c InterfaceLogic
Info: qfit2_default_script.tcl version:# 1
...
Info (171003): Fitter is performing an Auto Fit compilation, which may decrease Fitter effort to reduce compilation time
...
Info (332144): No user constrained base clocks found in the design
Info (332128): Timing requirements not specified -- optimizing circuit to achieve the following default global requirements
    Info (332127): Assuming a default timing requirement
Info (332111): Found 5 clocks
...
Info (186079): Completed User Assigned Global Signals Promotion Operation
...
Info (186079): Completed Auto Global Promotion Operation
Info (176234): Starting register packing
Info (186468): Started processing fast register assignments
Info (186469): Finished processing fast register assignments
Info (176235): Finished register packing
Info (171121): Fitter preparation operations ending: elapsed time is 00:00:01
Info (170189): Fitter placement preparation operations beginning
Error (170011): Design contains 178 blocks of type logic cell.  However, the device contains only 160 blocks.
Info (170190): Fitter placement preparation operations ending: elapsed time is 00:00:00

So I did some testing to find out if I can manage to solve this issue, I checked the settings and it seemed to be identical on both setups.

Running the 32bit of 13.1 also got the same issue.

Then I tried downloading the version 13.0 SP1 Web Edition again for the new PC, and successfully fitted the design.

Did this happened to someone?

Is this situation normal, due to new license limitations or something, or do I need to change any settings in the software?

Thank you

15 Replies

  • Altera_Forum's avatar
    Altera_Forum
    Icon for Honored Contributor rankHonored Contributor

    --- Quote Start ---

    Hi!

    I encounter a problem, namely Fitter was unsuccessful

    Following picture is sub message from Compilation report of Quartus

    Can you give me a way to solve this problem/

    Thank you so much!

    --- Quote End ---

    That's an unusual error message. Can you please provide the following information:

    • What device are you using?

    • What version of Quartus are you using?

    • Are you using Incremental Compilation?

    • What is the routing congestion in that region of the chip? (Refer to the Area and Timing Closure chapter of the Quartus Handbook

    • How many global signals does your design have? (Refer to the Global Signals panel of the Fit report)

  • Altera_Forum's avatar
    Altera_Forum
    Icon for Honored Contributor rankHonored Contributor

    --- Quote Start ---

    That's an unusual error message. Can you please provide the following information:

    • What device are you using?

    • What version of Quartus are you using?

    • Are you using Incremental Compilation?

    • What is the routing congestion in that region of the chip? (Refer to the Area and Timing Closure chapter of the Quartus Handbook

    • How many global signals does your design have? (Refer to the Global Signals panel of the Fit report)

    --- Quote End ---

    Dear aludwin!

    Thank you for your reply!

    I will offer several information that you need

    - My device is 5CSXFC6D6F31C8ES cyclone V

    - Quartus 13.0sp1

    - I don't use incremental compilation

    - Following picture that I open tab "Global and other fast signal in Fit Report

    http://www.alteraforum.com/forum/attachment.php?attachmentid=9717&stc=1

    I still don't find the way to resolve this problem.

    Thank you for your help!

    Best Regard,
  • Altera_Forum's avatar
    Altera_Forum
    Icon for Honored Contributor rankHonored Contributor

    --- Quote Start ---

    Dear aludwin!

    I still don't find the way to resolve this problem.

    --- Quote End ---

    Weird, this should have been caught earlier in the flow. I've asked around internally but I'm not sure if I'll be able to get an answer.

    Try demoting some of the signals from being clocks to using local routing - for example, those altera_reset_synchronizer_int_chain_out signals have fairly low fanout, and one of them is causing your problem anyway. Use the "GLOBAL_SIGNAL" assignment in your QSF to disable it. However, if that's actually being used as a reset signal, watch your recovery/removal slacks in the timing report.

    Are all the problems in Altera IP or Altera-generated HDL?
  • Altera_Forum's avatar
    Altera_Forum
    Icon for Honored Contributor rankHonored Contributor

    Hi & Good Day!

    Dear all,

    Info (176234): Starting register packing

    Info (186391): Fitter is using Minimize Area with Chains packing mode for logic elements with Auto setting for Auto Packed Registers logic option

    May I know, is it this statement is available for Quartus II 9.0 SP2 Web Edition?

    I'm having problem with my Logic Elements (Error: Can't fit design in device)

    I need 1348 Logic Elements by using Device: EPF6016ATI144-3 / EPF6016TI144-3, but this device only be able to support 1320 number of Logic Elements.

    I really need to use EPF6016TI144-3 device.

    Thanks in advance.
  • Altera_Forum's avatar
    Altera_Forum
    Icon for Honored Contributor rankHonored Contributor

    --- Quote Start ---

    I need 1348 Logic Elements by using Device: EPF6016ATI144-3 / EPF6016TI144-3, but this device only be able to support 1320 number of Logic Elements.

    --- Quote End ---

    None of the changes I was talking about were in 9.0. You may simply have to make your design a bit smaller.