HMC Controller IP Core Might Have Violation of set_max_skew Constraint - HMC Controller IP Core Might Have Violation of set_max_skew Constraint Description Compiling the HMC Controller IP core might cause a maximum allowed skew violation warning. In most cases, you can ignore this warning. However, in the following cases, the violation can cause individual transceiver channels to complete the reset process at different times: In full-width variations, if the violation is in the skew between transceiver channels 7 and 8. In full-width variations, if the violation is in the skew between transceiver channels 8 and 9. In half-width variations, if the violation is in the skew between transceiver channels 3 and 4. In half-width variations, if the violation is in the skew between transceiver channels 4 and 5. This issue could affect all variations of the Hybrid Memory Cube Controller IP core. It is most likely to affect full-width variations configured with a data rate of 12.5 Gbps. Resolution This issue has no workaround. However, you can compile with different seeds to achieve different place and route results. If you run multiple compilations with different seeds, one or more of the compilation runs might provide a placement that does not violate the skew requirement. This issue is fixed in version 15.1 of the Hybrid Memory Cube Controller IP core. Custom Fields values: ['novalue'] Troubleshooting novalue True ['novalue'] ['FPGA Dev Tools Quartus® Prime Software Pro'] 15.1 15.0 ['Programmable Logic Devices'] ['novalue'] ['novalue'] ['novalue']