ModelSim-Intel FPGA Starter Edition 18.1 exits with code 211 when pressing Restart button
Hello, I am using ModelSim-Intel FPGA Starter Edition included with Quartus Prime Lite Edition 18.1. When I press the Restart button in the ModelSim GUI after running RTL simulation, ModelSim exits with the following message: "ModelSim is exiting with code 211. Check the transcript file for more information on the fatal error." Environment: - Quartus Prime Lite Edition 18.1 - ModelSim-Intel FPGA Starter Edition 18.1 - Windows PC - ModelSim path: C:\intelFPGA_lite\18.1\modelsim_ase\win32aloem 確認したこと: - Quartus / ModelSim は再インストールされました。 - 環境変数とPATH設定を確認しました。 - 同じプロジェクトが別のPCで正しく再起動できる場合。 - このPCではGUIの再起動ボタンを押すと問題が発生します。 - PCにはTrend Micro Apex Oneがインストールされています。 - リアルタイムスキャンからIntel FPGA / ModelSimフォルダを除外した後、ModelSimは正しく動作しました。 質問: GUIの再起動ボタンを使う場合、ModelSim-Intel FPGA Starter Edition 18.1で既知の問題として、終了コード211はありますか? また、この問題はウイルス対策ソフトやエンドポイントセキュリティソフトに関係している可能性はありますか? この問題に対するおすすめの設定や回避策はありますか? ありがとうございます。
10CL040YF484 Programming fails
1st Vendor Batch (Date Code: 2525): - First Test (3 FPGAs): - Card 1: ISP and JTAG programming successful; functioning correctly. - Card 2: Programmed in ISP mode, but fails to execute and returns a JTAG error. Replacing the FPGA on this board with another one resulted in the same issue. - Second Test (3 FPGAs): - Cards 3 & 4: ISP and JTAG programming successful; functioning correctly. - Card 5: ISP and JTAG programming successful, but the device is not functioning correctly, and most pins are not working as required. - Mouser Batch (Date Code: 2619): - Third Test (2 FPGAs): - Card 6: ISP and JTAG programming successful, but the device fails to function properly, with most pins not meeting requirements. - Card 7: ISP programming successful, but returns a JTAG error and fails to execute. Based on these outcomes, could you please help us identify where the problem lies?
Unable to scan JTAG chain, TCK only 2V
I have trouble with some development board with 10CL006YE144G. While the configuation by JTAG worked a while, the FPGA is no longer recognized by the programmer using Autodetect. I checked the voltages of signals and while the power supply (JTAG Header Pin 4) is stable 2.5V, the TCK signal is only driven to 2V High level. As all I/Os are driven by 3.3V, I assume the 2V is not or at least no stable high signal. As two USB Blasters do not work / work on other designs and with the signal is 2.5V w/o connected development board. I'm afraeid the FPGA I/O is broken... Unfortunately, the dev-Board lacks protection devices (direct connection header to Pin, no protection diodes). I assume connecting the USB-Blaster being referenced to the PC to the board being referenced to board's power supply could cause voltages spikes on the interface overloading and damaging the FPGA :-( Is this a keep the board simple and cheap, i.e. not even a series resistor, trap? Thanks in advance and KR CarlhermannSubject: Hitless Update Implementation Guidelines (AN904)
Target Devices: 10M08SAU324I7G / 10M25SAU324I7G Reference Document: AN904: MAX 10 Hitless Update Implementation Guidelines KDB 000080468 https://community.altera.com/discussions/fpga-device/subject-issues-implementing-hitless-update-on-max-10-via-quartus-prime-programme/355534/replies/355841?emcs_t=S2h8ZW1haWx8dG9waWNfc3Vic2NyaXB0aW9ufE1TNzJGWlhLRUhRVlowfC0xfFNVQlNDUklQVElPTlN8aEs Problem Description: Hi Altera Team, Thank you for the detailed explanation. I apologize for the delayed response, as I took some time to run experiments based on your feedback. After completing my implementation testing, I would like to clarify a few points: 1. Clarification on Section 1.5 in AN904 Section 1.5 of AN904 is titled "1.5. Hitless Update using Intel Quartus Prime Programmer". However, since your response indicates that the Quartus Prime Programmer GUI itself cannot achieve a true hitless update during reconfiguration without logic/IO interruption, the section title seems misleading. Could you confirm if Section 1.5 is actually intended to describe using the Quartus Prime Programmer to generate .jbc, .jam files for external hitless execution, rather than executing the update directly via the Programmer GUI? 2. JBC Hitless Update Issue Following KDB 000080468 I generated a .jbc file by strictly following the workflow outlined in KDB 000080468: During execution, hitless update still fails (I/O states drop/reset during reconfiguration). However, after rebooting/power-cycling the CPLD, the new FW/image runs successfully. Could you help verify: • Is there any step missing in my .jbc generation flow based on KDB 000080468? • If the generation sequence is correct, which part of the execution flow (e.g., Jam Player ACTION parameter, TAP Reset timing, or clamp release sequence) could cause the I/O clamping to fail prematurely? 3. Support for Partial / CFM0-Only Hitless Update Is it supported to perform a Hitless Update when programming only CFM0 (ROM0) instead of the full flash image? Does the ISP Clamp and Boundary-Scan mechanism function the same way during a partial image update? Thanks and best regards,10CL080YF780I7G BSDL FILE
Hi, We are currently using your 10CL080YF780I7G in our design. in the BSDL file, pin F4 is defined as a linkage bit, which prevents us from toggling it through boundary scan. However, in our design, we are using pin F4 as an output. The design compiles successfully in Quartus without any errors or warnings indicating that this pin should not be used in such a manner. Could you please clarify why pin F4 is defined as a link bit in the BSDL file? Is there a recommended workaround or update we should apply to ensure proper JTAG functionality? .pin file: BSDL file: Please note that we have encountered the same problem with the following devices:: 10CL040YF484I7G and 10CL016YF484I7G pin E2 is defined as out bit, while it is IO. We appreciate your guidance and look forward to your advice.
Quartus Programmer 21.1: JTAG Server Error Code 82 – Port 1309 Cannot Be Bound
Hello Altera Community, I am working on an FPGA project using a Cyclone IV FPGA development board and an Altera USB-Blaster. I am currently unable to program the FPGA because Quartus Programmer cannot access the JTAG server. System details: - OS: Windows 11 64-bit - Software: Quartus Programmer 21.1 - Installation path: C:\intelFPGA\21.1\qprogrammer - Programmer: Altera USB-Blaster - FPGA: Cyclone IV development board The USB-Blaster is detected by Windows Device Manager and the driver is installed. The USB-Blaster also powers on normally. However, Quartus Programmer gives: "Attempted to access JTAG server -- internal error code 82 occurred" When I run: jtagconfig I get: Error when scanning hardware - Server error Sometimes it also hangs at: Connecting to server(s) [...] I checked the JTAG server using: jtagserver --status It reports: Installed JTAG server is 'C:\intelFPGA\21.1\qprogrammer\bin64\jtagserver.exe' Server is stopped Remote clients are disabled I tried reinstalling the JTAG server: jtagserver --install jtagserver --start But the server immediately stops. I also tried: net start "Altera JTAG Server" The result was: The Altera JTAG Server service could not be started. The service did not report an error. NET HELPMSG 3534. I then ran: jtagserver.exe --foreground and received: Unable to bind changedetect socket: 10048 Can't bind to TCP port 1309 - exiting I checked the port using: netstat -ano | findstr 1309 and found that TCP port 1309 was being used/listened to by another process, for example PID 12888. I tried terminating the process using: taskkill /F /PID 12888 but Windows reported: ERROR: The process with PID 12888 could not be terminated. Reason: There is no running instance of the task. I also tried stopping the JTAG server, reinstalling it, and restarting it. In addition, I already tried the following: 1. Disabled PCI Express → Link State Power Management. 2. Disabled USB Root Hub power saving ("Allow the computer to turn off this device to save power"). 3. Stopped the Print Spooler service. 4. Closed Quartus/Programmer-related applications. 5. Reinstalled the JTAG Server. 6. Restarted the computer. 7. Tried starting the JTAG server manually. 8. Checked TCP port 1309 using netstat. The problem still remains. My main questions are: 1. Why is Quartus Programmer 21.1 unable to start the JTAG Server? 2. What is causing TCP port 1309 to remain occupied? 3. Is there a known issue with Quartus Programmer 21.1 and Windows 11? 4. Is there a recommended patch, driver, or newer Quartus Programmer version for this problem? 5. Is it possible to configure the JTAG server to use another TCP port? 6. What is the correct way to completely remove and reinstall the JTAG Server on Windows 11? 7. Is there anything else I should check before reinstalling Quartus Programmer? I would appreciate any guidance on how to get the JTAG Server running so that jtagconfig can detect my USB-Blaster and FPGA. Thank you.
Agilex5 NSATUS signal behavior at power up.
Hello Again, We used the AGILEX5 device, After powers ramp up, we pulled nCONFIG low for ~500 ms and pull it up for configuration. The NSTATUS signal is follow the nCONFIG as expected but we observe falling and rising scenario for ~20us that we do not know to explain Please advise it it normal and can cause it. Thanks Asaf nSTATUS and nCONFIG after ramp up nSTATUS and nCONFIG after ramp up - falling and rising of nSTATUS nSTATUS and nCONFIG after ramp up - falling and rising of nSTATUS - zoom outCyclone 10 LP Bitstream Compression Failing
I am using the Altera Cyclone 10 LP Development Kit with the 10CL025YU256I7G Device. Do do the design, I am using Quartus Prime Version 24.1 Standard. I am trying to compress my bitstream in order to have a faster configuration. I am using Active Serial with the on-board flash device. Altera documentation suggests two ways of performing the compression: Cyclone 10 LP bitstream compression I can get the compression to work using the 2nd way, where the .sof file is compressed during "Convert Programming Files" by accessing the file properties. The 1st suggested way of compression is not working: "To enable compression before design compilation: Click Assignment Menu > Device. Select the appropriate Intel ® Cyclone ® 10 LP device and then click Device and Pin Options. In the Device and Pin Options window, select Configuration under the Category list and turn on Generate compressed bitstreams. Click OK." The checkbox for "Generate compressed bitstreams" is checked, but after compilation, the .sof file is not compressed and configuration takes the same amount of time as when the checkbox is not checked. Why is this occurring?
