New Contributor
New ContributorWe are using the Pro Version and an arria10 FPGA.
Creating a new stp does not create the problem, but there is one stp that was created with quartus 24.1. pro (worked fine for a while) and now somehow got this problem. There might be the chance (but I doubt it) that it has come in touch with quartus pro 24.2.
Anyways, the general question is: How do I fix it? In the long run, we are planing to upgrade our projects to either quartus pro 24.2 or even 25.3 and it would be nice to have a solution for that . Recreating every stp would be a real pain..
Unfortunately, I am neither allowed to share the design, nor do I know how to trigger this problem. So, I'm unable to create a small toy example.
Regards,
Michael
Super ContributorWithout the testcase and a known way to reproduce the problem, it will be very difficult to debug what might have gone wrong.
Additionally, I could not find any similar error in our database.
When you mentioned ‘it has come in touch with Quartus Pro 24.2,’ do you mean that you might have added and used the same .stp file in different Quartus version projects (e.g., 24.2) and then used it again in a previous used Quartus version?
Perhaps try archiving the project into a .qar file before upgrading to a newer Quartus version, or create a new .stp file when using it in another Quartus version to see if the issue can be avoided.
Regards,
Richard Tan
New ContributorIt could be the case that the project including the stp-file was opened (not created) with quartus pro 24.2 and then reopened with quartus pro 24.1
I will have a further look on that. Anyways, what is the expected way to upgrade stp files from an older to a newer version? Is there an expected way at all? Should it work out-of-the box? If not, what is the expected way to get rid of / handle the assertion?
Do I understand you correctly that "update the parent entity using the megawizard in the current release" as stated in the assertion is not possible, as we haven't (?) used the megawizard?
Super Contributor.stp files aren't version-specific. No "upgrade" is necessary.
But if you compiled the design in 24.2 and then recompiled in 24.1, that might change the logic analyzer enough so it doesn't work with the same .stp file.
If not, then I stand by that the .stp file might be corrupted.
