Stats

  • Locked Locked
  • Replies 2
  • Subscribers 127
  • Views 1038
  • Members are here 0
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Can't import techfile into abstract (IC6.1.4)

dura
No matter what I do to the techfile attached to the library I want to import into abstract generator, I can't get ERROR ABS-218 to go away:

"There are no vias specified in the technology file. Ensure that the selected constraint group has a ValidVias section or at least one via is specified in the standardViaDefs subsection of the viaDefs section in the technology file. In addition, ensure that the function argument is set to 'cut' for the via in the functions subsection of the layerRules section and then try again."

I am very clear in my techfile for the viaDefs, as well as specifying "cut" for the vias (though, I'm not clear which name "cut" needs to be set for, but it doesn't seem to matter which). Parts of the techfile are at the bottom of this post, but I haven't been able to find anything wrong.

I'd appreciate any ideas; this has become incredibly frustrating.

Note; for the rest of the .tf not shown, basically all of it came from a tech manager file dump (from inside virtuoso), there were just minor changes made to get all of the things abstract wanted in.

viaDefs(
standardViaDefs(
;( viaDefName layer1 layer2 (cutLayer cutWidth cutHeight [resistancePerCut])
; (cutRows cutCol (cutSpace))
; (layer1Enc) (layer2Enc) (layer1Offset) (layer2Offset) (origOffset)
; [implant1 (implant1Enc) [implant2 (implant2Enc) [well/substrate]]])
;( -------------------------------------------------------------------------- )
( M6_M5 METAL5 METAL6 ("VIA56" 0.3 0.3)
(1 1 (0.3 0.3))
(0.1 0.1) (0.5 0.5) (0.0 0.0) (0.0 0.0) (0.0 0.0)
; (more here not shown)
)
)


As well as:
layerRules(
functions(
( VIA56 "cut" 10 ) ; not sure if it should use cutLayer
( M6_M5 "cut" 10 ) ; or viaDefName
; plenty of others
)
)
Parents
  • Hi dura

    I think perhaps you are using IC613. IC614 has a clearer error message. I believe that you do not have a constraintGroup named "LEFDefaultRouteSpec" in your Virtuoso techfile. You will need to have a section similar to:

    ;( group       [override] )
    ;( -----    ---------- )
      ( "LEFDefaultRouteSpec"    nil
        interconnect(
         ( validLayers   (M8  M7  M6  M5  M4  M3  M2  M1  PO  ))
         ( validVias (M8_M7 M7_M6 M6_M5 M5_M4 M4_M3 M3_M2 M2_M1 M1_PO)) 
        ) ;interconnect

      )

    Please refer to COS solution 11518952 for the full explanation. 
    Please also refer to $CDSHOME/tools/dfII/samples/tutorial/abstract on
    the necessary info that the techfile should have.

    If you would like to use another constraintGroup instead of the default 
    "LEFDefaultRouteSpec", please add the following option in the 
    .abstract.options file which can be found in your library 
    directory:

    absSetOption("UseConstraintGroup" "yourCG")


    Best regards
    Quek
Reply
  • Hi dura

    I think perhaps you are using IC613. IC614 has a clearer error message. I believe that you do not have a constraintGroup named "LEFDefaultRouteSpec" in your Virtuoso techfile. You will need to have a section similar to:

    ;( group       [override] )
    ;( -----    ---------- )
      ( "LEFDefaultRouteSpec"    nil
        interconnect(
         ( validLayers   (M8  M7  M6  M5  M4  M3  M2  M1  PO  ))
         ( validVias (M8_M7 M7_M6 M6_M5 M5_M4 M4_M3 M3_M2 M2_M1 M1_PO)) 
        ) ;interconnect

      )

    Please refer to COS solution 11518952 for the full explanation. 
    Please also refer to $CDSHOME/tools/dfII/samples/tutorial/abstract on
    the necessary info that the techfile should have.

    If you would like to use another constraintGroup instead of the default 
    "LEFDefaultRouteSpec", please add the following option in the 
    .abstract.options file which can be found in your library 
    directory:

    absSetOption("UseConstraintGroup" "yourCG")


    Best regards
    Quek
Children
No Data

Community Guidelines

The Cadence Design Communities support Cadence users and technologists interacting to exchange ideas, news, technical information, and best practices to solve problems and get the most from Cadence technology. The community is open to everyone, and to provide the most value, we require participants to follow our Community Guidelines that facilitate a quality exchange of ideas and information. By accessing, contributing, using or downloading any materials from the site, you agree to be bound by the full Community Guidelines.