Honored Contributor
Honored ContributorI believe it was the second case. I did not have any false paths on either register. When Quartus did the merge, I guess it thought the two registers were related and flagged the violation. I can see that from the data path it is reporting - QT makes a jump in the middle of the path that does not make any sense.
I just created a false path as you suggested in your post and everything is compiling fine. I put a note on the sdc to remind me later that removing the false path exposes the anomaly in case I encounter issues later. Thank you so much for your help!
