Stats

  • Replies 8
  • Subscribers 17
  • Views 11924
  • Members are here 0
More Content

Inconsistent behavior of axlDBCloak?

migrg

Hi everyone,

I'm creating an array of vias using axlDBCloak. I realized that a number of my vias (seems like they are located in the same X coordinate) don't have a net associated. My code works as follows:

via_id=mrCreateViaPadstack() -> this function creates the padstack, this works fine all the time
axlDBCloak( 'mrCreateAllViasCloak(via_id))

procedure( mrCreateAllViasCloak(via_id)
...
...
axlDBCreateVia(via_id, -1497.7:10647.9, "VSS")
...

When I don't run axlDBCloak and just use the axlDBCreateVia command separately in the skill terminal everything works well. I am creating several hundreds of vias with axlDBCloak. Is there any limitation in this function? is it possible that it will 'misbehave' if it has to execute too many database accesses?

Help appreciated! Thanks!

  • eDave

    I have had problems with this too. It's to do with when you delete the original via. I have found that deleting the original via, before creating the next one, helps.

  • migrg
    in reply to eDave

    Hi Dave, thanks for the quick answer. What do you mean delete the original via? I create a different via with each call to axlDBCreateVia. Do you mean create one via, then delete it, then create it again?

  • eDave
    in reply to migrg

    I assumed that you were replacing existing vias - which is what I was doing. If I place a new via on top of the old one and then delete the old via, the connections are "confused". I think a Cadence expert can best describe the effects of using cloaking.

  • migrg

    the problem went away by making several 'smaller' calls to axlDBCloak instead. There is some bug with this function and the number of transactions it can queue that is not documented.

  • migrg

    actually I take that back, now I'm calling 100 vias at a time and it's not working. Is there any way to 'flush' the database write after calling axlDBCloak, before calling it again? This is getting really annoying...

Cadence Guidelines

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.