Stats

  • Locked Locked
  • Replies 1
  • Subscribers 91
  • Views 14974
  • 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

Re: Given the net name how do weget to know for which pin it connects

NigH
Hi, here is an example of how to get the net,term and instance names connected to a specific term of an instance. So you can edit the below commands to do what you wish. ############################# set instName pd_core/start_comp_fine_conv/pga_pls_1__pls/full_d_reg set termName Q proc GetCapNet { termName instName } { set value "" set instPtr [dbGetInstByName $instName] set termPtr [dbGetTermByName $instPtr $termName] set netPtr [dbTermNet $termPtr] set netName [dbNetName $netPtr] set netCap [dbGetCapUnitStr [dbGetNetTotCap $netPtr]] lappend value $netPtr $netCap $netName return $value } proc getInstsConnectedToNet {netPtr} { set termPtrList [dbGet -p $netPtr.allTerms] foreach term $termPtrList { if {[dbGet $term.objType] == "instTerm"} { Puts " Instance: [dbGet $term.inst.name]" lappend insts [dbGet $term.inst.name] }} return $insts } ############################### Regards Nigel On Fri, 2010-10-15 at 03:37 -0700, ssuhas wrote: > Hi, > > I wanted to know if there is any command in SOCE to get to know if I > give the net name I want to know to which cell and its pin name it is > gettin connected to. > > Please let me know if there are any other means to find the above. > > > > Thanks in advance > > > > > > -- > View this message online at: > www.cadence.com/.../1179665.aspx > -- > You received this email because you subscribed to notifications for > the Cadence Digital Implementation Forum. To unsubscribe, log in, go > to forums, and change your forum subscriptions. > > www.cadence.com/.../ForumSubscriptions.aspx -- ================== Nigel Hughes AnaFocus Digital Design ------------------------------------ Av. Isaac Newton s/n, Pabellón de Italia, 7ª Planta, Ático Parque Tecnológico Isla de la Cartuja 41092 Sevilla, España ------------------------------------ Fax: +34 954 08 12 42 E-Mail: nigel@anafocus.com Web: http://www.anafocus.com

  • Most of the replies so far have been using FEDB side Tcl APIs.  The timing APIs also provide
    some functionality in this area:

     [DEV]encounter 3> set collectionOfPinObjects [get_pins -of_objects [get_nets clk_3_1]]
     0x4


    [DEV]encounter 4> query_objects $collectionOfPinObjects
    C3_2/A C3_1/Y

    If you want a more human readable report you can see source and
    sink information of the net by:

     

    (unfortunately this is going to look a bit bad)

    [DEV]encounter 5> report_net -net clk_3_1


    ###############################################################
    #  Generated by:      Cadence Encounter 10.11-e008_1
    #  OS:                Linux x86_64(Host ID pe-opt3.cadence.com)
    #  Generated on:      Tue Oct 19 18:04:28 2010
    #  Design:            test
    #  Command:           report_net -net clk_3_1
    ###############################################################
    Net Name                 : clk_3_1
    Number of Sources        : 1
    Number of Sinks          : 1
    Number of Bidis          : 0
    Source of parasitics     : None
    Net Capacitance          : 0.00000
    Total Capacitance        : 0.00187
         +---------------------------------------------------------------------------------------------------------+
         |                                                 Source                                                  |
         |---------------------------------------------------------------------------------------------------------|
         |               Pin                | Reduced |   Driver Load    |       Slew        |                     |
         |----------------------------------+---------+------------------+-------------------+---------------------|
         |  Name  |  Dir  |  Cell |   Cap   |  Model  |  Model |  Ctotal |  Rise   |  Fall   |        Phase        |
         |--------+-------+-------+---------+---------+--------+---------+---------+---------+---------------------|
         | C3_1/Y |  OUT  | BUFX1 | 0.00000 | Unknown | CTOTAL | 1.00000 | 0.08050 | 0.06400 | PH1(D)(P)(testMax)* |
         | C3_1/Y |  OUT  | BUFX1 | 0.00000 | Unknown | CTOTAL | 1.00000 | 0.08050 | 0.06400 | PH1(D)(N)(testMax)* |
         | C3_1/Y |  OUT  | BUFX1 | 0.00000 | Unknown | CTOTAL | 1.00000 | 0.08050 | 0.06400 | PH1(C)(P)(testMax)* |
         +---------------------------------------------------------------------------------------------------------+
         +--------------------------------------------------------------------------------------------------------------+
         |                                             Sinks for pin C3_1/Y                                             |
         |--------------------------------------------------------------------------------------------------------------|
         |                Pin                | Reduced Ne |       Delay       |       Slew        |                     |
         |-----------------------------------+------------+-------------------+-------------------+---------------------|
         |  Name  |  Dir  |  Cell  |   Cap   | Parameters |  Rise   |  Fall   |  Rise   |  Fall   |        Phase        |
         |--------+-------+--------+---------+------------+---------+---------+---------+---------+---------------------|
         | C3_2/A |  IN   | AND2X1 | 0.00187 |     -      | 1.30000 |         | 0.08050 |         | PH1(D)(P)(testMax)* |
         | C3_2/A |  IN   | AND2X1 | 0.00187 |     -      |         | 1.30000 |         | 0.06400 | PH1(D)(N)(testMax)* |
         | C3_2/A |  IN   | AND2X1 | 0.00187 |     -      | 1.30000 | 1.30000 | 0.08050 | 0.06400 | PH1(C)(P)(testMax)* |
         +--------------------------------------------------------------------------------------------------------------+

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.