Lili_7
New ContributorJoined 2 years ago
User Profile
New Contributor
User Widgets
Contributions
Re: Quartus II 13 crash
hi everyone, i waited a few days to make sure of not crashing again and then post it. i succeeded to solve the problem by restoring windows 10 to my last save, and uninstalling Quartus 13.0 +completely removing anything left from it. and download and installing Quartus 13.1. this so far is working just fine. best regards Lili3.7KViews0likes0CommentsRe: Quartus II 13 crash
exactly, latest version is for sure not always the solution, especially on Windows. i will also try to restore windows from some updates and then install both 13.0 and if didn't help 13.1 in turn , hope to get some achievements. if not possible try VM. thank you for offering solutions. i will post the result3.9KViews0likes0CommentsRe: Quartus II 13 crash
thanks a lot for all the help. the version that was running just fine on the system was 13.0 while the latest version is 13.1 from the same year. so i dont expect that much of a difference. and i think the problem even got worse when i removed the current quartus and downloaded the 13.1 version. but i will try your solution and i will post the an update on result.3.9KViews0likes0CommentsRe: Quartus II 13 crash
quite right, sorry for the lack of information, running OS is 64-bit Windows 10, Core(TM) i7-4790 CPU @ 3.60GHz + 8.00 GB. honestly i cant recall for sure that if the crashing started exactly after some windows updates or no. since it was at the beginning twice a day but still working but after a while completely broke. and in this meanwhile there were plenty of windows update.3.9KViews0likes0CommentsQuartus II 13 crash
hi, i was using Quartus II 13 web edition for 2 years without any issues. suddenly 2 months ago it started crashing more often. so i uninstalled it, and installed it again. it did work for a month and now it crashes every time i try even to open the software. and this error message log appears: *** Fatal Error: Access Violation at 0X0000000067A5DA62 Module: quartus.exe Stack Trace: 0x45da61: QAccessible::queryAccessibleInterface + 0x31 0x46403c: QAccessible::setRootObject + 0x153c 0x4652e9: QAccessible::setRootObject + 0x27e9 0x9f06: CreateStdAccessibleProxyW + 0x4e6 0x32dad: UiaReturnRawElementProvider + 0x371d 0x7c546: UiaRegisterProviderCallback + 0x18336 0x74057: UiaRegisterProviderCallback + 0xfe47 0x1f217: DllCanUnloadNow + 0xd347 0x1c2ac: DllCanUnloadNow + 0xa3dc 0x1bf0f: DllCanUnloadNow + 0xa03f 0x1b5c8: DllCanUnloadNow + 0x96f8 0x3cfe4: UiaReturnRawElementProvider + 0xd954 0x3cca6: UiaReturnRawElementProvider + 0xd616 0x1e9b1: Ordinal2712 + 0x191 0x21632: SendMessageTimeoutW + 0x142 0xa13e3: KiUserCallbackDispatcher + 0x23 0x1063: NtUserPeekMessage + 0x13 0xa332: PeekMessageW + 0x1e2 0xa292: PeekMessageW + 0x142 0x132d77: QEventDispatcherWin32::processEvents + 0x1c7 0x83564: QApplicationPrivate::translateTouchEvent + 0x884 0x109cf0: QEventLoop::exec + 0x230 0x420e3c: QDialog::exec + 0xec 0x645ac: AFCQ_MSG_DISPLAY::internal_error_display + 0x1dc 0xe2c7: MSG_REPORT::internal_error + 0x127 0x1ebee: MSG_INTERNAL_ERROR::set_talkback_xml + 0x11be 0x1efc9: MSG_INTERNAL_ERROR::report_fatal + 0x179 0x4200: err_report_fatal_exception + 0x70 0x4499: err_report_fatal_exception + 0x309 0x12d826: UnhandledExceptionFilter + 0x1e6 0xcf4d7: LdrResolveDelayLoadsFromDll + 0xb37 0xa134f: KiUserApcDispatcher + 0xaf 0xa292e: __chkstk + 0x11e 0x52553: RtlRaiseException + 0x483 0xa143d: KiUserExceptionDispatcher + 0x2d 0x45da63: QAccessible::queryAccessibleInterface + 0x33 0x46403c: QAccessible::setRootObject + 0x153c 0x4652e9: QAccessible::setRootObject + 0x27e9 0x9f06: CreateStdAccessibleProxyW + 0x4e6 0x32dad: UiaReturnRawElementProvider + 0x371d 0x7c546: UiaRegisterProviderCallback + 0x18336 0x74057: UiaRegisterProviderCallback + 0xfe47 0x1f217: DllCanUnloadNow + 0xd347 0x1c2ac: DllCanUnloadNow + 0xa3dc 0x1bf0f: DllCanUnloadNow + 0xa03f 0x1b5c8: DllCanUnloadNow + 0x96f8 0x3cfe4: UiaReturnRawElementProvider + 0xd954 0x3cca6: UiaReturnRawElementProvider + 0xd616 0x1e9b1: Ordinal2712 + 0x191 0x21632: SendMessageTimeoutW + 0x142 0xa13e3: KiUserCallbackDispatcher + 0x23 0x1063: NtUserPeekMessage + 0x13 0xa332: PeekMessageW + 0x1e2 0xa292: PeekMessageW + 0x142 0x132d77: QEventDispatcherWin32::processEvents + 0x1c7 0x83564: QApplicationPrivate::translateTouchEvent + 0x884 0x109cf0: QEventLoop::exec + 0x230 0x420e3c: QDialog::exec + 0xec 0x64237: AFCQ_MSG_DISPLAY::prompt_display + 0x2f7 0x10648: MSG_O::prompt + 0x8 0x2683a: QUI_FRAME_WND::flow_finish_prompt + 0x91a 0x460d8: QUI_FRAME_WND::qt_static_metacall + 0xa78 0x11d699: QObject::event + 0xd9 0x6ada8: QWidget::event + 0xd18 0x3989a4: QMainWindow::event + 0x284 0x228f5: QApplicationPrivate::notify_helper + 0xf5 0x25297: QApplication::notify + 0x17f7 0x10a7c1: QCoreApplication::notifyInternal + 0x71 0x10c7cb: QCoreApplicationPrivate::sendPostedEvents + 0x29b 0x1311de: QEventDispatcherWin32::event + 0x70e 0xef5b: CallWindowProcW + 0x60b 0xe683: DispatchMessageW + 0x4a3 0x132f69: QEventDispatcherWin32::processEvents + 0x3b9 0x83564: QApplicationPrivate::translateTouchEvent + 0x884 0x109cf0: QEventLoop::exec + 0x230 0x10e5ff: QCoreApplication::exec + 0xdf 0x4ae8: msg_exe_fini + 0x58 0x522c: msg_exe_fini + 0x79c 0x1524: MEM_SEGMENT_INTERNAL::~MEM_SEGMENT_INTERNAL + 0x194 0x5e0f: msg_exe_main + 0x8f 0x17343: BaseThreadInitThunk + 0x13 0x4cc90: RtlUserThreadStart + 0x20 End-trace Quartus II 64-Bit Version 13.0.0 Build 156 04/24/2013 SJ Web Edition4.1KViews0likes14CommentsRe: qsys project and bonding top hardware module with nios
this pic.outline shows precisely what i want to do. so now i followed steps, in Eclipse i don't know how should i define inputs and outputs(which are nor accessible in de0 nano GPIO, but they are entered by user from keyboard) as you can see in pic.eclipse. and i am facing some errors. i tried some ways like editing my bsp properties but i Count solve this errors. best regards2.1KViews0likes0Comments