Skip navigation
Communities
Up to Discussions in DRC, LVS, Parasitic Extraction - Calibre

This Question is Not Answered

1 "correct" answer available (5 pts) 1 "helpful" answer available (4 pts)
7,495 Views 2 Replies Last post: May 16, 2012 6:04 PM by andrewng RSS
andrewng Active
andrewng
45 posts since
Apr 16, 2009
Reply
Currently Being Moderated

May 16, 2012 2:40 AM

DFM PROPERTY in LVS command file

Dear All,

 

There is a message when I running LVS:

 

//  Applying licensing  policy...

//  calibrehlvs license  acquired.

//  calibrelvs license  acquired.

 

//  Warning: MGLS203:

//  License request for  calibreadp feature failed

 

//  Warning: MGLS203:

//  License request for  calibrexrc feature failed

 

//  Warning: MGLS203:

//  License request for  calibrexrccb feature failed

 

//  Error: The following  products could not be licensed sufficiently:

//  Error: - DFM  PROPERTY (from LVS)

Job  finished.

 

 

I am using a LVS command file which containing the command set below:

 

P_BM_NM_CHK_SYM = DFM PROPERTY MOM_SYMESH_MMKF_P BM_NM_CHK1 BM_NM_CHK2 BM_NM_CHK3 BM_NM_CHK4 BM_NM_CHK5 BM_NM_CHK6 BM_NM_CHK7 NF_CHK_SYM SIZE2 OVERLAP ABUT ALSO

[ BN1 = COUNT(BM_NM_CHK1) ] [ BN2 = COUNT(BM_NM_CHK2) ] [ BN3 = COUNT(BM_NM_CHK3) ] [ BN4 = COUNT(BM_NM_CHK4) ] [ BN5 = COUNT(BM_NM_CHK5) ] [ BN6 = COUNT(BM_NM_CHK6) ] [ BN7 = COUNT(BM_NM_CHK7) ] [ NF = COUNT(NF_CHK_SYM) ] [ A = AREA(SIZE2) ] [ MH = COUNT(SIZE2) ]

 

 

I understand that it need to use Calibre XRC license.

However, is there replacable command for it?

 

Thanks in advance!

Andrew

samantha_lizak Aficionado
samantha_lizak
106 posts since
May 29, 2008
Currently Being Moderated
May 16, 2012 2:23 PM in response to: andrewng
Re: DFM PROPERTY in LVS command file

Hi Andrew-

 

DFM Property on its own consumes a DRC license. However, from the 2012.1 Administrator's Guide section on ADP licenses, "A calibreadp license is also required  during connectivity extraction, in cases where a device_layer,  pin_layer, or auxiliary_layer in a Device statement is derived from a DFM Property operation."  (The xRC licenses are just substitutes if an ADP license is not available.)

 

Does the rule file use layers derived from a DFM Property operation?  If so, can you rewrite them to use slightly different inheritance?

 

If this isn't the case, it would help to know what version you are running -- now and again license requirements do change.

 

Hope this helps-

 

Sam.

andrewng Active
andrewng
45 posts since
Apr 16, 2009
Currently Being Moderated
May 16, 2012 6:04 PM in response to: samantha_lizak
Re: DFM PROPERTY in LVS command file

Dear Samantha,

 

Thanks for your reply!

I would like to understand it more details.

I am using a calibre version in 2008.3.

Why it also required ADP license?

Is it a new guide for the coming administration?

 

No matter what reason.

I found that it is used for calculate the MOM capacitor related values (number of fingers, the length of the capacitor, number of metal used).

I will try to use another command set to calculate these values.

Is there any suggestion from you?

 

 

The command are as below:

P_BM_NM_CHK_SYM = DFM PROPERTY MOM_SYMESH_MMKF_P BM_NM_CHK1 BM_NM_CHK2 BM_NM_CHK3 BM_NM_CHK4 BM_NM_CHK5 BM_NM_CHK6 BM_NM_CHK7 NF_CHK_SYM SIZE2 OVERLAP ABUT ALSO

[ BN1 = COUNT(BM_NM_CHK1) ] [ BN2 = COUNT(BM_NM_CHK2) ] [ BN3 = COUNT(BM_NM_CHK3) ] [ BN4 = COUNT(BM_NM_CHK4) ] [ BN5 = COUNT(BM_NM_CHK5) ] [ BN6 = COUNT(BM_NM_CHK6) ] [ BN7 = COUNT(BM_NM_CHK7) ] [ NF = COUNT(NF_CHK_SYM) ] [ A = AREA(SIZE2) ] [ MH = COUNT(SIZE2) ]

 

