Version Found: DDR4/DDR3/RLDRAM3/QDRII+/QDRIV v1.0
Version Resolved: See (Xilinx Answer 58435)
In the 2015.3 release, pblock constraints for UltraScale Memory IP will be generated by the Vivado Placer during place_design.
These pblock constraints created by the Vivado Placer are hidden and not visible to the user.
However, if you add your own pblock constraints that include the UltraScale Memory IP, then the Vivado Placer will not generate the hidden pblock constraints, which could lead to timing issues.
In order to prevent timing issues, any user created pblocks that contain UltraScale Memory IP must be contained within the same clock region as the memory I/O.
Because the pblocks need to be constrained to the same region as the memory I/O, it is recommended to place the I/O and create the pblock in the post-synthesis DCP.
The following procedure can be followed to do this:
Note: Make sure pblock is contained in the same clock region as the memory I/O.
Revision History:
09/30/2015 - Initial Release
Answer Number | 问答标题 | 问题版本 | 已解决问题的版本 |
---|---|---|---|
58435 | MIG UltraScale - IP Release Notes and Known Issues for Vivado 2014.1 and newer tool versions | N/A | N/A |