Hey Professor. How can we identify intuitively (without tools) which net is aggressor and which is victim? Does it depend on frequency or any other parameters?
Hi, So, my intuitive, straightforward answer is that if two nets are routed close to each other for a substantial distance, then there is a good chance that an SI issue will occur. But it's very hard to actually see this without a tool, since you have lots (...millions... billions...) of nets with different segments and so forth. Which is a victim and which is aggressor. Well, first of all, they can "trade places". In other words, one of them can be the aggressor to the other for a certain timing path and can be the victim for a different timing path. But usually, the victim will be the one that is weakly driven, which can be seen as a slow transition on the net. You can look at DRVs - max capacitance and max transition (and max fanout) reports to find high potential candidates for SI problems. But really, just use the tool...
Very nice...
Thank you! Cheers!
Hey Professor. How can we identify intuitively (without tools) which net is aggressor and which is victim? Does it depend on frequency or any other parameters?
Hi,
So, my intuitive, straightforward answer is that if two nets are routed close to each other for a substantial distance, then there is a good chance that an SI issue will occur. But it's very hard to actually see this without a tool, since you have lots (...millions... billions...) of nets with different segments and so forth.
Which is a victim and which is aggressor. Well, first of all, they can "trade places". In other words, one of them can be the aggressor to the other for a certain timing path and can be the victim for a different timing path. But usually, the victim will be the one that is weakly driven, which can be seen as a slow transition on the net. You can look at DRVs - max capacitance and max transition (and max fanout) reports to find high potential candidates for SI problems. But really, just use the tool...