• 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. viva settings ADEL and ADEXL

Stats

  • Locked Locked
  • Replies 3
  • Subscribers 125
  • Views 15961
  • 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

viva settings ADEL and ADEXL

Clidre
Clidre over 9 years ago

Hello,

I was used to ADEL and only recently I've been using ADEXL. I've noticed the viva settings I have for ADEL are not valid for ADEXL. More precisely, I have a custom_init file in my work directory with this code

callInitProc("viva")

envSetVal("viva.trace" "lineThickness" 'string "thick") 

So in ADEL I could see the waveforms thicker and save my eyes.. Now that I switched to ADEXL the waveforms plotted with the plot all button are thin! So it seems that custom_init file is not taken into account. Can you please tell me how can I set permanently the waveforms think in ADEXL? 

Thanks a lot!

  • Cancel
Parents
  • Andrew Beckett
    Andrew Beckett over 9 years ago

    Rather than trying to figure out the syntax, it's much easier to use the Display Resource Editor to do this.

    Use Tools->Display Resource Manager (in the CIW) and set it to Application: Virtuoso, Tech Lib: your technology library (whatever that is).

    Set the filter to "y" (to pick the layers y0, y1 etc) then click (one at a time) the layers y0, y1 etc and for each alter the line style to a thicker line (note, you may need to move your cursor over each of the columns in the display resource editor to get it to refresh - this is a consequence of it being an old Motif-based UI; in IC617 it has been replaced with a newer, cleaner, better, Qt-based UI). Make sure you hit Apply after each change.

    Then do File->Save and save the display.drf in your working directory.

    Do note that whilst this display.drf would then (most likely) be picked up when Virtuoso starts, many PDKs explicitly call drLoadDrf() to load their display.drf which would override yours if this is done via the technology library's libInit.il file. You could always re-load (via the Display Resource Editor File menu, or using drLoadDrf("./display.drf") your file after that has happened if this is an issue for you).

    Regards,

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • Andrew Beckett
    Andrew Beckett over 9 years ago

    Rather than trying to figure out the syntax, it's much easier to use the Display Resource Editor to do this.

    Use Tools->Display Resource Manager (in the CIW) and set it to Application: Virtuoso, Tech Lib: your technology library (whatever that is).

    Set the filter to "y" (to pick the layers y0, y1 etc) then click (one at a time) the layers y0, y1 etc and for each alter the line style to a thicker line (note, you may need to move your cursor over each of the columns in the display resource editor to get it to refresh - this is a consequence of it being an old Motif-based UI; in IC617 it has been replaced with a newer, cleaner, better, Qt-based UI). Make sure you hit Apply after each change.

    Then do File->Save and save the display.drf in your working directory.

    Do note that whilst this display.drf would then (most likely) be picked up when Virtuoso starts, many PDKs explicitly call drLoadDrf() to load their display.drf which would override yours if this is done via the technology library's libInit.il file. You could always re-load (via the Display Resource Editor File menu, or using drLoadDrf("./display.drf") your file after that has happened if this is an issue for you).

    Regards,

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Children
No Data

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