Stats

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

Hierarchy delimiter and path suddenly changes in PSF

BradW
Hey all, I'm still stuck running in the 5.1 stream and using WaveView. Recently all my ocean scripts stopped working when trying to plot/access certain device currents. When I looked into it, it appears that the paths have changed in the psf file. For example, I was using i(“/Iload/L0/PLUS”) and now the same data is accessed i(“Iload:L0:1”) I've seen this in the past but I've never figured out what I did or what happened to make the paths changed. Anyone have an idea? Right now I'm using aps as my simulator but I've used spectre and seen the same thing. When I use the "outputs" command it still lists the "/Iload/L0/PLUS" node as being available but when I go use the waveform it can't find it. Thanks for any help
Parents

  • Do you really mean WaveView (which is a Synopsys viewer), or Wavescan?

    Anyway, what you're seeing is that you're unable to use "schematic" names (any name starting with a / is treated as a schematic name, and you give each element in the hierarchical name by whatever it's called in the schematic), and are having to use "netlist" names (i.e. the names which actually appear in the netlist - which may get mapped if reserved words etc are used) including the simulator's hierarchy delimiter (which is ".").

    If you can't use the schematic names, it generally means that it can't find the map or amap directories in the netlist directory - these are used to do the schematic to netlist (and vice-versa) mapping. To find this mapping, it looks in the runObjFile in the psf directory, for an entry saying netlistDir. If the runObjFile isn't found, it simply looks for "../netlist" (I believe) from the psf directory - and looks for amap within there.

    So usually this is because the results have been copied elsewhere, or the simulation has been run standalone and the results stored somewhere other than the usual ADE structure, or the amap dir omitted when the netlist directory was copied. Something like that.

    We (as Application Engineers) often see this kind of problem because customers send us their OCEAN script and the netlist file, and nothing else - so we end up having to modify all the signal references to use netlist names to make a testcase work.

    Hope that helps to pin-point the problem.

    Regards,

    Andrew.

Reply

  • Do you really mean WaveView (which is a Synopsys viewer), or Wavescan?

    Anyway, what you're seeing is that you're unable to use "schematic" names (any name starting with a / is treated as a schematic name, and you give each element in the hierarchical name by whatever it's called in the schematic), and are having to use "netlist" names (i.e. the names which actually appear in the netlist - which may get mapped if reserved words etc are used) including the simulator's hierarchy delimiter (which is ".").

    If you can't use the schematic names, it generally means that it can't find the map or amap directories in the netlist directory - these are used to do the schematic to netlist (and vice-versa) mapping. To find this mapping, it looks in the runObjFile in the psf directory, for an entry saying netlistDir. If the runObjFile isn't found, it simply looks for "../netlist" (I believe) from the psf directory - and looks for amap within there.

    So usually this is because the results have been copied elsewhere, or the simulation has been run standalone and the results stored somewhere other than the usual ADE structure, or the amap dir omitted when the netlist directory was copied. Something like that.

    We (as Application Engineers) often see this kind of problem because customers send us their OCEAN script and the netlist file, and nothing else - so we end up having to modify all the signal references to use netlist names to make a testcase work.

    Hope that helps to pin-point the problem.

    Regards,

    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.