Forum Discussion
Contributor22.1 PRO: (*preserve_for_debug*) signals not preserved
Hello,
Alright thanks for the feedback. I've let them know that you expect this fix to apply to all data types.
In the meantime your only workaround is to have the signal connected to an i/o port.
With that, I now transition this thread to community support. If you have a new question, feel free to open a new thread to get the support from Intel experts. Otherwise, the community users will continue to help you on this thread. Thank you.
Regards,
Nurina
P/S: If you like my comment, feel free to give Kudos. If my comment solved your problem, feel free to accept my comment as solution.
Super ContributorThe assignments to use are documented here:
https://www.intel.com/content/www/us/en/docs/programmable/683819/22-1/marking-signals-for-debug.html
and discussed in this training:
You mark nodes or entities in the Assignment Editor instead of editing your HDL code. The Assignment Editor is just a graphical tool to ease editing of the .qsf file. You can edit the .qsf file directly if you want.
After they're marked, you enable the feature, as you have done, do a full recompile, and then add the preserved nodes in Signal Tap using the dedicated Node Finder filter. These things are all discussed in the doc and training I linked to.
ContributorThank you but this is exactly the document I used (cf. the above screenshot).
Your statements differ from what is in the documentation.
I don't do anything wrong, I even do what is recommended.
Once more, the pragma preserve_for_debug is broken, it doesn't preserve the signals.
