2. Support
  3. AR# 5227: LogiCORE Initiator/Target for PCI - How does the LogiCORE interface handle a target abort?
  4. AR# 52277: Soft Error Mitigation (SEM) v3.3 - Vivado 2012.3 produces CRITICAL WARNINGs which can be ignored

AR# 52277

|

Soft Error Mitigation (SEM) v3.3 - Vivado 2012.3 produces CRITICAL WARNINGs which can be ignored

Description

When using Soft Error Mitigation (SEM) IP with Vivado 2012.3, there are new CRITICAL WARNINGs that may be issued in relation to the XDC constraints.

Solution

When implementing SEM v3.3 IP in Vivado 2012.3, the tools will issue CRITICAL WARNINGs associated with the set_max_delay constraints in the example XDC, which are used to constrain the timing paths from the FRAME_ECC primitive to the SEM controller. The CRITICAL WARNINGs have the following form:


CRITICALWARNING: [Constraints 18-515] set_max_delay: Forcing 'example_cfg/example_frame_ecc/SYNDROME[3]' to be timing startpoint. There will be no hold timing paths from this pin unless set_min_delay is used to constrain the paths.

CRITICAL WARNING: [Constraints 18-515] set_max_delay: Forcing 'example_cfg/example_frame_ecc/ECCERRORSINGLE' to be timing startpoint. There will be no hold timing paths from this pin unless set_min_delay is used to constrain the paths.

These CRITICAL WARNINGs may be safely ignored. These CRITICAL WARNINGs are incorrectly issued by the tools, and it is not necessary to use the set_min_delay constraint on the path, or to take any further action.

Linked Answer Records

Master Answer Records

Answer Number Answer Title Version Found Version Resolved
44541 Soft Error Mitigation Controller - Release Notes and Known Issues for v1.1 to v3.4 N/A N/A
AR# 52277
Date 11/02/2012
Status Active
Type General Article
Tools
IP
People Also Viewed