As part of the design constraints, waivers are automatically saved inside the checkpoint and restored from the checkpoint. Waivers are saved in both plain XDC and binary constraint formats.
- Use
write_xdcandwrite_waiversto export waivers into standalone XDC files. - Use
read_xdcorsourceto reload exported XDC files. - Use
write_xdcto export all waivers and design constraints in the order they apply to the design. This includes user-defined waivers and AMD IP waivers.Note: To export only waivers, add the-type waiveroption:write_xdc -type waiver -file waivers.xdcImportant: The IP waivers are created with the optioncreate_waiver -internal. Never usecreate_waiver -internalin your own waivers. This option is reserved for AMD IP waivers. - Use
write_waiversto export user CDC, DRC, and Methodology waivers. This option gives you more control and granularity.Note: AMD IP waivers are not exported with this command. - Use the
-typeoption to export a specific category of waivers. For example, export only CDC waivers:write_waivers -type CDC -file waivers_cdc.xdc - Use the
-idoption to export waivers for a specific check. For example, export all waivers for Methodology checkTIMING-15:write_waivers -id TIMING-15 -file waivers_timing_15.xdc
The following table summarizes the differences between write_xdc and write_waivers commands with
regards to the user waivers and AMD IP waivers.
| Vivado Command | Export User Waivers | Export AMD IP Waivers |
|---|---|---|
write_xdc
|
Yes | Yes |
write_waivers
|
Yes | No |