• 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. Custom IC Design
  3. @(cross) missing crossing?Why is

Stats

  • Locked Locked
  • Replies 1
  • Subscribers 125
  • Views 306
  • 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

@(cross) missing crossing?Why is

TerryL
TerryL over 8 years ago

Hello:

Can someone please tell me what I am doing wrong?

code snippet"

$strobe("LPIN report: @%rs => ov_check V(lpin, vssa):%r, ov_negate:%r", $abstime, V(lpin, vssa), ov_negate);

@(cross((V(lpin, vssa) - ov_negate), -1))
begin
  ov = 0;
  $strobe("LPIN report: @%rs => ov_off ov_negate:%r", $abstime, ov_negate);
end

output:

LPIN report: @51.8604ms => ov_check V(lpin, vssa):61.3485m, ov_negate:54.75m

LPIN report: @52.8437ms => ov_check V(lpin, vssa):52.8994m, ov_negate:54.75m

LPIN report: @54.6437ms => ov_check  V(lpin, vssa):37.4326m,  ov_negate:54.75m

Why is the @cross code not triggered as V(lpin, vssa) crosses 54.75mv ???

What am I missing?

  • Cancel
  • TerryL
    TerryL over 8 years ago
    I figured this out:

    It was simply a tolerance issue.
    cross (expr1 [ , direction [ , time_tol [ , expr_tol ] ] ] )
    The default expr_tol is:
    1e-9 + reltol*max_value_of_the_signal
    which in this case was:
    1e-9 + 1m*550 = 550mV

    I changed the cross call to:
    @(cross((V(lpin, vssa) - ov_negate), -1, 1, 10m))
    and the cross was detected.
    • 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