Are there any known issues creating .jbc files with Quartus 18?

Vikas, Thank you for the reply. I expect to revisit and resolve this issue in the coming 1-2 weeks. However, until I can get back in the lab and reproduce these difficulties, I can only provide low-detail answers. (I will be able to provide more specific failure mode symptoms when I reproduce them.) 1. Are you able to generate .JBC file using Q18 Lite – Yes. I can generate the .JBC file. However, the subsequent use of that file to program the device fails a few minutes into the process. Again, I will provide more details when I’m back in the lab. 2. what do you mean "it fails to program 100% of the time." ? which programming tool & cable are you using? – The actual .JBC file that Q18.1 Lite produces is different than the file Q15.1 produces. The Q18.1 generated file always fails to program. The Q15.1 file seems to work. As one forum post suggests, there seems to be a difference related to algorithm 68 (“ALG_VERSION 68”) used in the convert programming files program, which started, I think, with Q17? I am using the JAM player in an embedded application (i.e. “no cable”). 3. "So, is Intel aware of any issues regarding the ability of Quartus 18.0 (Lite Edition) and later to generate reliable .JBC files?" I could able to generate .JBC file using Q18.1 Lite, refer below user guide, -- I too can generate the .JBC file. It is the file’s content that changes with different versions of Quartus. I understand if I haven’t provided all the necessary details in my responses above. I will be able to do better in a couple weeks. However, I had asked a general question of “known issues” because it would seem that others may have raised this issue. For example, I’ve seen Bug ID: 461822 which suggests a similar problem with Q17. Is this bug still active in Q18.1? Are there other, similar issues that have not been resolved yet? As a side note, I find the website particularly non-intuitive with respect to searching. This complicates and frustrates my efforts to reliably find answers that may have already been posted on this (or similar) issues. Thanks again for your response. I look forward to finding/understanding an Intel-suggested solution for my issue. Sincerely, Bob Weggel Electronics Engineer Performance Controls, Inc. 151 Domorah Drive Montgomeryville, PA 18936 USA <http://www.pcipa.com/> www.pcipa.com Main: +1 215-619-4920 Desk: +1 215-619-4952 . CONFIDENTIALITY NOTICE The information contained in this message, including any attachment, may be privileged and confidential and protected by applicable law from unauthorized disclosure. If the reader of this message is not the intended recipient, or is not an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this message or any attachment is strictly prohibited and can subject such person to penalties. If you have received this message in error, please notify us immediately by calling 215-619-4920; then delete the message and any attachment from your computer. Any content delivered to an intended recipient shall be destroyed or returned to PCI, Inc. when no longer required for authorized purposes.