Stats

  • Locked Locked
  • Replies 1
  • Subscribers 143
  • Views 735
  • 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

Device name including "-" in name is modified to "#2d" in cadence database

FrankvM

Hi,

We have a qualification flow to check a component library using skill commands. The problem we have with new libraries is that some devices includes a minus in their names (i.e. lv-ndmos). When creating the netlist (using skill function amsProcessCellViews) the directory names in the cadence database are modified into "cell_lv#2dndmos" instead of "cell_lv-2ndmos" (also not all filenames) where internal in the files the component name remains the name including the minus. When setup the simulation (using ocean: simulator, design, resultsDir and option command) this causes many problems because the simulation commands are trying to find the views at the wrong directories. Is it possible to switch of this namespace behaviour? I use cadence_ic5.

 

Best regards,

Frank

  • Hi Frank,

    The mapping (to the "LibraryUnix" namespace was to handle unusual characters unsupported (historically) in some file systems. It should not cause any problems - unfortunately from your description, I couldn't actually see where you really had a problem.

    I would suggest if there's really a flow problem caused by this mapping, you contact Cadence Customer Support via support.cadence.com with details on precisely when the flow breaks and what you have to do to break it. It's not familiar to me.

    To be honest, I would personally avoid having such characters in device names, as there are numerous tools that would have a problem with such a name and you're then dependent on mapping working properly everywhere (which it should of course, but the pragmatist in me would always say "why make life hard for myself if I don't have to?")

    Regards,

    Andrew.

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.