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.
Regular ContributorHi,
I've tried to reproduce your problem on my machine. It would only be preserved if you use the sigtodebug in your design.
Maybe this is happening because it's been synthesised away.
I'll bring this up to our internal team and ask if this is intentional.
Regards,
Nurina
alexislmsHi @Nurina,
Please define "use". The signal exists, it's driven by something but doesn't have any fanouts. (it can be a link_up, some counters or anything meaningful only for debugging purpose)
Also, as @sstrell suggested, adding the signal as virtual pin doesn't change anything, the signal is still optimized out.
After Analysis&Synthesis:
This needs to be fixed.
Regards,
- alexislms
I've also tried via the Assignment Editor:
set_instance_assignment -name PRESERVE_FOR_DEBUG ON -to *sigtodebug*without success. The signal isn't kept.
