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 ContributorI don't want to argue. I'm just explaining how I use the features. Virtual pins have been around in the software forever to prevent unconnected I/O from being optimized away. Preserve for debug was only recently introduced because it was frustrating if you wanted to tap a deeply buried signal that was post-fit (as opposed to pre-synthesis directly from your RTL). A happy side effect of doing this is it can reduce or eliminate recompiles since tapping post-fit signals uses incremental routing (aka available post-fit routing wires).
ContributorIndeed, not for debugging purpose. My signal is not an I/O pin.
If that's the way to go, I'll waste my time with manual work the tool should do.
Thanks for your help.
