[resolved] Length matching constraint for buses show unknown

Upverter Support
#1

I’m not sure what to make of this one. Constraints (length matching) that specify nets that belong to a bus show “unknown” (just the busconnect portion) even when the net is completely connected.

I suspect that the “unknown” portion of the constraint violations are being pulled in from schematic heuristics although I don’t see why any length matching constraints per se would ever be defined as schematic specific.

I assume this to be a bug. I just ignore the constraint violations but, again, is this something that’s come up before or am I not understanding something about busses and bus connectors that produce this behavior?

#2

The reason that the bus connectors were showing up in the length matching violation is that it has terminals in the net that you’re trying to match. All of the terminals are considered as viable for length matching.

I’ve just pushed a change to exclude bus connector pins from evaluation in length matching rules.

#3

OK cool. Thanks for looking into it.

#4