Programmable Devices
CPLDs, FPGAs, SoC FPGAs, Configuration, and Transceivers
Announcements
Need Forum Guidance? Click here

Search our FPGA Knowledge Articles here.

MAX 10 ADC

Devi_Puthra
Beginner
261 Views

Following exceptional error observed when ADC core is instantiated in the quartus prime device 

Problem Details
Error:
*** Fatal Error: Access Violation at 0X00007FFE18DFE84C
Module: quartus_fit.exe
Stack Trace:
    0x3e84b: DEV_PKG_INFO_BODY::get_pin_string_data + 0xeb (DDB_DEV)
   0x15f3c3: FIOMGR_STRATIXIII_DYNAMICTERMINATIONCONTROL_LEGALITY::operator= + 0xa3f93 (FITTER_FIOMGR)
   0x160e66: FIOMGR_STRATIXIII_DYNAMICTERMINATIONCONTROL_LEGALITY::operator= + 0xa5a36 (FITTER_FIOMGR)
   0x138159: FIOMGR_STRATIXIII_DYNAMICTERMINATIONCONTROL_LEGALITY::operator= + 0x7cd29 (FITTER_FIOMGR)
    0x8236a: FIOMGR_IO_MANAGER_INTERFACE::operator= + 0x16fca (FITTER_FIOMGR)
   0x164c67: FIOMGR_STRATIXIII_DYNAMICTERMINATIONCONTROL_LEGALITY::operator= + 0xa9837 (FITTER_FIOMGR)
   0x134667: FIOMGR_STRATIXIII_DYNAMICTERMINATIONCONTROL_LEGALITY::operator= + 0x79237 (FITTER_FIOMGR)
   0x135364: FIOMGR_STRATIXIII_DYNAMICTERMINATIONCONTROL_LEGALITY::operator= + 0x79f34 (FITTER_FIOMGR)
    0x9d01f: FIOMGR_IO_MANAGER::legality_check + 0x22f (FITTER_FIOMGR)
    0xa3bb4: FIOMGR_IO_MANAGER::update_io_manager_atom_information + 0x174 (FITTER_FIOMGR)
    0x9f2ce: FIOMGR_IO_MANAGER::post_fit_legality_check + 0x12e (FITTER_FIOMGR)
     0xbcb7: fcuda_execute + 0x21d7 (fitter_fcuda)
    0x55230: FITCC_EXPERT::fitter_post_check + 0x1b0 (FITTER_FITCC)
    0x5697a: FITCC_EXPERT::invoke_fitter + 0x8fa (FITTER_FITCC)
     0x9ccb: fcuda_execute + 0x1eb (fitter_fcuda)
     0xeb9b: fmain_start + 0x8eb (FITTER_FMAIN)
 
 
    0x18367: Legacy_fitter_Unload + 0x6b7 (comp_qfit_legacy_flow)
    0x14410: TclInvokeStringCommand + 0xf0 (tcl86)
    0x161e2: TclNRRunCallbacks + 0x62 (tcl86)
    0x17a65: Tcl_EvalEx + 0xa95 (tcl86)
    0xa6f8b: Tcl_FSEvalFileEx + 0x22b (tcl86)
    0xa5646: Tcl_EvalFile + 0x36 (tcl86)
    0x12877: qexe_evaluate_tcl_script + 0x367 (comp_qexe)
    0x11ac3: qexe_apply_ini_vars + 0x2763 (comp_qexe)
    0x16c34: qexe_run_tcl_option + 0x584 (comp_qexe)
    0x39285: qcu_run_tcl_option + 0xf95 (comp_qcu)
    0x1658d: qexe_process_cmdline_arguments + 0x260d (comp_qexe)
    0x17371: qexe_standard_main + 0xc1 (comp_qexe)
 
    0x13258: msg_initialize_out_of_memory_handler + 0x368 (CCL_MSG)
    0x14a5e: msg_set_stack_size + 0x7e (CCL_MSG)
    0x16af0: mem_tbb_tracking_flush_peak + 0x2b0 (ccl_mem)
    0x12af1: msg_exe_main + 0xa1 (CCL_MSG)
 
    0x17c23: BaseThreadInitThunk + 0x13 (KERNEL32)
    0x6d720: RtlUserThreadStart + 0x20 (ntdll)
 
End-trace


Executable: quartus_fit
Comment:
None

System Information
Platform: windows64
OS name: Windows 10
OS version: 10.0

Quartus Prime Information
Address bits: 64
Version: 20.1.0
Build: 711
Edition: Standard Edition

 

0 Kudos
6 Replies
Ash_R_Intel
Employee
217 Views

Hi,


I am enquiring about this error with our internal team. Will keep you posted when I get the information.

Is it possible for you to provide a sample design where this error can be reproduced. .qar would be helpful.


Regards.


Devi_Puthra
Beginner
213 Views

This error appeared when we integrated  ADC with our design 

Ash_R_Intel
Employee
200 Views

Hi,

We need a reference design to reproduce this error. Please provide the same.


Regards.


Devi_Puthra
Beginner
193 Views

Looks like bug in 20.1.x versions, I tried 19 version --> works fine. 

Please let us know once you release next stable version 

Ash_R_Intel
Employee
172 Views

Hi Hariprasad,


Glad to know that you can go ahead for now. To understand what caused this issue, and to help fix it in future Quartus releases, please provide an example scenario to reproduce the error. It would be of great help to all of our customers.


Regards.


Devi_Puthra
Beginner
167 Views

With all 4 PLLs utilized, instantiate ADC in the MAX 10, then you will see the above error

Reply