• Skip to main content
  • Skip to search
  • Skip to footer
Cadence Home
  • This search text may be transcribed, used, stored, or accessed by our third-party service providers per our Cookie Policy and Privacy Policy.

  1. Community Forums
  2. Digital Implementation
  3. justification for Warnings :SETUP HIGH VIOLATION,SETUP LOW...

Stats

  • Locked Locked
  • Replies 1
  • Subscribers 92
  • Views 1078
  • Members are here 0
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

justification for Warnings :SETUP HIGH VIOLATION,SETUP LOW VIOLATION ,SETUP X VIOLATION ,HOLD HIGH VIOLATION ,HOLD LOW VIOLATION ,HOLD X VIOLATION.

ASHU BHAI
ASHU BHAI over 10 years ago

Hi All,

I am getting the Following Warnings in the logs for the test runs.

Can anyone  please provide justification of these warnings as to why they occur and justification for same?

 

SETUP HIGH VIOLATION

ASSERT/WARNING   (time 138746564 PS) from procedure @ieee.VITAL_Timing:ReportViolation
  _MGIOL SETUP High VIOLATION ON DI WITH RESPECT TO CLK;
  Expected := 0.933 NS; Observed :=   0.39 NS; At : 138746.564 NS

ASSERT/WARNING   (time 837385656 PS) from procedure @ieee.VITAL_Timing:ReportViolation
  SLOGICB SETUP High VIOLATION ON DI0 WITH RESPECT TO CLK;
  Expected := 0.072 NS; Observed :=   0.071 NS; At : 837385.656 NS

SETUP LOW VIOLATION

ASSERT/WARNING   (time 838802564 PS) from procedure @ieee.VITAL_Timing:ReportViolation
  MGIOL SETUP Low VIOLATION ON   DI WITH RESPECT TO CLK;
  Expected := 0.933 NS; Observed :=   0.228 NS; At : 838802.564 NS

ASSERT/WARNING   (time 837385656 PS) from procedure @ieee.VITAL_Timing:ReportViolation
  SLOGICB SETUP Low VIOLATION ON DI1   WITH RESPECT TO CLK;
  Expected := 0.072 NS; Observed :=   0.056 NS; At : 837385.656 NS

SETUP X VIOLATION

ASSERT/WARNING   (time 839119256 PS) from procedure @ieee.VITAL_Timing:ReportViolation
  MGIOL SETUP   X VIOLATION ON DI WITH RESPECT TO CLK;
  Expected := 0.933 NS; Observed :=   0.247 NS; At : 839119.256 NS

ASSERT/WARNING   (time 839835852 PS) from procedure @ieee.VITAL_Timing:ReportViolation
  SLOGICB SETUP   X VIOLATION ON DI1 WITH RESPECT TO CLK;
  Expected := 0.072 NS; Observed := 0.021   NS; At : 839835.852 NS

HOLD HIGH VIOLATION

ASSERT/WARNING (time 1273470731 PS) from procedure @ieee.VITAL_Timing:ReportViolation
MGIOL HOLD High VIOLATION ON DI WITH RESPECT TO CLK;
  Expected := 0.099 NS; Observed :=   0.063 NS; At : 1273470.731 NS

ASSERT/WARNING   (time 1189163797 PS) from procedure @ieee.VITAL_Timing:ReportViolation
  SLOGICB HOLD High VIOLATION ON DI0 WITH RESPECT TO CLK;
  Expected := 0.002 NS; Observed :=   0.001 NS; At : 1189163.797 NS

HOLD   LOW VIOLATION

ASSERT/WARNING   (time 1230250575 PS) from procedure @ieee.VITAL_Timing:ReportViolation
 MGIOL HOLD Low VIOLATION   ON DI WITH RESPECT TO CLK;
  Expected := 0.099 NS; Observed :=   0.031 NS; At : 1230250.575 NS

ASSERT/WARNING   (time 1191263965 PS) from procedure @ieee.VITAL_Timing:ReportViolation
  SLOGICB HOLD Low VIOLATION ON DI0 WITH   RESPECT TO CLK;
  Expected := 0.002 NS; Observed :=   0.001 NS; At : 1191263.965 NS

HOLD   X VIOLATION

ASSERT/WARNING   (time 1273437397 PS) from procedure @ieee.VITAL_Timing:ReportViolation
 MGIOL HOLD   X VIOLATION ON DI WITH RESPECT TO CLK;
  Expected := 0.099 NS; Observed :=   0.065 NS; At : 1273437.397 NS

ASSERT/WARNING   (time 873905245 PS) from procedure @ieee.VITAL_Timing:ReportViolation
  SLOGICB HOLD   X VIOLATION ON DI0 WITH RESPECT TO CLK;
  Expected := 0.002 NS; Observed :=   0.001 NS; At : 873905.245 NS

Thanks and Regards,
Ashutosh Bisht

  • Cancel
  • DESIGNARCHITEC
    DESIGNARCHITEC over 9 years ago
    Hey, what is the clock frequency? Is it the same clock or different clock? I m asking regarding setup.
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel

Community Guidelines

The Cadence Design Communities support Cadence users and technologists interacting to exchange ideas, news, technical information, and best practices to solve problems and get the most from Cadence technology. The community is open to everyone, and to provide the most value, we require participants to follow our Community Guidelines that facilitate a quality exchange of ideas and information. By accessing, contributing, using or downloading any materials from the site, you agree to be bound by the full Community Guidelines.

© 2025 Cadence Design Systems, Inc. All Rights Reserved.

  • Terms of Use
  • Privacy
  • Cookie Policy
  • US Trademarks
  • Do Not Sell or Share My Personal Information