Stats

  • Locked Locked
  • Replies 5
  • Subscribers 92
  • Views 1351
  • 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

need to access the first registers to I/O pads using db commands

abhaska

Hi all

 I need to access the first registers  to i/o pads using db commands... i've used procedures calling technique.. i'm able to access the

instances upto 2nd level.. but unable to further proceed  through the path as the instance are more between i/os and registers.

I've used a pointer  for the further access of the instances by recalling the procedure.. but the infinite loop prob occurs..

Can anyone pls help me in this regard..

Thanks

Arun

 

Parents
  • BobD

    I think your script is looping because it's calling itself from within the foreach loop.  When I wrote similar I had a lot of issues with infinite loops to and it was a tough to troubleshoot for sure.  You can see how I went about it in userAddMenuPullInstsToIos.tcl in the "userTraceIoTerm" and "userInstInsts" procs.  It was pretty ugly!

    You know, when I wrote that script it was a few years ago- before CTE-TCL commands existed in Encounter.  I think those commands might be much better suited to your need than performing the traversal manually yourself.  Being timing-engine related commands, the CTE-TCL commands have the ability to traverse through logic cones.  Like this:

    all_fanout
                  -from {<collection> | <object_list>}
                  [-levels <value>]
                  [-pin_levels <value>]
                  [-endpoints_only]
                  [-only_cells]
                  [> <file_name>] 

    For instance, in your case you could do:

    all_fanout -from [get_pins i0/Y] -levels 2 -endpoints_only -only_cells

    What do you think?

    For more information on CTE-TCL commands, see the Advanced Timing Tcl Scripting chapter of the Encounter User's Guide.

     

Reply
  • BobD

    I think your script is looping because it's calling itself from within the foreach loop.  When I wrote similar I had a lot of issues with infinite loops to and it was a tough to troubleshoot for sure.  You can see how I went about it in userAddMenuPullInstsToIos.tcl in the "userTraceIoTerm" and "userInstInsts" procs.  It was pretty ugly!

    You know, when I wrote that script it was a few years ago- before CTE-TCL commands existed in Encounter.  I think those commands might be much better suited to your need than performing the traversal manually yourself.  Being timing-engine related commands, the CTE-TCL commands have the ability to traverse through logic cones.  Like this:

    all_fanout
                  -from {<collection> | <object_list>}
                  [-levels <value>]
                  [-pin_levels <value>]
                  [-endpoints_only]
                  [-only_cells]
                  [> <file_name>] 

    For instance, in your case you could do:

    all_fanout -from [get_pins i0/Y] -levels 2 -endpoints_only -only_cells

    What do you think?

    For more information on CTE-TCL commands, see the Advanced Timing Tcl Scripting chapter of the Encounter User's Guide.

     

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.