• 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. PCB Design
  3. ibis to dml error

Stats

  • Locked Locked
  • Replies 1
  • Subscribers 164
  • Views 13917
  • Members are here 0
More Content
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

ibis to dml error

ChrisZhao
ChrisZhao over 12 years ago

Hi experts,

I was trying to make a postroute simulation, I had a problem when I translated IBIS model to DML model. I pasted both warnings in parse, errors during translation, and part of ibis model

////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////// 

Results of the most recent parse:
IBISCHK5 V5.0.3

Checking D:\Projects\SPB_Data\Simulation_models\tusb1310a.ibs for IBIS 4.2 Compatibility...

NOTE (line 1017) - Pulldown Minimum data is non-monotonic
NOTE (line 1019) - Pulldown Typical data is non-monotonic
NOTE (line 1019) - Pulldown Maximum data is non-monotonic
NOTE (line 1266) - Pullup Minimum data is non-monotonic
NOTE (line 1277) - Pullup Typical data is non-monotonic
NOTE (line 1281) - Pullup Maximum data is non-monotonic
NOTE (line 1918) - Pulldown Minimum data is non-monotonic
NOTE (line 1920) - Pulldown Typical data is non-monotonic
NOTE (line 1920) - Pulldown Maximum data is non-monotonic
NOTE (line 2167) - Pullup Minimum data is non-monotonic
NOTE (line 2178) - Pullup Typical data is non-monotonic
NOTE (line 2182) - Pullup Maximum data is non-monotonic
NOTE (line 2855) - Pulldown Maximum data is non-monotonic
NOTE (line 2857) - Pulldown Typical data is non-monotonic
NOTE (line 2861) - Pulldown Minimum data is non-monotonic
NOTE (line 3061) - Pullup Minimum data is non-monotonic
NOTE (line 3073) - Pullup Typical data is non-monotonic
NOTE (line 3082) - Pullup Maximum data is non-monotonic
NOTE (line 3530) - Pulldown Maximum data is non-monotonic
NOTE (line 3532) - Pulldown Typical data is non-monotonic
NOTE (line 3536) - Pulldown Minimum data is non-monotonic
NOTE (line 3744) - Pullup Minimum data is non-monotonic
NOTE (line 3755) - Pullup Typical data is non-monotonic
NOTE (line 3764) - Pullup Maximum data is non-monotonic
NOTE (line 4174) - Pulldown Minimum data is non-monotonic
NOTE (line 4175) - Pulldown Typical data is non-monotonic
NOTE (line 4176) - Pulldown Maximum data is non-monotonic
NOTE (line 4433) - Pullup Minimum data is non-monotonic
NOTE (line 4442) - Pullup Typical data is non-monotonic
NOTE (line 4450) - Pullup Maximum data is non-monotonic
NOTE (line 5076) - Pulldown Minimum data is non-monotonic
NOTE (line 5077) - Pulldown Typical data is non-monotonic
NOTE (line 5078) - Pulldown Maximum data is non-monotonic
NOTE (line 5335) - Pullup Minimum data is non-monotonic
NOTE (line 5344) - Pullup Typical data is non-monotonic
NOTE (line 5352) - Pullup Maximum data is non-monotonic
NOTE (line 9245) - Pulldown Typical data is non-monotonic
NOTE (line 9245) - Pulldown Minimum data is non-monotonic
NOTE (line 9245) - Pulldown Maximum data is non-monotonic
NOTE (line 9339) - Pullup Maximum data is non-monotonic
NOTE (line 9342) - Pullup Typical data is non-monotonic
NOTE (line 9349) - Pullup Minimum data is non-monotonic
NOTE (line 10047) - Pulldown Typical data is non-monotonic
NOTE (line 10047) - Pulldown Minimum data is non-monotonic
NOTE (line 10047) - Pulldown Maximum data is non-monotonic
NOTE (line 10142) - Pullup Maximum data is non-monotonic
NOTE (line 10146) - Pullup Typical data is non-monotonic
NOTE (line 10151) - Pullup Minimum data is non-monotonic
NOTE (line 11307) - Pulldown Typical data is non-monotonic
NOTE (line 11307) - Pulldown Minimum data is non-monotonic
NOTE (line 11307) - Pulldown Maximum data is non-monotonic
NOTE (line 11402) - Pullup Maximum data is non-monotonic
NOTE (line 11406) - Pullup Typical data is non-monotonic
NOTE (line 11411) - Pullup Minimum data is non-monotonic
NOTE (line 12182) - Pulldown Typical data is non-monotonic
NOTE (line 12182) - Pulldown Minimum data is non-monotonic
NOTE (line 12182) - Pulldown Maximum data is non-monotonic
NOTE (line 12271) - Pullup Maximum data is non-monotonic
NOTE (line 12273) - Pullup Typical data is non-monotonic
NOTE (line 12276) - Pullup Minimum data is non-monotonic
NOTE (line 13017) - Pulldown Typical data is non-monotonic
NOTE (line 13017) - Pulldown Minimum data is non-monotonic
NOTE (line 13017) - Pulldown Maximum data is non-monotonic
NOTE (line 13109) - Pullup Maximum data is non-monotonic
NOTE (line 13113) - Pullup Typical data is non-monotonic
NOTE (line 13118) - Pullup Minimum data is non-monotonic
NOTE (line 13776) - Pulldown Typical data is non-monotonic
NOTE (line 13776) - Pulldown Minimum data is non-monotonic
NOTE (line 13776) - Pulldown Maximum data is non-monotonic
NOTE (line 13871) - Pullup Maximum data is non-monotonic
NOTE (line 13875) - Pullup Typical data is non-monotonic
NOTE (line 13880) - Pullup Minimum data is non-monotonic
WARNING - Model usb3_WODE: The [Rising Waveform]
      with [R_fixture]=50 Ohms and [V_fixture_max]=1.155V
      has MAX column DC endpoints of  0.60V and  1.12v, but
      an equivalent load applied to the model's I-V tables yields
      different voltages ( 0.61V and  1.12V),
      a difference of  2.74% and  0.09%, respectively.
