Stats

  • Locked Locked
  • Replies 3
  • Subscribers 143
  • Views 13879
  • 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

leMarkNet() excluded purpose layers problem

Juan Pons

Hi,

I would like to use the Exclude Purpose info that it can be set in the leHiMarkNet() menu, but with leMarkNet() function. I tried to define this exclude purpose layers in the optionFile but leMarkNet() seems to not be using this info. I also tried to set the environment variable like this: envGetVal("layout" "markNetExcludePurposes" 'boolean t) but it does not work either.


This is the line I have in the option file that is supposed to define the exclude purpose layers:

excludePurposes(

blockage bridge boundary grid keepout label net nobias slot slotPath text track

)


I would appreciate any help.


Regards, Juan.

Parents
  • Juan Pons

    It is possible to use the exclude purpose information with leMarkNet() function? I need it to paint a net without painting for example a resistor which can be done if leMarkNet has into account the exclude purpose layer "keepout".

    I would really appreciate any help..

  • Amar Kumar
    in reply to Juan Pons

    Hi Juan,

    I am also facing the same problem. Looks like there is a bug with "leMarkNet" optionFile argument. It doesn't take every purpose given.

    So I jumped to "preXY(coordinaeList) leHiMarkNet()". I am modifying "<workarea>/.cadence/dfII/markNet/<pdk>/markNetOptions" file with required data and using the command to mark in the layout.

    It works for me.

    You can go through below post for more details.

    https://community.cadence.com/cadence_technology_forums/f/custom-ic-skill/38418/specifying-options-for-lemarknet-with-skill-interactively

    Regards,

    Amar

  • Andrew Beckett
    in reply to Amar Kumar

    This issue has been recently reported to R&D (I can reproduce it) via CCR 2188611 and will be fixed in the IC6.1.8/ICADMV18.1 ISR9 hot fix which is due to be available at the end of this month (January 2020).

    Andrew

Reply
  • Andrew Beckett
    in reply to Amar Kumar

    This issue has been recently reported to R&D (I can reproduce it) via CCR 2188611 and will be fixed in the IC6.1.8/ICADMV18.1 ISR9 hot fix which is due to be available at the end of this month (January 2020).

    Andrew

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.