Forum Discussion

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

Signaltap II, compile project, internal error

Internal Error: Sub-system: VPR20KMAIN, File: /quartus/fitter/vpr20k/quartus_interface/qi_common/vpr_qi_soft_constraint_manager.cpp, Line: 1513

Quartus II 32-bit Version 11.1 Build 173 11/01/2011 SJ Full Version

----------------

Hi

My steps are

1, compile project, success

2, use Signaltap (which means project need to be re-compiled)

3, re-compile project, error happens.

Anyone shed a light ? Thanks

PS:

We've searched extensively. Interestingly, quite some solutions/pacthes are available to solve similar problems, but not this one we have.

For example, you can google another error as below, and find its solution patch immediately:

"Internal Error: Sub-system: VPR20KMAIN, File: /quartus/fitter/vpr20k/quartus_interface/ qi_common/vpr_qi_high_speed_low_power_tiles.cpp, Line: 5985"

---------------

Internal Error: Sub-system: VPR20KMAIN, File: /quartus/fitter/vpr20k/quartus_interface/qi_common/vpr_qi_soft_constraint_manager.cpp, Line: 1513

Internal Error

Stack Trace:

0x1c86ea: _vpr_qi_jump_to_exit + 0x64 (fitter_vpr20kmain)

0x2820ac: _pl_move_add_block + 0x1e8 (fitter_vpr20kmain)

0x2820e5: _vpr_exit_at_line + 0x37 (fitter_vpr20kmain)

0x1fb970: _handle_assertion_failure_stripped + 0x25 (fitter_vpr20kmain)

0x36632a: _vpr_qi_scm_update_clustering_information_after_netlist_change + 0x2d (fitter_vpr20kmain)

0x39fb5d: _aa_rt_dchain_adjust_delays_to_include_delay_chains_used_in_ic_delay + 0x119 (fitter_vpr20kmain)

0x3ae745: _aa_pl_rebuild_netlists_after_atom_netlist_modification + 0x17b (fitter_vpr20kmain)

0x1c3a68: ___sse2_available_init + 0x95bb4 (fitter_vpr20kmain)

0x115d86: _aa_postpl_do_post_placement_ops + 0x16 (fitter_vpr20kmain)

0xf8d9f: _vpr_qi_llr_back_annotate + 0x15f (fitter_vpr20kmain)

0xfef6c: _aa_flow_fit + 0x5c (fitter_vpr20kmain)

0xed312: _vpr_main_internal + 0x2b2 (fitter_vpr20kmain)

0x115c7a: VPR_QI_FACADE::vpr_qi_main + 0xfa (fitter_vpr20kmain)

0x2d5c2: _fitapi_run_vpr + 0x72 (fitter_fitapi)

0x3934d: FITCC_EXPERT::run_vpr + 0x11d (FITTER_FITCC)

0x3a40c: FITCC_EXPERT::place_and_route + 0x13c (FITTER_FITCC)

0x3b8f1: FITCC_EXPERT::invoke_fitter + 0x701 (FITTER_FITCC)

0x2bda: _ftitan_execute + 0x22a (fitter_ftitan)

0x9c10: fmain_start + 0x710 (FITTER_FMAIN)

0x7c1c: qfit_execute_fit + 0x19c (quartus_fit)

0x12275: QFIT_FRAMEWORK::execute + 0x4b5 (quartus_fit)

0xff71: qexe_get_command_line + 0x14c1 (comp_qexe)

0x12474: qexe_process_cmdline_arguments + 0x3d4 (comp_qexe)

0x12563: qexe_standard_main + 0x83 (comp_qexe)

0xbfae: qfit_main + 0x5e (quartus_fit)

0x1c51: msg_main_thread + 0x11 (CCL_MSG)

0x1be8: _thr_final_wrapper + 0x8 (ccl_thr)

0x1bc5: msg_thread_wrapper + 0x85 (CCL_MSG)

0x443a: mem_thread_wrapper + 0x4a (ccl_mem)

0x2b5d1: msg_exe_main + 0x81 (CCL_MSG)

0xc44c: _main + 0x1c (quartus_fit)

0x14377: _memset + 0x15f (quartus_fit)

0x51113: BaseThreadInitThunk + 0x11 (kernel32)

0x5b428: RtlInitializeExceptionChain + 0x62 (ntdll)

0x5b3fb: RtlInitializeExceptionChain + 0x35 (ntdll)

End-trace

Quartus II 32-bit Version 11.1 Build 173 11/01/2011 SJ Full Version

4 Replies

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

    I get this in 12.0. Haven't submitted an SR yet, but found that reducing the signaltap size and number of signals helps.

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

    This is an interesting error. I have not seen this one before. I think it is hard to say what the root cause of the error is. One suggestion, however, would be to shorten the data depth for the signals (say if you were at 2K, try 512 or even smaller) and see if that makes a difference. Best, James

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

    Thanks jderrick and James.

    Installed Quartus II version 12 and use this version 12. Now the SignalTap II works, even 5 signals are probed at the same time.

    Did not expect solve the problem in this way ...