Forum Discussion
sstrell My stp. file is straight forward; it was created with the gui: Multiple signals, one trigger window, two triggers (AND and OR). However, what I did change was to add (and remove) a power-up trigger. However this was the first time, I used a power-up-trigger, but I don't think this is the root cause, because previously the same problems (with version 24.3) existed, and there was no power-up trigger
Yes, these settings enable Evaluation of the above mentioned assertion. If I deactivate them (never tried VHDL and SV individually) and cause the failure.
P.S. Please be aware, that I'm ooo from 13. Feb to 13 Mar, so please don't close this threat in the meanwhile!
Could you share your .qar design (Project > Archieve Project) so we can see if we can try to duplicate the issue.
Currently we do not have any idea what could be the cause. This might need debugging.
Do you have a different machine to test if the issue persists?
Also, which operating system are you currently using?
For reference, here are the tool versions and error details involved:
Quartus Software: With Quartus Pro 25.3 (patched)
Device Family: Arria 10 devices
Error Message:
Error(22148): VHDL error at sld_ela_control.vhd(1263): Failure: "The design file sld_ela_control.vhd is released with Quartus Prime software Version 25.3.0. It is not compatible with the parent entity. If you generated the parent entity using the Signal Tap megawizard, then you must update the parent entity using the megawizard in the current release.
Debug done:
1. Run using Administrator privileges - no change
2. Deleted qdb/dni folder - no change
Let me know if I missed any information.
Regards,
Richard Tan
- MichaelL25 days ago
New Contributor
Hi RichardT,
first of all thanks for sticking to this topic. Unfortunately, I'm not allowed to share our project. I can try to add a signaltap to an altera-IP-core and then remove all our IPs/subsystems, but this might also remove the problem...
I'm still using Win10, but the problem is also persistent on a Win11 system. So the problem is more related to quartus/our project than to the operating system/machine. But I will double check this as well
To me, it looks like a faulty assertion, as the problem can be suppressed by disabling static assertions.
Regards,
Michael