WARNING - Model usb3_WODE: The [Falling Waveform]
      with [R_fixture]=50 Ohms and [V_fixture_max]=1.155V
      has MAX column DC endpoints of  0.60V and  1.12v, but
      an equivalent load applied to the model's I-V tables yields
      different voltages ( 0.61V and  1.12V),
      a difference of  2.66% and  0.06%, respectively.
WARNING - Combined Pullup for Model: usb2_LS_RC Minimum data is non-monotonic
WARNING - Combined Pullup for Model: usb2_LS_R Minimum data is non-monotonic

Errors  : 0
Warnings: 4

File Passed

END OF IBISCHK COMMAND OUTPUT

READING IBIS FILE D:\Projects\SPB_Data\Simulation_models\tusb1310a.ibs

ERROR @line 45: Syntax error after parsing the token <Package Model> :
    The previous token began on line 45 and was <[>

RUNNING DMLCHECK for D:\Projects\SPB_Data\Simulation_models\tusb1310a.dml


Translation failed due to IBIS2DML errors.
Output saved as D:\Projects\SPB_Data\Simulation_models\tusb1310a.dml.txt.
Run ibis2signoise -d, a DML will be generated.
Examine it with line numbers from the log message.
////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////

The setence starts with "[Package Model]" is line 45. 

////////////////////////////////////////////

                - Please use [Package Model] for system analysis
                - Removed parasitics from [Pin] for POWER and GND pins
                as they do not accurately represent pwr pkg parasitics
                [Package Model] includes mutuals and selfs more appropriately
                - C_comp although listed in numerical order of value are obtained from varying
                PVT conditions. For PVT conditions for each specific value refer the buffer
                description under respective [Model]. IBIS model user is responsible for using
                appropriate C_comp to simulate for Signal Integrity

////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////

Three questions:

a) What is the influence of "NOTE (line 1017) - Pulldown Minimum data is non-monotonic," ?

b) About the error, how do I to solve it?

c) I guessed it might be syntax error, is there any guideline in Allegro' documentation?

Thanks.

Chris
"

  • Cancel
  • ChrisZhao
    ChrisZhao over 12 years ago

    I found the error located at the part of [notes] in IBIS model, so I deleted all under [notes]. Then I can translate from IBIS to DML.

    Any comments are welcomed.

    Chris

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Cadence Guidelines

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