jtagserver.exe causing BSOD together with ftdi driver
Dear developers in the same shoe like me, I am facing a strange issue, and would like to ask others whether they have similar problem: Quartus Prime Pro 25.3.0 was installed first and in use with USB Blaster III (evalkit) After some time (probably windows pulled some newer driver components) each time when I plugged in the evalboard it was crashing the system. With WinDBG analyzing the minidump it turned out the responsible was jtagserver.exe calling some unknown function in ftdibus.sys "PROCESS_NAME: jtagserver.exe SYMBOL_NAME: ftdibus+f4d4 MODULE_NAME: ftdibus IMAGE_NAME: ftdibus.sys STACK_COMMAND: .cxr; .ecxr ; kb BUCKET_ID_FUNC_OFFSET: f4d4 FAILURE_BUCKET_ID: 0x139_a_GUARD_ICALL_CHECK_FAILURE_ftdibus!unknown_function OSPLATFORM_TYPE: x64 OSNAME: Windows 10 --> this is windows 11 FAILURE_ID_HASH: {3a7c8e82-5c61-9acf-ceb5-61656fa0b04c}" And here comes the strange part: Reinstalling the driver with dp_inst.exe from Quartus directory helped until next restart or at least for 1-2 hours. Then power cycling evalboard caused a crash again. When I fresh reinstalled driver and plugged in again the evalboard again everything was fine. When I updated to the latest quartus, the driver package in it was causing crash again. And I mean here reinstalling driver from the 25.3.1 quartus version did not change a thing. Anybody facing similar issue: I recommend installing Windows SDK and use WinDBG there for crashdump analysis to confirm this. I am looking forward for any feedback or stable solution idea. Kind regards, Peter
When you double click on a word, the other instances do not highlight due to the Find Box being open
When I am using Quartus and I happen to have the Find Box open and nothing is in it and I double click on a word in a file, the other instances will not highlight due to the fact that I have the Find Box open. You must close the Find Box before the other instances of a word will highlight again. Specs: OS = Windows Enterprise 11 Software = Quartus Prime Version 25.3.0 Build 109 09/24/2025 SC Pro Edition Patches Installed = 0.27 Steps to recreate 1. Open Quartus program 2. Open a file (HDL or Verilog, doesn’t matter) 3. Left double click on a word within the file and observe how other instances are highlighted 4. Open the Find Box (Ctrl+F) 5. Remove any word that is in the Find Box 6. Left double click on a word within the file expecting other instances to be highlighted 7. Observe that they are not highlighted due to the fact that the Find Box is still open 8. Close the Find Box 9. Left double click on a word within the file and observe how other instances are highlighted again now that the Find Box is closed This is a bug with the functionality of the Find Box.Agilex3 - unknown IDCODE
Hi everyone We are bringing up an Agilex3 A3CZ100BB18A based board where IDCODE is unknown for the Quartus Programmer. Currently the attached NOR flash is empty. This would be the first time configuration. The labels/texts on the chip seems right and correct and the same part we are trying to use. Quartus Programmer has proper access to the JTAG chain, but the IDCODE contains some 0xF nibbles jtagconfig.exe --debug (JTAG Server Version 25.3.0 Build 109 09/24/2025 SC Pro Edition) F36FF0DD (IR=10) Captured DR after reset = (F36FF0DD) [32] Captured IR after reset = (001) [10] Captured Bypass after reset = (0) [1] Captured Bypass chain = (0) [1] JTAG clock speed 1 MHz IDCODE should be 0x4365B0DD As you can see there is only minor difference, only some sub ID’s are wrong. F36FF0DD 4365B0DD I need ideas what could have gone possibly wrong as in documentation I did not find any explanation to this symptom. The JTAG interface seems electrically right. Testing the IDCODE 1000x in JTAG chain debugger of Quartus gives back consistently this very same IDCODE at any startup. Thank you for your help in advance! Kind regards, Petererror in JTAG server (error code 35) and autodetect (unable to scan device chain) Quartus 18.1
Hello fellow members, I have a Max10 FPGA Evaluation Kit board (10M08SAE144C8G) which i want to flash via JTAG. For this, i have installed Quartus Prime (18.1 version) and have USB Blaster 2 as an interface. After connecting the hardware, the LEDs on the board are stable. When i execute autodetect on the programmer , i get a dialog box stating "unable to scan device chain . Hardware is not connected"(screenshot attached). In the hardware setup , i coulkd see the usb blaster variant is added but still this error occurs. Similary when i try to run the .pof file , the diagnosis show "unexpected error in JTAG server -- error code 35" (screenshot attached). I checked the driver and it seems the USB blaster driver is also updated. On the command prompt, it shows 1) USB-Blaster variant [USB-1] Unable to lock chain - Hardware not attached Has someone encountered this issue before. Any help or suggestion would be highly appreciated. The screenshots can be seen in the attachments. Thanks. Best Regards, Ali
Warning at Standard 25.1 by Arria 10
Hi all. recent Queatus Prime Pro 25.3.1 drops Arria 10 support. (no Arria 10 support files in individual download page) But latest Standard 25.1 warns at compile Arria 10 project, by these message Info (24153): Support for Arria 10 devices is deprecated in the Quartus Prime Standard Edition software. For new Arria 10 designs, use the Quartus Prime Pro Edition software. For existing Arria 10 designs, continue to use the Quartus Prime Standard Edition software. Is this due to the difference in release dates between 25.3.1 and 25.1? Will we no longer see this warning when Standard 25.3 is released in the near future?Floating point operation on Cyclone 10 GX
Hello, I have a few questions regarding the way DSP resources are used in the FPGA I’m working with, a Cyclone 10 GX 10CX220YF780I5G. I want to perform an FMA (Fused Multiply-Add) operation using one of the available IPs in the catalog for floating-point operations, but I suspect that the one I’m currently using doesn’t execute the operation jointly as a + b * c; instead, it performs a + (b * c), which leads to errors due to intermediate rounding. The IP I’m using is Floating Point Functions FPGA IP, but there are others available that I believe might accomplish the same operation, such as Floating Point Hardware 2 Multi‑Cycle Intel FPGA or Native Floating Point DSP Cyclone 10 GX FPGA. I can’t find any information in the documentation about whether these operations are fused or not. Does anyone have any information on this? Thanks in advance.
Quartus Eda_Writer keeps crashing
Quartus Prime v25 keeps crashing at the eda_writer step during the flow on Windows 11. I have tried different Quartus versions (II v13.1, Prime Lite v25, Prime Standard v25). All of them crashed at this step multiple times. Is this an issue with the design that I am trying to implement? I searched for this error on Google and I found a message that said it was a bug that was fixed in version 21.1. Strange that its still occuring now in v25 standard. Problem Details Error: Internal Error: Sub-system: WSC, File: /quartus/neto/wsc/wsc_hierarchy_builder.cpp, Line: 1097 m_bp_manager != NULL Stack Trace: 0x48eca: WSC_HIERARCHY_BUILDER::build_map_from_partitions + 0x8a (NETO_WSC) 0x46dd5: WSC_HIERARCHY_BUILDER::build_hierarchy_from_partitions + 0x35 (NETO_WSC) 0x45e1b: WSC_HIERARCHY_BUILDER::build + 0x22b (NETO_WSC) 0x16282: QNETO_START::build_hierarchy_netlist + 0x242 (quartus_eda) 0x28548: QNETO_START::generate_simulation_files + 0x688 (quartus_eda) 0x1a1e3: QNETO_START::generate_eda_files + 0x43 (quartus_eda) 0x33fd0: qneto_execute + 0x210 (quartus_eda) 0xa79b: QNETO_FRAMEWORK::execute + 0x26b (quartus_eda) 0x10b5f: qexe_do_normal + 0x22f (comp_qexe) 0x16fa0: qexe_run + 0x420 (comp_qexe) 0x18012: qexe_standard_main + 0xb2 (comp_qexe) 0x10d17: qneto_main + 0x77 (quartus_eda) 0x12208: msg_main_thread + 0x18 (CCL_MSG) 0x13b18: msg_thread_wrapper + 0x78 (CCL_MSG) 0x15f13: mem_thread_wrapper + 0x73 (ccl_mem) 0x11a41: msg_exe_main + 0xa1 (CCL_MSG) 0x36423: __scrt_common_main_seh + 0x10b (quartus_eda) 0x2e8d6: BaseThreadInitThunk + 0x16 (KERNEL32) 0x8c53b: RtlUserThreadStart + 0x2b (ntdll) End-trace Executable: quartus Comment: None System Information Platform: windows64 OS name: Windows 10 OS version: 10.0 Quartus Prime Information Address bits: 64 Version: 25.1std.0 Build: 1129 Edition: Standard Edition