09-26-2020 02:44 AM
When implementing the project with Vivado /19.2, I noticed that one of the modules had been optimized away. When I used the run-time optimized compilation strategy, the module was not optimized. In addition, I implemented the project in Vivado /2018.2, and found that the module was not optimized. So this is very strange。
10-11-2020 07:12 PM
Do you mean it's optimized away in default impl strategy?
Please make sure the input and output ports of this module are correctly connected.
Alternatively, add DONT_TOUCH to the module.