Forum Discussion
Occasional ContributorQPP 26.1 fails to generate PLL IP
I confirm that the problem of not being able to generate a PLL IP in QPP 26.1 went away when I used a different Windows 11 account that did NOT have a space in the user folder name under "C:\Users\". Note that this was change was made on the same PC that had the reported error above.
Therefore, it appears that Quartus has a bug in the Parameter Editor generate process that it can not handle spaces in the path it creates under the user's Temp folder during the generate IP process.
Please let me know how I can track this bug report and potentially know that it's fixed in a future QPP version or patch.
Thank you.
Regular ContributorHi,
Please confirm if my understanding is correct.
Did the issue you observed occur only on one specific Windows 11 machine, or are multiple of them failing?
Other than this IP, are there any other IPs that failed to generate?
Regards,
Aqid
Occasional ContributorHello Aqid.
Yes, that's correct. QPP 26.1 is only failing this way on one particular Win 11 machine for this Agilex 3 project. The same problem is NOT observed on our other Win 11 machine or two different Ubuntu Linux machines.
The Agilex 3 project uses four IPs, and only the PLL fails to generate. We also use QPP for a complex Cyclone 10 GX project, and there have been no observed failures to generate IP blocks on any machines.
Thank you.
- AqidAyman_Altera
Hello Robert,
Thank you for the detailed information.
Does this error also happen with any other QPP version that you have? Also, have you tried changing the other Agilex 3 devices? Or perhaps another device family? I appreciate your input on this.
In parallel, I will report this internally to further investigate this.Regards,
Aqid
- Robert_PIN_ASAP
Hello Aqid,
I have been testing PLL IP generation between the two different Win 11 PCs. As far as I can tell, the temporary folder alt066_XXXXXX is indeed generated under Temp and populated with the altera_falconmesa_ph2_iopll.sdc file. However, it seems that the Parameter Editor does not read it back during IP generation.
The one difference I see between the two PCs is that the username is two words on the PC where it fails and only one word on the PC where it passes (see Error log snippet below). I'm going to guess that having a space in the path name to the SDC file during IP generation is causing the problem.
Error: add_fileset_file: No such file C:/altera_pro/26.1/ip/altera/altera_iopll/top/{C:/Users/<username>/AppData/Local/Temp/alt0637_15290807326924327962.dir/0003_iopll_0_gen/altera_falconmesa_ph2_iopll.sdc}
Please let me know if you think this is the problem, and I'll see whether the username can be changed on this lab PC. Unfortunately, Windows is very convoluted with account settings (local vs MSFT managed), so I'm not sure that we can change it.
Thank you.
ShengN_alteraSuper Contributor
Yes, space is really dangerous. I would suggest you replace the space with underscore
