Forum Discussion

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

Strange, ambiguous Fitter Error

Hi,

I am fairly new to Quartus and was working on a MIPS processor for school, when all of the sudden I get this error when I compile:

Info: Running Quartus II Fitter

Info: Command: quartus_fit --read_settings_files=off --write_settings_files=off test -c test

error: cannot find device that meets compiler settings specifications

Error: Quartus II Fitter was unsuccessful. 1 error, 0 warnings

Error: Peak virtual memory: 191 megabytes

Error: Processing ended: Sun May 02 05:44:00 2010

Error: Elapsed time: 00:00:01

Error: Total CPU time (on all processors): 00:00:00

Error: Quartus II Full Compilation was unsuccessful. 3 errors, 128 warnings

I noticed that the error went away once I removed a recently added 32-bit output pin.

But if I add another pin and make it 32 bits (e.g. testpin[31..0]), I get the same error again. If I make the new pin 1 bit instead, it compiles successfully.

Does anyone know why this would happen? Is there a limit on the number of 32-bit pins you can have or something?

Thanks in advance.

2 Replies

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

    Interesting. I removed some extra components I made that had several input and output pins, and now it compiles.

    Apparently there is a limit on the number of pins.. I guess Quartus tests that the power consumption for the device isn't exceeded.. or something to that effect?

    I'm only using Quartus for logic design and didn't know about some of this other stuff.
  • Altera_Forum's avatar
    Altera_Forum
    Icon for Honored Contributor rankHonored Contributor
    15 years ago

    --- Quote Start ---

    I guess Quartus tests that the power consumption for the device isn't exceeded

    --- Quote End ---

    Surely not. You simply have specified more port pins than any available device of the selected FPGA family has. You should easily see it when you check the compiler report.