DEVICE MOMCAPS_SYMESH_MMKFEHV MOM_SYMESH_MMKF_P_b1 MOM_SYMESH_P1_b1(PLUS1) MOM_SYMESH_M1_b1(MINUS1) MOM_SYMESH_P2_b1(PLUS2) MOM_SYMESH_M2_b1(MINUS2) HVPW_P(B) <P_BM_NM_CHK_SYM>

 

CMACRO MAC_MOM_SYMESH P_BM_NM_CHK_SYM

 

DMACRO MAC_MOM_SYMESH BM_NM_CHK_SYM {

[

#IFDEF PEXRUN_MC_HSPICE

  PROPERTY NF,MH,NM,MIS_FLAG,PRESIM_FLAG,L,CAP //,BM

  MIS_FLAG = 1

#ELSE

  #IFDEF PEXRUN

   PROPERTY NF,MH,NM,PRESIM_FLAG,L,CAP //,BM

  #ELSE

   #IFDEF RCFLOW_CCI

    PROPERTY NF,MH,NM,PRESIM_FLAG,L,CAP //,BM

   #ELSE

    #IFDEF RCFLOW_ACI

     PROPERTY NF,MH,NM,PRESIM_FLAG,L,CAP //,BM

    #ELSE

     PROPERTY NF,MH,NM,PRESIM_FLAG,L,CAP //,BM

    #ENDIF

   #ENDIF

  #ENDIF

#ENDIF

PRESIM_FLAG = 0

METAL_RING_FLAG = 0

WB = 0.14E-6

W = 0.14E-6

S = 0.14E-6

cho_tb_bm1 = 683e-18

cv_tb_bm1 = 50e-18

ratio_bm1 = 1.2

BN1 = DFM_NUM_VAL(BM_NM_CHK_SYM,"BN1")

BN2 = DFM_NUM_VAL(BM_NM_CHK_SYM,"BN2")

BN3 = DFM_NUM_VAL(BM_NM_CHK_SYM,"BN3")

BN4 = DFM_NUM_VAL(BM_NM_CHK_SYM,"BN4")

BN5 = DFM_NUM_VAL(BM_NM_CHK_SYM,"BN5")

BN6 = DFM_NUM_VAL(BM_NM_CHK_SYM,"BN6")

MH = DFM_NUM_VAL(BM_NM_CHK_SYM,"MH")/2

NF = DFM_NUM_VAL(BM_NM_CHK_SYM,"NF")/(MH*2)

A = DFM_NUM_VAL(BM_NM_CHK_SYM,"A")

L = A/((NF*2-1)*0.14)*1e-6/(MH*2)

bm1 = 0

bm2 = 0

bm3 = 0

bm4 = 0

bm5 = 0

bm6 = 0

bm7 = 0

BM = 0

IF(BN1 == 1){

  bm1 = 1

  BM = 1

}else{

  IF(BN2 == 1){

   bm2 = 1

   BM = 2

  }else{

   IF(BN3 == 1){

    bm3 = 1

    BM = 3

   }else{

    IF(BN4 == 1){

     bm4 = 1

     BM = 4

    }else{

     IF(BN5 == 1){

      bm5 = 1

      BM = 5

     }

    }

   }

  }

}

m3 = 0

m4 = 0

m5 = 0

m6 = 0

m7 = 0

NM = BN1 +  BN2 + BN3 + BN4 + BN5 + BN6

IF(NM == 7){

  m7 = 1

}else{

  IF(NM == 6){

   m6 = 1

  }else{

   IF(NM == 5){

    m5 = 1

   }else{

    IF(NM == 4){

     m4 = 1

    }else{

     IF(NM == 3){

      m3 = 1

     }

    }

   }

  }

}

factor = 1*m6+0.842*m5+0.672*m4+0.505*m3

C2 = ((L/1E-6*((NF-3)*cho_tb_bm1 + 2*ratio_bm1*cho_tb_bm1) + (NF-2) *cv_tb_bm1) * factor)

CAP = C2*MH

]

}

 

    TRACE PROPERTY MOMCAPS_SYMESH_MMKFEHV NF NF momNF_Tol

    TRACE PROPERTY MOMCAPS_SYMESH_MMKFEHV L L momL_Tol

    TRACE PROPERTY MOMCAPS_SYMESH_MMKFEHV NM NM momNM_Tol

    TRACE PROPERTY MOMCAPS_SYMESH_MMKFEHV MH MH momMH_Tol

 

Andrew

More Like This

  • Retrieving data ...

Bookmarked By (0)