What is the maximum downward pressure that can be applied to the top of Intel® FPGA BGA packages?
Description The following guidelines refer to the downward pressure or compressive load that can be applied to the top of Intel® FPGA BGA packages: For packages with eutectic SnPb (tin-lead) balls, use the following constant compressive loads: - 3g per solder ball for 0.5mm pitch MBGA package - 6g per solder ball for 0.8mm pitch UBGA package - 7g per solder ball for 0.92mm hex pitch FBGA package - 8g per solder ball for 1.00mm hex pitch FBGA package - 8g per solder ball for 1.00mm pitch FBGA package - 12g per solder ball for 1.27mm pitch BGA package For packages with SAC (tin-silver-copper) solder balls, use the following constant compressive loads: - 7g per solder ball for 0.5mm pitch MBGA package - 12g per solder ball for 0.8mm pitch UBGA package - 14g per solder ball for 0.92mm hex pitch FBGA package - 15g per solder ball for 1.00mm hex pitch FBGA package - 16g per solder ball for 1.00mm pitch FBGA package - 24g per solder ball for 1.27mm pitch BGA package For heat-sink application, Intel's recommendation is to not exceed 20g load per solder ball Your PCB and the supporting frame should be designed to withstand the pressure of the downward force to prevent bending or flexing of your PCB.Can a 9-transceiver channel Arria V GT device support an Rx only channel that already has four 6.144-Gbps duplex or Tx channels?
Description No, a 9-transceiver channel Arria® V GT device cannot support an Rx only channel that already has four 6.144-Gbps duplex or Tx channels. Due to a bug in the Quartus® II software versions 13.1 and earlier, the Fitter will not produce an error message for the configuration above. Resolution This problem is fixed in Quartus II software version 13.1 and an error message is produced with the above illegal configuration.Is programming of a serial configuration device that is different from one selected in a .jic file possible?
Description The Quartus® II programmer supports programming of serial configuration devices via JTAG and the Serial Flash Loader which are a higher density than the device that the .jic file was originally targeted at. For example a .jic file that was targeted to an EPCS64 device may be used to program an EPCS128 device using the Quartus II programmer. SVF and JAM files that are generated from the .jic file may only be used to program the targeted device. The Quartus II programmer will allow an EPCQ256 device to be programmed by a .jic file targeted at a lower density device. In this case FPGA configuration may fail due to a difference in the format of the data for devices of 256Mb or greater. Resolution The Quartus II prgrammer is scheduled to be updated to not allow programming of EPCQ256 devices using .jic files intended for lower density devices.How do I change the clock frequency of the USB-Blaster II download cable?
Description The USB-Blaster™ II download cable has a default clock frequency for TCK (JTAG) or DCLK (Active Serial programming) of 24MHz. The frequency may be changed to lower frequencies where signal integrity and timing does not allow operation at 24MHz. Resolution The following comamnd may be used to change the clock frequency of the USB-Blaster II: jtagconfig --setparam <cable number> JtagClock <frequency> <cable number> is the USB-Blaster II cable to be modified. <frequency> is the desired TCK or DCLK frequency. 24M, 16M and 6M are supported. Related Articles What is the nominal operational frequency of TCK in the USB-Blaster download cable? Why does Quartus II Programmer prompt the error message Can't recognize silicon ID when programming an EPCS/EPCQ serial flash device with a .jic file using the USB-Blaster II download cable? Can I change the TCK frequency when using the ByteBlasterMV or ByteBlaster II download cables? Why does the TCK frequency setting of the USB-Blaster II download cable revert to the default value of 24 MHz after being changed? Can I change the TCK frequency when using the USB-Blaster download cable?Does the Advanced clock phase control adjustment in the HPS DDR3 work?
Description You may notice the Advanced clock phase control setting in the HPS GUI PHY Settings tab. Changing the phase value has no effect on the phase of the PLL output clocks. Resolution The Advanced clock phase control adjustment will be removed in a future version of the Quartus® II software. This problem was fixed in Quartus® II software version 13.1Why does the Intel® Quartus® II software report that no devices are installed despite installing them?
Description Due to a problem in the the Intel® Quartus® II software version 13.0, you might see the following message during installation if your license is not valid or no longer under maintenance. You successfully installed the Quartus® II software, but did not install any devices. Do you want to launch the device installer to add devices? Resolution To avoid this problem, use the valid license file that is currently under maintenance. The message has been updated beginning with version 13.1 of the Intel® Quartus® II software.Vulnerability in JTAG server potentially allows a local attacker to execute arbitary code
Description With Intel® Quartus® Prime software versions from 15.1 to 18.0 and Quartus II software versions from 11.0 to 15.0, unquoted service paths may cause JTAG server to be vulnerable to the replacement of required executables. On reboot, these may be run with elevated privileges. This problem only occurs if the installation path contains spaces, if there are no spaces in the installation path then you are not affected by this vulnerability. This problem affects Intel Quartus Prime Pro, Standard and Lite editions as well as the subscription and web editions of the Quartus II software. This problem only affects installations on Windows. This problem also affects the Intel Quartus Prime and Quartus II standalone programmer version 18.0 and earlier. The Quartus II software and standalone programmer, version 10.1 and earlier, are not affected by this problem. Resolution To avoid this vulnerability, perform one of the following actions: If the Intel® Quartus® Prime software has already been installed to a path with spaces, remedy this vulnerability by downloading and installing the patch intel_sa00151_patch.exe (md5sum: 35ce4d672cef67efebdd3d5b866e58f3), then running the script that is extracted from the patch. If the Intel® Quartus® Prime software version 18.0 and earlier has not yet been installed, ensure that the installation path does not contain spaces. Install the Intel® Quartus® Prime software version 18.0 Update 1 or later where the vulnerability has been fixed. Acknowledgements: Intel® would like to thank Stefan (@Skanthak) for reporting this problem and working with us on coordinated disclosure.The Text Editor toolbar is not displayed in the Quartus II software
Description The Text Editor toolbar is not displayed. Resolution To display the Text Editor toolbar, perform the following:1. Open the Text Editor,2. On the Window menu of the main Quartus II window, click Detach Window.3. Right-click anywhere on the menu bar of the Text Editor.4. Click Text Editor.Audio Embed IP Design Transmits Unstable 3G Video Image
Description Designs using SDI Audio Embed IP core transmit unstable and flickering 3G video images. This issue affects all designs using the SDI Audio Embed MegaCore function version 13.1. Resolution To work around this problem, set exclusive clock group to aud_clk and vid_clk of the audio_embed block. Add the following line to the audio_embed.sdc file. set_false_path -to [get keepers {*audio_embed_core:*|g_audio_pair*toggle_meta}]Why can I only see one source file for my Qsys component in the component editor?
Description When loading an existing custom peripheral into the Qsys component editor, only the top level HDL file is displayed in the GUI. On saving the peripheral, all other source files are lost from the generated _hw.tcl peripheral file. Resolution This is a current known issue in the Quartus® II 12.0 Qsys tool, and shall be fixed in a later version. The user will need to add the other required files into the component GUI before saving, or alternatively make edits to the peripheral using a text editor.