• Skip to main content
  • Skip to search
  • Skip to footer
Cadence Home
  • This search text may be transcribed, used, stored, or accessed by our third-party service providers per our Cookie Policy and Privacy Policy.

  1. Community Forums
  2. Digital Implementation
  3. Voltus - Unable to get correct scope string for read_activity_file...

Stats

  • Locked Locked
  • Replies 0
  • Subscribers 92
  • Views 855
  • 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

Voltus - Unable to get correct scope string for read_activity_file -scope command when using generate loop in hierarchy above DUT

frank2023
frank2023 over 1 year ago

Using Voltus v21.18-s100_1, and all other tools are v21.x

Hello all, I'm attempting to run static and dynamic rail analysis on my design using an SHM database as an activity input. I've been having trouble figuring out what the -scope argument string should be for the read_activity_file command when loading in the SHM database. So far with all my attempts I've been getting this error:

** INFO: (VOLTUS_POWR-3482): SHM: Provided scope name: {tb_YODAWG/gen_yodawg[0]/yodawg}

** INFO: (VOLTUS_POWR-3494): SHM: Scale used: 0.001 ns.

** INFO: (VOLTUS_POWR-3484): SHM: Scope not found, please review read_activity_file -scope <name>


Filename (activity) :
./power_analysis/power_shm/digital_core_top/digital_core_top.trn
Names in file that matched to design : 0/0
Annotation coverage for this file
(Unique nets matched/Total nets) : 0/132763 = 0%


Total annotation coverage for all files of type SHM: 0/132763 = 0%
Percent of SHM annotated nets with zero toggles: 0/132763 = 0%

Which I assume means it's not recognizing the scope string I've entered.

The DUT I'm implementing in Genus/Innovus is "digital_core_top", and I need the generate loop in my testbench at a higher level in order to be able to easily model N chips instead of just one. I've written an entire python module utilizing cocotb with many "analog" models around the DUT in order to stimulate the DUT accurately, so unfortunately I can't easily remove this generate loop without needing to significantly change my verification library.

This is the command I'm inputting right now:

read_activity_file -format shm \
-scope {{tb_YODAWG/gen_yodawg[0]/yodawg}} \
-block digital_core_top \
-start 258917ns \
-end 264581ns \
./power_analysis/power_shm/digital_core_top/digital_core_top.trn

And this is what the hierarchy looks like in my Simvision when I open the SHM I've generated:

I can right-click on "digital_core_top" then hit copy to get the scope and it gives me "tb_YODAWG.gen_yodawg[0].yodawg.digital_core_top", but I know the hierarchy separator needs to match the one used in the actual netlist we're running Voltus on, which I believe is "/" in this case, as I'm using all cadence tools, Genus, Innovus all run with flowtool.

I've done trial and error with many versions of this, as I know unpacked syntax can get kind of weird. These are the variations I've tried for the scope:

{{tb_YODAWG/gen_yodawg[0]/yodawg}}

{{tb_YODAWG/\gen_yodawg[0] /yodawg}}

{{tb_YODAWG.gen_yodawg[0]/yodawg}}

{{tb_YODAWG.\gen_yodawg[0] /yodawg}}

{{tb_YODAWG.gen_yodawg[0].yodawg}}

{{tb_YODAWG.\gen_yodawg[0] /yodawg}}

{{tb_YODAWG/gen_yodawg[0]/yodawg/digital_core_top}} (and all variations of this as above with "digital_core_top")

Is there a way I can get the tool to spit out the correct scope string I need? If not does anyone know how this needs to be formatted?

  • Cancel

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.

© 2025 Cadence Design Systems, Inc. All Rights Reserved.

  • Terms of Use
  • Privacy
  • Cookie Policy
  • US Trademarks
  • Do Not Sell or Share My Personal Information