Stats

  • Locked Locked
  • Replies 1
  • Subscribers 124
  • Views 12837
  • 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

Generic signal names in VEC files

itos

Hi,

This question is based on https://community.cadence.com/cadence_technology_forums/f/38/t/37113 which explains that for AMS, the signal names have to be preceded by the name of my top level module (e.g. "tb_spi.") whereas not for Spectre etc.

Now I face the problem that I have about 10 stimulus files which I use a) for Spectre, AFS and AMS b) for different test benches.

I end up copying each file 7 times, replacing only the "vname" line, e.g.:

vname MOSI

vname tb_spi.MOSI

vname tb_top.MOSI

etc.

Is there an easy way to handle this? E.g. Telling AMS the vname prefix via a command line switch set through ADE L or an additional config file included via ADE L?

In the worst case, I would write a 'sed' script to do auto replacement but I would like to avoid this to avoid inconsistencies ...

Thanks!

  • At the moment all you can do is edit the files. I actually had thought exactly the same yesterday and so have filed an enhancement request, CCR 1725988, to add something like a scope=XXX parameter to the vec_include statement in spectre/AMS.

    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.