Programmable Devices
CPLDs, FPGAs, SoC FPGAs, Configuration, and Transceivers
20689 Discussions

Quartus Build Crash - it used to compile

Altera_Forum
Honored Contributor II
1,130 Views

I have a Cyclone IV E design that used to build I was using signaltap and built a couple of debug load and now it's no longer able to compile.I removed the .stp and it still crashes, I removed and reinstalled the Quartus software - still crashes. Problem Details 

Error: 

 

*** Fatal Error: Access Violation at 0X000007FEB53FC717 

Module: quartus_map.exe 

Stack Trace: 

0x7c716: sgn_source_file_processing + 0x68596 (synth_sgn) 

0x7363b: sgn_source_file_processing + 0x5f4bb (synth_sgn) 

0x7291a: sgn_source_file_processing + 0x5e79a (synth_sgn) 

0x77a83: sgn_source_file_processing + 0x63903 (synth_sgn) 

0x7bc2d: sgn_source_file_processing + 0x67aad (synth_sgn) 

0x793bd: sgn_source_file_processing + 0x6523d (synth_sgn) 

0x87da2: sgn_source_file_processing + 0x73c22 (synth_sgn) 

0xbdf6d: sgn_create_qsys_generation_report + 0x6c4d (synth_sgn) 

0xc8262: sgn_create_qsys_generation_report + 0x10f42 (synth_sgn) 

0xc340b: sgn_create_qsys_generation_report + 0xc0eb (synth_sgn) 

0x136b4: sgn_qic_full + 0x1b4 (synth_sgn) 

 

 

 

 

 

 

0x1252c: qexe_apply_ini_vars + 0x245c (comp_qexe) 

0x17872: qexe_process_cmdline_arguments + 0x2762 (comp_qexe) 

0x18601: qexe_standard_main + 0xc1 (comp_qexe) 

 

 

0xcbe8: msg_initialize_out_of_memory_handler + 0x378 (CCL_MSG) 

0xe31c: msg_set_stack_size + 0x7c (CCL_MSG) 

0x4c0c: mem_malloc_wrapper + 0x18c (ccl_mem) 

0xc831: msg_exe_main + 0xa1 (CCL_MSG) 

 

 

0x159cc: BaseThreadInitThunk + 0xc (kernel32) 

0x5383c: RtlUserThreadStart + 0x1c (ntdll) 

 

 

End-trace 

 

 

Executable: quartus_map 

Comment: 

None 

 

System Information 

Platform: windows64 

OS name: Windows 7 

OS version: 6.1 

 

Quartus II Information 

Address bits: 64 

Version: 15.0.0 

Build: 145 

Edition: Full Version
0 Kudos
1 Reply
Altera_Forum
Honored Contributor II
410 Views

Have you tried trashing the db and incremental_db folders? Something may be corrupted in there.

0 Kudos
Reply