layer map table from LEF to GDS

[laurentc2]

Just to share my experience, I found 2 ways to setup the layer map table from LEF to GDS within the OpenROAD flow :

• in the klayout .lyt file, in the statement, you need this line to describe the layer_map table for each layer of the LEF tech file :
  layer_map('METAL1:1/0'; 'METAL1.LABEL:1/3'; 'METAL1.PIN:1/9'; 'METAL2:2/0'; 'METAL2.LABEL:2/3'; 'METAL2.PIN:2/9'; 'METAL3:3/0'; 'METAL3.LABEL:3/3'; 'METAL3.PIN:3/9'; 'VIA1:5/0'; 'VIA2:6/0'; 'OUTLINE:10/0')

• you can describe it in a separate file stated in the platform/my_tech/config.mk file with :
  export GDS_LAYER_MAP = $(PLATFORM_DIR)/layermap.txt
  then, you need to write that file : platform/my_tech/layermap.txt as described here :
  https://www.klayout.de/forum/discussion/2092/syntax-for-layoutoptions-lefdef-config-map-file :

  # KLayout LEF mapping file for my_tech
  DIEAREA ALL 10 0
  MET1 NET,VIA 1 0
  NAME MET1/PIN 1 3
  MET1 PIN 1 9
  MET2 NET,VIA 2 0
  NAME MET2/PIN 2 3
  MET2 PIN 2 9
  MET3 NET,VIA 3 0
  NAME MET3/PIN 3 3
  MET3 PIN 3 9
  VIA1 NET,VIA 5 0
  VIA2 NET,VIA 6 0
  OUTLINE LEFPIN 10 0
  

BRgds,
Laurent

[laurentc2]

For the sky130hs and sky130hs process and libraries, the only way I have found to get the proper GDS layers in the 6_final.gds is to add the file layermap.txt (below) in the platforms/sky130hs and platforms/sky130hs and add the following line :

export GDS_LAYER_MAP = ../../../../$(PLATFORM_DIR)/layermap.txt

in the files platforms/sky130hs/config.mk and platforms/sky130hd/config.mk

BRgds,
Laurent

layermap.txt file : also in : https://github.com/laurentc2/SKY130_for_KLayout/blob/main/layermap.txt :

KLayout mapping file for sky130

DIEAREA ALL 100 0

li1 NET,SPNET,VIA 67 20
NAME li1/PIN 67 5
li1 PIN,LEFPIN 67 16

mcon VIA 67 44
mcon PIN,LEFPIN 67 48

met1 NET,SPNET,VIA 68 20
NAME met1/PIN 68 5
met1 PIN,LEFPIN 68 16

via VIA 68 44
via PIN,LEFPIN 68 58

met2 NET,SPNET,VIA 69 20
NAME met2/PIN 69 5
met2 PIN 69 16

via2 VIA 69 44
via2 PIN,LEFPIN 69 58

met3 NET,SPNET,VIA 70 20
NAME met3/PIN 70 5
met3 PIN,LEFPIN 70 16

via3 VIA 70 44
via3 PIN 70 58

met4 NET,SPNET,VIA 71 20
NAME met4/PIN 71 5
met4 PIN 71 16

via4 VIA 71 44
via4 PIN,LEFPIN 71 48

met5 NET,SPNET,VIA 72 20
NAME met5/PIN 72 5
met5 PIN,LEFPIN 72 16