Daniel Schultz

package with `detail_route`: https://fileshare.phytec.com/index.php/s/oJgdBLG4zrYeJe8 This chip has 13 M2.d violations - (1510.825,1634.96;1510.825,1635.16;1511.5,1635.16;1511.5,1634.96) - (1470.985,1547.6;1470.985,1547.8;1471.66,1547.8;1471.66,1547.6) - (1207.465,1544.24;1207.465,1544.44;1208.14,1544.44;1208.14,1544.24) - (1304.425,1328.36;1304.425,1328.56;1305.1,1328.56;1305.1,1328.36) - (1567.465,1226.72;1567.465,1226.92;1568.14,1226.92;1568.14,1226.72) - (572.905,1676.12;572.905,1676.32;573.58,1676.32;573.58,1676.12) - (772.585,1657.64;772.585,1657.84;773.26,1657.84;773.26,1657.64) - (764.905,1630.76;764.905,1630.96;765.58,1630.96;765.58,1630.76) - (750.985,1241.84;750.985,1242.04;751.66,1242.04;751.66,1241.84) - (738.23,768.92;738.23,769.12;738.905,769.12;738.905,768.92)...

@osamahammad21 any update on that topic? Can I help or test something?

@KrzysztofHerman yes, I will check the layout rules for 800x800 windows. What's the ideal density? Just in the middle of min/max?

> Part of the motivation to implement metal fill in OR was to allow future support for timing aware fill. If fill can be accomplished in OR it might be...

> If you require FEOL fill beyond the usual fill cells that would have to be done in KLayout. I'll wait on this PR for @KrzysztofHerman 's comments I'm gonna...

Latest update. - Dropped the fill.json patch. #2089 fixes the USE_FILL variable. - Added a sed command to `flow/Makefile` to proper support `sg13g2.map`. There should be no ORFS specific relative...

> @dnltz since we have to generate very specific filler in FEOL we have to use klayout so in a case of IHP platform lests use this tool for generating...

@KrzysztofHerman is this something we could update later? I would like to continue with the other pull-request to finally send ElemRV...

> As this PR is proceeding slowly I've opened #2171 to merge the RAM related files (only typ corner) to enable the user in #2099 Rebased to master and pinged...

@maliberty it failed to build an asap7 design. Still fine?