Stats

  • Locked Locked
  • Replies 5
  • Subscribers 126
  • Views 14031
  • 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

cb2oa, missing vias

stuso

 Hi guys, when i translate from 5141 to OA i have some missing vias in my IC6 layout. Our PDK providers have the same process in 5141 and OA so we have only converted the design libs.

Looking at my PDK providers OA techlib it looks more complex regards via definitions, compared to 5141. In the OA techfile i see a standard vias & viaSpecs definition. I tried to manually edit the tech file and put my missing via definitions into these 2 sections but i noticed when i import this hacked OA techfile and dump it back out again that the viaSpec part has reverted to default...i.e my edits are gone, but the standardVias i added are still there. Crucially however when i open the layout with my new hached techfile attached to the lib the vias are still missing. any advice greatly appreciated, if this is a complex process i'll log an SR.

Thanks

Stu

 

 

 

 

 

Parents

  •  Hi Stu,

    that really depends on the type of via you are using. Sounds like a custom via in your case which is
    missed in your target oa techlib. Is the via in question missed or does it just have a new/different name
    in the OA kit? Maybe you could try a via mapping with cdb2oa (check the docu).

    But to be save hand it over to support. I've done some cdb2oa calls and vias usually causing most of
    the trouble.

    Kind regards,
    Marc

Reply

  •  Hi Stu,

    that really depends on the type of via you are using. Sounds like a custom via in your case which is
    missed in your target oa techlib. Is the via in question missed or does it just have a new/different name
    in the OA kit? Maybe you could try a via mapping with cdb2oa (check the docu).

    But to be save hand it over to support. I've done some cdb2oa calls and vias usually causing most of
    the trouble.

    Kind regards,
    Marc

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.