Description
Looking at ORFS asap7/sha3, I see a lot of V2 cut spacing violations that take a number of iterations to resolve. The ones I looked at are all between cut shapes on the same net, where the net has multiple pins.
When routing to multiple pins, it looks like we route to the first pin, then create those tracks without adding any costs. Then we route to the second pin which could create cut spacing violations because there is no concept of cost for track to the first pin. What should we be doing? I guess not all costs will count because it's the same net, but some definitely will (like cut spacing).
Here's an example, which also shows some sub-optimal routing because we have 2 M2 (red) wires going to the 2 destinations on the left that could have been a single M2 wire. The cut spacing violation is towards the right where the two M2 (red) wires connected to the M3 (green):
Suggested Solution
No response
Additional Context
No response
Description
Looking at ORFS asap7/sha3, I see a lot of V2 cut spacing violations that take a number of iterations to resolve. The ones I looked at are all between cut shapes on the same net, where the net has multiple pins.
When routing to multiple pins, it looks like we route to the first pin, then create those tracks without adding any costs. Then we route to the second pin which could create cut spacing violations because there is no concept of cost for track to the first pin. What should we be doing? I guess not all costs will count because it's the same net, but some definitely will (like cut spacing).
Here's an example, which also shows some sub-optimal routing because we have 2 M2 (red) wires going to the 2 destinations on the left that could have been a single M2 wire. The cut spacing violation is towards the right where the two M2 (red) wires connected to the M3 (green):
Suggested Solution
No response
Additional Context
No response