Routing fails when the diearea origin is non-zero

[ax3ghazy]

Hello,

For an unconventional definition of the die area (e.g., with a positive offset of the origin), routing fails finding no tracks for certain pins.

This should be easy to replicate, and I have shared a couple of test cases privately; please let me know if you have questions.

This is possibly related to this, but I included a test case that shows that this is actually not the only issue.

Thanks.

[eder-matheus]

Hi, @ax3ghazy.
I found that the problem occurs in the global routing stage. Your testcase with a positive offset of the origin has objects out-of-die (like I/O pins), which leads FastRoute to map these objects to the global routing grid in a wrong way. The generated guides may be disconnected and/or not properly covering the pins.

The testcase where the die area origin is zero doesn't have this issue, and when I modified the die area with negative origin (e.g.: (-2000, -2000)) also works.

[eder-matheus]

@ax3ghazy If you can share with us how did you change the die area origin through the tools (at the floorplan, placement, etc.), it could help us to find where these objects out-of-die are being created.