• 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. antenna diodes

Stats

  • Locked Locked
  • Replies 3
  • Subscribers 90
  • Views 16614
  • 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

antenna diodes

archive
archive over 19 years ago

How would I add antenna diodes on the input pins in encounter. I can add on the instace pins but I am not able to add on the input toplevel pins.


Originally posted in cdnusers.org by usha
  • Cancel
  • archive
    archive over 19 years ago

    Can you explain what do you mean by "input toplevel pins". Any net in a design should connect to a instance pin. The instance can be a pad, std cell, mem macro or a analog macro.

    li siang


    Originally posted in cdnusers.org by lisiang
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • archive
    archive over 19 years ago

    I am talking about the top level I/O pins. Input /output to the platform from SOC.
    When I try to add antenna diodes to the top_level I/O pins the tool does not add it. What can be the reason?.
    Hope I have answered your doubt.

    Usha



    Originally posted in cdnusers.org by usha
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • archive
    archive over 19 years ago

    Hi usha,

    Until the attachDiode command is enhanced to allow IO pins in addition to instance pins, you'll need to use a script to attach the diode cells to the input IO pins.

    There's an example script shipped with the software that attaches diodes to all of the IO pins. It's called "userAddDiodesToIOs.tcl" and it is in the $ENCOUNTER/tools/fe/gift/scripts/tcl directory. Note that this script attaches the specified diode cell to *all* IO pins (input and output). You'd need to modify the script to only work on input pins to get your desired functionality.

    Here's a similar script that only operates on inputs:

    proc userAttachIoDiodesToInputs {diodeCellName} {
    Puts "Attaching diode cells to each block-level inputs ports..."
    set count 0
    set diodeCell [dbGetCellByName $diodeCellName]
    if {$diodeCell == "0x0"} {
    Puts "Couldn't find a diode cell in the library called \"$diodeCellName\""
    Puts "Quitting..."
    return
    }
    dbForEachCellFTerm [dbGetCellByName $diodeCellName] fterm {
    set diodeCellFTermName [dbFTermName $fterm]
    }
    dbForEachCellFTerm [dbHeadTopCell] fterm {
    if {[dbIsFTermInput $fterm]} {
    set net [dbFTermNet $fterm]
    if {$net > 0} {
    set netName [dbNetName $net]
    set ftermName [dbFTermName $fterm]
    set instName "${ftermName}_user_added_diode"
    addInst -cell $diodeCellName -inst $instName
    set ftermLoc [dbFTermLoc $fterm]
    set x [dbDBUToMicrons [dbLocX $ftermLoc]]
    set y [dbDBUToMicrons [dbLocY $ftermLoc]]
    placeInstance $instName $x $y -placed
    attachTerm $instName $diodeCellFTermName $netName
    incr count
    }
    }
    }
    refinePlace
    setBlockPlacementStatus -name *user_added_diode -status preplaced
    Puts "Done. Added $count diode cell(s)."
    }

    This script is intended to be run on a design that has the floorplan loaded prior to running placement.

    Hope this helps,
    Bob


    Originally posted in cdnusers.org by BobD
    • 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