Skip to content

LEF/DEF topics #1307

Description

@klayoutmatthias

This ticket is collecting some feedback regarding LEF/DEF implementation:

  1. IOTIMINGS section needs to be parsed / skipped:
DESIGN test ;
IOTIMINGS 206 ;
- ( PIN a ) + RISE SLEWRATE 500 500 + FALL SLEWRATE 500 500 ;
- ( PIN b ) + RISE SLEWRATE 500 500 + FALL SLEWRATE 500 500 ;
- ( PIN c ) + RISE SLEWRATE 500 500 + FALL SLEWRATE 500 500
  + CAPACITANCE 250000 ;
END IOTIMINGS
END DESIGN
  1. COMPONENTS + UNPLACED appears to potentially have a point and rotation in some flavors -> in that case, place it.

  2. PIN labels are taken from NET, not PIN name

  3. reading hierarchical def files (blending?) - If there is no lef MACRO for one of the def files, use the def DIEAREA bounding box instead of the lef SIZE/ORIGIN

NOTE: right now, KLayout does not support hierarchical DEF as is. 'blending' is an option to blindly merge files. The included files do now know about details of the cell calls and vice versa.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions