Quartus II internal Error

--- Quote Start ---

Hi all,

I am making compilation for my RTL design.

At first I used Quartus II 10.0 (32-bit)

(Analysis & synthesis are OK)

The process stopped at Fitter (Place & Rount) with an ERROR "Out of memory in module quartus_fit.exe"

I was told maybe it will be fixed if I use Quartus II 10.0 (64-bit)

But when I retry it using Quartus II 10.0 (64-bit),

(Analysis & synthesis are OK)

some internal error occur at Fitter (Place & Rount)

Following is the log in a pop-up window,

*** Fatal Error: Access Violation at 0X000000003E8B34EB

Module: quartus_fit.exe

Processors in use: 2

Lock in use: 9

Stack Trace:

0x332897: VPR_QI_FACADE::vpr_qi_main + 0x177 (fitter_vpr20kmain)

0x30890: fitapi_run_vpr + 0x70 (fitter_fitapi)

0x40c2f: FITCC_EXPERT::run_vpr + 0x15f (FITTER_FITCC)

0x421d4: FITCC_EXPERT::place_and_route + 0x174 (FITTER_FITCC)

0x438b9: FITCC_EXPERT::invoke_fitter + 0x759 (FITTER_FITCC)

0x2385: ftitan_execute + 0x265 (fitter_ftitan)

0xb17d: fmain_start + 0x7cd (FITTER_FMAIN)

0xfd5b: qexe_get_tcl_sub_option + 0xefb (comp_qexe)

0x133f5: qexe_process_cmdline_arguments + 0x605 (comp_qexe)

0x13521: qexe_standard_main + 0xa1 (comp_qexe)

0x1a88: msg_exe_fini + 0xf8 (CCL_MSG)

0x1a2c: msg_exe_fini + 0x9c (CCL_MSG)

0xa2b0: operator new[] + 0x130 (ccl_mem)

0x35ff4: msg_exe_main + 0x74 (CCL_MSG)

0x1f56c: BaseThreadInitThunk + 0xc (kernel32)

0x33280: RtlUserThreadStart + 0x20 (ntdll)

End-trace

Is there anybody can help me ?

Any suggestion is welcome.

Thanks a lot.

Best Regards

Evander

--- Quote End ---

Hi,

which OS are you using and what is your target device ?

Kind regards

GPK

--- Quote Start ---

Hi,

which OS are you using and what is your target device ?

Kind regards

GPK

--- Quote End ---

Hi GPK,

The OS I am using is Windows 7 (64-bit)

and my target device is Stratix III EP3SL340F1517C3.

Thank you very much.

Evander

--- Quote Start ---

Hi GPK,

The OS I am using is Windows 7 (64-bit)

and my target device is Stratix III EP3SL340F1517C3.

Thank you very much.

Evander

--- Quote End ---

Hi,

what is the size of your physical Ram ?

Altera recommendation:

EP3SE260, EP3SL340 (32bit) 4.0 GB , (64bit) 6.0 GB

Kind regards

GPK

--- Quote Start ---

Hi,

what is the size of your physical Ram ?

Altera recommendation:

EP3SE260, EP3SL340 (32bit) 4.0 GB , (64bit) 6.0 GB

Kind regards

GPK

--- Quote End ---

Hi,

The RAM for 32-bit OS is 4G (3.24G usable)

You mean it's still not big enough for EP3SL340 ?

But as I know, the max RAM size support by 32bit OS is 3.24G.

The RAM for 64-bit OS is 4G which is less than 6.0G as you said.

So the root cause of the internal error in quartus 64-bit is still the less of RAM ?

I feel dizzy why didn't it show "out of memory" just like situation in quartus 32-bit ?

Thank you very much.

Evander

--- Quote Start ---

Hi,

The RAM for 32-bit OS is 4G (3.24G usable)

You mean it's still not big enough for EP3SL340 ?

But as I know, the max RAM size support by 32bit OS is 3.24G.

The RAM for 64-bit OS is 4G which is less than 6.0G as you said.

So the root cause of the internal error in quartus 64-bit is still the less of RAM ?

I feel dizzy why didn't it show "out of memory" just like situation in quartus 32-bit ?

Thank you very much.

Evander

--- Quote End ---

Hi,

unfortunately it is diffcult to say what the root cause for internal error of the 64bit version is. Can you try Quartus version 11.0 or 9.1 ?

After "Analysis & synthesis " you could see the device utilization. If possible try a run with a smaller target device ( with less memory requirement). If the run finished succesfully we can be sure that the problem is not design related.

Kind regards

GPK