Stats

  • Locked Locked
  • Replies 5
  • Subscribers 125
  • Views 15455
  • 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

BUG: Drawing path in Virtuoso 6.1.6 only possible in routing layers

Sheppy

Hello,

Today, a colleague noticed a change between Virtuoso 6.1.5 and 6.1.6:

In the former it was possible to draw a path in any layer available in the LSW, in the latter it is only possible to draw in routing layers.

In our process we have a layer that defines the lateral isolation (LATISO), which we have to draw as a path around (a group of) active components. With the new version (6.1.6) we are unable to do that, it (the path procedure) simply selects the first routing layer (in our case METAL1).

This is a big inconvenience and the default setting of Virtuoso is obviously wrong. The only change we made is the version of Virtuoso, the PDK is still the same version, even using the same layout-cell-view to test this.

One method of "fixing" this is to specify LATISO as one of the routing layers. This will then also allow automatic routers to use LATISO, which is somehting we don't want, so we're not going to do that.

My question:

Is there a setting available to turn-off this behavior?

By the way: we are developing the PDK ourselves, so if something has to be done in the technology file, that is possible as well. Although this is not the preferred solution since it is a change in Virtuoso behavior that is the issue.

With kind regards,

Sjoerd

edit: added the part about PDK

Parents
  • Sheppy

    Hi Colin,

    You are spot-on, and you just posted your reply a bit soner then I had time to update this post.

    What has happened:

    The bindkey "p" in 6.1.5 was used to create a path. In 6.1.6 it has been changed to create a wire.

    The solution:

    I re-mapped the bindkey for "p" back to creating a path. Creating a wire is now available with the "w" key (no-one used the zoom-history function of the "w" hey anyway).

    So yes, luckily, Cadence just  changed the behavior of the bindkey, not the actual function of the path creating procedure.

    Thanks for your response.

    With kind regards,

    Sjoerd

Reply
  • Sheppy

    Hi Colin,

    You are spot-on, and you just posted your reply a bit soner then I had time to update this post.

    What has happened:

    The bindkey "p" in 6.1.5 was used to create a path. In 6.1.6 it has been changed to create a wire.

    The solution:

    I re-mapped the bindkey for "p" back to creating a path. Creating a wire is now available with the "w" key (no-one used the zoom-history function of the "w" hey anyway).

    So yes, luckily, Cadence just  changed the behavior of the bindkey, not the actual function of the path creating procedure.

    Thanks for your response.

    With kind regards,

    Sjoerd

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.