Using a regex for set_io_pin_constraint -names

[oharboe]

How can I get a list of the names of the pins, such that I can pass in a list of names to set_io_pin_constraint that match a regex?

Something like:

set_io_pin_constraint ... -names [lsearch -all -inline $pins $regex]

Answering myself..

This will do it:

proc match_pins { regex } {
    set pins {}
    foreach pin [sta::find_port_pins_matching $regex 1 0] {
        lappend pins [get_property $pin name]
    }
    return $pins
}

set_io_pin_constraint -region top:* -pin_names [match_pins someregex]

[maliberty]

See discussion in #2839

[oharboe]

Can you give me a bit more precise pointer? I don't see an example of enumerating the pins of the design.

[maliberty]

The point being there isn't a default mechanism right now but rather a discussion of how best to do it. get_pins will return a list of pins objects rather than names. You could convert them to names or you could use the odb APIs to traverse the db yourself.

[oharboe]

I see. So it would seem that the capability exists, all that is lacking is an example of how to use it. I did try to grep ORFS for a get_pins example or docs, but I didn't find anything.

[oharboe]

I tried:

foreach net [get_nets *] {
    foreach pin [get_pins -of_object $net] {
        puts "pin [get_property $pin full_name]"
    }
}

But I don't get the Verilog pin names, I get something else:

...
pin _10198_/E
pin _10235_/C
pin _10432_/E
pin _10575_/C
pin _10718_/E
pin _11435_/E
pin _11722_/E
pin _12008_/E
pin _12151_/E
pin _12294_/E
pin _11578_/B
pin _10861_/C
...

[oharboe]

This will do it:

set_io_pin_constraint ... -names [sta::find_port_pins_matching $regex 1 0]

[maliberty]

What do you mean by "verilog pin names"? Those look ok to me for instance pins

[oharboe]

What do you mean by "verilog pin names"? Those look ok to me for instance pins

These are the same names as the Verilog module input outputs, so "Verilog names"

[maliberty]

Perhaps you want get_ports? I would call those port names as Verilog includes the instance pins as well.

[oharboe]

get_ports requires an argument, what should I pass it?

I couldn't find an example in ORFS.

[maliberty]

same as get_pins in your example above. get_pins is for instance pins and get_ports is for top level ports

[oharboe]

Like so?

proc match_pins { regex } {
    set pins {}
    foreach pin [get_ports -regexp $regex] {
        lappend pins [get_property $pin name]
    }
    return $pins
}

set_io_pin_constraint -region right:* -pin_names [match_pins io_foo.*]

[maliberty]

lgtm

[oharboe]

I havent found a more elegant idiomatic way to articulate this in Tcl. I wanted to map get_property function onto the list, so I dont have to introduce the match_pin function. That is an orthogonal Tcl language question though.