Working with DSPF Files: Rules for Adding Prefixes to Instance Names

The netlister determines the naming prefix for instances using the namePrefix property set in the Simulation Information section of the Edit CDF form.

The namePrefix for instances is decided as follows:

  • If the namePrefix is not found in the CDF Simulation Information section, the netlister prints X as the namePrefix.
  • If the namePrefix is the same as the first character of the device name, the netlister does not add a prefix to the instance name in the netlist.

If none of these conditions are met, the netlister adds the prefix namePrefix in the output of the instance. You can modify the prefixes that are chosen by either using the dspfNamePrefixSimInfo environment variable or the useSelfCDFInPostLayoutNetlist environment variable.

Examples
  • When the namePrefix and the first character of the device name are the same
    The mimcap device is netlisted in the DSPF as C0, when the simulator used is auCdl .

    复制代码
    C0 outm#64 net044#67 AVSS g45cmim w=5e-06 l=5e-06 m=1 $x=15.29 $y=25.58
    复制代码


    Here, the namePrefix in the Edit CDF form is set to C, which is the same as the first character of the device name. According to the pre-defined rules, no prefix is added for mimcap in the DSPF file.
    Setting dspfNamePrefixSimInfo to ams or spectre will add an X prefix and the DSPF will print the device as follows:

    复制代码
    XC0 outm#64 net044#67 AVSS g45cmim w=5e-06 l=5e-06 m=1 $x=15.29 $y=25.58 
  • When namePrefix has no specified value
    Set the dspfNamePrefixSimInfo environment variable to a simulator, such as spectre , that does not have a namePrefix specified for mimcap.


    Based on the namePrefix rules, the X prefix is added to the devices.

    复制代码
    XC0 outm#64 net044#67 AVSS g45cmim w=5e-06 l=5e-06 m=1 $x=15.29 $y=25.58
  • When the device name and namePrefix are different
    Consider that you have resistors in the netlist as shown below:

    复制代码
    R14@2 (net#222 net0178#12 gnd#1330 ) rhim_m lr=3.5e-06 wr=8e-07 + multi=(1) $x=69.656 $y=38.422

    To netlist this correctly with an X prefix, set dspfNamePrefixSimInfo to auCdl because the namePrefix for auCdl is X.

    复制代码
    XR14@2 (net#222 net0178#12 gnd#1330 ) rhim_m lr=3.5e-06 wr=8e-07 + multi=(1) $x=69.656 $y=38.422

    This is applicable in cases when the auCdl prefix is not the same as the first character of the device name.

  • When namePrefix has a value for a specific simulator and none for others
    Consider that a device has the namePrefix set to R for only the auCdl simulator, and no value for other simulators in the Edit CDF form. On netlisting, no prefix will be added to resistors if you set dspfNamePrefixSimInfo to auCdl .


    If you set dspfNamePrefixSimInfo to any other simulator name, the prefix X will be added as per the namePrefix rules.

  • When namePrefix value is not shown
    The namePrefix for mimcap is C for the auCdl , auLvs , and hspiceD simulators, and disabled for ams and spectre .


    If you set dspfNamePrefixSimInfo to auCdl , auLvs , and hspiceD , no prefix is added, but if you set the environment variable to ams , or spectre , the prefix X is added to the devices.

    复制代码
    XC0 outm#64 net044#67 AVSS g45cmim w=5e-06 l=5e-06 m=1 $x=15.29 $y=25.58

Prefixes in Instance Names in the DSPF File

dspfNamePrefixSimInfo

useSelfCDFInPostLayoutNetlist

相关推荐
cesium vue39 分钟前
nginx 流媒体配置
运维·nginx
木心术11 小时前
GitHub Actions自动化运维实战:从CI/CD到全链路DevOps
运维·自动化·github
糯米导航1 小时前
实践教程|搭建电商 AI 无限画布,实现百款商品主图自动化批量生成
运维·人工智能·自动化
朴马丁1 小时前
从制造到智造:PLM如何赋能企业研发创新
大数据·运维·人工智能·食品行业·流程行业plm·化工新材料行业·新能源材料行业
爱小黄2 小时前
使用docker搭建集群-使用 Docker 搭建 KingbaseES 集群
运维·docker·容器
zhougl9962 小时前
Gateway 和 Nginx 路由区别
运维·nginx·gateway
听风3473 小时前
Arch Linux 软件安装完全指南
linux·运维·archlinux·pacman
韩楚风4 小时前
【参天引擎】一次宕机后的数据恢复,让我把 Cantian 持久化与恢复的六大机制全搞明白了
服务器·网络·数据库·分布式·mysql·架构·cantian
沉迷学习 日益消瘦4 小时前
10-Gateway API
运维·kubernetes·gateway
网络安全零基础教程4 小时前
网络安全春招面试避坑与复盘指南
linux·网络·安全·web安全·面试·职场和发展